Bug 403113 - After logging out of plasma session, plasma is restarted.
Summary: After logging out of plasma session, plasma is restarted.
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Lock/logout widget (show other bugs)
Version: 5.14.5
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-11 18:29 UTC by Lukas Sabota
Modified: 2019-01-11 22:35 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
SDDM's ~/.local/share/sddm/xorg-session.log when this issue occurs (21.68 KB, text/x-log)
2019-01-11 18:29 UTC, Lukas Sabota
Details
journalctl -b output (304.62 KB, text/plain)
2019-01-11 18:39 UTC, Lukas Sabota
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lukas Sabota 2019-01-11 18:29:08 UTC
Created attachment 117407 [details]
SDDM's ~/.local/share/sddm/xorg-session.log when this issue occurs

I am running into an annoying issue where I cannot log out of plasma properly.  When I attempt to log out of plasma (using Start->Leave->Logout), I am logged back into plasma.  The second time I attempt to logout, the logout succeeds.

I initially thought this was a issue related to SDDM.  However, I am able to reproduce this issue with LightDM as well.

STEPS TO REPRODUCE
1. Start a plasma session (X11) from a Display Manager
2. Attempt to log out of the session (I use "Start->Leave->Logout")

OBSERVED RESULT
After attempting to log out, the applications for the session are killed.. However, another session is immediately started under the same X11 server.  At this point, if you logout of plasma, the session will be properly terminated


EXPECTED RESULT
I expected the session to logout


NOTE:
I am unable to reproduce this issue with a brand new user and a brand new plasma configuration.  However, plasma should never open an additional session after a user logs out, regardless of the user configuration.  I will be happy to provide any additional information to assist in debugging this issue.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  5.14.5
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.53.0
Qt Version: 5.12.0

ADDITIONAL INFORMATION
I have been experiencing this issue for a few months now - this is not a new issue with the latest plasma/kde packages
Comment 1 Lukas Sabota 2019-01-11 18:39:52 UTC
Created attachment 117408 [details]
journalctl -b output

I am attaching the journalctl output from a boot where I did the following:

1) Turned the computer on and booted into linux w/ sddm enabled
2) Logged into plasma
3) attempted to log out of plasma, which failed
4) attempted to log out of plasma again, which succeeded

at that point I switched to VT2 and ran "journalctl -b > thisBootDump2.txt" to get the log information

Please let me know what other information I can provide to assist in identifying the issue - I do realize how difficult it is to look into an issue without firm steps to reproduce
Comment 2 Lukas Sabota 2019-01-11 19:00:24 UTC
UPDATE:
This is a case of user error, but a very difficult case to track down.

I had a "~/.xsession" file for the user that was experiencing this issue that had just "startkde" in it.  So the login manager (both SDDM and LightDM) were correctly parsing this file which caused two sessions to be launched.

Not sure how kde or sddm/lightdm could have possibly prevented this - since sddm/lightdm were doing the "right thing" here as far as I know.

I hope somebody having a similar issue will find this PEBKAC bug and think to check their .xsession :D

I'm going to go ahead and close this - sorry for the noise and hopefully this helps someone in the future.  If anything, SDDM/LightDm could potentially be more verbose in its logs ("parsing entries from ~/.xsession" or something would have immediately clued me or any user to check that file).
Comment 3 Lukas Sabota 2019-01-11 19:00:56 UTC
(Actually; it looks like I can't change the bug status to CLOSED - so if a mod could step in here at some point that would be great)
Comment 4 David Edmundson 2019-01-11 22:35:49 UTC
Thanks for tracking it down.