Bug 418845 - Kwin crashes every time system wakes from suspend if display is powered down
Summary: Kwin crashes every time system wakes from suspend if display is powered down
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.12.9
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-14 12:15 UTC by shout
Modified: 2020-04-13 04:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Backtrace error (1) (506.17 KB, image/jpeg)
2020-03-14 12:15 UTC, shout
Details
Backtrace error (2) (460.06 KB, image/jpeg)
2020-03-14 12:16 UTC, shout
Details

Note You need to log in before you can comment on or make changes to this bug.
Description shout 2020-03-14 12:15:24 UTC
Created attachment 126777 [details]
Backtrace error (1)

Kwin crashes every time I wake from suspend if the monitor is powered down when the system wakes. This is a replicable bug on my system with the crash occurring every time under this scenario.

I'm unable to get a backtrace due to further issues installing required debug symbol packages. See below for further explanation. If someone could assist in getting a successful backtrace I'll provide that.

The crash only occurs when I manually power down the monitor after suspend (which is necessary in my case), then attempt to wake from sleep *before* powering the monitor back up. If I power up the monitor before wake, the bug does not occur.

Crash text simply says:

`Application: KWin (kwin_x11), signal: Segmentation fault`

Furthermore, when clicking the button on the bug report app to install missing symbols for the backtrace, the process fails with an error stating the packages cannot be installed. No additional information is presented, nor does it say what the missing packages are.

Clicking the link below that bug report dialog to list missing debug packages (with a view to installing manually) just lists the following: 

`/usr/bin/kwin_x11`.

Please see attached screenshots of these errors. Note, the screen resolution is also incorrect following the crash and remains so until a new session is started.

The monitor is attached through DisplayPort.

Journald provides the following related log entries:

```
Mar 11 12:09:29 aninstanceofubuntu kernel: kuiserver5[3455]: segfault at c ip 00007fb21507f60b sp 00007ffedc47e010 error 4 in libQt5XcbQpa.so.5.9.5[7fb215044000+fe000]
Mar 11 12:09:29 aninstanceofubuntu kernel: nextcloud[2560]: segfault at c ip 00007f9b9825460b sp 00007ffdf30070b0 error 4 in libQt5XcbQpa.so.5.9.5[7f9b98219000+fe000]
Mar 11 12:09:29 aninstanceofubuntu kernel: kwalletd5[2333]: segfault at c ip 00007fe7af82660b sp 00007ffcb49751e0 error 4 in libQt5XcbQpa.so.5.9.5[7fe7af7eb000+fe000]
Mar 11 12:09:29 aninstanceofubuntu kernel: kdeconnectd[2516]: segfault at c ip 00007f6877d8660b sp 00007ffda4bfe5c0 error 4 in libQt5XcbQpa.so.5.9.5[7f6877d4b000+fe000]
Mar 11 12:09:29 aninstanceofubuntu kernel: kactivitymanage[2462]: segfault at c ip 00007fee76fd360b sp 00007fff0eff7300 error 4 in libQt5XcbQpa.so.5.9.5[7fee76f98000+fe000]
Mar 11 12:09:29 aninstanceofubuntu kernel: xembedsniproxy[2508]: segfault at c ip 00007f3db9a2e60b sp 00007ffe71020820 error 4 in libQt5XcbQpa.so.5.9.5[7f3db99f3000+fe000]
Mar 11 12:09:29 aninstanceofubuntu kernel: baloorunner[3521]: segfault at c ip 00007f3be7a5960b sp 00007ffc1f7bf180 error 4 in libQt5XcbQpa.so.5.9.5[7f3be7a1e000+fe000]
Mar 11 12:09:29 aninstanceofubuntu kernel: kscreen_backend[2531]: segfault at c ip 00007fcf211da60b sp 00007ffddeb4eb40 error 4 in libQt5XcbQpa.so.5.9.5[7fcf2119f000+fe000]
```

System info:

- Kubuntu 18.04, with Kubuntu backports PPA (kubuntu-ppa-ubuntu-backports-bionic)
- KDE Plasma Version: 5.12.9
- KDE Frameworks Version: 5.47.0
- QT Version: 5.9.5
- Kernel Version: 5.3.0-40-generic
- CPU: 4 x AMD Ryzen 3 3200G with Radeon Vega Graphics (onboard)
- Memory: 29.4 GiB DDR4 RAM
Comment 1 shout 2020-03-14 12:16:08 UTC
Created attachment 126778 [details]
Backtrace error (2)
Comment 2 Christoph Feck 2020-03-14 16:32:15 UTC
Please ask for help in a forum of your distribution how to install debug packages for PPAs.
Comment 3 shout 2020-03-14 20:00:30 UTC
(In reply to Christoph Feck from comment #2)
> Please ask for help in a forum of your distribution how to install debug
> packages for PPAs.

I have a lot of PPA debug packages for the Kwin backport installed, including kwin-common-dbgsym, kwin-x11-dbgsym, kwin-wayland-dbgsym, qml-module-org-kde-kwindowsystem-dbgsym.

However, each time the crash occurs, different packages are being identified by the system as the source of the crash; initially it was "kwin" as below, then it became installed apps (e.g. Yakuake, then something else the next time, depending on what was running when the machine was suspended). 

It is as if an initial crash causes a crash cascade.

The crash / backtrace dialog is quite useless here - it simply reports an error in downloading the debug packages, but does not provide any further details. Precise missing debug packages are not identified.

After clicking to restart the session (with the crash reporter failing to have made a bug report due to inadequate information), I'm then presented with another X-Message dialog:

`Could not start Ksmserver. Check your installation`.

I click "okay" - which then punts me back to the login screen, where I'm able to finally start a new session.

I don't know where to go from here. Without knowing exactly which additional packages are actually required for a backtrace, I'm at a loss. 

I've already spent too much time faffing about trying to report this bug, as whilst annoying, is not a showstopper, and is likely an edge-case for my system setup (PPA on top of Kubuntu 18.04, for example). I'm content to simply remember to switch the monitor on before waking from sleep - however just thought a bug report might be helpful to the project. But if the information I've provided is inadequate and you're not in a position to provide precise guidance as to which additional packages, exactly, I need to install to get a useful backtrace, then please feel free to close this report. Thanks.
Comment 4 Bug Janitor Service 2020-03-29 04:33:10 UTC
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!
Comment 5 Bug Janitor Service 2020-04-13 04:33:12 UTC
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!