Bug 494330 - Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
Summary: Infinite loop of disconnection/connection notification sounds when certain sc...
Status: CONFIRMED
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 6.2.0
Platform: Gentoo Packages Linux
: HI normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
: 495215 (view as bug list)
Depends on:
Blocks:
 
Reported: 2024-10-09 07:33 UTC by Julien Delquié
Modified: 2025-09-16 13:51 UTC (History)
22 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Julien Delquié 2024-10-09 07:33:58 UTC
SUMMARY
When screens go to sleep, there is a notification sound about screen being disconnected.
But after some seconds, a loop of notification sound about screen being disconnected/connected keeps looping like hell. 

Furthermore, even if I deactivate notification sound about devices disconnection/connection, it keeps playing it when issue happens, so no workaround at all except mute sound.
It’s really disturbing.

STEPS TO REPRODUCE
1. Wait for screens to go to sleep

OBSERVED RESULT
Infinite loop of disconnection/connection notification sound.

EXPECTED RESULT
No sound at all, or at least, just one disconnection notification sound when screens are disconnected, then just one connection notification sound when screens are connected.

SOFTWARE/OS VERSIONS
Operating System: Gentoo Linux 2.15
KDE Plasma Version: 6.2.0
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.3
Kernel Version: 6.11.2-gentoo-x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz
Memory: 31.3 Gio of RAM
Graphics Processor: AMD Radeon RX 7800 XT

ADDITIONAL INFORMATION
I had no issue prior to Plasma 6.2.0, it started with this version.
I don’t know where to have a look to search useful information to help more on this issue.
Comment 1 Nate Graham 2024-10-10 21:36:56 UTC
Is it possible the notification and sound are exposing an underlying hardware issue of one of the ends of the cables being loose? Maybe the monitor really does keep connecting and reconnecting because of a physical problem. Can you check it?
Comment 2 Julien Delquié 2024-10-10 22:10:05 UTC
(In reply to Nate Graham from comment #1)
> Is it possible the notification and sound are exposing an underlying
> hardware issue of one of the ends of the cables being loose? Maybe the
> monitor really does keep connecting and reconnecting because of a physical
> problem. Can you check it?

I think there is no underlying hardware issue, both my screens works visually perfectly well, each cables are well connected on both end.

What I can tell, is when the issue happen, when screen goes to sleep, I have plenty of messages in journalctl about this:

oct. 10 21:12:15 pasokon.maison org_kde_powerdevil[9588]: dh=Display_Handle[i2c-6: fd=130], Replacing adjusted sleep multiplier 0,00 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
oct. 10 21:12:17 pasokon.maison org_kde_powerdevil[9588]: dh=Display_Handle[i2c-8: fd=130], Replacing adjusted sleep multiplier 0,20 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
oct. 10 21:12:17 pasokon.maison org_kde_powerdevil[9588]: dh=Display_Handle[i2c-6: fd=130], Replacing adjusted sleep multiplier 0,00 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
oct. 10 21:12:24 pasokon.maison org_kde_powerdevil[9588]: dh=Display_Handle[i2c-6: fd=130], Replacing adjusted sleep multiplier 0,00 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
oct. 10 21:12:25 pasokon.maison org_kde_powerdevil[9588]: dh=Display_Handle[i2c-6: fd=130], Replacing adjusted sleep multiplier 0,00 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
oct. 10 21:12:25 pasokon.maison org_kde_powerdevil[9588]: dh=Display_Handle[i2c-8: fd=130], Replacing adjusted sleep multiplier 0,20 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
oct. 10 21:12:27 pasokon.maison org_kde_powerdevil[9588]: dh=Display_Handle[i2c-8: fd=130], Replacing adjusted sleep multiplier 0,20 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
oct. 10 21:12:27 pasokon.maison org_kde_powerdevil[9588]: dh=Display_Handle[i2c-6: fd=130], Replacing adjusted sleep multiplier 0,00 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS

And of course, nothing when the screen comes back from sleep.
Comment 3 Julien Delquié 2024-10-10 22:12:03 UTC
(In reply to Julien Delquié from comment #2)
> And of course, nothing when the screen comes back from sleep.

Also, the looping sounds stops as soon as the screen comes back from sleep.
Comment 4 Jakob Petsovits 2024-10-10 22:35:08 UTC
> oct. 10 21:12:15 pasokon.maison org_kde_powerdevil[9588]: dh=Display_Handle[i2c-6: fd=130], Replacing adjusted sleep multiplier 0,00 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
> ...

Those are libddcutil logs. This is not directly related to the notifications, because powerdevil/ddcutil don't play a notable part in the main connection/disconnection logic.

KWin is the component that directly reacts to display (un)plug events. Although it looks like the "Display Detected" / "Display Removed" notifications are issued by plasma-workspace/devicenotifications/devicenotifications.cpp in response to that. It would be a good idea to look at logs for plasma-kwin_wayland to see whether it also thinks the connection keeps changing. Might also make sense to check logs for plasma-plasmashell, although it probably won't say much without first enabling extra verbose log output. I don't know enough about these components off the top of my head to say which environment variables will yield the best logs.
Comment 5 Julien Delquié 2024-10-11 17:56:38 UTC
When the issue is happening (as I said, only when screens goes to sleep, no problem when they are awake), I can see thoses logs about kwin_wayland:

oct. 11 19:43:52 pasokon.maison kwin_wayland[169333]: kwin_core: KWin::LayerShellV1Window doesn't support setting maximized state
oct. 11 19:43:52 pasokon.maison kwin_wayland[169333]: kwin_core: KWin::LayerShellV1Window doesn't support setting fullscreen state
oct. 11 19:45:02 pasokon.maison kwin_wayland[169333]: kwin_core: KWin::LayerShellV1Window doesn't support setting maximized state
oct. 11 19:45:02 pasokon.maison kwin_wayland[169333]: kwin_core: KWin::LayerShellV1Window doesn't support setting fullscreen state
oct. 11 19:45:03 pasokon.maison kwin_wayland[169333]: kwin_core: KWin::LayerShellV1Window doesn't support setting maximized state
oct. 11 19:45:03 pasokon.maison kwin_wayland[169333]: kwin_core: KWin::LayerShellV1Window doesn't support setting fullscreen state
oct. 11 19:45:10 pasokon.maison kwin_wayland[169333]: kwin_core: KWin::LayerShellV1Window doesn't support setting maximized state
oct. 11 19:45:10 pasokon.maison kwin_wayland[169333]: kwin_core: KWin::LayerShellV1Window doesn't support setting fullscreen state
oct. 11 19:45:11 pasokon.maison kwin_wayland[169333]: kwin_core: KWin::LayerShellV1Window doesn't support setting maximized state
oct. 11 19:45:11 pasokon.maison kwin_wayland[169333]: kwin_core: KWin::LayerShellV1Window doesn't support setting fullscreen state
oct. 11 19:45:18 pasokon.maison kwin_wayland[169333]: kwin_core: KWin::LayerShellV1Window doesn't support setting maximized state
oct. 11 19:45:18 pasokon.maison kwin_wayland[169333]: kwin_core: KWin::LayerShellV1Window doesn't support setting fullscreen state
oct. 11 19:45:20 pasokon.maison kwin_wayland[169333]: kwin_core: KWin::LayerShellV1Window doesn't support setting maximized state
oct. 11 19:45:20 pasokon.maison kwin_wayland[169333]: kwin_core: KWin::LayerShellV1Window doesn't support setting fullscreen state

I can also see some firefox logs, but I don’t know if it is useful:

oct. 11 19:43:51 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4c720 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:43:51 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4f4a0 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:43:51 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4f7e0 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:43:51 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe96a9d6120 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:43:51 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe96a9d5420 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:43:51 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4c720 as subsurface because its parent is not mapped.
oct. 11 19:43:51 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4f4a0 as subsurface because its parent is not mapped.
oct. 11 19:43:51 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4f7e0 as subsurface because its parent is not mapped.
oct. 11 19:43:51 pasokon.maison firefox[170755]: Couldn't map window 0x7fe96a9d6120 as subsurface because its parent is not mapped.
oct. 11 19:43:51 pasokon.maison firefox[170755]: Couldn't map window 0x7fe96a9d5420 as subsurface because its parent is not mapped.
oct. 11 19:43:52 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4c720 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:43:52 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4f4a0 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:43:52 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4f7e0 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:43:52 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe96a9d6120 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:43:52 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe96a9d5420 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:43:52 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4c720 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:43:52 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4f4a0 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:43:52 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4f7e0 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:43:52 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe96a9d6120 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:43:52 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe96a9d5420 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:43:52 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4c720 as subsurface because its parent is not mapped.
oct. 11 19:43:52 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4f4a0 as subsurface because its parent is not mapped.
oct. 11 19:43:52 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4f7e0 as subsurface because its parent is not mapped.
oct. 11 19:43:52 pasokon.maison firefox[170755]: Couldn't map window 0x7fe96a9d6120 as subsurface because its parent is not mapped.
oct. 11 19:43:52 pasokon.maison firefox[170755]: Couldn't map window 0x7fe96a9d5420 as subsurface because its parent is not mapped.
oct. 11 19:43:52 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4c720 as subsurface because its parent is not mapped.
oct. 11 19:43:52 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4f4a0 as subsurface because its parent is not mapped.
oct. 11 19:43:52 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4f7e0 as subsurface because its parent is not mapped.
oct. 11 19:43:52 pasokon.maison firefox[170755]: Couldn't map window 0x7fe96a9d6120 as subsurface because its parent is not mapped.
oct. 11 19:43:52 pasokon.maison firefox[170755]: Couldn't map window 0x7fe96a9d5420 as subsurface because its parent is not mapped.
oct. 11 19:43:53 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:43:53 pasokon.maison firefox[170755]: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed
oct. 11 19:43:53 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:43:53 pasokon.maison firefox[170755]: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed
oct. 11 19:45:02 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4c720 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:02 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4f4a0 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:02 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4f7e0 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:02 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe96a9d6120 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:02 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe96a9d5420 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:02 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4c720 as subsurface because its parent is not mapped.
oct. 11 19:45:02 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4f4a0 as subsurface because its parent is not mapped.
oct. 11 19:45:02 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4f7e0 as subsurface because its parent is not mapped.
oct. 11 19:45:02 pasokon.maison firefox[170755]: Couldn't map window 0x7fe96a9d6120 as subsurface because its parent is not mapped.
oct. 11 19:45:02 pasokon.maison firefox[170755]: Couldn't map window 0x7fe96a9d5420 as subsurface because its parent is not mapped.
oct. 11 19:45:02 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:02 pasokon.maison firefox[170755]: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed
oct. 11 19:45:02 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:02 pasokon.maison firefox[170755]: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed
oct. 11 19:45:03 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4c720 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:03 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4f4a0 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:03 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4f7e0 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:03 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe96a9d6120 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:03 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe96a9d5420 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:03 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4c720 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:03 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4f4a0 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:03 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4f7e0 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:03 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe96a9d6120 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:03 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe96a9d5420 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:03 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4c720 as subsurface because its parent is not mapped.
oct. 11 19:45:03 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4f4a0 as subsurface because its parent is not mapped.
oct. 11 19:45:03 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4f7e0 as subsurface because its parent is not mapped.
oct. 11 19:45:03 pasokon.maison firefox[170755]: Couldn't map window 0x7fe96a9d6120 as subsurface because its parent is not mapped.
oct. 11 19:45:03 pasokon.maison firefox[170755]: Couldn't map window 0x7fe96a9d5420 as subsurface because its parent is not mapped.
oct. 11 19:45:03 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4c720 as subsurface because its parent is not mapped.
oct. 11 19:45:03 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4f4a0 as subsurface because its parent is not mapped.
oct. 11 19:45:03 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4f7e0 as subsurface because its parent is not mapped.
oct. 11 19:45:03 pasokon.maison firefox[170755]: Couldn't map window 0x7fe96a9d6120 as subsurface because its parent is not mapped.
oct. 11 19:45:03 pasokon.maison firefox[170755]: Couldn't map window 0x7fe96a9d5420 as subsurface because its parent is not mapped.
oct. 11 19:45:10 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4c720 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:10 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4f4a0 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:10 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4f7e0 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:10 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe96a9d6120 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:10 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe96a9d5420 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:10 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4c720 as subsurface because its parent is not mapped.
oct. 11 19:45:10 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4f4a0 as subsurface because its parent is not mapped.
oct. 11 19:45:10 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4f7e0 as subsurface because its parent is not mapped.
oct. 11 19:45:10 pasokon.maison firefox[170755]: Couldn't map window 0x7fe96a9d6120 as subsurface because its parent is not mapped.
oct. 11 19:45:10 pasokon.maison firefox[170755]: Couldn't map window 0x7fe96a9d5420 as subsurface because its parent is not mapped.
oct. 11 19:45:11 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4c720 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:11 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4f4a0 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:11 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4f7e0 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:11 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe96a9d6120 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:11 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe96a9d5420 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:11 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4c720 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:11 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4f4a0 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:11 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4f7e0 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:11 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4c720 as subsurface because its parent is not mapped.
oct. 11 19:45:11 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe96a9d6120 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:11 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe96a9d5420 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:11 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4f4a0 as subsurface because its parent is not mapped.
oct. 11 19:45:11 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4f7e0 as subsurface because its parent is not mapped.
oct. 11 19:45:11 pasokon.maison firefox[170755]: Couldn't map window 0x7fe96a9d6120 as subsurface because its parent is not mapped.
oct. 11 19:45:11 pasokon.maison firefox[170755]: Couldn't map window 0x7fe96a9d5420 as subsurface because its parent is not mapped.
oct. 11 19:45:11 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4c720 as subsurface because its parent is not mapped.
oct. 11 19:45:11 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4f4a0 as subsurface because its parent is not mapped.
oct. 11 19:45:11 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4f7e0 as subsurface because its parent is not mapped.
oct. 11 19:45:11 pasokon.maison firefox[170755]: Couldn't map window 0x7fe96a9d6120 as subsurface because its parent is not mapped.
oct. 11 19:45:11 pasokon.maison firefox[170755]: Couldn't map window 0x7fe96a9d5420 as subsurface because its parent is not mapped.
oct. 11 19:45:18 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4c720 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:18 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4f4a0 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:18 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4f7e0 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:18 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe96a9d6120 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:18 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe96a9d5420 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:18 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4c720 as subsurface because its parent is not mapped.
oct. 11 19:45:18 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4f4a0 as subsurface because its parent is not mapped.
oct. 11 19:45:18 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4f7e0 as subsurface because its parent is not mapped.
oct. 11 19:45:18 pasokon.maison firefox[170755]: Couldn't map window 0x7fe96a9d6120 as subsurface because its parent is not mapped.
oct. 11 19:45:18 pasokon.maison firefox[170755]: Couldn't map window 0x7fe96a9d5420 as subsurface because its parent is not mapped.
oct. 11 19:45:20 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4c720 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:20 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4f4a0 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:20 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4f7e0 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:20 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe96a9d6120 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:20 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe96a9d5420 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:20 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4c720 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:20 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4f4a0 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:20 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe979f4f7e0 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:20 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4c720 as subsurface because its parent is not mapped.
oct. 11 19:45:20 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe96a9d6120 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:20 pasokon.maison firefox[170755]: [Parent 170755, Main Thread] WARNING: Couldn't map window 0x7fe96a9d5420 as subsurface because its parent is not mapped.: 'glib warning', file /var/tmp/portage/www-client/firefox-131.0.2/work/firefox-131.0.2/toolkit/xre/nsSigHandlers.cpp:187
oct. 11 19:45:20 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4f4a0 as subsurface because its parent is not mapped.
oct. 11 19:45:20 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4f7e0 as subsurface because its parent is not mapped.
oct. 11 19:45:20 pasokon.maison firefox[170755]: Couldn't map window 0x7fe96a9d6120 as subsurface because its parent is not mapped.
oct. 11 19:45:20 pasokon.maison firefox[170755]: Couldn't map window 0x7fe96a9d5420 as subsurface because its parent is not mapped.
oct. 11 19:45:20 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4c720 as subsurface because its parent is not mapped.
oct. 11 19:45:20 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4f4a0 as subsurface because its parent is not mapped.
oct. 11 19:45:20 pasokon.maison firefox[170755]: Couldn't map window 0x7fe979f4f7e0 as subsurface because its parent is not mapped.
oct. 11 19:45:20 pasokon.maison firefox[170755]: Couldn't map window 0x7fe96a9d6120 as subsurface because its parent is not mapped.
oct. 11 19:45:20 pasokon.maison firefox[170755]: Couldn't map window 0x7fe96a9d5420 as subsurface because its parent is not mapped.

I can also see something about kde6 and pulseaudio (I use pipewire actually):

oct. 11 19:43:40 pasokon.maison kded6[169513]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
oct. 11 19:43:52 pasokon.maison kded6[169513]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
oct. 11 19:44:51 pasokon.maison kded6[169513]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
oct. 11 19:45:21 pasokon.maison kded6[169513]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"

Same things with plasmashell:

oct. 11 19:43:40 pasokon.maison plasmashell[169577]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
oct. 11 19:43:53 pasokon.maison plasmashell[169577]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
oct. 11 19:44:51 pasokon.maison plasmashell[169577]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
oct. 11 19:45:21 pasokon.maison plasmashell[169577]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"

Same thing with kdeconnectd:

oct. 11 19:43:40 pasokon.maison kdeconnectd[169923]: 2024-10-11T19:43:40 org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
oct. 11 19:43:52 pasokon.maison kdeconnectd[169923]: 2024-10-11T19:43:52 org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
oct. 11 19:44:51 pasokon.maison kdeconnectd[169923]: 2024-10-11T19:44:51 org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
oct. 11 19:45:21 pasokon.maison kdeconnectd[169923]: 2024-10-11T19:45:21 org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"

And… I don’t know where or what else to look.
Comment 6 Jakob Petsovits 2024-10-11 20:34:14 UTC
Thanks. Let's set this back to REPORTED and see if the KWin devs have any thoughts on it.
Comment 7 Zamundaaa 2024-10-23 14:52:50 UTC
How often does the sound play? Like every few seconds?
Comment 8 Julien Delquié 2024-10-23 15:27:35 UTC
(In reply to Zamundaaa from comment #7)
> How often does the sound play? Like every few seconds?

I would say :
- 1 second between disconnection sound and connection sound,
- 5 seconds between connection sound and disconnection sound.

This, in loop, until I wake up screens.
Comment 9 Zamundaaa 2024-10-23 15:38:35 UTC
Okay, that definitely sounds like the screen and/or GPU driver are doing funny things. It doesn't affect KWin directly, because it has a workaround for screens that do such nonsense (https://invent.kde.org/plasma/kwin/-/merge_requests/2940) but the device notifier doesn't have that.
Comment 10 Julien Delquié 2024-10-23 16:17:27 UTC
In case these information are useful, here are my screens (I removed the serial numbers and binary serial numbers):

$ ddcutil detect
Display 1
   I2C bus:  /dev/i2c-6
   DRM connector:           card0-HDMI-A-1
   EDID synopsis:
      Mfg id:               AUS - UNK
      Model:                VZ249
      Product code:         9420  (0x24cc)
      Serial number:        
      Binary serial number: 
      Manufacture year:     2019,  Week: 12
   VCP version:         2.1

Display 2
   I2C bus:  /dev/i2c-8
   DRM connector:           card0-DP-2
   EDID synopsis:
      Mfg id:               AUS - UNK
      Model:                VG249QM1A
      Product code:         9263  (0x242f)
      Serial number:        
      Binary serial number: 
      Manufacture year:     2023,  Week: 33
   VCP version:         2.2

The DisplayPort screen is my primary screen (on the right), and the HDMI screen is my secondary screen (on the left)
Comment 11 sebi.loew 2024-10-26 10:34:56 UTC
I can confirm this bug since plasma 6.2 (now also with 6.2.2) with fedora 40.
No chance for my monitors that they go to sleep. Only workaround is to use standby every time I leave my pc.
Doesn't matter if it is the lockscreen or normal desktop.

Before plasma 6.2 I never encountered this bug. Hardware didn`t change.
Comment 12 Metz 2024-10-27 12:08:42 UTC
I can confirm this behavior. When my 3 displays go to standby its starts with a disconnect / connect loop. it is relatively inconsistent when the problem gets triggered. but i just tested with a 60 second timeout and got this:


Okt 27 12:42:00 x570 kded6[1458]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_0e_00.4.analog-stereo.monitor"
Okt 27 12:42:00 x570 plasmashell[2958]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_0e_00.4.analog-stereo.monitor"
Okt 27 12:42:00 x570 kded6[1458]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_0e_00.4.analog-stereo.monitor"
Okt 27 12:42:00 x570 kded6[1458]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_0e_00.4.analog-stereo.monitor"
Okt 27 12:42:00 x570 kernel: amdgpu 0000:0c:00.0: [drm] REG_WAIT timeout 1us * 100 tries - dcn32_program_compbuf_size line:140
Okt 27 12:42:01 x570 kded6[1458]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_0e_00.4.analog-stereo.monitor"
Okt 27 12:42:01 x570 kded6[1458]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_0e_00.4.analog-stereo.monitor"
Okt 27 12:42:01 x570 kded6[1458]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_0e_00.4.analog-stereo.monitor"
Okt 27 12:42:01 x570 kded6[1458]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_0e_00.4.analog-stereo.monitor"
Okt 27 12:42:01 x570 kded6[1458]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_0e_00.4.analog-stereo.monitor"
Okt 27 12:42:01 x570 kded6[1458]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_0e_00.4.analog-stereo.monitor"
Okt 27 12:42:01 x570 kded6[1458]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_0e_00.4.analog-stereo.monitor"
Okt 27 12:42:01 x570 kded6[1458]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_0e_00.4.analog-stereo.monitor"
Okt 27 12:42:01 x570 org_kde_powerdevil[1574]: Sleep event. connector=card1-DP-1, dref not set
Okt 27 12:42:03 x570 org_kde_powerdevil[1574]: Emitting DDCA_Display_Status_Event( 3160.632:  DDCA_EVENT_DPMS_ASLEEP, card1-DP-1, dref: Display_Ref[NULL], io_path:/dev/i2c-6]
Okt 27 12:42:03 x570 org_kde_powerdevil[1574]: Executed 1 registered callbacks.
Okt 27 12:42:03 x570 org_kde_powerdevil[1574]: Emitting DDCA_Display_Status_Event( 3160.632:  DDCA_EVENT_DPMS_ASLEEP, card1-DP-3, dref: Display_Ref[bus /dev/i2c-8], io_path:/dev/i2c-8]
Okt 27 12:42:03 x570 org_kde_powerdevil[1574]: Executed 1 registered callbacks.
Okt 27 12:42:03 x570 org_kde_powerdevil[1574]: Emitting DDCA_Display_Status_Event( 3160.632:  DDCA_EVENT_DPMS_ASLEEP, card1-HDMI-A-1, dref: Display_Ref[bus /dev/i2c-5], io_path:/dev/i2c-5]
Okt 27 12:42:03 x570 org_kde_powerdevil[1574]: Executed 1 registered callbacks.
Okt 27 12:42:09 x570 org_kde_powerdevil[1574]: Delaying 6 seconds to avoid a false disconnect/connect sequence...
Okt 27 12:42:16 x570 org_kde_powerdevil[1574]: DRM connectors with newly disconnected displays: card1-HDMI-A-1
Okt 27 12:42:16 x570 org_kde_powerdevil[1574]: Removing connected display, drm_connector: card1-HDMI-A-1, dref Display_Ref[bus /dev/i2c-5]
Okt 27 12:42:18 x570 org_kde_powerdevil[1574]: Emitting DDCA_Display_Status_Event( 3175.638:  DDCA_EVENT_DISPLAY_DISCONNECTED, card1-HDMI-A-1, dref: Display_Ref[bus /dev/i2c-5], io_path:/dev/i2c-5]
Okt 27 12:42:18 x570 org_kde_powerdevil[1574]: Executed 1 registered callbacks.
Okt 27 12:42:21 x570 org_kde_powerdevil[1574]: Emitting DDCA_Display_Status_Event( 3178.639:  DDCA_EVENT_DISPLAY_CONNECTED, card1-HDMI-A-1, dref: Display_Ref[NULL], io_path:/dev/i2c-5]
Okt 27 12:42:21 x570 org_kde_powerdevil[1574]: Executed 1 registered callbacks.
Okt 27 12:42:21 x570 org_kde_powerdevil[1574]: Sleep event. connector=card1-HDMI-A-1, dref not set
Okt 27 12:42:21 x570 org_kde_powerdevil[1574]: Display redetection starting.
Okt 27 12:42:21 x570 org_kde_powerdevil[1574]: Emitting DDCA_Display_Status_Event( 3180.640:  DDCA_EVENT_DPMS_ASLEEP, card1-HDMI-A-1, dref: Display_Ref[NULL], io_path:/dev/i2c-5]
Okt 27 12:42:21 x570 org_kde_powerdevil[1574]: Executed 1 registered callbacks.
Okt 27 12:42:21 x570 org_kde_powerdevil[1574]: Watch thread terminated.
Okt 27 12:42:21 x570 org_kde_powerdevil[1574]: busno=5, sleep-multiplier =  0,20. Testing for supported feature 0x10 returned Error_Info[DDCRC_DPMS_ASLEEP in ddc_write_read_with_retry, causes: EIO]
Okt 27 12:42:21 x570 org_kde_powerdevil[1574]: busno=8, sleep-multiplier =  2,00. Testing for supported feature 0x10 returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: EREMOTEIO(10)]
Okt 27 12:42:21 x570 org_kde_powerdevil[1574]: busno=8, sleep-multiplier= 1,00.Retesting for supported feature 0x10 returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: EREMOTEIO(10)]
Okt 27 12:42:23 x570 org_kde_powerdevil[1574]: busno=6, sleep-multiplier =  2,00. Testing for supported feature 0x10 returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: ETIMEDOUT(10)]
Okt 27 12:42:23 x570 org_kde_powerdevil[1574]: Watch thread started
Okt 27 12:42:23 x570 org_kde_powerdevil[1574]: Display redetection finished.
Okt 27 12:42:26 x570 kded6[1458]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_0e_00.4.analog-stereo.monitor"
Okt 27 12:42:26 x570 plasmashell[2958]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_0e_00.4.analog-stereo.monitor"
Okt 27 12:42:36 x570 rtkit-daemon[1349]: Supervising 7 threads of 4 processes of 1 users.
Okt 27 12:42:36 x570 rtkit-daemon[1349]: Supervising 7 threads of 4 processes of 1 users.

So my suspicion was that pulseaudio detects the HDMI audio device of one of my 3 dispalys over and over again for some reason. so i disabled only this display and at first nothing happened. but after powering it back up i got the disconnect/connect sound again and this:

Okt 27 13:06:43 x570 kded6[1458]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_0e_00.4.analog-stereo.monitor"
Okt 27 13:06:43 x570 plasmashell[2958]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_0e_00.4.analog-stereo.monitor"
Okt 27 13:06:43 x570 firefox[8408]: [Parent 8408, Main Thread] WARNING: Couldn't map window 0x7a26934d2ae0 as subsurface because its parent is not mapped.: 'glib warning', file /usr/src/debug/firefox/firefox-131.0.3/toolkit/xre/nsSigHandlers.cpp:187
Okt 27 13:06:43 x570 firefox[8408]: [Parent 8408, Main Thread] WARNING: Couldn't map window 0x7a2693bb52c0 as subsurface because its parent is not mapped.: 'glib warning', file /usr/src/debug/firefox/firefox-131.0.3/toolkit/xre/nsSigHandlers.cpp:187
Okt 27 13:06:43 x570 firefox[8408]: [Parent 8408, Main Thread] WARNING: Couldn't map window 0x7a26934d2ae0 as subsurface because its parent is not mapped.: 'glib warning', file /usr/src/debug/firefox/firefox-131.0.3/toolkit/xre/nsSigHandlers.cpp:187
Okt 27 13:06:43 x570 firefox[8408]: [Parent 8408, Main Thread] WARNING: Couldn't map window 0x7a2693bb52c0 as subsurface because its parent is not mapped.: 'glib warning', file /usr/src/debug/firefox/firefox-131.0.3/toolkit/xre/nsSigHandlers.cpp:187
Okt 27 13:06:43 x570 firefox[8408]: Couldn't map window 0x7a26934d2ae0 as subsurface because its parent is not mapped.
Okt 27 13:06:43 x570 firefox[8408]: Couldn't map window 0x7a2693bb52c0 as subsurface because its parent is not mapped.
Okt 27 13:06:43 x570 firefox[8408]: Couldn't map window 0x7a26934d2ae0 as subsurface because its parent is not mapped.
Okt 27 13:06:43 x570 firefox[8408]: Couldn't map window 0x7a2693bb52c0 as subsurface because its parent is not mapped.
Okt 27 13:06:43 x570 systemsettings[11600]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_0e_00.4.analog-stereo.monitor"
Okt 27 13:06:44 x570 org_kde_powerdevil[1574]: Sleep event. connector=card1-HDMI-A-1, dref not set
Okt 27 13:06:44 x570 org_kde_powerdevil[1574]: Delaying 6 seconds to avoid a false disconnect/connect sequence...
Okt 27 13:06:44 x570 firefox[8408]: [Parent 8408, Main Thread] WARNING: Couldn't map window 0x7a26934d2ae0 as subsurface because its parent is not mapped.: 'glib warning', file /usr/src/debug/firefox/firefox-131.0.3/toolkit/xre/nsSigHandlers.cpp:187
Okt 27 13:06:44 x570 firefox[8408]: [Parent 8408, Main Thread] WARNING: Couldn't map window 0x7a2693bb52c0 as subsurface because its parent is not mapped.: 'glib warning', file /usr/src/debug/firefox/firefox-131.0.3/toolkit/xre/nsSigHandlers.cpp:187
Okt 27 13:06:44 x570 firefox[8408]: Couldn't map window 0x7a26934d2ae0 as subsurface because its parent is not mapped.
Okt 27 13:06:44 x570 firefox[8408]: Couldn't map window 0x7a2693bb52c0 as subsurface because its parent is not mapped.
Okt 27 13:06:44 x570 firefox[8408]: [Parent 8408, Main Thread] WARNING: Couldn't map window 0x7a26934d2ae0 as subsurface because its parent is not mapped.: 'glib warning', file /usr/src/debug/firefox/firefox-131.0.3/toolkit/xre/nsSigHandlers.cpp:187
Okt 27 13:06:44 x570 firefox[8408]: [Parent 8408, Main Thread] WARNING: Couldn't map window 0x7a2693bb52c0 as subsurface because its parent is not mapped.: 'glib warning', file /usr/src/debug/firefox/firefox-131.0.3/toolkit/xre/nsSigHandlers.cpp:187
Okt 27 13:06:44 x570 firefox[8408]: Couldn't map window 0x7a26934d2ae0 as subsurface because its parent is not mapped.
Okt 27 13:06:44 x570 firefox[8408]: Couldn't map window 0x7a2693bb52c0 as subsurface because its parent is not mapped.
Okt 27 13:06:44 x570 firefox[8408]: [Parent 8408, Main Thread] WARNING: Couldn't map window 0x7a26934d2ae0 as subsurface because its parent is not mapped.: 'glib warning', file /usr/src/debug/firefox/firefox-131.0.3/toolkit/xre/nsSigHandlers.cpp:187
Okt 27 13:06:44 x570 firefox[8408]: [Parent 8408, Main Thread] WARNING: Couldn't map window 0x7a2693bb52c0 as subsurface because its parent is not mapped.: 'glib warning', file /usr/src/debug/firefox/firefox-131.0.3/toolkit/xre/nsSigHandlers.cpp:187
Okt 27 13:06:44 x570 firefox[8408]: Couldn't map window 0x7a26934d2ae0 as subsurface because its parent is not mapped.
Okt 27 13:06:44 x570 firefox[8408]: Couldn't map window 0x7a2693bb52c0 as subsurface because its parent is not mapped.
Okt 27 13:06:44 x570 systemsettings[11600]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_0e_00.4.analog-stereo.monitor"
Okt 27 13:06:44 x570 systemsettings[11600]: qrc:/kcm/kcm_pulseaudio/CardListItem.qml:16:5: TypeError: Cannot read property 'width' of null
Okt 27 13:06:44 x570 kded6[1458]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_0e_00.4.analog-stereo.monitor"
Okt 27 13:06:45 x570 plasmashell[2958]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_0e_00.4.analog-stereo.monitor"
Okt 27 13:06:52 x570 org_kde_powerdevil[1574]: stabilized_connector_names required 1 extra calls to get_sysfs_drm_connector_names()

So yeah, i would say that is more a pulseaudio problem.
Comment 13 Julien Delquié 2024-10-27 12:16:02 UTC
On my side, I use PipeWire.
The screen using HDMI has no audio options.
The screen using DisplayPort has audio options, but muted.
Comment 14 Metz 2024-10-27 12:35:14 UTC
Yeah i had to check. I'm on EndeavourOS (arch) and it is using Pipewire as well but with pipewire-pulse as drop-in replacement for native Pulseaudio. so its Pulseaudio on top of Pipewire if i understand this correctly.

in the Sound System Settings i got

Line Out = Analog Stereo Output. Which is my normal soundcard with speakers.
and
Navi 31 HDMI/DP Audio set to Off. I have 3 other options there. "HDMI", "HDMI 4" and "Pro Audio"

I just thought i had a eureka moment because it only triggered the problem when set to "off" and not when set to "HDMI" but now it does that as well again. it is very inconsistent. i have to do more tests.
Comment 15 Zamundaaa 2024-10-28 15:55:54 UTC
(In reply to sebi.loew from comment #11)
> I can confirm this bug since plasma 6.2 (now also with 6.2.2) with fedora 40.
> No chance for my monitors that they go to sleep. Only workaround is to use
> standby every time I leave my pc.
> Doesn't matter if it is the lockscreen or normal desktop.
> 
> Before plasma 6.2 I never encountered this bug. Hardware didn`t change.
The problem of constant connection/disconnections was almost certainly already there before; it's only now made visible (or rather audible) by Plasma 6.2 making a sound when it happens.
Ideally we'd fix the underlying issue of course, but that hasn't happened in the past two decades, so I wouldn't wait for that. I think the device notifier just needs the same workaround as KWin has.
Comment 16 sebi.loew 2024-10-29 10:35:40 UTC
(In reply to Zamundaaa from comment #15)
> (In reply to sebi.loew from comment #11)
> > I can confirm this bug since plasma 6.2 (now also with 6.2.2) with fedora 40.
> > No chance for my monitors that they go to sleep. Only workaround is to use
> > standby every time I leave my pc.
> > Doesn't matter if it is the lockscreen or normal desktop.
> > 
> > Before plasma 6.2 I never encountered this bug. Hardware didn`t change.
> The problem of constant connection/disconnections was almost certainly
> already there before; it's only now made visible (or rather audible) by
> Plasma 6.2 making a sound when it happens.
> Ideally we'd fix the underlying issue of course, but that hasn't happened in
> the past two decades, so I wouldn't wait for that. I think the device
> notifier just needs the same workaround as KWin has.

But does the notifier also ensure that my screen no longer goes into standby mode? It's not just the sound; the monitor also briefly becomes brighter (without displaying an image) and then goes dark again, and so on. This definitely wasn’t happening before—back then, the monitor would go into power-saving mode.
Comment 17 major-mayer 2024-11-26 17:21:40 UTC
(In reply to sebi.loew from comment #16)
> (In reply to Zamundaaa from comment #15)
> > (In reply to sebi.loew from comment #11)
> > > I can confirm this bug since plasma 6.2 (now also with 6.2.2) with fedora 40.
> > > No chance for my monitors that they go to sleep. Only workaround is to use
> > > standby every time I leave my pc.
> > > Doesn't matter if it is the lockscreen or normal desktop.
> > > 
> > > Before plasma 6.2 I never encountered this bug. Hardware didn`t change.
> > The problem of constant connection/disconnections was almost certainly
> > already there before; it's only now made visible (or rather audible) by
> > Plasma 6.2 making a sound when it happens.
> > Ideally we'd fix the underlying issue of course, but that hasn't happened in
> > the past two decades, so I wouldn't wait for that. I think the device
> > notifier just needs the same workaround as KWin has.
> 
> But does the notifier also ensure that my screen no longer goes into standby
> mode? It's not just the sound; the monitor also briefly becomes brighter
> (without displaying an image) and then goes dark again, and so on. This
> definitely wasn’t happening before—back then, the monitor would go into
> power-saving mode.

Same problem here on Manjaro Unstable, but in my case both displays don't become brighter when the notification sound appears.
The first one is connected via HDMI and has no speakers, while the second one is connected via DisplayPort and has the speakers turned off (in Plasma and the display itself).

Operating System: Manjaro Linux rolling
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.12.1-4-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 6 × Intel® Core™ i5-8600K CPU @ 3.60GHz
Memory: 31.2 GiB of RAM
Graphics Processor: AMD Radeon RX 6800 (DP/ HDMI Connection) + Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630] (not connected)
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7B46
System Version: 1.0
Comment 18 TraceyC 2024-11-27 17:52:09 UTC
*** Bug 495215 has been marked as a duplicate of this bug. ***
Comment 19 Julien Delquié 2024-11-27 18:50:13 UTC
I found something interesting, If I turn off (with its button) my DisplayPort Screen, the infinite loop sounds stop.
As a reminder, my other screen uses HDMI.

And of course, if I switch on my DisplayPort Screen, the infinite loop sounds start again.
Comment 20 sebi.loew 2025-01-04 13:54:08 UTC
Does anyone have an idea how to fix it or knows a workaround? Screen sleep was an function I was using all day long always before and now it doesn`t work anymore. Other than that plasma works so great for me right now, would love to have a fix for this.
Comment 21 biscuits196+kde 2025-01-19 03:08:53 UTC
Sorry to bump; I can confirm this problem still happens on Fedora 41, Plasma 6.2.5. I have a dual DisplayPort/HDMI monitor setup like some other folks here. I used to experience a similar bug where the screens would awake soon after entering sleep mode; this was promptly fixed, but this new behavior took its place.

The timing is also pretty similar; a short delay, then a disconnect->reconnect sequence, then the delay again, on repeat. I've taken to disabling my speakers every lock because of it :P

SOFTWARE/OS VERSIONS
Operating System: Fedora Kinoite 41
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1
Kernel Version: 6.12.9-200.fc41.x86_64
Graphics Platform: Wayland
Graphics Processor: AMD Radeon RX 6600 XT

MONITORS (ddcutil)
Display 1
   I2C bus:  /dev/i2c-5
   DRM connector:           card1-HDMI-A-1
   EDID synopsis:
      Mfg id:               ACR - Acer Technologies
      Model:                Acer H226HQL
      Product code:         793  (0x0319)
      Serial number:        [removed]
      Binary serial number: [removed]
      Manufacture year:     2015,  Week: 32
   VCP version:         2.1

Display 2
   I2C bus:  /dev/i2c-6
   DRM connector:           card1-DP-1
   EDID synopsis:
      Mfg id:               GSM - Goldstar Company Ltd (LG)
      Model:                LG ULTRAGEAR
      Product code:         23476  (0x5bb4)
      Serial number:        [removed]
      Binary serial number: [removed]
      Manufacture year:     2021,  Week: 1
   VCP version:         2.1
Comment 22 Metz 2025-01-19 10:40:18 UTC
I'm pretty sure the problem was gone. It is back now. Unfortunately hard to exactly pinpoint the update that brought it back but must have been the last 1 or 2 versions on Arch. I can also confirm that it is only 1 of my 3 monitor that causes the trouble. One with DVI connected to an DP adapter. If i power it down completely, the problem does not appear. 

It makes using standby right now basically impossible unless i either power off my speaker or this one monitor every time. 

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS (Arch)
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1
Kernel Version: 6.12.9-arch1-1
Graphics Platform: Wayland
Processors: AMD Ryzen 7 3700X
Memory: 31.27 GiB
Graphics Processor: AMD Radeon RX 7800 XT
Comment 23 major-mayer 2025-02-04 18:09:48 UTC
Any chance that this will get fixed or worked-around anytime soon?
This is a really annoying problem that persists in my case since November 2024... 

It would be great if at least the workaround from Kwin could be applied to the "device notifier" (as Zamundaaa suggested).
I would be happy to test if this helps with the problem.

Operating System: Manjaro Linux 
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.2
Kernel Version: 6.12.12-2-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 6 × Intel® Core™ i5-8600K CPU @ 3.60GHz
Memory: 31.2 GiB of RAM
Graphics Processor: AMD Radeon RX 6800
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7B46
System Version: 1.0
Comment 24 Oliver 2025-02-17 22:20:16 UTC
I have recently done a clean install and experience this behaviour. I had this problem a few months ago but I muted system sounds and forgot about it. I came across this bug report while looking for a solution so I shall post some information about my setup.

Operating System: CachyOS Linux 
KDE Plasma Version: 6.3.0
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.14.0-rc2-2-cachyos-rc-gcc (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: AMD Radeon RX 7800 XT
Display (DP) MSI G322CQP

I get a back-to-back disconnect reconnect sounds and these occur roughly seven seconds apart. This is one loop:

Feb 17 21:57:37 cachyos-x8664 xdg-desktop-portal-kde[2211]: qt.qpa.wayland: There are no outputs - creating placeholder screen
Feb 17 21:57:37 cachyos-x8664 plasmashell[2162]: kde.plasmashell: requesting unexisting screen available rect -1
Feb 17 21:57:37 cachyos-x8664 plasmashell[2162]: kde.plasmashell: requesting unexisting screen available rect -1
Feb 17 21:57:37 cachyos-x8664 plasmashell[2162]: kde.plasmashell: requesting unexisting screen available rect -1
Feb 17 21:57:37 cachyos-x8664 plasmashell[2162]: kde.plasmashell: requesting unexisting screen available rect -1
Feb 17 21:57:37 cachyos-x8664 plasmashell[2162]: qt.qpa.wayland: There are no outputs - creating placeholder screen
Feb 17 21:57:38 cachyos-x8664 firefox[3710]: [Parent 3710, Main Thread] WARNING: Couldn't map window 0x76bcc2491420 as subsurface because its parent is not mapped.: 'glib warning', file /tmp/pkg/src/mozilla-unified/toolkit/xre/nsSigHandlers.cpp:201
Feb 17 21:57:38 cachyos-x8664 firefox[3710]: Couldn't map window 0x76bcc2491420 as subsurface because its parent is not mapped.
Feb 17 21:57:38 cachyos-x8664 firefox[3710]: [Parent 3710, Main Thread] WARNING: Couldn't map window 0x76bcc2491420 as subsurface because its parent is not mapped.: 'glib warning', file /tmp/pkg/src/mozilla-unified/toolkit/xre/nsSigHandlers.cpp:201
Feb 17 21:57:38 cachyos-x8664 firefox[3710]: Couldn't map window 0x76bcc2491420 as subsurface because its parent is not mapped.
Feb 17 21:57:45 cachyos-x8664 kwalletd6[1504]: qt.qpa.wayland: There are no outputs - creating placeholder screen
Feb 17 21:57:45 cachyos-x8664 kactivitymanagerd[2204]: qt.qpa.wayland: There are no outputs - creating placeholder screen
Feb 17 21:57:45 cachyos-x8664 kded6[2044]: qt.qpa.wayland: There are no outputs - creating placeholder screen
Feb 17 21:57:45 cachyos-x8664 firefox[3710]: [Parent 3710, Main Thread] WARNING: Couldn't map window 0x76bcc2491420 as subsurface because its parent is not mapped.: 'glib warning', file /tmp/pkg/src/mozilla-unified/toolkit/xre/nsSigHandlers.cpp:201
Feb 17 21:57:45 cachyos-x8664 polkit-kde-authentication-agent-1[2209]: qt.qpa.wayland: There are no outputs - creating placeholder screen
Feb 17 21:57:45 cachyos-x8664 kdeconnectd[2483]: 2025-02-17T21:57:45 qt.qpa.wayland: There are no outputs - creating placeholder screen
Feb 17 21:57:45 cachyos-x8664 openrgb[2566]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Feb 17 21:57:45 cachyos-x8664 keepassxc[2565]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Feb 17 21:57:45 cachyos-x8664 baloorunner[3692]: qt.qpa.wayland: There are no outputs - creating placeholder screen
Feb 17 21:57:45 cachyos-x8664 org_kde_powerdevil[2210]: qt.qpa.wayland: There are no outputs - creating placeholder screen
Feb 17 21:57:45 cachyos-x8664 firefox[3710]: Couldn't map window 0x76bcc2491420 as subsurface because its parent is not mapped.
Feb 17 21:57:45 cachyos-x8664 kscreenlocker_greet[5229]: qt.qpa.wayland: There are no outputs - creating placeholder screen
Feb 17 21:57:45 cachyos-x8664 plasmashell[2162]: kde.plasmashell: requesting unexisting screen available rect -1
Comment 25 Julien Delquié 2025-07-11 16:02:24 UTC
Since my last update, I do not have this infinite loop bug… but another one!

Both screens goes to sleep, then the sound of disconnected/connected happen, then only DP screen turns on and stays on indefinitely (the HDMI one stays sleeping indefinitely).

Anyone here faces this new strange behavior?

Operating System: Gentoo Linux 2.17
KDE Plasma Version: 6.4.2
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1
Kernel Version: 6.15.5-gentoo-dist (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz
Memory: 32 Gio of RAM (31.3 Gio usable)
Graphics Processor: AMD Radeon RX 7800 XT
Comment 26 Julien Delquié 2025-07-16 12:03:21 UTC
After updating again, this bug is back.

Operating System: Gentoo Linux 2.17
KDE Plasma Version: 6.4.3
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Kernel Version: 6.15.6-gentoo-dist (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz
Memory: 32 Gio of RAM (31.3 Gio usable)
Graphics Processor: AMD Radeon RX 7800 XT
Comment 27 mock 2025-07-22 03:40:26 UTC
Using KDE here in CatchyOS and also Bazzite and can indeed confirm. Sound of disconnect/connect loops infinitely when monitors sleep.
Comment 28 Xico26 2025-07-25 09:33:08 UTC
Hello. I can confirm this issue also happens on a fresh install of Fedora 42 KDE, and does not happen on other DEs like Gnome and Cinnamon. However, I don't get an infinite loop, the loop only repeats once (so, in total, I get 4 sounds).

Operating System: Fedora Linux 42
KDE Plasma Version: 6.4.3
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Kernel Version: 6.15.7-200.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700X3D 8-Core Processor
Memory: 16 GiB of RAM (15,5 GiB usable)
Graphics Processor: AMD Radeon RX 6700 XT
Manufacturer: ASUS
Comment 29 TraceyC 2025-07-25 18:17:00 UTC
Bumping priority since so many people are affected.
Comment 30 Julien Delquié 2025-07-27 15:33:43 UTC
Also, I found something interesting, when this infinite loop happen, sometimes, the DP screen is turned on and keeps turned on, with a really small resolution (like maybe 640x400), and if I unlock session at this moment, it keeps that resolution and I can’t change it back to 1920x1080. The workaround is to press esc twice when locked to dim all screen, wait a little and press esc again to un-dim screens, sometimes it works sometimes not. But when it works, after unlock session, any X applications using Xwayland is not able to run (xrandr, Steam, Wine, etc.). The reason is the following:
$ xrandr 
Maximum number of clients reached
Can't open display :0

But, if I perform a simple « systemctl --user restart plasma-powerdevil.service »
Then:
$ xrandr 
Screen 0: minimum 16 x 16, current 3840 x 1080, maximum 32767 x 32767
HDMI-A-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 527mm x 296mm
   1920x1080     59.96*+
   1440x1080     59.99  
   1400x1050     59.98  
   1280x1024     59.89  
   1280x960      59.94  
   1152x864      59.96  
   1024x768      59.92  
   800x600       59.86  
   640x480       59.38  
   320x240       59.29  
   1680x1050     59.95  
   1440x900      59.89  
   1280x800      59.81  
   1152x720      59.97  
   960x600       59.63  
   928x580       59.88  
   800x500       59.50  
   768x480       59.90  
   720x480       59.71  
   640x400       59.95  
   320x200       58.14  
   1600x900      59.95  
   1368x768      59.88  
   1280x720      59.86  
   1024x576      59.90  
   864x486       59.92  
   720x400       59.27  
   640x350       59.28  
DP-2 connected primary 1920x1080+1920+0 (normal left inverted right x axis y axis) 527mm x 296mm
   1920x1080    239.66*+
   1440x1080    239.57  
   1400x1050    239.75  
   1280x1024    239.75  
   1280x960     239.55  
   1152x864     239.57  
   1024x768     239.35  
   800x600      239.48  
   640x480      239.21  
   320x240      238.24  
   1680x1050    239.75  
   1440x900     239.56  
   1280x800     239.65  
   1152x720     239.53  
   960x600      239.45  
   928x580      239.49  
   800x500      239.33  
   768x480      239.29  
   720x480      239.35  
   640x400      238.88  
   320x200      238.84  
   1600x900     239.51  
   1368x768     239.44  
   1280x720     239.62  
   1024x576     239.52  
   864x486      239.23  
   720x400      239.07  
   640x350      238.88  

And all X applications under Xwayland works again.
Comment 31 Raman Gupta 2025-08-01 12:14:01 UTC
I seem to have this, or a very similar, problem as well. Its very strange and very annoying. I don't see anything in the logs that would indicate why it is happening. What can we do to debug it or find more information?

Operating System: Fedora Linux 42
KDE Plasma Version: 6.4.3
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Kernel Version: 6.15.7-200.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × 12th Gen Intel® Core™ i9-12900KS
Memory: 128 GiB of RAM (124.8 GiB usable)
Graphics Processor: AMD Radeon RX 6600 XT
Comment 32 Julien Delquié 2025-08-16 15:59:24 UTC
Disconnect HDMI screen (secondary screen) from graphic card, and keep connected DP screen (primary screen) only on graphic card does not change the behavior.
The infinite loop still happens. So multiple screens environment does not seem to be necessary.

Operating System: Gentoo Linux 2.17
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.1
Kernel Version: 6.15.9-gentoo-dist (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz
Memory: 32 Gio of RAM (31.3 Gio usable)
Graphics Processor: AMD Radeon RX 7800 XT
Comment 33 Julien Delquié 2025-08-16 16:04:07 UTC
It would be interesting if anyone having an NVIDIA or INTEL graphic card try to reproduce.
If it does not reproduce, I really fear of an AMD GPU driver issue…
Comment 34 TraceyC 2025-08-18 19:57:40 UTC
I'm not able to reproduce this with git-master on a system with an NVIDIA GPU

1. Disconnect HDMI cable, wait 10 seconds. Only one disconnect sound heard.
2. Reconnect that and disconnect the DP cable. Only one disconnect sound heard.
3. Reconnect DP cable.
4. Set screens to turn off after 1 minute, let the system idle until screens go to sleep. Wait 10 seconds. No disconnect sounds heard at all.
Comment 35 Guilherme Soares 2025-08-18 20:23:17 UTC
I’m on a laptop without a dedicated GPU, only integrated graphics:

00:02.0 VGA compatible controller: Intel Corporation Arrow Lake-U [Intel Graphics]

and I get the infinite notification sound.
Comment 36 Julien Delquié 2025-09-07 11:48:25 UTC
An additional behavior happens now, since some releases of Plasma (I didn’t found the first one that occurred): sometimes kwin_wayland and plasmashell jump to nearly 100 % CPU indefinitely during the infinite loop of disconnection/connection notification sounds.
This additional behavior does not happen if I deactivate screen powersaving in settings (and of course, after doing so, the infinite loop of disconnection/connection notification sounds also does not occurs, obviously).

Operating System: Gentoo Linux 2.17
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.2
Kernel Version: 6.16.5-gentoo-dist (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz
Memory: 32 Gio of RAM (31.3 Gio usable)
Graphics Processor: AMD Radeon RX 7800 XT
Comment 37 zac 2025-09-13 03:05:28 UTC
Also experiencing this...  when the displays turn off for power saving, I get a reconnect/disconnect sound every ten seconds forever.   I think it's the "Device plugged in" system notification?  

The display mentioned by the journalctl logs is "card1-HDMI-A-1", 

Operating System: Aurora 42
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.1
Kernel Version: 6.15.9-201.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor
Memory: 64 GiB of RAM (62.7 GiB usable)
Graphics Processor: AMD Radeon RX 590 Series
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B450 AORUS M

ddcutil detect:
Display 1
   I2C bus:  /dev/i2c-3
   DRM_connector:           card1-HDMI-A-1
   EDID synopsis:
      Mfg id:               MSI - Microstep
      Model:                MSI MP275Q
      Product code:         16579  (0x40c3)
      Serial number:        PC3M255301068
      Binary serial number: 4294967295 (0xffffffff)
      Manufacture year:     2025,  Week: 10
   VCP version:         2.1

Display 2
   I2C bus:  /dev/i2c-5
   DRM_connector:           card1-DVI-D-1
   EDID synopsis:
      Mfg id:               DEL - Dell Inc.
      Model:                DELL U2212HM
      Product code:         53319  (0xd047)
      Serial number:        D4FKG35617GL
      Binary serial number: 825706316 (0x3137474c)
      Manufacture year:     2013,  Week: 19
   VCP version:         2.1

Display 3
   I2C bus:  /dev/i2c-6
   DRM_connector:           card1-DP-1
   EDID synopsis:
      Mfg id:               GSM - Goldstar Company Ltd (LG)
      Model:                IPS235
      Product code:         22652  (0x587c)
      Serial number:        308NDLS9G704
      Binary serial number: 322704 (0x0004ec90)
      Manufacture year:     2013,  Week: 8
   VCP version:         2.1

Invalid display
   I2C bus:  /dev/i2c-7
   DRM_connector:           card1-DP-2
   EDID synopsis:
      Mfg id:               ACR - Acer Technologies
      Model:                Acer B286HK
      Product code:         1023  (0x03ff)
      Serial number:        
      Binary serial number: 1932551429 (0x73306505)
      Manufacture year:     2017,  Week: 33
   DDC communication failed



journalctl for powerdevil:
Sep 12 22:45:10 Desktop-Aurora org_kde_powerdevil[3425]: [1227198] Required 3 extra 100 millisecond calls to i2c_buses_w_edid_as_bitset()
Sep 12 22:45:11 Desktop-Aurora org_kde_powerdevil[3425]: [1227198] Removing connected display on bus 3
Sep 12 22:45:11 Desktop-Aurora org_kde_powerdevil[3425]: [1227198] (dw_remove_display_by_businfo) No Display_Ref found for i2c bus: 3
Sep 12 22:45:13 Desktop-Aurora org_kde_powerdevil[3425]: [1227198] Adding connected display with bus 3
Sep 12 22:45:13 Desktop-Aurora org_kde_powerdevil[3425]: [1227198] Emitting DDCA_Display_Status_Event[364058.116:  DDCA_EVENT_DISPLAY_CONNECTED, card1-HDMI-A-1, dref: DDCA_Display_Ref[940], io_path:/dev/i2c-3, ddc working: true]
Sep 12 22:45:13 Desktop-Aurora org_kde_powerdevil[3425]: [1227198] Starting 1 callback threads
Sep 12 22:45:13 Desktop-Aurora org_kde_powerdevil[3425]: [1227198] libddcutil callback thread 0x7f6eb8017ee0 started
Sep 12 22:45:13 Desktop-Aurora org_kde_powerdevil[3425]: [1227198] Started 1 event callback thread(s)
Sep 12 22:45:13 Desktop-Aurora org_kde_powerdevil[3425]: [1227434] Invoking callback function 0x7f6f06709ad0 for event DDCA_Display_Status_Event[364058.116:  DDCA_EVENT_DISPLAY_CONNECTED, card1-HDMI-A-1, dref: DDCA_Display_Ref[940], io_path:/dev/i2c-3, ddc working: true] in this thread [1227434]
Sep 12 22:45:13 Desktop-Aurora org_kde_powerdevil[3425]: [1227434] Callback function 0x7f6f06709ad0 for event DDCA_Display_Status_Event[364058.116:  DDCA_EVENT_DISPLAY_CONNECTED, card1-HDMI-A-1, dref: DDCA_Display_Ref[940], io_path:/dev/i2c-3, ddc working: true] complete
Sep 12 22:45:13 Desktop-Aurora org_kde_powerdevil[3425]: [  3425] Quiescing libddcutil API...
Sep 12 22:45:13 Desktop-Aurora org_kde_powerdevil[3425]: [  3425] Quiesce libddcutil API complete
Sep 12 22:45:13 Desktop-Aurora org_kde_powerdevil[3425]: [  3425] Display redetection starting.
Sep 12 22:45:13 Desktop-Aurora org_kde_powerdevil[3425]: [1227197] recheck thread terminating because watch thread terminated
Sep 12 22:45:13 Desktop-Aurora org_kde_powerdevil[3425]: [  3425] Watch thread terminated.
Sep 12 22:45:16 Desktop-Aurora org_kde_powerdevil[3425]: [1227446] (check_supported_feature) busno=7, sleep-multiplier =  2.00. Testing for supported feature 0x10 returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: DDCRC_NULL_RESPONSE(10)]
Sep 12 22:45:16 Desktop-Aurora org_kde_powerdevil[3425]: [  3425] Watching for display connection changes, resolved watch mode = Watch_Mode_Xevent, poll loop interval = 100 millisec
Sep 12 22:45:16 Desktop-Aurora org_kde_powerdevil[3425]: [  3425]                                          extra_stabilization_millisec: 0,  stabilization_poll_millisec: 100
Sep 12 22:45:16 Desktop-Aurora org_kde_powerdevil[3425]: [  3425] libddcutil recheck thread 0x56121a5f8740 started
Sep 12 22:45:16 Desktop-Aurora org_kde_powerdevil[3425]: [1227615] (dw_recheck_displays_func) Recheck interval: Sleeping for 200 milliseconds
Sep 12 22:45:16 Desktop-Aurora org_kde_powerdevil[3425]: [  3425] libddcutil watch thread 0x56121a707e40 started
Sep 12 22:45:16 Desktop-Aurora org_kde_powerdevil[3425]: [  3425] Display redetection finished.
Sep 12 22:45:16 Desktop-Aurora org_kde_powerdevil[3425]: [  3425] Unquiescing libddcutil API...
Comment 38 screendisconnectloop 2025-09-16 13:51:02 UTC
Same issue on fresh install of Bazzite.

Operating System: Bazzite 42
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.1
Kernel Version: 6.16.4-108.bazzite.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor: AMD Radeon RX 7800 XT
Manufacturer: ASUS

Display 1 on HDMI: LG 24MP58VQ-P
Display 2 on HDMI / DVI converter: Fujitsu L20T-3 LED

The Fujitsu turns of without complaint, but the LG stays on with "no signal found" message and the plugin/unplug notifications are looping.