https://bugs.kde.org/show_bug.cgi?id=520274
--- Comment #3 from M3 <[email protected]> --- I have tested multiple different display settings (lowering resolution, refresh rate and bits per color), no color profile. The issue persists in all cases. After testing the display configurations, I tried to pinpoint the cause more precisely and found that the kernel continuously emits HOTPLUG events for the HDMI output even when no physical reconnection occurs. (The first KERNEL and UDEV logs it's me disconnecting the hdmi, the next one is me reconnecting the hdmi, the rest is the loop) > $ udevadm monitor > monitor will print the received events for: > UDEV - the event which udev sends out after rule processing > KERNEL - the kernel uevent > > KERNEL[2866.945752] change > /devices/pci0000:00/0000:00:03.1/0000:06:00.0/0000:07:00.0/0000:08:00.0/drm/card1 > (drm) > UDEV [2866.962143] change > /devices/pci0000:00/0000:00:03.1/0000:06:00.0/0000:07:00.0/0000:08:00.0/drm/card1 > (drm) > KERNEL[2874.743139] change > /devices/pci0000:00/0000:00:03.1/0000:06:00.0/0000:07:00.0/0000:08:00.0/drm/card1 > (drm) > UDEV [2874.757375] change > /devices/pci0000:00/0000:00:03.1/0000:06:00.0/0000:07:00.0/0000:08:00.0/drm/card1 > (drm) > KERNEL[2874.845821] change > /devices/pci0000:00/0000:00:03.1/0000:06:00.0/0000:07:00.0/0000:08:00.0/drm/card1 > (drm) > UDEV [2874.851117] change > /devices/pci0000:00/0000:00:03.1/0000:06:00.0/0000:07:00.0/0000:08:00.0/drm/card1 > (drm) > KERNEL[2875.571963] change > /devices/pci0000:00/0000:00:03.1/0000:06:00.0/0000:07:00.0/0000:08:00.0/drm/card1 > (drm) > UDEV [2875.577071] change > /devices/pci0000:00/0000:00:03.1/0000:06:00.0/0000:07:00.0/0000:08:00.0/drm/card1 > (drm) > KERNEL[2875.677900] change > /devices/pci0000:00/0000:00:03.1/0000:06:00.0/0000:07:00.0/0000:08:00.0/drm/card1 > (drm) > UDEV [2875.684554] change > /devices/pci0000:00/0000:00:03.1/0000:06:00.0/0000:07:00.0/0000:08:00.0/drm/card1 > (drm) > KERNEL[2876.402129] change > /devices/pci0000:00/0000:00:03.1/0000:06:00.0/0000:07:00.0/0000:08:00.0/drm/card1 > (drm) > UDEV [2876.406965] change > /devices/pci0000:00/0000:00:03.1/0000:06:00.0/0000:07:00.0/0000:08:00.0/drm/card1 > (drm) > KERNEL[2876.505902] change > /devices/pci0000:00/0000:00:03.1/0000:06:00.0/0000:07:00.0/0000:08:00.0/drm/card1 > (drm) > UDEV [2876.511412] change > /devices/pci0000:00/0000:00:03.1/0000:06:00.0/0000:07:00.0/0000:08:00.0/drm/card1 > (drm) > KERNEL[2877.231946] change > /devices/pci0000:00/0000:00:03.1/0000:06:00.0/0000:07:00.0/0000:08:00.0/drm/card1 > (drm) > UDEV [2877.236967] change > /devices/pci0000:00/0000:00:03.1/0000:06:00.0/0000:07:00.0/0000:08:00.0/drm/card1 > (drm) > KERNEL[2877.339233] change > /devices/pci0000:00/0000:00:03.1/0000:06:00.0/0000:07:00.0/0000:08:00.0/drm/card1 > (drm) > UDEV [2877.345656] change > /devices/pci0000:00/0000:00:03.1/0000:06:00.0/0000:07:00.0/0000:08:00.0/drm/card1 > (drm) > ... (This continues for however long I let it go before I press Ctrl+C or > disconnect the cable) This loop does not occur under GNOME Wayland on the same system, hardware and kernel. GNOME only emits the manual disconnect, the manual connect and 2 more additional events. The system is a clean, fresh install. So I don't think it's a configuration or anything like that that causes it to behave differently. -- You are receiving this mail because: You are watching all bug changes.
