[kwin] [Bug 408754] kwin-5.16.0: GUI (Wayland) freezes
https://bugs.kde.org/show_bug.cgi?id=408754 David Edmundson changed: What|Removed |Added CC||alo...@gmx-topmail.de --- Comment #13 from David Edmundson --- *** Bug 409036 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408754] kwin-5.16.0: GUI (Wayland) freezes
https://bugs.kde.org/show_bug.cgi?id=408754 David Edmundson changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED --- Comment #12 from David Edmundson --- I see what's wrong. We can infinite loop if we're placing a window with an invalid size in some conditions. Will fix. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408754] kwin-5.16.0: GUI (Wayland) freezes
https://bugs.kde.org/show_bug.cgi?id=408754 Mike changed: What|Removed |Added Version|5.16.0 |5.16.1 --- Comment #11 from Mike --- I installed plasma-5.16.1 today and I repeated the test. The bug is still there. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408754] kwin-5.16.0: GUI (Wayland) freezes
https://bugs.kde.org/show_bug.cgi?id=408754 --- Comment #10 from Mike --- Thanh, thanks for your post! I'm not sure that we talk about the same bug: - In your case, there seems to be a memory leak - I don't see a memory leak. - In your case, mouse and GUI are still responding (although sluggish) - in my case, desktop, keyboard and mouse freeze immediately. What you describe looks more like bug 407612. On the other hand, it well could be that we all suffer from the same problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408754] kwin-5.16.0: GUI (Wayland) freezes
https://bugs.kde.org/show_bug.cgi?id=408754 Thanh changed: What|Removed |Added CC||than...@vivaldi.net --- Comment #9 from Thanh --- Created attachment 120955 --> https://bugs.kde.org/attachment.cgi?id=120955&action=edit (KSysGuard) kwin_wayland memory I can confirm this on KDE Neon 5.16. When I switched to Wayland session at login screen, kwin_wayland was running with a load of ~25% (KSysGuard) CPU and memory ram was increase, cursor was sluggish moving, GUI was sluggish responding. Here my machine info: SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.16 User Edition KDE Plasma Version: 5.16.0 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 Kernel Version: 4.18.0-21-generic Graphics: Card-1: Intel Skylake GT2 [HD Graphics 520] Card-2: NVIDIA GM108M [GeForce 930M] Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting,nvidia (unloaded: fbdev,vesa,nouveau) Resolution: 1366x768@60.32hz OpenGL: renderer: GeForce 930M/PCIe/SSE2 version: 4.6.0 NVIDIA 390.116 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408754] kwin-5.16.0: GUI (Wayland) freezes
https://bugs.kde.org/show_bug.cgi?id=408754 --- Comment #8 from Mike --- Created attachment 120949 --> https://bugs.kde.org/attachment.cgi?id=120949&action=edit kwin_wayland gdb backtrace with debug symbols Andreas Sturmlechner showed me how to compile packages with debug symbols on. I repeated the test and created another backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408754] kwin-5.16.0: GUI (Wayland) freezes
https://bugs.kde.org/show_bug.cgi?id=408754 --- Comment #7 from Mike --- I did some more tests. Comment #5 is wrong. I am able to reproduce this error with a new user account. So the problem is not related to a migration from a previous release. One more observation: the error occurs *only* if the Wireshark window was maximized in a previous session. So here is a better version of 'Steps to Reproduce': 1) Create a new user (or delete all configuration files) 2) Start Plasma in Wayland mode 3) open a konsole terminal 4) enter wireshark 5) a wireshark window will pop up. Double-klick on the title bar to maximise it 6) Close Wireshark using File/Quit 7) enter wireshark in konsole terminal 8) GUI freezes, mouse disappears, top shows 100% CPU for /usr/bin/kwin_wayland My screen has a resolution of 1920x1200 pixels. > Can you do that again with debug symbols for kwin I'd like to do that, but I don't fully understand how to do it. Which CFLAGS and cmake options do you want me to use for kwin? Do you want me to create another backtrace with debug symbols on? Or will there be a debug log file if I run kwin with debug symbols on? Please point me to a HOWTO. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408754] kwin-5.16.0: GUI (Wayland) freezes
https://bugs.kde.org/show_bug.cgi?id=408754 --- Comment #6 from David Edmundson --- >Created attachment 120906 [details] That seems plausible, I did move when we do the initial placement with 5.16 Can you do that again with debug symbols for kwin and/or upload your kwinrc with the backup that causes the breakage. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408754] kwin-5.16.0: GUI (Wayland) freezes
https://bugs.kde.org/show_bug.cgi?id=408754 --- Comment #5 from Mike --- One more observation. I was able to reproduce the freeze reliably with 'wireshark'. I changed a few settings in 'systemsettings' and the error was gone. It never happened again. Then I restored my home directory from a backup - and the error was back: the freeze occurred every time I started 'wireshark'. It might well be that the error only occurs with certain system settings - or after you migrated from an older version of KDE Plasma. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408754] kwin-5.16.0: GUI (Wayland) freezes
https://bugs.kde.org/show_bug.cgi?id=408754 --- Comment #4 from Mike --- Created attachment 120906 --> https://bugs.kde.org/attachment.cgi?id=120906&action=edit kwin_wayland gdb backtrace I was able to write a gdb backtrace. 1) I started Plasma, opened a konsole window and started 'wireshark' 2) The GUI froze 3) I connected from another machine via SSH 4) kwin_wayland was running with a load of 100% 5) I started GDB and attached to the kwin_wayland process 6) I created the backtrace -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408754] kwin-5.16.0: GUI (Wayland) freezes
https://bugs.kde.org/show_bug.cgi?id=408754 --- Comment #3 from Mike --- Could be the same as bug 406548 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408754] kwin-5.16.0: GUI (Wayland) freezes
https://bugs.kde.org/show_bug.cgi?id=408754 --- Comment #2 from Mike --- > you run startx to get a wayland session? My fault. I'm sorry. I run a script 'startk' and its contents is export XDG_SESSION_TYPE=wayland export $(dbus-launch) && startplasmacompositor -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408754] kwin-5.16.0: GUI (Wayland) freezes
https://bugs.kde.org/show_bug.cgi?id=408754 David Edmundson changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||k...@davidedmundson.co.uk Resolution|--- |WAITINGFORINFO --- Comment #1 from David Edmundson --- >2. Start GUI (KDE Plasma) with 'startx' >5. GUI freezes, mouse disappears, top shows 100% CPU for /usr/bin/kwin_wayland you run startx to get a wayland session? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408754] kwin-5.16.0: GUI (Wayland) freezes
https://bugs.kde.org/show_bug.cgi?id=408754 Mike changed: What|Removed |Added Platform|Other |Gentoo Packages -- You are receiving this mail because: You are watching all bug changes.
