42.2 on Intel NUC style devices - detects no battery - Apper therefore won't update "device offline"

English Hardware
1

Hi there,

There seems to be some default behavior for laptops, whereby Apper wants you to be plugged in to mains power before it will search for and install updates.
All very sensible in principle.

However, this behaviour is problematic for Intel NUC style devices that use mobile hardware in SFF and low power desktops.

The taskbar shows an icon saying “No battery is available”, which is true, there isn’t.
But, because it seems to think its a mobile device and therefore expects a battery, it then leaves Apper in the situation of not wanting to fetch updates.
I don’t seem to be able to tell the system that this [isn’t] a mobile device, and therefore Apper shouldn’t be subject to behaviour designed for laptops.

Yes, I can use YAST to pull down updates, but I want Apper.

This happens both with a Boradwell PC and a Kabini PC.

Any advice?

2

I’m not familiar with these devices, but this is no doubt a BIOS/kernel-related issue. Just to get a handle on how the kernel and desktop environment see this system, please run the following commands, capture the output and post here

ls -l /sys/class/power_supply/*

upower -d

It may be that a bug report is required.