[kscreenlocker] [Bug 482841] Screenlocker fails (suspend, disconnect from dock, resume)

2024-04-13 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=482841

Justin Zobel  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 482841] Screenlocker fails (suspend, disconnect from dock, resume)

2024-04-12 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=482841

--- Comment #4 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 bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 482841] Screenlocker fails (suspend, disconnect from dock, resume)

2024-03-29 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=482841

--- Comment #3 from Justin Zobel  ---
Created attachment 167913
  --> https://bugs.kde.org/attachment.cgi?id=167913=edit
Journalctl Log

Nothing in coredumpctl at all. I've just replicated the issue now and no
crashes at all from the current day.

I figured I'd check journalctl and grabbed 10 minutes of where it happened and
I saw in there: Mar 29 19:46:27 lenovo-laptop kernel: kscreenlocker_g[3795669]:
segfault at 8 ip 7f552a6b6598 sp 7ffef2fc9d80 error 4 in
libPlasmaQuick.so.6.0.3[7f552a68b000+4c000] likely on CPU 4 (core 2, socket 0)

The whole log is attached, as Bugzilla has a comment limit size.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 482841] Screenlocker fails (suspend, disconnect from dock, resume)

2024-03-24 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=482841

--- Comment #2 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 bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 482841] Screenlocker fails (suspend, disconnect from dock, resume)

2024-03-09 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=482841

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO
 CC||n...@kde.org
   Severity|normal  |crash

--- Comment #1 from Nate Graham  ---
Generally this means the kscreenlocker_greet process has crashed. And if
something crashed, we need a backtrace of it so we can figure out what's going
on. Can you please attach a backtrace of the crash using the `coredumpctl`
command-line program, as detailed in
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl?

Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.