Bug 688128 – kde-plasma/kwin-5.16.0: GUI (Wayland) freezes

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Michael Hofmann 2019-06-15 20:11:13 UTC]

I use KDE plasma in Wayland mode (kwin is the Wayland compositor).
Last week I updated to:
- kde-plasma-5.16.0
- kde-frameworks-5.59.0
- kde-apps-19.04.2 
After that, my screen randomly froze once or twice a day.
Today I found out that I can trigger a freeze by starting Wireshark-3.0.2 from konsole: GUI freezes, mouse disappears, top shows 100% CPU for /usr/bin/kwin_wayland, Alt-Ctrl-Fn or Ctrl-BS don't work.
I downgraded kde-plasma/kwin to 5.15.5 (only this package). I haven't had any freezes since then and I can start Wireshark-3.0.2 without problems. 

Reproducible: Always

Steps to Reproduce:
1. Login as ordinary user on Linux TTY console
2. Start GUI (KDE Plasma) with 'startx'
3. open a konsole terminal
4. enter 'wireshark'
5. GUI freezes, mouse disappears, top shows 100% CPU for /usr/bin/kwin_wayland

[Comment 1 Andreas Sturmlechner 2019-06-15 20:13:16 UTC]

Please file an upstream bug.

[Comment 2 Michael Hofmann 2019-06-15 20:16:42 UTC]

Created attachment 579880 [details]
emerge --info

[Comment 3 Michael Hofmann 2019-06-15 20:31:16 UTC]

> Please file an upstream bug.
Done: https://bugs.kde.org/show_bug.cgi?id=408754

[Comment 4 Andreas Sturmlechner 2019-06-17 05:30:16 UTC]

Since upstream asked you for debug symbols, here's a crash course: https://wiki.gentoo.org/wiki/Debugging

You can selectively enable that using a package.env: https://wiki.gentoo.org/wiki//etc/portage/package.enB but then you'll have more work to do identifying all dependencies involved in the backtrace (those .so files with empty '()')and add those to the debug config as well.

[Comment 5 Michael Hofmann 2019-06-17 11:59:23 UTC]

Thanks! I'll do that!

[Comment 6 Michael Hofmann 2019-06-17 13:52:07 UTC]

OK, I created /etc/portage/env/{debugsyms,installsources}. I searched for empty '()' my first backtrace and created /etc/portage/package.env:

 dev-libs/glib              debugsyms installsources
 dev-libs/libffi            debugsyms installsources
 dev-libs/wayland           debugsyms installsources
 dev-qt/qtcore              debugsyms installsources
 dev-qt/qtdbus              debugsyms installsources
 dev-qt/qtdeclarative       debugsyms installsources
 dev-qt/qtscript            debugsyms installsources
 dev-qt/qtvirtualkeyboard   debugsyms installsources
 dev-qt/qtwayland           debugsyms installsources
 dev-qt/qtwidgets           debugsyms installsources
 kde-frameworks/kdbusaddons debugsyms installsources
 kde-frameworks/kwayland    debugsyms installsources
 kde-plasma/kwin            debugsyms installsources
 media-libs/mesa            debugsyms installsources
 sys-apps/dbus              debugsyms installsources
 sys-libs/glibc             debugsyms installsources

I re-emerged those packages, repeated my test and created a new backtrace.

[Comment 7 Michael Hofmann 2019-06-25 12:16:24 UTC]

Upstream fixed the bug. The fix will probably be included in kde-plasma-5.16.2.

For those who need a fix in kde-plasma-5.16.1: https://phabricator.kde.org/D21997

[Comment 8 Andreas Sturmlechner 2019-06-25 18:02:03 UTC]

5.16.2 is now in tree.