[frameworks-kglobalaccel] [Bug 429426] kglobalaccel5 repeatedly crashes on boot in QGuiApplicationPrivate::createPlatformIntegration(), which can delay login
https://bugs.kde.org/show_bug.cgi?id=429426 --- Comment #43 from mintjulep --- Ok ! followed your instructions (thank you very much by the way, I relay need to learn about shell scripts) Tryed to logout login just after reboot, worked fine. Tryed to run some app (firefox) and logout login, worked fine. Tryed to run several app, wait for a couple minute with normal usage, logout, login and... It worked too ! Seems like a resolved bug to me !! Keep you posted if I have any more issue. Thank you very much to everybody who helped on this. This is not a very important usecase (less than ever as with an ssd disk, complete reboot is incredibly fast) but it has been bugging me for month to have this little malfunction that I couldn't solve. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 429426] kglobalaccel5 repeatedly crashes on boot in QGuiApplicationPrivate::createPlatformIntegration(), which can delay login
https://bugs.kde.org/show_bug.cgi?id=429426
--- Comment #41 from mintjulep ---
(In reply to flan_suse from comment #40)
> The template you are presented with defaults to everything being "commented
> out" and thus ignored.
>
> The file in its entirety should appear as such:
>
> ### Editing
> /home/mint/.config/systemd/user/plasma-kglobalaccel‧service‧d/override‧conf
> ### Anything between here and the comment below will become the new contents
> of the file
>
> [Unit]
> Description=KDE Global Shortcuts Server
> PartOf=graphical-session‧target
>
> [Service]
> ExecStart=/usr/bin/kglobalaccel5
> BusName=org‧kde‧kglobalaccel
> Slice=background‧slice
> TimeoutSec=5sec
> Restart=on-failure
> SuccessExitStatus=0 1
>
> ### Lines below this comment will be discarded
>
> ### /usr/lib/systemd/user/plasma-kglobalaccel‧service
> # [Unit]
> # Description=KDE Global Shortcuts Server
> # PartOf=graphical-session‧target
> #
> # [Service]
> # ExecStart=/usr/bin/kglobalaccel5
> # BusName=org‧kde‧kglobalaccel
> # Slice=background‧slice
> # TimeoutSec=5sec
> # Restart=on-failure
Tried that, kglobalaccell never started and global shortcut where down after
reboot :/
Maybe I did something worng ?
As for the 2nd solution, I don't know how to create an executable file like you
did (and for the record, I don't understand what this solution is about. The
first one I get it : we feed a parameter meaning that we don't care either
kglobalaccel started or not)
if it's any help, here's the log from journal -f at reloging :
Apr 08 16:00:31 Indiana systemd[1001]: Failed to start KDE Plasma Workspace.
Apr 08 16:00:31 Indiana systemd[1001]: plasma-plasmashell‧service: Failed with
result 'timeout'.
Apr 08 16:00:31 Indiana systemd[1001]: plasma-plasmashell‧service: start
operation timed out. Terminating.
Apr 08 16:00:17 Indiana kded5[4063]: 3
Apr 08 16:00:17 Indiana kded5[4063]: 4
Apr 08 16:00:17 Indiana kded5[4063]:
Apr 08 16:00:17 Indiana kded5[4063]: kcm_touchpad: Using X11 backend
Apr 08 16:00:17 Indiana NetworkManager[519]: [1617890417.1789]
agent-manager:
agent[f3c3c8c03ee7bb31,:1.223/org‧kde‧plasma‧networkmanagement/1000]: agent
registered
Apr 08 16:00:17 Indiana kded5[4063]: org‧kde‧bolt‧kded: Couldn't connect to
Bolt DBus daemon
Apr 08 16:00:17 Indiana kded5[4063]: org‧kde‧libkbolt: Failed to connect to
Bolt manager DBus interface:
Apr 08 15:59:51 Indiana systemd[1001]: Starting KDE Plasma Workspace...
Apr 08 15:59:51 Indiana systemd[1001]: Started KDE Session Management Server.
Apr 08 15:59:27 Indiana systemd-timesyncd[506]: Timed out waiting for reply
from 217.91.44.17:123 (3.arch‧pool‧ntp.org).
Apr 08 15:59:27 Indiana kactivitymanagerd[4093]: Couldn't start kglobalaccel
from org‧kde‧kglobalaccel‧service:
QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply.
Possible causes include>
Apr 08 15:59:27 Indiana kwin_x11[4065]: Couldn't start kglobalaccel from
org‧kde‧kglobalaccel‧service: QDBusError("org.freedesktop.DBus.Error.NoReply",
"Did not receive a reply. Possible causes include: the rem>
Apr 08 15:59:27 Indiana kded5[4063]: 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>
Apr 08 15:59:26 Indiana ksmserver[4064]: Couldn't start kglobalaccel from
org‧kde‧kglobalaccel‧service: QDBusError("org.freedesktop.DBus.Error.NoReply",
"Did not receive a reply. Possible causes include: the re>
Apr 08 15:59:19 Indiana dhcpcd[527]: wlp5s0: no IPv6 Routers available
Apr 08 15:59:18 Indiana kernel: audit: type=1110 audit(1617890358.836:386):
pid=4154 uid=0 auid=1000 ses=12 msg='op=PAM:setcred
grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock
acct="mint">
Apr 08 15:59:18 Indiana kernel: audit: type=1105 audit(1617890358.836:385):
pid=4154 uid=0 auid=1000 ses=12 msg='op=PAM:session_open
grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam>
Apr 08 15:59:18 Indiana login[4154]: LOGIN ON tty2 BY mint
Apr 08 15:59:18 Indiana audit[4154]: CRED_REFR pid=4154 uid=0 auid=1000 ses=12
msg='op=PAM:setcred
grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock
acct="mint" exe="/usr/bin/login" hostnam>
Apr 08 15:59:18 Indiana audit[4154]: USER_START pid=4154 uid=0 auid=1000 ses=12
msg='op=PAM:session_open
grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env
acct="mint">
Apr 08 15:59:18 Indiana login[4154]: pam_env(login:session): deprecated reading
of user environment enabled
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 429426] kglobalaccel5 repeatedly crashes on boot in QGuiApplicationPrivate::createPlatformIntegration(), which can delay login
https://bugs.kde.org/show_bug.cgi?id=429426 --- Comment #39 from mintjulep --- (In reply to flan_suse from comment #37) > (In reply to mintjulep from comment #33) > > Ok, as for me, the first one didn't work : login logout make the same issue. > > It finaly start, after a very long time. > > > > The second option is kind of out of reach for me, as I don't know how to > > call > > systemctl --user reset-failed during boot > > Did you try out the method I used for Solution #2? Since you're running Arch > and I'm on Manjaro, we should share similar base systems. :) > > As for Solution #1, which file did you edit? I'm not a very experienced user so here's what I did : systemctl edit --user plasma-kglobalaccel‧service it opened this in vim : ### Editing /home/mint/.config/systemd/user/plasma-kglobalaccel‧service‧d/override‧conf ### Anything between here and the comment below will become the new contents of the file ### Lines below this comment will be discarded ### /usr/lib/systemd/user/plasma-kglobalaccel‧service # [Unit] # Description=KDE Global Shortcuts Server # PartOf=graphical-session‧target # # [Service] # ExecStart=/usr/bin/kglobalaccel5 # BusName=org‧kde‧kglobalaccel # Slice=background‧slice # TimeoutSec=5sec # Restart=on-failure where I added "SuccesExitStatus=0 1 " this way : ### Editing /home/mint/.config/systemd/user/plasma-kglobalaccel‧service‧d/override‧conf ### Anything between here and the comment below will become the new contents of the file SuccesExitStatus=0 1 ### Lines below this comment will be discarded ### /usr/lib/systemd/user/plasma-kglobalaccel‧service # [Unit] # Description=KDE Global Shortcuts Server # PartOf=graphical-session‧target # # [Service] # ExecStart=/usr/bin/kglobalaccel5 # BusName=org‧kde‧kglobalaccel # Slice=background‧slice # TimeoutSec=5sec # Restart=on-failure after checking, /home/mint/.config/systemd/user/plasma-kglobalaccel‧service‧d/override‧conf content is just : SuccesExitStatus=0 1 When I log out log in, it bugged as ever (maybe took a little less time to finally start) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 429426] kglobalaccel5 repeatedly crashes on boot in QGuiApplicationPrivate::createPlatformIntegration(), which can delay login
https://bugs.kde.org/show_bug.cgi?id=429426 --- Comment #36 from mintjulep --- Sweet ! When do you think it would be updated ? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 429426] kglobalaccel5 repeatedly crashes on boot in QGuiApplicationPrivate::createPlatformIntegration(), which can delay login
https://bugs.kde.org/show_bug.cgi?id=429426 --- Comment #33 from mintjulep --- Ok, as for me, the first one didn't work : login logout make the same issue. It finaly start, after a very long time. The second option is kind of out of reach for me, as I don't know how to call systemctl --user reset-failed during boot -- 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 #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 #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 --- 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 --- Comment #7 from mintjulep --- How would I do that ? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Login after logout bug hard
https://bugs.kde.org/show_bug.cgi?id=429426 --- Comment #1 from mintjulep --- JourLancel show errors related to kglobalaccel. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 429426] New: Login after logout bug hard
https://bugs.kde.org/show_bug.cgi?id=429426 Bug ID: 429426 Summary: Login after logout bug hard Product: kde Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: guillaume.ga...@hotmail.fr Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. start computer on Arch linux and login with KDe plasma 5 2. logout 3. try to log back in OBSERVED RESULT stuck on spash screen for a while. After 1 min or so, the cursor appears and can be moved, but I'm still stuck on splash screen. After 5 min, KDE finally start EXPECTED RESULT Instant KDE start SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch linux (linux kernel 5.9) Kde plasma 5 (available in About System) KDE Plasma Version: 5.20 KDE Frameworks Version: Qt Version: 5 ADDITIONAL INFORMATION I don't have the issue with gnome, so it's KDE related. interesting :when I do pkill -u *myusername* I'm logged out (duh) but log back in is normal. So maybe it's a process that makes it crash ? -- You are receiving this mail because: You are watching all bug changes.
