| Summary: | On X11, plasma crashed after monitors left power save mode | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | cat22 <erbenton> |
| Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | REPORTED --- | ||
| Severity: | crash | CC: | ahjolinna, justin, mathias, nate |
| Priority: | NOR | Keywords: | drkonqi, multiscreen, qt-crash, X11-only |
| Version First Reported In: | 6.1.4 | ||
| Target Milestone: | 1.0 | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
coredumpctl gdb 2814
inxi dump crash on monitor wake |
||
|
Description
cat22
2024-09-01 16:20:15 UTC
Could you please install debug symbols and attach a new symbolicated backtrace generated by using coredumpctl gdb in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this. Thank you. I'd prefer not to wreck my current setup. I only filled that dialog in because i was prompted to Installing debug symbols will not wreck your setup. Without them, it is unlikely the bug report will get any traction and will likely be closed due to lack of information. I'll set this to NEEDSINFO, if you can provide it, then please do so, otherwise the Janitor Bot will close it in 30 days. This thing went through a good ten minutes of downloading stuff before it fled the original report. Was tat the debug stuff you mentioned? If not, what was it downloading? Created attachment 173250 [details]
coredumpctl gdb 2814
That last attachment looks better, no missing symbols, thanks for the updated backtrace! Will the downloaded debug stuff be persistent? e.g after a zyppper dup if i download new symbols wilt the old ones be replaced? if the old symbols are out dated after an update how do i delete them? I see on my system they're stored in ~/.cache/debuginfod_client and cache_clean_interval_s in that folder seems to indicate they are automatically cleared out after 1 day. Unfortunately the backtrace still doesn't indicate any KDE code at fault. Looks like you have an NVIDIA GPU, right? Can you do the following: - See if it still happens in the Wayland session - Mention how many monitors you have and how they're connected - If you have the ability to remove or disable the NVIDIA GPU and use a different or integrated GPU, try using that setup and seeing if the issue still happens (if possible; I know this is a larger request) Thanks! It doesn't happen under wayland, as far ass i can tell. This is a desktop and i have no other GPU' s to try it with I have 2 monitors, they connected => one vi DP and the other via HDMI. Please see the inxi dump attached I am really convinced the issue is with kscreen2 Created attachment 173368 [details]
inxi dump
Created attachment 173378 [details]
crash on monitor wake
When my dual monitors are sleeping, (kscreen2 is disabled) and i press a key to wake them up. Sometimes only 1 monitor wakes up. I then have to press Ctrl-Alt-F1 and wait for both monitors to wake in terminal mode. Then I press Ctrl-Alt-F2 to get back to GUI mode and the crash dialog is there. Perhaps this crash dump (plasmashell-20240906-035534.kcrash ) will be helpful
note sure if related, but I'm using the Git version of KDE with Wayland on an Nvidia RTX 3060 Ti (v560.35.03 driver), running openSUSE Tumbleweed. After returning from sleep, I occasionally receive (multiple) crash notifications related to X11. If I resume from sleep directly from X11, it just fails—the monitor stays blank, and nothing happens. Adding the x11-only keyword |