| Summary: | Login after logout hangs for 3 minutes | ||
|---|---|---|---|
| Product: | [Unmaintained] ksmserver | Reporter: | medin <med.medin.2014> |
| Component: | general | Assignee: | David Edmundson <kde> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | bharadwaj.raju777, eric.donkersloot, kde, nate, plasma-bugs, popov895, postix, storagebin95, windows2linux |
| Priority: | NOR | ||
| Version First Reported In: | 5.21.2 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=432316 | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
medin
2021-03-13 20:46:37 UTC
Are you using systemd startup? I tried it once and found problems with kwallet appearing with every boot then I disabled it forever by putting "systemdBoot=false" in ~/.config/startkderc, so I think systemd startup is disabled. Thanks. Can reproduce with the wayland session and systemd boot. Just log out and log back in. The second login takes forever. Rebooting instead of logging out fixes it. It seems like there could be some dangling processes or something. I have the same problem on kde neon: Operating System: KDE neon 5.21 KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-70-generic OS Type: 64-bit Graphics Platform: X11 The problem usually occurs after mounting and unmounting operations of encryption software (veracrypt, cryfs, cryptomator). A "solution" I have discovered is that before logging back in change to wayland. Then log out again and change back to x and login again. Everything goes smoothly but is a serious annoyance. > It seems like there could be some dangling processes or something. If it's only with Wayland then it is probably related to https://bugs.kde.org/show_bug.cgi?id=433293 (In reply to Bharadwaj Raju from comment #6) > > It seems like there could be some dangling processes or something. > > If it's only with Wayland then it is probably related to > https://bugs.kde.org/show_bug.cgi?id=433293 No, I use only X11, Wayland has many weird problems. If you do use systemd boot, does the problem go away? I know the KWallet issue will come back, but can you try again just for testing purposes? The problem occurs only with x11, never wayland. -------------------------------- Without systemd startup : -------------------------------- => Wayland Wayland always starts desktop without failing or being stuck even if it generates these crashes (coredumpctl) /usr/bin/akonadi_maildir_resource /usr/bin/kwalletd5 /usr/lib/baloorunner /usr/lib/kactivitymanagerd /usr/bin/korgac /usr/bin/akonadi_migration_agent /usr/bin/akonadi_newmailnotifier_agent /usr/bin/kalarm /usr/bin/akonadi_followupreminder_agent /usr/bin/akonadi_maildispatcher_agent /usr/bin/yakuake /usr/bin/akonadi_notes_agent /usr/bin/akonadi_mailfilter_agent /usr/bin/akonadi_sendlater_agent /usr/bin/akonadi_unifiedmailbox_agent /usr/bin/msm_kde_notifier /usr/bin/akregator => X11 With X11 it fails a lot with little success to logout then login, it generates this crash (coredumpctl) /usr/bin/kglobalaccel5 When it fails (which is often) it becomes either stuck infinitely at boot splash or takes many minutes to show desktop. -------------------------------- With systemd startup : -------------------------------- => Wayland Wayland always starts desktop without failing or being stuck even if it generates these crashes (coredumpctl) /usr/lib/kf5/klauncher /usr/bin/kded5 /usr/bin/kwalletd5 /usr/bin/yakuake /usr/bin/kded5 /usr/bin/akregator /usr/lib/xdg-desktop-portal-kde /usr/bin/ksplashqml => X11 With X11 it fails (not always) and generates this crash (coredumpctl) /usr/bin/kglobalaccel5 When it fails (which is often) it becomes either stuck infinitely at boot splash or takes many minutes to show desktop. And running thissystemd-analyze shows : systemd-analyze --user blame 50.983s plasma-ksmserver.service 39.376s plasma-ksplash-ready.service 31.259s plasma-plasmashell.service 30.843s plasma-restoresession.service This is a truly annoying bug, any updates on this? I'm having this issue on a fresh KDE Neon install: Operating System: KDE neon 5.21 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.8.0-48-generic OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Whoever's reading, this might be related to another bug. Can you try out the two temporary fixes and see if they work? Namely the steps on comment #42 and comment #40: https://bugs.kde.org/show_bug.cgi?id=429426#c42 https://bugs.kde.org/show_bug.cgi?id=429426#c40 @David Edmundson already submitted two patches to be merged: https://invent.kde.org/frameworks/kglobalaccel/-/merge_requests/17 https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/773 I'm not saying this *is* the bug for everyone, but it might affect a decent number of people and there might be some overlap in our login crashes / 3-min freezes. FYI: The above links (to the steps) might be different for each distro. Those comments are for Arch-based / Manjaro systems. Sounds similar, lets assume they fix it until we have any evidence otherwise *** This bug has been marked as a duplicate of bug 429426 *** |