Bug 424297

Summary: Cannot log out of KDE
Product: [Unmaintained] ksmserver Reporter: Chris <chris>
Component: generalAssignee: David Edmundson <kde>
Status: RESOLVED DUPLICATE    
Severity: major CC: chris, nate, plasma-bugs-null
Priority: NOR    
Version First Reported In: 5.18.5   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Chris 2020-07-16 18:34:02 UTC 
SUMMARY

Cannot log out of KDE


STEPS TO REPRODUCE
1. Click the start menu
2. Click Leave
3. Click Logout

OBSERVED RESULT The screen goes black and all you are left with is a cursor on the screen. The log out process does not complete and take you back to the log in screen


EXPECTED RESULT -- To be logged out


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 5.18.5
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2020-07-17 02:53:31 UTC 
Cannot reproduce. Is there any chance a system upgrade was interrupted in the middle? Sometimes that can cause these symptoms.
Comment 2 Chris 2020-07-17 21:11:38 UTC 
(In reply to Nate Graham from comment #1)
> Cannot reproduce. Is there any chance a system upgrade was interrupted in
> the middle? Sometimes that can cause these symptoms.

No.. I upgraded just fine from 31 to 32.
Comment 3 Chris 2020-07-17 21:13:54 UTC 
(In reply to Nate Graham from comment #1)
> Cannot reproduce. Is there any chance a system upgrade was interrupted in
> the middle? Sometimes that can cause these symptoms.

No.. I upgraded just fine from 31 to 32. (In reply to Nate Graham from comment #1)
> Cannot reproduce. Is there any chance a system upgrade was interrupted in
> the middle? Sometimes that can cause these symptoms.

I sat here and watched the computer upgrade from Fedora 31 to 32 and I never saw any error messages or anything.
Comment 4 Nate Graham 2020-07-18 00:55:12 UTC 
Weird.
Comment 5 Nate Graham 2020-10-12 03:43:51 UTC 

*** This bug has been marked as a duplicate of bug 374538 ***