Summary: | plasmashell crashes after extended period of lock time | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Mark Deneen <mdeneen+kde> |
Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | kdedev, nate |
Priority: | NOR | Keywords: | drkonqi |
Version First Reported In: | 6.2.5 | ||
Target Milestone: | 1.0 | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | https://crash-reports.kde.org/organizations/kde/issues/7089/events/29f93bc0faab40aba262e4bc7677b62f/ |
Description
Mark Deneen
2025-01-30 14:00:09 UTC
I don't see any KDE code in the crashing thread; looks like it might be in Qt or the GPU drivers. Can you comment on what kind of GPU the system has? Also, while locked, is the system configured to never go to sleep? Or does it sleep after a little while after being locked? Hey Nate, The system is not configured to sleep unless it's on battery power, which it is not. The device itself has two GPUs and I have the nvidia drivers installed. 01:00.0 VGA compatible controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] (rev a1) 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [Radeon Vega Series / Radeon Vega Mobile Series] (rev c7) extra/nvidia 565.77-12 [installed] extra/nvidia-utils 565.77-3 [installed] I'm not super familiar with how Wayland uses multiple GPUs, but I do know that only certain processes will use it and that plasmashell does not appear to be, according to the output of nvidia-smi. If this is a bug with the nvidia drivers, I suppose that we can close this bug report and I can try to narrow it down on the nvidia side. Of course, if you have any insightful knowledge to send me in the right direction, I would be more than happy to accept it. :-) I also wanted to note that I have both the laptop screen and an external monitor active. I disabled the laptop monitor last week, and unlocked the screen today. I also set "Preferred Ozone platform" to "Wayland" in Chrome. There was no delay and no crash when unlocking my desktop this morning. ๐๐งน โ ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! This is definitely still a problem, although I've worked around it by disabling the laptop monitor. You may be able to recreate it by adding an external monitor to a laptop and making it the primary display. After locking the desktop for a weekend and receiving a fair number of notifications it will lock up when the screen is unlocked again. Based on the backtrace this looks like a duplicate of bug 487699. Please follow that report if you would like updates on the progress of this issue. Thanks! *** This bug has been marked as a duplicate of bug 487699 *** |