| Summary: | Plugging in new display crashes Plasmashell | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | miranda |
| Component: | generic-multiscreen | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | aleixpol, miranda, nate, notmart |
| Priority: | NOR | ||
| Version First Reported In: | 5.27.3 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
crash on new monitor
coredumpctl output coredumpctl list 1934 coredumps from journalctl |
||
Also forgot to add: This was using an X11 session, Xorg version 21.1.7 I see a full stack trace in the log but it's hard to read. Can you clean it up? You can do so like this in a terminal window: `coredumpctl gdb 1934` [Wait until it downloads all debug symbols] `bt` [hit Return or Enter key until it shows everything] [copy and paste the backtrace until a comment here] Thanks! Attached is the output of "coredumpctl gdb 1934". Notably, it ends in: "Cannot access "/var/lib/systemd/coredump/core.plasmashell.1000.c3d61e41a8eb4699a6001b4a3df4791d.1934.1680143402000000.zst": No such file or directory" Created attachment 157835 [details]
coredumpctl output
Created attachment 157836 [details]
coredumpctl list 1934
And here's the output of "coredumpctl list 1934"
Fairly certain this is because /usr/lib/tmpfiles.d/systemd.conf defaults to deleting files from the directory after 3 days: d /var/lib/systemd/coredump 0755 root root 3d Created attachment 157837 [details]
coredumps from journalctl
Hm, well here's the output of "journalctl MESSAGE_ID=fc2e22bc6ee647b6b90729ab34a250b1 -o verbose -S 2023-03-28"
If you know of a way to export this formatted for coredump/core*.zst so I can run it through gdb like you've requested, feel free to let me know. :)
I'm not that advanced, sorry. But if you can reproduce the issue at will, you could always just get it to crash again and then follow the steps at https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl. The latest attachment (2023-04-04 00:32 UTC) should have the full stack trace. Is it not formatted in a readable manner? If not, let me know, because I can't reproduce this reliably and it takes some effort to recreate. The display is in the other room, so there's a lot of peeking around the corner to check if it broke as I unplug and replug stuff. The problem is, it's weird and unreadable and also missing debug symbols for plasmashell:
#5 0x00005632318481dd n/a (plasmashell + 0x4e1dd)
#6 0x00007f4dc66bea71 n/a (libQt5Core.so.5 + 0x2bea71)
#7 0x00007f4dc66c0fcf _ZN6QTimer7timeoutENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2c0fcf)
#8 0x00007f4dc66b1b56 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2b1b56)
#9 0x00007f4dc7378b5c _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x178b5c)
#10 0x00007f4dc668df48 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x28df48)
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! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! |
Created attachment 157712 [details] crash on new monitor SUMMARY When plugging in a new display, plasmashell can crash (mulitple times over) resulting in the new display having a blank screen (no shell). So far unable to reproduce after saving display settings and unplugging/replugging, but until that point the "new display" part may or may not be relevant. STEPS TO REPRODUCE 1. Plug in new monitor OBSERVED RESULT Plasmashell crashes (three times over in this case), leaving new screen blank EXPECTED RESULT Plasmashell does not crash, and loads properly on new display SOFTWARE/OS VERSIONS Linux/KDE Plasma KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Video Card: AMD RX 6600 XT Mesa Version: 23.0.1 Kernel Version: 6.2.8-arch1-1 Attached is journal output starting from once I plugged in the new screen, to when I first opened the display configuration in the settings app to check what had happened. Before the crash, I had DP-2 and DP-3, both 1920x1080@60, with DP-3 left of DP-2 I then plugged in HDMI-1 with a native res of 3840x2160@120, which lead to the crashing