https://bugs.kde.org/show_bug.cgi?id=494330
Akseli Lahtinen <[email protected]> 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 <[email protected]> --- 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 <[email protected]> M +5 -0 devicenotifications/CMakeLists.txt M +46 -9 devicenotifications/devicenotifications.cpp M +29 -1 devicenotifications/devicenotifications.h https://invent.kde.org/plasma/plasma-workspace/-/commit/bc268f1d8597b7545cf9c225138f11fd38874ef7 -- You are receiving this mail because: You are watching all bug changes.
