SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Switch HDMI source to another input 2. Switch back to the desktop input OBSERVED RESULT 1. Plasma freezes for a few seconds 2. media playing stops and crashes, along with i.e. Firefox 3. the taskbar disappears while I guess Plasma restarts 4. desktop is again responsive EXPECTED RESULT Nothing SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20221022 KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Graphics Platform: Wayland ADDITIONAL INFORMATION This didn't use to happen till 5.25.5. I held back until 5.26.1 hoping that this https://bugs.kde.org/show_bug.cgi?id=460322 was the fix, but it still happens.
Oct 24 12:12:48 suse kdeconnectd[4433]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Oct 24 12:12:48 suse foot[4425]: wayland: unknown global removed: 0x00000034 Oct 24 12:13:11 suse foot[4425]: warn: wayland.c:1207: unknown global removed: 0x00000034 Oct 24 12:13:11 suse foot[4425]: info: wayland.c:1152: monitor unplugged or disabled: HDMI-A-1 Oct 24 12:12:48 suse polkit-kde-authentication-agent-1[4333]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Oct 24 12:12:48 suse foot[4425]: wayland: monitor unplugged or disabled: HDMI-A-1 Oct 24 12:12:48 suse xdg-desktop-portal-kde[4335]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Oct 24 12:12:48 suse kwalletd5[4551]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Oct 24 12:12:48 suse kalendarac[4454]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Oct 24 12:12:48 suse kmozillahelper[29646]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Oct 24 12:12:48 suse klauncher[4623]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Oct 24 12:12:48 suse drkonqi-coredump-gui[32660]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Oct 24 12:12:48 suse krunner[14036]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Oct 24 12:12:48 suse kactivitymanagerd[4331]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Oct 24 12:12:48 suse kwalletmanager5[4652]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Oct 24 12:12:48 suse corectrl[4430]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Oct 24 12:12:48 suse kwin_wayland[4227]: libkwinglutils: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" Oct 24 12:12:48 suse kwin_wayland[4227]: libkwinglutils: Can't enable invalid framebuffer object! Oct 24 12:12:48 suse org_kde_powerdevil[4334]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Oct 24 12:12:48 suse kded5[4284]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Oct 24 12:12:49 suse systemd[1500]: Starting KScreen OSD service... Oct 24 12:12:49 suse plasmashell[4307]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Oct 24 12:12:49 suse systemd[1]: Started Process Core Dump (PID 469/UID 0). Oct 24 12:12:50 suse plasmashell[4307]: file:///usr/lib64/qt5/qml/org/kde/plasma/private/containmentlayoutmanager/BasicAppletContainer.qml:144: TypeError: Cannot read property 'width' of null Then there's a big spam of "plasmashell[4307]: requesting unexisting screen 0"
This should be fixed automatically by fixing 450068. > 3. the taskbar disappears while I guess Plasma restarts This means Plasma crashed--despite the line in the config file that says, "Creating a fake screen in order for Qt not to crash." I guess that didn't work. :( Can you attach a symbolicated backtrace of the crash? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports. Thanks!
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!