When fast switching windows and (possibly?) try to switch activity, screen going black and there's no chance to bring it back, but only CTRL+ALT+BACKSPACE twice. I cannot reproduce this bug always. It was causing (probably) by clicking alt+tab twice and pressing super + tab, I think. OBSERVED RESULT Screen going black EXPECTED RESULT Switch windows, but (maybe) activity will be switched too. Operating System: openSUSE Tumbleweed 20240104 KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 6.6.9-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ZenBook UX562IQ_UM562IQ System Version: 1.0 ADDITIONAL INFORMATION It exists since many updates on my system, with plasma6-beta updates. Possibly duplicate (but I am in doubt); https://bugs.kde.org/show_bug.cgi?id=427920
Might be a kwin crash. Could you switch to a virtual console via Ctrl-Alt-F3 and provide the output of journalctl -b when that happens? If you notice any crashes in the system journal, could you provide the relevant backtraces with debug symbols following the instructions here? https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Thanks!
Created attachment 164729 [details] Log part take from journalctl -b Some memory access bug?
Sorry I still do not prepare core dump. No time yet.
kwin_wayland do not crash. Once black screen appear, I switched to VT and kill kwin_wayland. I see also, that some app did not die (I think), since windows gets restored.
(In reply to Lach Sławomir from comment #4) > kwin_wayland do not crash. Once black screen appear, I switched to VT and > kill kwin_wayland. I see also, that some app did not die (I think), since > windows gets restored. Ah I see. Is kwin_wayland still using the CPU? If so, when your system hangs, would you be able to attach a gdb to the kwin_wayland process from the VT and attach a backtrace with debug symbols so that we could see where it is stuck at? Thanks again!
(In reply to fanzhuyifan from comment #5) > (In reply to Lach Sławomir from comment #4) > > kwin_wayland do not crash. Once black screen appear, I switched to VT and > > kill kwin_wayland. I see also, that some app did not die (I think), since > > windows gets restored. > > Ah I see. Is kwin_wayland still using the CPU? If so, when your system > hangs, would you be able to attach a gdb to the kwin_wayland process from > the VT and attach a backtrace with debug symbols so that we could see where > it is stuck at? > > Thanks again! I will attach gdb session, thanks for help! I must wait for case caused by bug now.
(In reply to fanzhuyifan from comment #5) > (In reply to Lach Sławomir from comment #4) > > kwin_wayland do not crash. Once black screen appear, I switched to VT and > > kill kwin_wayland. I see also, that some app did not die (I think), since > > windows gets restored. > > Ah I see. Is kwin_wayland still using the CPU? If so, when your system > hangs, would you be able to attach a gdb to the kwin_wayland process from > the VT and attach a backtrace with debug symbols so that we could see where > it is stuck at? > > Thanks again! Hi. Today it happens again. I ran: gdb -p PID /usr/bin/kwin_wayland, but it seems it do not have debug symbols. Backtrace shown only question marks in place of routine/function names. I install packages properly, I think: Name : kwin6 Version : 6.0.80git.20240115T185654~4433fb48 Release : 82.1 Architecture: x86_64 Install Date: wto, 16 sty 2024, 16:11:38 Group : Unspecified Size : 10212602 License : GPL-2.0-or-later AND GPL-3.0-or-later Signature : DSA/SHA1, pon, 15 sty 2024, 20:33:17, Key ID 2e85baee9ebd09c4 Source RPM : kwin6-6.0.80git.20240115T185654~4433fb48-82.1.src.rpm Build Date : pon, 15 sty 2024, 20:18:20 Build Host : i02-ch2d Vendor : obs://build.opensuse.org/KDE:Unstable URL : https://www.kde.org Summary : KDE Window Manager Description : KWin is Plasma window manager. Distribution: KDE:Unstable:Frameworks / openSUSE_Factory Name : kwin6-debuginfo Version : 6.0.80git.20240115T185654~4433fb48 Release : 82.1 Architecture: x86_64 Install Date: wto, 16 sty 2024, 18:44:39 Group : Development/Debug Size : 87618973 License : GPL-2.0-or-later AND GPL-3.0-or-later Signature : DSA/SHA1, pon, 15 sty 2024, 20:33:17, Key ID 2e85baee9ebd09c4 Source RPM : kwin6-6.0.80git.20240115T185654~4433fb48-82.1.src.rpm Build Date : pon, 15 sty 2024, 20:18:20 Build Host : i02-ch2d Vendor : obs://build.opensuse.org/KDE:Unstable URL : https://www.kde.org Summary : Debug information for package kwin6 Description : This package provides debug information for package kwin6. Debug information is useful when developing applications that use this package or when debugging this package. Distribution: KDE:Unstable:Frameworks / openSUSE_Factory
(In reply to Lach Sławomir from comment #7) > (In reply to fanzhuyifan from comment #5) > > (In reply to Lach Sławomir from comment #4) > > > kwin_wayland do not crash. Once black screen appear, I switched to VT and > > > kill kwin_wayland. I see also, that some app did not die (I think), since > > > windows gets restored. > > > > Ah I see. Is kwin_wayland still using the CPU? If so, when your system > > hangs, would you be able to attach a gdb to the kwin_wayland process from > > the VT and attach a backtrace with debug symbols so that we could see where > > it is stuck at? > > > > Thanks again! > > Hi. > Today it happens again. I ran: > gdb -p PID /usr/bin/kwin_wayland, but it seems it do not have debug symbols. > Backtrace shown only question marks in place of routine/function names. > > I install packages properly, I think: > Name : kwin6 > Version : 6.0.80git.20240115T185654~4433fb48 > Release : 82.1 > Architecture: x86_64 > Install Date: wto, 16 sty 2024, 16:11:38 > Group : Unspecified > Size : 10212602 > License : GPL-2.0-or-later AND GPL-3.0-or-later > Signature : DSA/SHA1, pon, 15 sty 2024, 20:33:17, Key ID 2e85baee9ebd09c4 > Source RPM : kwin6-6.0.80git.20240115T185654~4433fb48-82.1.src.rpm > Build Date : pon, 15 sty 2024, 20:18:20 > Build Host : i02-ch2d > Vendor : obs://build.opensuse.org/KDE:Unstable > URL : https://www.kde.org > Summary : KDE Window Manager > Description : > KWin is Plasma window manager. > Distribution: KDE:Unstable:Frameworks / openSUSE_Factory > Name : kwin6-debuginfo > Version : 6.0.80git.20240115T185654~4433fb48 > Release : 82.1 > Architecture: x86_64 > Install Date: wto, 16 sty 2024, 18:44:39 > Group : Development/Debug > Size : 87618973 > License : GPL-2.0-or-later AND GPL-3.0-or-later > Signature : DSA/SHA1, pon, 15 sty 2024, 20:33:17, Key ID 2e85baee9ebd09c4 > Source RPM : kwin6-6.0.80git.20240115T185654~4433fb48-82.1.src.rpm > Build Date : pon, 15 sty 2024, 20:18:20 > Build Host : i02-ch2d > Vendor : obs://build.opensuse.org/KDE:Unstable > URL : https://www.kde.org > Summary : Debug information for package kwin6 > Description : > This package provides debug information for package kwin6. > Debug information is useful when developing applications that use this > package or when debugging this package. > Distribution: KDE:Unstable:Frameworks / openSUSE_Factory For opensuse I think you can just use debuginfod: https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#openSUSE
(In reply to fanzhuyifan from comment #8) > (In reply to Lach Sławomir from comment #7) > > (In reply to fanzhuyifan from comment #5) > > > (In reply to Lach Sławomir from comment #4) > > > > kwin_wayland do not crash. Once black screen appear, I switched to VT and > > > > kill kwin_wayland. I see also, that some app did not die (I think), since > > > > windows gets restored. > > > > > > Ah I see. Is kwin_wayland still using the CPU? If so, when your system > > > hangs, would you be able to attach a gdb to the kwin_wayland process from > > > the VT and attach a backtrace with debug symbols so that we could see where > > > it is stuck at? > > > > > > Thanks again! > > > > Hi. > > Today it happens again. I ran: > > gdb -p PID /usr/bin/kwin_wayland, but it seems it do not have debug symbols. > > Backtrace shown only question marks in place of routine/function names. > > > > I install packages properly, I think: > > Name : kwin6 > > Version : 6.0.80git.20240115T185654~4433fb48 > > Release : 82.1 > > Architecture: x86_64 > > Install Date: wto, 16 sty 2024, 16:11:38 > > Group : Unspecified > > Size : 10212602 > > License : GPL-2.0-or-later AND GPL-3.0-or-later > > Signature : DSA/SHA1, pon, 15 sty 2024, 20:33:17, Key ID 2e85baee9ebd09c4 > > Source RPM : kwin6-6.0.80git.20240115T185654~4433fb48-82.1.src.rpm > > Build Date : pon, 15 sty 2024, 20:18:20 > > Build Host : i02-ch2d > > Vendor : obs://build.opensuse.org/KDE:Unstable > > URL : https://www.kde.org > > Summary : KDE Window Manager > > Description : > > KWin is Plasma window manager. > > Distribution: KDE:Unstable:Frameworks / openSUSE_Factory > > Name : kwin6-debuginfo > > Version : 6.0.80git.20240115T185654~4433fb48 > > Release : 82.1 > > Architecture: x86_64 > > Install Date: wto, 16 sty 2024, 18:44:39 > > Group : Development/Debug > > Size : 87618973 > > License : GPL-2.0-or-later AND GPL-3.0-or-later > > Signature : DSA/SHA1, pon, 15 sty 2024, 20:33:17, Key ID 2e85baee9ebd09c4 > > Source RPM : kwin6-6.0.80git.20240115T185654~4433fb48-82.1.src.rpm > > Build Date : pon, 15 sty 2024, 20:18:20 > > Build Host : i02-ch2d > > Vendor : obs://build.opensuse.org/KDE:Unstable > > URL : https://www.kde.org > > Summary : Debug information for package kwin6 > > Description : > > This package provides debug information for package kwin6. > > Debug information is useful when developing applications that use this > > package or when debugging this package. > > Distribution: KDE:Unstable:Frameworks / openSUSE_Factory > > For opensuse I think you can just use debuginfod: > > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#openSUSE I see. Debuginfod do not work probably, because to trace/debug kwin_wayland, I need root privileges. I will set required environment variable in root shell :-D .
(In reply to Lach Sławomir from comment #9) > I see. Debuginfod do not work probably, because to trace/debug kwin_wayland, > I need root privileges. I will set required environment variable in root > shell :-D . Glad you traced down the issue! You could also just do "sudo -E gdb ..."
No problems since last post. Did someone pull any changes, which could repair problem?
I remind myself I did copy of NVidia driver from older kernel to never, because I need working NVidia drivers. I think this could be a case. So sorry, if you lost your time. I think, you could close this request and (if problem still persist), I will reopen it.
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!
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!