| Summary: | Crashes after Screen Locks | ||
|---|---|---|---|
| Product: | [Unmaintained] ksmserver | Reporter: | Dimitris Giannos <aclassifiedmail> |
| Component: | general | Assignee: | David Edmundson <kde> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | nate, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 5.21.0 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
My Displays
Crash Reports WeirdDesktop |
||
|
Description
Dimitris Giannos
2021-02-20 12:31:57 UTC
Are you using systemd startup? Could you attach backtraces for the two crashing processes? I have reinstalled plasma and I will see whether they will pop up again. Sorry, I thought I had attached a screenshot with dev info from all 3 crashes. Also forgot to mention that this happened in wayland. I'l see if it happens again. Created attachment 136089 [details]
My Displays
Okay, I was given the luck to find more info about this case. This will take some comments because of many attachments (4 or 3).
So, in this attachment you can see my 2 displays. For some reason there are 2 displays but I have only 1 screen. Notice that DP is on 60Hz and the other HDMI one on 30Hz. No crashes are reported when I put the one display on top of the other (preferably 60Hz (DP) on top)...
Created attachment 136090 [details]
Crash Reports
Here are the 3 reports I get after every screen lock WHILE I have ONLY the DP (60Hz) display enabled (and the other disabled). Those don't appear when I have both displays one on top of the other.
Created attachment 136092 [details] WeirdDesktop And here is what I saw after a screen lock while having both displays enabled (one on top of the other again). But I'm not sure whether this could happen again. It seems like the one display somehow is used for the applets on desktop while the other is used for the panels. This whole thing could be related to bug 433115, monitor details here as well. I have heard that the drivers of the monitor are kind of buggy. Thanks. In the future can you attach the text of the crash reports as text, rather than taking a picture of the text? We'll need debug symbols to be able to figure out what's going on. In particular, that line that says: > in () at /usr/lib/libQt5WaylandClient.s.5 We need to know what goes inside the (), but it's missing because your packages don't have debug symbols. Can you please rebuild that library with debug symbols acsording to the Arch documentation (https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces) and get a new backtrace when it happens again so we can figure out what's causing the crash? Alright, I'll try the next times... But I really wonder why they don't contain debug symbols by default... A good question for the Arch packagers. I can tell you with my bug triaging hat on that it's pretty darn annoying, especially because we get a lot of crash reports from Arch users acting basically as QA for people who use LTS distros. Perhaps you can see the discussion here: https://bugs.archlinux.org/task/38755 Ye, now I have to recompile everything from source :/ (or I don't get it). Would be so much better if debug symbols were enabled by default in official packages. Yep, that's one of the trade-offs you make when you use Arch. :) Every distro has quirks like this. 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! Well I don't get the bug anymore after rearranging screens. I get it rarely but I don't know how to reproduce it. I also suspect it's a drivers' issue. Should this be closed for now? (In reply to Dimitris Giannos from comment #12) > Well I don't get the bug anymore after rearranging screens. I get it rarely > but I don't know how to reproduce it. I also suspect it's a drivers' issue. > Should this be closed for now? I meant the crashes* 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! |