https://bugs.kde.org/show_bug.cgi?id=519630
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #7 from [email protected] --- Created attachment 196752 --> https://bugs.kde.org/attachment.cgi?id=196752&action=edit Five stuck laptop battery notifications with unresponsive close buttons, Plasma 6.7.5 I am experiencing the same problem on Fedora Linux 44 (KDE Plasma Desktop Edition), with Plasma and PowerDevil 6.7.5 and Qt 6.11.2. The attached screenshot shows five Power Management notifications: - 04:13 — Battery Low (30% Remaining) - 04:34 — Battery Low (14% Remaining) - 04:35 — Battery Low (13% Remaining) - 04:35 — Battery Low (11% Remaining) - 04:36 — Battery Critical (10% Remaining), with Sleep Now and Cancel buttons Clicking the × close buttons does not dismiss the notifications. The old alerts remain visible after charging. During diagnosis, the laptop battery reported 100%. Expected behavior: Clicking × should dismiss the notification. Obsolete battery alerts should disappear once the battery has recovered. System and package versions: - Fedora Linux 44, KDE Plasma Desktop Edition - plasma-workspace-6.7.5-1.fc44.x86_64 - powerdevil-6.7.5-1.fc44.x86_64 - qt6-qtbase-6.11.2-2.fc44.x86_64 - qt6-qtdeclarative-6.11.2-2.fc44.x86_64 Relevant existing configuration: powerdevilrc: [BatteryManagement] BatteryCriticalLevel=10 BatteryLowLevel=30 plasmanotifyrc: [Notifications] LowPriorityHistory=true PopupPosition=BottomCenter PopupTimeout=3000 [Services][powerdevil] ShowInHistory=false ShowPopups=false Diagnostic observations: Plasmashell still responds over D-Bus. Its journal contains the following warnings around the time shown in the screenshot and again later that day. I cannot confirm that these warnings are caused by the close-button clicks or establish the root cause from them. Journal excerpt (local timestamps; hostname and process ID omitted): 2026-10-01 04:36:19 plasmashell: Index QModelIndex(-1,-1,0x0,QObject(0x0)) is not valid (expected valid) 2026-10-01 04:36:20 plasmashell: Index QModelIndex(-1,-1,0x0,QObject(0x0)) is not valid (expected valid) 2026-10-01 04:36:21 plasmashell: Index QModelIndex(-1,-1,0x0,QObject(0x0)) is not valid (expected valid) 2026-10-01 04:36:21 plasmashell: Index QModelIndex(-1,-1,0x0,QObject(0x0)) is not valid (expected valid) 2026-10-01 04:36:21 plasmashell: Index QModelIndex(-1,-1,0x0,QObject(0x0)) is not valid (expected valid) 2026-10-01 04:36:21 plasmashell: Index QModelIndex(-1,-1,0x0,QObject(0x0)) is not valid (expected valid) 2026-10-01 15:11:42 plasmashell: Index QModelIndex(-1,-1,0x0,QObject(0x0)) is not valid (expected valid) 2026-10-01 15:11:43 plasmashell: Index QModelIndex(-1,-1,0x0,QObject(0x0)) is not valid (expected valid) 2026-10-01 15:11:43 plasmashell: Index QModelIndex(-1,-1,0x0,QObject(0x0)) is not valid (expected valid) Could this report be reopened, or linked to the appropriate active issue? -- You are receiving this mail because: You are watching all bug changes.
