https://bugs.kde.org/show_bug.cgi?id=455874
Bug Janitor Service changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|BACKTRACE
https://bugs.kde.org/show_bug.cgi?id=455874
--- Comment #12 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=455874
Nate Graham changed:
What|Removed |Added
Resolution|--- |BACKTRACE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=455874
--- Comment #10 from Jonathan Riddell ---
I do confirm that gdb doesn't like talking to kscreenlocker_greet with the
unhelpful message of "Cannot find user-level thread for LWP 186659: generic
error". But gdb and glib are stuff handled by Ubuntu, we do
https://bugs.kde.org/show_bug.cgi?id=455874
Jonathan Riddell changed:
What|Removed |Added
CC||j...@jriddell.org
--- Comment #9 from Jonath
https://bugs.kde.org/show_bug.cgi?id=455874
--- Comment #8 from Andrej Falout ---
(In reply to Nate Graham from comment #7)
> > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> > Cannot find user-level thread for LWP 317551: generic error
>
> Well that's weird. Appare
https://bugs.kde.org/show_bug.cgi?id=455874
Nate Graham changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=455874
--- Comment #7 from Nate Graham ---
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> Cannot find user-level thread for LWP 317551: generic error
Well that's weird. Apparently it's an issue in glibc???
https://bugs.archlinu
https://bugs.kde.org/show_bug.cgi?id=455874
--- Comment #6 from Andrej Falout ---
(In reply to ratijas from comment #3)
> > No coredumps found.
>
> Is coredump service enabled at all? It might be turned off by default.
>
> https://wiki.archlinux.org/title/Core_dump
Thanks for the link. That pa
https://bugs.kde.org/show_bug.cgi?id=455874
--- Comment #5 from Andrej Falout ---
(In reply to Nate Graham from comment #4)
> Looks like you'll need to get the backtrace manually. Here's how you can do
> it.
>
> 1. run `gdb --args /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet
> --testing
https://bugs.kde.org/show_bug.cgi?id=455874
--- Comment #4 from Nate Graham ---
Looks like you'll need to get the backtrace manually. Here's how you can do it.
1. run `gdb --args /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet
--testing` in a terminal window
2. enter "run" at the prompt
3.
https://bugs.kde.org/show_bug.cgi?id=455874
ratijas changed:
What|Removed |Added
CC||m...@ratijas.tk
--- Comment #3 from ratijas ---
> No
https://bugs.kde.org/show_bug.cgi?id=455874
--- Comment #2 from Andrej Falout ---
(In reply to Nate Graham from comment #1)
> Can you please paste the output of `coredumpctl list kscreenlocker_greet`?
coredumpctl list kscreenlocker_greet
No coredumps found.
--
You are receiving this mail becau
https://bugs.kde.org/show_bug.cgi?id=455874
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
Status|REPORTED
14 matches
Mail list logo