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
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
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
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.
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 CEST
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.
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 CEST
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
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
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
https://bugs.kde.org/show_bug.cgi?id=429426
Nate Graham changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
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
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. :(
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
https://bugs.kde.org/show_bug.cgi?id=429426
flan_suse changed:
What|Removed |Added
CC||windows2li...@zoho.com
--- Comment #12 from
https://bugs.kde.org/show_bug.cgi?id=429426
Carlo changed:
What|Removed |Added
CC||cirlo...@msn.com
--
You are receiving this mail
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.
https://bugs.kde.org/show_bug.cgi?id=429426
Felipe Peter changed:
What|Removed |Added
Resolution|FIXED |---
Status|VERIFIED
https://bugs.kde.org/show_bug.cgi?id=429426
Felipe Peter changed:
What|Removed |Added
Status|RESOLVED|VERIFIED
CC|
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.
https://bugs.kde.org/show_bug.cgi?id=429426
Nate Graham changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/kgl
|
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.
https://bugs.kde.org/show_bug.cgi?id=429426
David Edmundson changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
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.
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
https://bugs.kde.org/show_bug.cgi?id=429426
outloudvi changed:
What|Removed |Added
URL||https://bugzilla.redhat.com
|
https://bugs.kde.org/show_bug.cgi?id=429426
outloudvi changed:
What|Removed |Added
CC||i...@outv.im
Summary|Login after logout
27 matches
Mail list logo
