Hi,

When I bought Logitec K520 keyboard and M310 mouse two weeks ago, I was pleasantly surprised that the KDE Battery Monitor shows their battery status as well, alongside the battery of the laptop. It was in KDE 4.11. Few days ago I updated to 4.12, and this functionality disappeared! Now only the laptop battery status is shown. "upower -d" shows all devices correctly. What can be the problem?
I'm using Arch Linux (x86_64).

Thanks!

Does disconnecting the keyboard/mouse and reconnecting it have any effect? Also, are you automatically logging in?
If so, does logging out and logging back in have any effect?

Thanks for the reply.

1) disconnecting/reconnecting the wireless adapter does not have any effect.
2) Yes, I'm automatically logged in.
3) Logging out and back in DOES solve this.

But it worked fine with auto-login in 4.11...

Can you please check the output of the following command to see if KDE is able to see the keyboard battery on the initial login?

Code: Select all

solid-hardware list| grep -i upower

If it is showing, then it appears that the battery applet is not responding to runtime changes of battery device availability.

As for why this changed between 4.11 and 4.12 - i'm not sure, it could be a simple timing difference, due to Plasma starting applets or other components quicker or in a different order.

The output is:

Code: Select all

Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
udi = '/org/freedesktop/UPower'
udi = '/org/freedesktop/UPower/devices/battery_BAT0'
udi = '/org/freedesktop/UPower/devices/line_power_AC'
udi = '/org/freedesktop/UPower/devices/mouse_0003o046DoC52Bx0004'
udi = '/org/freedesktop/UPower/devices/keyboard_0003o046DoC52Bx0005'

So it appears to show.

Okay, the bug then lies with the inability of the applet to respond to newly available batteries. Please file a bug report at bugs.kde.org.
Whether this is a regression in KDE 4.12, or if other changes have simply exposed it I do not know however.

As an interim measure, I would suggest delaying the onset of KDE startup in order to allow for the keyboard/mouse battery to be detected by the system.