Created attachment 135635 [details] crash message about wayland SUMMARY KDE crashes while using wayland session If I close my laptop's lid while using dual monitor and wayland session, second monitor freezes and I saw black screen. If I re-open lid, I saw crash messages about wayland. I don't have any problem with X11. STEPS TO REPRODUCE 1. Close lid 2. Wait 2 seconds 3. Re-open lid OBSERVED RESULT Most KDE components crashed (including desktop, drkonqi, kdeconnectd, ...) EXPECTED RESULT Everything works normally SOFTWARE/OS VERSIONS Operating System: Fedora 33 KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.14-200.fc33.x86_64 OS Type: 64-bit Graphics Platform: Wayland Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx Memory: 5.8 GiB of RAM Graphics Processor: AMD RAVEN ADDITIONAL INFORMATION $ neofetch --stdout fedora@rip --------- OS: Fedora release 33 (Thirty Three) x86_64 Host: VivoBook_ASUSLaptop X509DJ_D509DJ 1.0 Kernel: 5.10.14-200.fc33.x86_64 Uptime: 1 hour, 2 mins Packages: 3120 (rpm) Shell: bash 5.0.17 Resolution: 1360x768 DE: Plasma 5.20.90 WM: kwin WM Theme: Ant-Dark Theme: Genome Dark [Plasma], Adwaita [GTK2], Orchis-dark-compact [GTK3] Icons: Vimix-dark [Plasma], Vimix-dark [GTK2/3] Terminal: konsole CPU: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx (8) @ 2.100GHz GPU: AMD ATI 04:00.0 Picasso GPU: NVIDIA GeForce MX230 Memory: 2965MiB / 5944MiB
> #7 QMessageLogger::fatal (this=this@entry=0x7ffc18a866e0, > msg=msg@entry=0x7f28a8759e90 "The Wayland connection broke. > Did the Wayland compositor die?") at global/qlogging.cpp:893 This means that the KWin compositor crashed. When that happens, all apps die, sadly. Can you attach a backtrace of the kwin_wayland crash? Thanks!
How to get kwin_wayland traceback?
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
I tried to get stack trace but I'm failed Stack trace of thread 48458: #0 0x00007f4a1927f9d5 n/a (n/a + 0x0) so I have 3MB coredump file only, do you want this?
Created attachment 135666 [details] core.kwin_wayland.1000.6228932f8e0044079fba4c863a792347.48458.1613268119000000.zst kwin_wayland coredump file
You'll need to open that coredump file in gdb to see the actual backtrace, like this: gdb /usr/bin/kwin_wayland [path to coredump file]
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!