| Summary: | KWin crashes when laptop goes to sleep | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | olanti-p |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | kde.org, lanvag |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.16.5 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
olanti-p
2020-04-06 13:56:34 UTC
Created attachment 127680 [details]
New crash information added by DrKonqi
kwin_x11 (5.18.4) using Qt 5.14.2
- What I was doing when the application crashed:
Sent the laptop to sleep, woke it up a few hours later. Received an error message after logging on.
-- Backtrace (Reduced):
#6 0x00007fcd8eb55109 in () at /usr/lib/libkwin4_effect_builtins.so.1
#7 0x00007fcd8eb551c7 in () at /usr/lib/libkwin4_effect_builtins.so.1
#8 0x00007fcd8eb57062 in () at /usr/lib/libkwin4_effect_builtins.so.1
#9 0x00007fcd8eb5798b in () at /usr/lib/libkwin4_effect_builtins.so.1
#10 0x00007fcd9047c370 in KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion const&, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5
Thank you for reporting this bug. Unfortunately, the backtrace doesn't contain proper debugging information. Can you still reproduce this issue with KDE 5.23? If so, can you please install debugging packages following the info provided in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports, try to reproduce the bug and resubmit a backtrace with debugging information. 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! (In reply to kde.org from comment #2) > Thank you for reporting this bug. Unfortunately, the backtrace doesn't > contain proper debugging information. Can you still reproduce this issue > with KDE 5.23? If so, can you please install debugging packages following > the info provided in > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports, try to reproduce the bug and resubmit a > backtrace with debugging information. Unfortunately it's been year and a half since the report, and in that time I've replaced that OS with a clean install of newer version, which included setting up graphics and drivers from scratch and in a different way. I have no idea how to get back to the old setup and reproduce the issue, but it is absent in the new setup (with KDE 5.18.5), so something helped. I half-hoped that even without my setup available the backtrace and description by themselves would be enough to shed some light, but apparently that's not the case, so the issue can be closed I guess... |