-
Notifications
You must be signed in to change notification settings - Fork 10
Cannot switch Desktops #48
Comments
Hi, sorry for the delay, thank you for the report. What happens when you attempt to log in? Does Entrance crash or anything? Have you tried other desktops or just Plasma? I am curious if it is specific to Plasma/Qt or all other desktops in general. Can you also check the entrance.log file, or add a copy to this issue for review? Thank you! |
Thanks for tuning in. Entrance work for Enlightenment; on Plasma is loops back to Entrance and asks me to log in again, and it does indefinitely (I tried 5+ times). I don't have access to my logs at this particular moment, but I will do so soon. |
Interesting, I hope the log file can give some clues as to what is going wrong. I believe, plasma is still capable of running under X. If it is trying to start a Wayland session, that might be part of why its looping back. I have not tested Entrance with other desktops just E, EFL applications like Emotion Media Center, and basic XSession. I need to look into using other desktops with entrance, time permitting. |
Sorry it has taken me so long to get back to this. I'm trying to find the logs from my attempts to log into plasma via entrance. however, I am having trouble. I thought they would be in /tmp/ the logs I find there are blank, so I can't see anything. I've tried searching around the internet for more information, but have not been success in finding anything. |
No worries, the default location for entrance logs would be /var/log/entrance.log, unless it was changed in /etc/entrance/entrance.conf. Typically, the /tmp dir is wiped on boot/reboot, so it would be odd if anything was logging there that was meant to persist a reboot. But I am not familiar with Manjaro and it could be logging things else where. I believe there are other places Plasma/Qt will log within your home directory. That would be an additional place to check if the entrance.log file does not provide any useful information. Hopefully, that helps you out some. Thank you for looking for the logs and following up! |
Here's a snippet of the entrance.log file after trying to start plasma. I can give you the whole file if you would prefer, just need to know where to upload (having trouble remembering what most people use). Sorry I'm not very good at this. Its my first issue I have ever reported. `INF<797>:entrance ../src/daemon/entrance_pam.c:33 _entrance_pam_conv() echo off sh: /usr/bin/sessreg: No such file or directory INF<5052>:entrance ../src/daemon/entrance_session.c:200 _entrance_session_run() Executing: /bin/zsh --login -c /etc/entrance/Xsession /usr/bin/startplasma-x11 > /home/mouse/.entrance_session.log 2>&1 INF<797>:entrance_client ../src/daemon/entrance.c:109 _entrance_client_data() ../src/bin/entrance_client.c:124 ecore x shutdown INF<797>:entrance ../src/daemon/entrance_server.c:66 _entrance_server_del() server client disconnected INF<797>:entrance_client ../src/daemon/entrance.c:109 _entrance_client_data() ../src/bin/entrance_client.c:128 eina shutdown INF<797>:entrance_client ../src/daemon/entrance.c:109 _entrance_client_data() ../src/bin/entrance_client.c:130 exit ` |
Your doing great for your first issue. You should be able to drag and drop the log file here on Github. But you managed to provide the most relevant portion of the log file, so the entire file is not really necessary at this time.
This might be the issue, but it should affect Enlightenment as well as Plasma. E maybe more forgiving of such than Plasma. See about installing sessreg and see if that makes any difference. |
So looking at enlightenment, after trying to start plasma, it does the same thing. If I try plasma first, then it works flawlessly. I have installed sessreg from the pacman repos, and it still does the same thing. In case it is of any interest, I have the log after my most recent attempt (post installing sessreg). |
Maybe Enlightenment changes something, that is gone after reboot (?) Can you log into Enlightenment twice in a row? |
These issues maybe a result of the lack of consolekit, and also lack of support for logind/elogind. Starting Plasma first, might initialize the seat, and that may remain for E. But if you start E, that is not the case on log out, and has some issues for Plasma. Just a quick assumption, based on other issues, and my own experience when I stop using consolekit. Replacing consolekit with logind/elogind is on the TODO list, high priority, as I am affected by it as others. Consolekit was removed from Gentoo, so, I need to get in to it ASAP for my own login purposes. This affects several open issues. Sorry for the delay, I have been really busy. I will try to get on this after the 15th. Thanks! |
Description
Description of issue
Steps to reproduce
How entrance is started
systemd service
System information
Manjaro
The text was updated successfully, but these errors were encountered: