[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 --- Comment #47 from Julien Delquié --- (In reply to Nate Graham from comment #44) > (In reply to Julien Delquié from comment #42) > > Just tested this patch on my Gentoo. > > Infinite loop of sound is gone (yay~!). > > But still, infinite loop of flood in journalctl exists. > > And also 100 % CPU for kwin_wayland and plasmashell, as well. > > Those issues are probably worth tracking with a new bug report. Can you open > one? Done! => https://bugs.kde.org/show_bug.cgi?id=512444 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 --- Comment #42 from Julien Delquié --- Just tested this patch on my Gentoo. Infinite loop of sound is gone (yay~!). But still, infinite loop of flood in journalctl exists. And also 100 % CPU for kwin_wayland and plasmashell, as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 --- Comment #46 from Fernando M. Muniz --- There should only be one notification with the exact same text, in this case 1 "Detected" and 1 "Removed" notification, and each time the device changes state; the older notification should change places with newer one and reset its fade out timer. And if there is only one notification; just reset the fade out timer. I guess the non-artsy-fartsy way to implement this is to simply delete older duplicate notifications. But I prefer my first suggestion because it would allow fancy switcheroo effect between notifications. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 Akseli Lahtinen changed: What|Removed |Added CC||[email protected] --- Comment #45 from Akseli Lahtinen --- *** Bug 510545 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 --- Comment #44 from Nate Graham --- (In reply to Julien Delquié from comment #42) > Just tested this patch on my Gentoo. > Infinite loop of sound is gone (yay~!). > But still, infinite loop of flood in journalctl exists. > And also 100 % CPU for kwin_wayland and plasmashell, as well. Those issues are probably worth tracking with a new bug report. Can you open one? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 Nate Graham changed: What|Removed |Added Version Fixed In||6.5.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 Akseli Lahtinen changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/-/commi |ma/plasma-workspace/-/commi |t/1f292200f436489a4bfe6df49 |t/bc268f1d8597b7545cf9c2251 |4a4aef4a65dff88 |38f11fd38874ef7 --- Comment #43 from Akseli Lahtinen --- Git commit bc268f1d8597b7545cf9c225138f11fd38874ef7 by Akseli Lahtinen. Committed on 23/09/2025 at 16:51. Pushed by akselmo into branch 'Plasma/6.5'. DeviceNotifications: Cooldown before notifications In some cases, for example having faulty monitor or faulty wire, the monitor can inform itself to be plugged/unplugged multiple times. In these cases, we should check if the output was recently added/removed, and if so, ignore sending notifications: Wait for 2000ms before allowing for the added/removed display to create a notification. Otherwise the notification will be sent as usual. (cherry picked from commit 1f292200f436489a4bfe6df494a4aef4a65dff88) b5f316b9 DeviceNotifications: Cooldown before notifications 19d0ca88 Use sharedptr 49770265 Fix cmakelists 7a00971c Remove m_recentlyAddedOutputs 12e85fa6 use stdvector and uniqueptr f706061f use iterator 36989751 erase instead of reset Co-authored-by: Akseli Lahtinen M +5-0devicenotifications/CMakeLists.txt M +46 -9devicenotifications/devicenotifications.cpp M +29 -1devicenotifications/devicenotifications.h https://invent.kde.org/plasma/plasma-workspace/-/commit/bc268f1d8597b7545cf9c225138f11fd38874ef7 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 Akseli Lahtinen changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/1f292200f436489a4bfe6df49 ||4a4aef4a65dff88 Resolution|--- |FIXED --- Comment #41 from Akseli Lahtinen --- Git commit 1f292200f436489a4bfe6df494a4aef4a65dff88 by Akseli Lahtinen. Committed on 23/09/2025 at 16:12. Pushed by akselmo into branch 'master'. DeviceNotifications: Cooldown before notifications In some cases, for example having faulty monitor or faulty wire, the monitor can inform itself to be plugged/unplugged multiple times. In these cases, we should check if the output was recently added/removed, and if so, ignore sending notifications: Wait for 2000ms before allowing for the added/removed display to create a notification. Otherwise the notification will be sent as usual. M +5-0devicenotifications/CMakeLists.txt M +46 -9devicenotifications/devicenotifications.cpp M +29 -1devicenotifications/devicenotifications.h https://invent.kde.org/plasma/plasma-workspace/-/commit/1f292200f436489a4bfe6df494a4aef4a65dff88 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #40 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/5832 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 [email protected] changed: What|Removed |Added CC||[email protected] --- Comment #39 from [email protected] --- Same issue in Arch Linux, and have had it since I've installed on my new desktop in June. I have two monitors, one connected via DisplayPort and one via HDMI. Running `systemctl suspend` works perfectly fine. System Info: Operating System: Arch Linux KDE Plasma Version: 6.4.5 KDE Frameworks Version: 6.18.0 Qt Version: 6.9.2 Kernel Version: 6.16.8-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 9800X3D 8-Core Processor Memory: 64 GiB of RAM (60.4 GiB usable) Graphics Processor 1: AMD Radeon RX 9070 XT Graphics Processor 2: AMD Radeon Graphics Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B850 AORUS ELITE WIFI7 System Version: Default string-CF-WCP-ADO ❯ ddcutil detect Display 1 I2C bus: /dev/i2c-6 DRM_connector: card1-HDMI-A-1 EDID synopsis: Mfg id: AOC - UNK Model:24B2W1G5 Product code: 9218 (0x2402) Serial number:RSKN61A000560 Binary serial number: 560 (0x0230) Manufacture year: 2022, Week: 25 VCP version: 2.1 Display 2 I2C bus: /dev/i2c-9 DRM_connector: card1-DP-1 EDID synopsis: Mfg id: AUS - UNK Model:VG27AQ1A Product code: 9991 (0x2707) Serial number:R7LMQS160329 Binary serial number: 16843009 (0x01010101) Manufacture year: 2023, Week: 30 VCP version: 2.2 ❯ ddcutil capabilities Unparsed capabilities string: (prot(monitor)type(lcd)model(24B2XH)cmds(010203070C4EF3E3)vcp(020405080B0C101214(010506080B)16181A6C6E70ACAEB6C0C6C8C9CA60(010F1112)CC(0102030405060708090A0B0D1214161E)D6(0104)DFDC(000B0C0D0E0F10)86(0205)628D(0102)FF)mswhql(1)asset_eep(40)mccs_ver(2.2)) Errors parsing capabilities string: Error processing commands list: 010203070C4EF3E3 Invalid VCP value in list for feature x14: 010506080B Invalid VCP value in list for feature x60: 010F1112 Invalid VCP value in list for feature xcc: 0102030405060708090A0B0D1214161E Invalid VCP value in list for feature xd6: 0104 Invalid VCP value in list for feature xdc: 000B0C0D0E0F10 Invalid VCP value in list for feature x86: 0205 Invalid VCP value in list for feature x8d: 0102 Model: 24B2XH MCCS version: 2.2 VCP Features: Feature: 02 (New control value) Feature: 04 (Restore factory defaults) Feature: 05 (Restore factory brightness/contrast defaults) Feature: 08 (Restore color defaults) Feature: 0B (Color temperature increment) Feature: 0C (Color temperature request) Feature: 10 (Brightness) Feature: 12 (Contrast) Feature: 14 (Select color preset) Values: Feature: 16 (Video gain: Red) Feature: 18 (Video gain: Green) Feature: 1A (Video gain: Blue) Feature: 6C (Video black level: Red) Feature: 6E (Video black level: Green) Feature: 70 (Video black level: Blue) Feature: AC (Horizontal frequency) Feature: AE (Vertical frequency) Feature: B6 (Display technology type) Feature: C0 (Display usage time) Feature: C6 (Application enable key) Feature: C8 (Display controller type) Feature: C9 (Display firmware level) Feature: CA (OSD) Feature: 60 (Input Source) Values: Feature: CC (OSD Language) Values: Feature: D6 (Power mode) Values: Feature: DF (VCP Version) Feature: DC (Display Mode) Values: Feature: 86 (Display Scaling) Values: Feature: 62 (Audio speaker volume) Feature: 8D (Audio Mute) Values: dB[ (interpretation unavailable) Feature: FF (Manufacturer specific feature) Capabilities string not completely parsed Errors: Error processing commands list: 010203070C4EF3E3 Invalid VCP value in list for feature x14: 010506080B Invalid VCP value in list for feature x60: 010F1112 Invalid VCP value in list for feature xcc: 0102030405060708090A0B0D1214161E Invalid VCP value in list for feature xd6: 0104 Invalid VCP value in list for feature xdc: 000B0C0D0E0F10 Invalid VCP value in list for feature x86: 0205 Invalid VCP value in list for feature x8d: 0102 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 [email protected] changed: What|Removed |Added CC||screendisconnectloop@mailin ||ator.com --- Comment #38 from [email protected] --- 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. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 zac changed: What|Removed |Added CC||[email protected] --- Comment #37 from zac --- 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 (0x) 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 chan
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 --- Comment #36 from Julien Delquié --- 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 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 Nate Graham changed: What|Removed |Added Summary|Infinite loop of|Infinite loop of |disconnection/connection|disconnection/connection |notification sounds when|notification sounds when |certain screens connected |certain screens go to sleep |to an AMD GPU go to sleep | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 --- Comment #34 from TraceyC --- 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. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 --- Comment #32 from Julien Delquié --- 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 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 --- Comment #33 from Julien Delquié --- 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… -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 Raman Gupta changed: What|Removed |Added CC||[email protected] --- Comment #31 from Raman Gupta --- 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 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 [email protected] changed: What|Removed |Added CC||[email protected] ||om -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 --- Comment #30 from Julien Delquié --- 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 1920x1080239.66*+ 1440x1080239.57 1400x1050239.75 1280x1024239.75 1280x960 239.55 1152x864 239.57 1024x768 239.35 800x600 239.48 640x480 239.21 320x240 238.24 1680x1050239.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. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 TraceyC changed: What|Removed |Added Priority|NOR |HI --- Comment #29 from TraceyC --- Bumping priority since so many people are affected. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 [email protected] changed: What|Removed |Added CC||[email protected] --- Comment #28 from [email protected] --- 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 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 [email protected] changed: What|Removed |Added CC||[email protected] --- Comment #27 from [email protected] --- Using KDE here in CatchyOS and also Bazzite and can indeed confirm. Sound of disconnect/connect loops infinitely when monitors sleep. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 --- Comment #26 from Julien Delquié --- 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 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 --- Comment #25 from Julien Delquié --- 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 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 Oliver changed: What|Removed |Added CC||[email protected] --- Comment #24 from Oliver --- 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 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 [email protected] changed: What|Removed |Added CC||[email protected] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 --- Comment #23 from [email protected] --- 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 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 Phil changed: What|Removed |Added CC||[email protected] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 --- Comment #22 from Metz --- 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 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 [email protected] changed: What|Removed |Added CC||[email protected] --- Comment #21 from [email protected] --- 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 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 --- Comment #20 from [email protected] --- 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. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 [email protected] changed: What|Removed |Added CC||[email protected] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 --- Comment #19 from Julien Delquié --- 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. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 TraceyC changed: What|Removed |Added CC||[email protected] --- Comment #18 from TraceyC --- *** Bug 495215 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 [email protected] changed: What|Removed |Added CC||[email protected] --- Comment #17 from [email protected] --- (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 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 --- Comment #16 from [email protected] --- (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. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 --- Comment #15 from Zamundaaa --- (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. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494330] Infinite loop of disconnection/connection notification sounds when certain screens go to sleep
https://bugs.kde.org/show_bug.cgi?id=494330 Nate Graham changed: What|Removed |Added Target Milestone|--- |1.0 Summary|Infinite loop of|Infinite loop of |disconnection/connection|disconnection/connection |notification sound when |notification sounds when |screens go to sleep |certain screens go to sleep Product|kwin|plasmashell Component|output configuration|Disks & Devices CC||[email protected] Severity|major |normal Assignee|[email protected] |[email protected] -- You are receiving this mail because: You are watching all bug changes.
