https://bugs.kde.org/show_bug.cgi?id=462346
Bug ID: 462346
Summary: GNOME 43 application cause kwin_wayland to freeze when
using header bar buttons or menus
Classification: Plasma
Product: kwin
Version: git master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: o...@geek.co.il
Target Milestone: ---
SUMMARY
When using GNOME 43 applications under kwin_wayland, every time the user clicks
on a header bar button, or a header bar menu action, kwin freezes for about a
minute - there's no mouse cursor movement, nor does it respond to any key - not
even vt switching keys.
After about a minute, the action completes and everything continues normally,
including the action that was requested by the mouse click. This was observed
with GNOME Text Editor and GNOME Console.
- Kwin is installed from neon unstable - currently at
4:5.26.3+p22.04+tunstable+git20221124.0014-0
- GNOME applications where installed from DEB files built for Ubuntu kinetic -
text editor is at 43.1-1ubuntu1, console is at 43.0-2
The same use case with kwin_x11 (currently at
4:5.26.3+p22.04+tunstable+git20221124.0014-0) works fine.
STEPS TO REPRODUCE
1. Start a Plasma Wayland session
2. Launch a GNOME 43 application (such as Text Editor or Console)
3. Use the mouse cursor to press the application's close button (or any other
header bar button).
OBSERVED RESULT
The entire graphical session stops responding for about a minute - nothing
happens on the display and no key strokes are accepted. When the session
unfreezes, key strokes sent during the freeze are processed. Whatever behavior
the application expected to trigger happens normally.
EXPECTED RESULT
The application should behave normally, i.e. the close button should
immediately start the application's close behavior.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 5.26.80
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7
ADDITIONAL INFORMATION
I managed to get full thread back traces of kwin while it is frozen, and it
seems to be stuck on waiting for a dbus message reply. I'll attach the back
traces next.
--
You are receiving this mail because:
You are watching all bug changes.
