I am facing random complete freeze of Kunbuntu when using KVM HDMI switch. This happens with 25.10 but also with previous versions including LTS.
When the issue occurs, i don’t have access to anything: keyboard, mouse… the only solution is to restart using power button. The problem can happen several times per day or not…
How could this be fixed please?
From the journal logs i get:
nov. 05 08:51:23 papadou kactivitymanagerd[2684]: qt.qpa.wayland: There are no outputs - creating placeholder screen
nov. 05 08:51:23 papadou polkit-kde-authentication-agent-1[2689]: qt.qpa.wayland: There are no outputs - creating placeholder screen
nov. 05 08:51:23 papadou plasmashell[2656]: kde.plasmashell: requesting unexisting screen available rect -1
nov. 05 08:51:23 papadou kded6[2627]: qt.qpa.wayland: There are no outputs - creating placeholder screen
nov. 05 08:51:24 papadou DiscoverNotifier[2942]: qt.qpa.wayland: There are no outputs - creating placeholder screen
nov. 05 08:51:24 papadou xdg-desktop-portal-kde[3189]: qt.qpa.wayland: There are no outputs - creating placeholder screen
nov. 05 08:51:24 papadou systemsettings[3067]: qt.qpa.wayland: There are no outputs - creating placeholder screen
nov. 05 08:51:24 papadou kdeconnectd[2902]: qt.qpa.wayland: There are no outputs - creating placeholder screen
nov. 05 08:51:24 papadou kwin_wayland_wrapper[2495]: kwin_xwl: Could not find a matching X RandR CRTC/output to set as primary for KWin::PlaceholderOutput(0x622284079db0, name="Placeholder-1", geometry=QRect(0,0 1920x1080), scale=1)
nov. 05 08:51:24 papadou kwin_wayland_wrapper[2495]: kwin_xwl: Could not find a matching X RandR CRTC/output to set as primary for KWin::PlaceholderOutput(0x622284079db0, name="Placeholder-1", geometry=QRect(0,0 1920x1080), scale=1)
nov. 05 08:51:24 papadou konsole[3066]: qt.qpa.wayland: There are no outputs - creating placeholder screen
nov. 05 08:51:24 papadou org_kde_powerdevil[2690]: qt.qpa.wayland: There are no outputs - creating placeholder screen
nov. 05 08:51:24 papadou plasmashell[2656]: qt.qpa.wayland: There are no outputs - creating placeholder screen
nov. 05 08:51:24 papadou org_kde_powerdevil[2690]: [ 8913] Removing connected display on bus 1
nov. 05 08:51:24 papadou org_kde_powerdevil[2690]: [ 8913] Emitting DDCA_Display_Status_Event[2986.607: DDCA_EVENT_DISPLAY_DISCONNECTED, card1-HDMI-A-1, dref: DDCA_Display_Ref[11], io_path:/dev/i2c-1, ddc working: false]
nov. 05 08:51:24 papadou org_kde_powerdevil[2690]: [ 8913] libddcutil callback thread 0x74fed8013440 started
nov. 05 08:51:24 papadou org_kde_powerdevil[2690]: [ 8913] Started 1 event callback thread(s)
nov. 05 08:54:03 papadou rtkit-daemon[2300]: Supervising 10 threads of 7 processes of 1 users.
nov. 05 08:54:03 papadou rtkit-daemon[2300]: Supervising 10 threads of 7 processes of 1 users.
nov. 05 08:54:19 papadou PackageKit[8635]: daemon quit
nov. 05 08:54:19 papadou systemd[1]: packagekit.service: Deactivated successfully.
My own KVM switch works differently. As I switched computers, screens are still there even though they don’t output anything, so I don’t get notifications.
You can disable this notification if that’s annoying.
Unfortunately, it crashed again this morning, here are the journal logs.
There are no core dumps generated, it just freezes the entire gui, no mouse or keyboard available.
Should I file a bug somewhere ?
Thanks,
nov. 12 07:32:16 papadou polkit-kde-authentication-agent-1[2701]: qt.qpa.wayland: There are no outputs - creating placeholder screen
nov. 12 07:32:16 papadou kded6[2625]: qt.qpa.wayland: There are no outputs - creating placeholder screen
nov. 12 07:32:16 papadou plasmashell[2656]: kde.plasmashell: requesting unexisting screen available rect -1
nov. 12 07:32:16 papadou kactivitymanagerd[2687]: qt.qpa.wayland: There are no outputs - creating placeholder screen
nov. 12 07:32:16 papadou DiscoverNotifier[2846]: qt.qpa.wayland: There are no outputs - creating placeholder screen
nov. 12 07:32:16 papadou konsole[3005]: qt.qpa.wayland: There are no outputs - creating placeholder screen
nov. 12 07:32:16 papadou kdeconnectd[2803]: qt.qpa.wayland: There are no outputs - creating placeholder screen
nov. 12 07:32:16 papadou dolphin[3003]: qt.qpa.wayland: There are no outputs - creating placeholder screen
nov. 12 07:32:16 papadou rclone-browser[3006]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
nov. 12 07:32:16 papadou xdg-desktop-portal-kde[3155]: qt.qpa.wayland: There are no outputs - creating placeholder screen
nov. 12 07:32:16 papadou krunner[16220]: qt.qpa.wayland: There are no outputs - creating placeholder screen
nov. 12 07:32:16 papadou libreoffice[16371]: qt.qpa.wayland: There are no outputs - creating placeholder screen
nov. 12 07:32:16 papadou baloorunner[16283]: qt.qpa.wayland: There are no outputs - creating placeholder screen
nov. 12 07:32:16 papadou plasma-discover[13869]: qt.qpa.wayland: There are no outputs - creating placeholder screen
nov. 12 07:32:16 papadou org_kde_powerdevil[2702]: qt.qpa.wayland: There are no outputs - creating placeholder screen
Report your kscreen-doctor -o and kinfo command line output.
The output for journalctl -t kwin_wayland would also be interesting.
The creating placeholder screen is normal business when there are no screens, few applications can de with it in practise so a fake screen is exposed to them, until a real screen is available again.
This happens with 25.10 but also with previous versions including LTS.