https://bugs.kde.org/show_bug.cgi?id=512244
--- Comment #2 from maxlefou <[email protected]> --- (In reply to David Edmundson from comment #1) > Please include output of journalctl --user -r after performing this and > scrollback to where logout started After trying, this is what I got: ``` 23:04:43.050 UTC [email protected] QCoreApplication::postEvent: Unexpected null receiver 23:04:43.469 UTC [email protected] KWin failed to complete logout 23:04:44.164 UTC [email protected] QThreadStorage: entry 8 destroyed before end of thread 0x385c0065ff60 23:04:44.165 UTC [email protected] QThreadStorage: entry 7 destroyed before end of thread 0x385c0065ff60 23:04:44.165 UTC [email protected] QThreadStorage: entry 2 destroyed before end of thread 0x385c0065ff60 23:04:44.165 UTC [email protected] QThreadStorage: entry 1 destroyed before end of thread 0x385c0065ff60 23:04:44.190 UTC [email protected] app-com.vivaldi.Vivaldi-1462.scope: Consumed 18min 9.319s CPU time, 1.4G memory peak, 18.6M memory swap peak. 23:04:44.194 UTC [email protected] app-vivaldi\[email protected]: Consumed 2h 22min 52.164s CPU time, 2.4G memory peak, 61.7M memory swap peak. 23:04:45.677 UTC [email protected] [email protected]: Consumed 10h 41min 37.506s CPU time, 17.4G memory peak, 1.1G memory swap peak. ``` I see that it says Kwin fails to complete logout but it doesn't say much why. I don't get why it happens with the countdown and not when I click to shutdown now. -- You are receiving this mail because: You are watching all bug changes.
