Erroneous Low Battery Notifications

Ask Fedora
1

Operating System: Fedora Linux 44
KDE Plasma Version: 6.7.5
KDE Frameworks Version: 6.30.0
Qt Version: 6.11.2
Kernel Version: 7.2.4-200.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × 11th Gen Intel® Core™ i7-11700 @ 2.50GHz
Memory: 32 GiB of RAM (31.1 GiB usable)
Graphics Processor: Intel® Graphics
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B560M DS3H

I keep receiving erroneous low battery notifications for my Logitech K350 keyboard. The following cycle keeps repeating:

  • Notification warning reporting battery at ~1%
  • Warning dismissed
  • Later check Power & Battery, which reports battery at 70% (not 100% as expected).

What I’ve done so far:

  • Tried several fully charged battery sets (confirmed with a voltmeter)
  • Tried full power cycling of the system, keyboard, and keyboard transceiver
  • Fully updated my system.

These erroneous notifications are occurring about every 20 minutes. This issue just began today.

Any suggestions for troubleshooting this issue?

2

I have the same keyboard along with a logitech MX Ergo trackball. The trackball is usb charged and the keyboard uses batteries.

I see the same message when the trackball needs charged, and have never seen that message with the keyboard. The last time I had to replace batteries in the keyboard was when it quit working – no message about the battery.

Do you also have a mouse/trackball that uses the same unified receiver? Have you checked batteries or charge on the mouse?

I suspect your messages may be the same as mine – says keyboard but cannot tell the difference between the 2 devices for that message.

$ inxi -Bxx
Battery:
  Device-1: hidpp_battery_4 model: Logitech MX Ergo Multi-Device Trackball
    serial: 06-e4-a3-3c charge: 100% (should be ignored) status: discharging
  Device-2: hidpp_battery_5 model: Logitech K350 serial: e6-28-b0-cb
    charge: 70% (should be ignored) status: discharging
3

I have a Logitech Lift mouse, battery powered, which uses a different transceiver than the K350.

clayton@voron:~$ inxi -Bxx
Battery:
Device-1: hidpp_battery_0 model: Logitech K350 serial: 5f-9f-bb-39
charge: 70% (should be ignored) status: discharging

Interesting that the Lift mouse is not listed…

The mouse battery was low (1.18 V), so I replaced it. Will monitor to see if the keyboard notifications stop.

4

Even using a different receiver it still probably was generating the message for you.

5

I have a Logitech keyboard and mouse set, and the same problem suddenly appeared, even though the batteries are fine.
I suspect an issue with KF6, as the notifications started after the update from KF6 6.29 to 6.30.
It’s possible to block these notifications, but I’d like to confirm the cause first.

6

It’s been reported to the KDE bugzilla:

7

stupid logitech sending the battery level to the kernel so it can annoy us lol

mx400+ here doing the same like each 15 minutes

the wireless mouse is not doing it, even if batteries are low, i will leave them low, because it works like that for like 3 years

i will turn off those notifications because i dont need kernel to report me the state of a keyboard batery, because it is a keyboard.

8

I vaguely remember seeing many KF6 packages in the last update. No changes in hardware for several years and it seemed odd for this issue to suddenly appear.

This raises another question. Before these notifications appeared, I had not really paid any attention to the hardware configuration (just plug and played it). Upon investigation, I found something very odd.

In Settings > Keyboard, there is no Model option for a Logitech K350. It defaults to a Generic 104-key PC.

In Settings > Mouse, it defaults to Logitech K350 (no generic option shown). I think Logitech once marketed a K350 combo keyboard/mouse. However, that is not what I purchased; only the keyboard (I use a Logitech Lift mouse).

The K350 keyboard uses the Unifying receiver. The Lift mouse originally used the Logi Bolt receiver (after this issue arose, I switched to Bluetooth to see if it would help).

The very odd thing is that if the Settings > Mouse > Device does not have the Device > Logitech 350 set to ‘Enable device’, my keyboard does not work! A setting for a mouse that is not installed determines whether my keyboard works or not.

After switching the mouse to Bluetooth, Logitech Lift appears as a device under Mouse settings. I can select and enable the Lift device and everything works fine. However if, under Mouse settings, I disable the K350, the keyboard stops working.

So, there seems to be some kind of weird cross linking between the K350 keyboard/mouse drivers. No idea how to correct this.

clayton@voron:~$ upower -d
Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_0
native-path: hidpp_battery_0
model: Logitech K350
serial: 5f-9f-bb-39
power supply: no
updated: Sat Sep 12 09:42:13 2026 (24 seconds ago)
has history: yes
has statistics: yes
keyboard
present: yes
rechargeable: yes
state: discharging
warning-level: none
battery-level: high
percentage: 70% (should be ignored)
icon-name: ‘battery-good-symbolic’

Device: /org/freedesktop/UPower/devices/mouse_dev_D2_C1_D5_CC_C8_5A
native-path: /org/bluez/hci0/dev_D2_C1_D5_CC_C8_5A
model: LIFT
serial: D2:C1:D5:CC:C8:5A
power supply: no
updated: Sat Sep 12 08:46:06 2026 (3391 seconds ago)
has history: yes
has statistics: no
mouse
present: yes
rechargeable: no
state: unknown
warning-level: none
percentage: 60%
icon-name: ‘battery-missing-symbolic’

Device: /org/freedesktop/UPower/devices/DisplayDevice
power supply: no
updated: Sat Sep 12 08:45:29 2026 (3428 seconds ago)
has history: no
has statistics: no
unknown
warning-level: none
percentage: 0%
icon-name: ‘battery-missing-symbolic’

Daemon:
daemon-version: 1.91.4
on-battery: no
lid-is-closed: no
lid-is-present: no
critical-action: Sleep

So this trace does not list a keyboard device and shows a K350 (which is not listed in Settings), not a K350. Don’t understand what’s going on here.

9

Your issue in this post seems different than the one noted by the topic title and the first post.
Please open your own topic for the issues with the mouse/keyboard config since that is totally different. A different issue should be handled in a different topic.

In your posts above you stated

but failed to note that the mouse was using bluetooth. Bluetooth devices should show under bluetooth in the inxi listing (their battery status is not normally reported by inxi) or be seen by using the lsusb command (they exist as a usb device)

10

To clarify:

11

Now there is more confusion. The upower output shows K350 as does the earlier inxi output, yet your text now shows K360. which is correct.??

Note that this topic began on the K350 keyboard, and if yours is a K360 then my earlier posts may be totally useless.

12

Apologies. It is a K350. I’ve corrected the typos.

14

I’d still like to find a solution mouse/keyboard configuration issues posed (AFAIK, there is no such thing as a K350 mouse. Logitech did market a K350 keyboard and MK550 mouse combo). However, for the original issue, I will for now settle for turning the low battery notifications off (as shown below):

low_battery
low_battery2120×2190 527 KB

Many thanks for the helpful replies!

15

logitech often makes combos of decent keyboards with a pos mouse and some report different names and it doesnt really matter how is detected in this particular cae i think, because it seems to affect multiple logitech devices, but not all, my m170 is not annoying me, well,was, before i turned off the pop ups for that

i turned both sound and messages on that menu you shared there, yes

16

I’m also getting for my K270. I can duel boot my machine with Tumbleweed, where it doesn’t alert.

OS: openSUSE Tumbleweed x86_64
Kernel: Linux 7.2.3-1-default

Desktop Environment: KDE Plasma 6.7.4

OS: Fedora Linux 44 (KDE Plasma Desktop Edition) x86_64
Kernel: Linux 7.2.4-200.fc44.x86_64

DE: KDE Plasma 6.7.5

I also had it on the previous kernel 7.13, on F44. there was no issues on 7.12 but what I’ve noticed between Suse and Fedora is the point difference in Plasma.

17

Yes, it seems to be a Plasma 6.7.5 thing. This openSUSE user also got the problem after updating to 6.7.5.

18

Cheers, I see a bug report has been filed with KDE, hopefully it be patched or at least fixed in Plasma 6.7.6

19

i doubt that

we are already in kde 6.8 in testing, perhaps after that, i mean 6.7.8 was ready like 2 months ago

we are just in 6.7.5, patience

20

I don’t think the issue stems from Plasma itself, as I’m running Rawhide with its frequent updates.
I didn’t have this problem with Plasma 6.7.4 and KF6-6.29; it started with Plasma 6.7.4 and KF6-6.30 .
Since I’m on Rawhide, I can’t downgrade to test whether it’s actually a KF6 issue.

21

Very revealing - that does sound like it’s Frameworks 6.30 rather than Plasma 6.7.5 then.