[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 --- Comment #26 from flan_suse --- If it means anything, this is what I get from "coredumpctl debug kglobalaccel5": Stack trace of thread 8649: #0 0x7fe650683ef5 raise (libc.so.6 + 0x3cef5) #1 0x7fe65066d862 abort (libc.so.6 + 0x26862) #2 0x7fe650a819ac _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0x909ac) #3 0x7fe651079646 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5 + 0x131646) #4 0x7fe651079ae1 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x131ae1) #5 0x7fe650cad686 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x2bc686) #6 0x7fe65107cb20 _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x134b20) #7 0x7fe65107da88 _ZN15QGuiApplicationC1ERiPPci (libQt5Gui.so.5 + 0x135a88) #8 0x55b77a53408f n/a (kglobalaccel5 + 0x208f) #9 0x7fe65066eb25 __libc_start_main (libc.so.6 + 0x27b25) #10 0x55b77a5343fe n/a (kglobalaccel5 + 0x23fe) -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 --- Comment #25 from flan_suse --- coredumpctl -r yields the same output as @mintjulop above, even after applying the kwriteconfig / systemdboot workaround. After multiple reboots (to be certain), the re-login issue remains, even after confirming that "plasma-plasmashell.service" is enabled and active. I tried to follow the steps to provide a backtrace, but I get this warning: "Coredump entry has no core attached (neither internally in the journal nor externally on disk)." My system info once again is: Operating System: Manjaro Linux KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.10.23-1-MANJARO OS Type: 64-bit Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 11.6 GiB of RAM Graphics Processor: GeForce GTX 1650/PCIe/SSE2 Nvidia Driver Version: 460.56 (proprietary) I think if this resolves for @mintjulep, it will resolve for others, including myself. I don't want to distract nor interrupt anything, but if providing another coredump or backtrace would be useful, let me know. So far, what @mintjulep is pasting looks nearly identical to my own terminal output. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 --- Comment #24 from mintjulep --- [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db‧so.1". Core was generated by `/usr/bin/kglobalaccel5'. Program terminated with signal SIGABRT, Aborted. #0 0x7f1052a57ef5 in raise () from /usr/lib/libc‧so.6 (gdb) bt #0 0x7f1052a57ef5 in raise () from /usr/lib/libc‧so.6 #1 0x7f1052a41862 in abort () from /usr/lib/libc‧so.6 #2 0x7f1052e579ac in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/libQt5Core‧so.5 #3 0x7f105344d646 in QGuiApplicationPrivate::createPlatformIntegration() () from /usr/lib/libQt5Gui‧so.5 #4 0x7f105344dae1 in QGuiApplicationPrivate::createEventDispatcher() () from /usr/lib/libQt5Gui‧so.5 #5 0x7f1053083686 in QCoreApplicationPrivate::init() () from /usr/lib/libQt5Core‧so.5 #6 0x7f1053450b20 in QGuiApplicationPrivate::init() () from /usr/lib/libQt5Gui‧so.5 #7 0x7f1053451a88 in QGuiApplication::QGuiApplication(int&, char**, int) () from /usr/lib/libQt5Gui‧so.5 #8 0x55d528b2308f in ?? () #9 0x7f1052a42b25 in __libc_start_main () from /usr/lib/libc‧so.6 #10 0x55d528b234de in ?? () (gdb) -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 --- Comment #23 from Nate Graham --- Darn. Can you attach a backtrace from one of those new crashlogs? `coredumpctl debug kglobalaccel5` and then type `bt` -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 --- Comment #22 from mintjulep --- Ok, made coredumpctl -r and got this : Mon 2021-04-05 20:36:22 CEST2753 1000 985 SIGABRT present /usr/bin/kglobalaccel5 403.1K Mon 2021-04-05 20:36:21 CEST2739 1000 985 SIGABRT present /usr/bin/kglobalaccel5 403.4K Mon 2021-04-05 20:36:21 CEST2701 1000 985 SIGABRT present /usr/bin/kglobalaccel5 403.2K Mon 2021-04-05 20:36:20 CEST2681 1000 985 SIGABRT present /usr/bin/kglobalaccel5 417.0K Mon 2021-04-05 20:36:20 CEST2665 1000 985 SIGABRT present /usr/bin/kglobalaccel5 410.3K Mon 2021-04-05 20:32:15 CEST2172 1000 985 SIGABRT present /usr/bin/kglobalaccel5 402.9K Mon 2021-04-05 20:32:15 CEST2158 1000 985 SIGABRT present /usr/bin/kglobalaccel5 403.0K Mon 2021-04-05 20:32:14 CEST2120 1000 985 SIGABRT present /usr/bin/kglobalaccel5 402.9K Mon 2021-04-05 20:32:13 CEST2099 1000 985 SIGABRT present /usr/bin/kglobalaccel5 403.2K Mon 2021-04-05 20:29:17 CEST2427 1000 985 SIGABRT present /usr/bin/kglobalaccel5 403.6K Mon 2021-04-05 20:29:17 CEST2413 1000 985 SIGABRT present /usr/bin/kglobalaccel5 403.5K Mon 2021-04-05 20:29:16 CEST2375 1000 985 SIGABRT present /usr/bin/kglobalaccel5 402.9K Mon 2021-04-05 20:29:15 CEST2354 1000 985 SIGABRT present /usr/bin/kglobalaccel5 403.2K so yeah, seems like the same issue -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 --- Comment #21 from mintjulep --- wich is weird cause we're not Tuesday 2020/10/22 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 --- Comment #20 from mintjulep --- Here is the result of cordumpctl : Thu 2020-10-22 19:18:43 CEST1026 1000 985 SIGABRT missing /usr/bin/plasmashell n/a Thu 2020-10-22 19:18:43 CEST1027 1000 985 SIGABRT missing /usr/lib/drkonqi n/a Thu 2020-10-22 19:18:43 CEST 999 1000 985 SIGABRT missing /usr/bin/kglobalaccel5 n/a Thu 2020-10-22 19:18:46 CEST 713 1000 985 SIGSEGV missing /usr/bin/plasmashell n/a Thu 2020-10-22 19:26:00 CEST2659 1000 985 SIGABRT missing /usr/bin/plasmashell n/a Thu 2020-10-22 19:26:00 CEST2660 1000 985 SIGABRT missing /usr/lib/drkonqi n/a Thu 2020-10-22 19:26:00 CEST2629 1000 985 SIGABRT missing /usr/bin/kglobalaccel5 n/a Thu 2020-10-22 19:26:03 CEST1206 1000 985 SIGSEGV missing /usr/bin/plasmashell n/a Thu 2020-10-22 19:30:03 CEST4149 1000 985 SIGABRT missing /usr/bin/kglobalaccel5 n/a Thu 2020-10-22 19:30:03 CEST4184 1000 985 SIGABRT missing /usr/lib/drkonqi n/a Thu 2020-10-22 19:30:03 CEST4183 1000 985 SIGABRT missing /usr/bin/plasmashell n/a Thu 2020-10-22 19:30:06 CEST2837 1000 985 SIGSEGV missing /usr/bin/plasmashell n/a Thu 2020-10-22 19:43:44 CEST 662 1000 985 SIGSEGV missing /usr/bin/kded5 n/a Thu 2020-10-22 20:31:49 CEST 26836 1000 985 SIGABRT missing /usr/lib/drkonqi n/a Thu 2020-10-22 20:31:49 CEST 26835 1000 985 SIGABRT missing /usr/bin/plasmashell n/a Thu 2020-10-22 20:31:53 CEST 708 1000 985 SIGSEGV missing /usr/bin/plasmashell n/a Thu 2020-10-22 21:00:36 CEST 17077 1000 985 SIGABRT missing /usr/bin/plasmashell n/a Thu 2020-10-22 21:00:36 CEST 17078 1000 985 SIGABRT missing /usr/lib/drkonqi n/a Thu 2020-10-22 21:00:39 CEST 715 1000 985 SIGSEGV missing /usr/bin/plasmashell n/a Thu 2020-10-22 21:12:39 CEST 988 1000 985 SIGSEGV missing /usr/bin/kdeinit5 n/a Thu 2020-10-22 21:29:39 CEST 10467 1000 985 SIGABRT missing /usr/lib/drkonqi n/a Thu 2020-10-22 21:29:39 CEST 10466 1000 985 SIGABRT missing /usr/bin/plasmashell n/a Thu 2020-10-22 21:29:42 CEST 717 1000 985 SIGSEGV missing /usr/bin/plasmashell n/a Thu 2020-10-22 21:40:50 CEST 12881 1000 985 SIGABRT missing /usr/lib/drkonqi n/a -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 --- Comment #19 from Nate Graham --- Yay! ... almost lol. Can you see if it's still kglobalaccel that's crashing on boot, or is it something else now? `coredumpctl` should be able to tell you. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 --- Comment #18 from mintjulep --- EDIT : No it doesn't, talk to fast. the bug came back. Not the first time I get this tho : it's hard to know what's up because sometimes, it doesn't bug -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 --- Comment #17 from mintjulep --- (In reply to Nate Graham from comment #16) > Are you using systemd startup, or not? See also > http://blog.davidedmundson.co.uk/blog/plasma-and-the-systemd-startup/ sweet jesus lord of mercy it worked !!! what I did : kwriteconfig5 --file startkderc --group General --key systemdBoot true then check the status with : systemctl --user status plasma-plasmashell‧service and saw that the service was inactive. I enabled it : systemctl --user enable plasma-plasmashell‧service reboot and it's perfect ! Not only can I now logout and login without any problem, but also Plasma starts faster than before Thanks for the hint !! -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #16 from Nate Graham --- Are you using systemd startup, or not? See also http://blog.davidedmundson.co.uk/blog/plasma-and-the-systemd-startup/ -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 --- Comment #15 from flan_suse --- Can we safely change this bug's status to "Confirmed" and remove that it has been "Fixed" for KDE Framework 5.77, since it still exists in 5.80? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 --- Comment #14 from outloudvi --- (In reply to flan_suse from comment #13) > > systemctl --user mask plasma-kglobalaccel.service > > If I do this, then it seems to fix the login delay problem, but now I cannot > use *any* keyboard shortcuts. :( That's expected as kglobalaccel is required for global keyboard shortcuts. Also, I want to amend that this bug is still there at the follow version: * Plasma 5.21.3 * KDE Framework 5.80.0 * kglobalaccel 5.80.0 (Arch Linux 5.80.0:2, [1]) Also I noticed that kglobalaccel crashed before that failure of KDE re-login: Process 4312 (kglobalaccel5) of user 1000 dumped core. Stack trace of thread 4312: #0 0x7faaea8c4ef5 raise (libc.so.6 + 0x3cef5) #1 0x7faaea8ae862 abort (libc.so.6 + 0x26862) #2 0x7faaeacc49ac _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0x909ac) #3 0x7faaeb2ba646 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5 + 0x131646) #4 0x7faaeb2baae1 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x131ae1) #5 0x7faaeaef0686 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x2bc686) #6 0x7faaeb2bdb20 _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x134b20) #7 0x7faaeb2bea88 _ZN15QGuiApplicationC1ERiPPci (libQt5Gui.so.5 + 0x135a88) #8 0x56524a34b08f n/a (kglobalaccel5 + 0x208f) #9 0x7faaea8afb25 __libc_start_main (libc.so.6 + 0x27b25) #10 0x56524a34b4de n/a (kglobalaccel5 + 0x24de) 1. https://github.com/archlinux/svntogit-packages/blob/c1075e2b63a192d98d8ef19ab6a242edd14e6fce/trunk/PKGBUILD -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 --- Comment #13 from flan_suse --- > systemctl --user mask plasma-kglobalaccel.service If I do this, then it seems to fix the login delay problem, but now I cannot use *any* keyboard shortcuts. :( -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 flan_suse changed: What|Removed |Added CC||windows2li...@zoho.com --- Comment #12 from flan_suse --- I am suffering from the same issue as described by the bug report. If I logout and then try to log back in, the SDDM screen will freeze for about three minutes before finally logging in to a new Plasma session. Disabling Compositing made no difference. Using TripleBuffering made no difference. Removing ~/.cache/ seems to help sometimes, but other times it makes no difference. Not very consistent. Removing ~/.Xauthority made no difference. Here is my system info, and let me know what logs/debug I can provide to help diagnose and fix this bug: Operating System: Manjaro Linux KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.10.23-1-MANJARO OS Type: 64-bit Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 11.6 GiB of RAM Graphics Processor: GeForce GTX 1650/PCIe/SSE2 Nvidia Driver Version: 460.56 (proprietary) I cannot recall how long this has been a problem, but I tried to ignore it in hopes that maybe it's already been addressed and will be fixed with an update to KDE. I would say I've noticed it for months, perhaps. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 --- Comment #11 from Nate Graham --- David, does this require changes in Plasma 5.21 too? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 Felipe Peter changed: What|Removed |Added Resolution|FIXED |--- Status|VERIFIED|REPORTED -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 Felipe Peter changed: What|Removed |Added Status|RESOLVED|VERIFIED CC||mr-pei...@web.de --- Comment #10 from Felipe Peter --- I'm on Manjaro with frameworks 5.77.0 and get the same problem with kglobalaccel. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 --- Comment #9 from mintjulep --- Hum... after checking, I'm allready on kglobalaccel 5.77 :/ -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 Nate Graham changed: What|Removed |Added Latest Commit||https://commits.kde.org/kgl ||obalaccel/25e84f3f6ac54097d ||9c021705dc18b187352fa02 Version Fixed In||5.77 --- Comment #8 from Nate Graham --- You would upgrade to Frameworks 5.77 when your distro makes it available. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 --- Comment #7 from mintjulep --- How would I do that ? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 David Edmundson changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #6 from David Edmundson --- commit 25e84f3f6ac54097d9c021705dc18b187352fa02 Author: David Edmundson Date: Wed Dec 2 14:57:27 2020 + Avoid autostarting kglobalaccel when shutting down in kglobalaccel should hide the problem triggering this. That'll be in the next frameworks 5.77. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 --- Comment #5 from outloudvi --- Sorry for the repeated comment submission. (In reply to outloudvi from comment #2) > systemctl --user mask plasma-kglobalaccel.service It seems that masking the kglobalaccel service will solve the stuck problem. After the plasmashell started, I ran kglobalaccel5 manually and global key shortcuts work as usual. I think that there are two reasons for the problem, but not sure which: 1. kglobalaccel5 should not be started before plasmashell, but dbus asks it to do so, which results in the problem. 2. kglobalaccel5 is meant to be started before plasmashell, but it does not work now because of some problems. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426
--- Comment #4 from outloudvi ---
Hi, please allow me to amend on this bug report.
The problem is that an immediate login after logout will cause stuck in Plasma.
>From the logs, we see that it's the failure to start kglobalaccel that causes
the problem. After the timeout, Plasma starts and kglobalaccel also starts
successfully.
Related systemd logs:
dbus-daemon[1298]: [session uid=1000 pid=1298] Activating via systemd: service
name='org.kde.kglobalaccel' unit='plasma-kglobalaccel.service' requested by
':1.597' (uid=1000 pid=44701 comm="/usr/bin/ksmserver ")
systemd[1067]: plasma-kglobalaccel.service: Start request repeated too quickly.
systemd[1067]: plasma-kglobalaccel.service: Failed with result 'core-dump'.
ksmserver[44701]: Couldn't start kglobalaccel from
org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.NoReply",
"Did not receive a reply. Possible causes include: the remote application did
not send a reply, the message bus security policy blocked the reply, the reply
timeout expired, or the network connection was broken.")
kded5[44696]: Couldn't start kglobalaccel from org.kde.kglobalaccel.service:
QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply.
Possible causes include: the remote application did not send a reply, the
message bus security policy blocked the reply, the reply timeout expired, or
the network connection was broken.")
kaccess[44719]: Couldn't start kglobalaccel from org.kde.kglobalaccel.service:
QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply.
Possible causes include: the remote application did not send a reply, the
message bus security policy blocked the reply, the reply timeout expired, or
the network connection was broken.")
org_kde_powerdevil[44816]: Couldn't start kglobalaccel from
org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.NoReply",
"Did not receive a reply. Possible causes include: the remote application did
not send a reply, the message bus security policy blocked the reply, the reply
timeout expired, or the network connection was broken.")
dbus-daemon[1298]: [session uid=1000 pid=1298] Failed to activate service
'org.kde.kglobalaccel': timed out (service_start_timeout=12ms)
kactivitymanagerd[44827]: Couldn't start kglobalaccel from
org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.TimedOut",
"Failed to activate service 'org.kde.kglobalaccel': timed out
(service_start_timeout=12ms)")
dbus-daemon[1298]: [session uid=1000 pid=1298] Activating via systemd: service
name='org.kde.kglobalaccel' unit='plasma-kglobalaccel.service' requested by
':1.610' (uid=1000 pid=44816 comm="/usr/lib/org_kde_powerdevil ")
dbus-daemon[1298]: [session uid=1000 pid=1298] Successfully activated service
'org.kde.kglobalaccel'
kglobalaccel5[44876]: The X11 connection broke (error 1). Did the X11 server
die?
systemd[1067]: plasma-kglobalaccel.service: Main process exited, code=exited,
status=1/FAILURE
systemd[1067]: plasma-kglobalaccel.service: Failed with result 'exit-code'.
We have seen similar reports in multi distros:
- https://bugzilla.redhat.com/show_bug.cgi?id=1787230
- https://forums.gentoo.org/viewtopic-t-1046222-start-0.html
- https://forum.manjaro.org/t/cant-login-after-logout/40887
--
You are receiving this mail because:
You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 outloudvi changed: What|Removed |Added URL||https://bugzilla.redhat.com ||/show_bug.cgi?id=1787230 --- Comment #3 from outloudvi --- Hi, -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 outloudvi changed: What|Removed |Added CC||i...@outv.im Summary|Login after logout bug hard |Immediate login after ||logout will stuck till ||timeout because of ||kglobalaccel5 --- Comment #2 from outloudvi --- Hi, systemctl --user mask plasma-kglobalaccel.service -- You are receiving this mail because: You are watching all bug changes.
