From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 220722] Non existent battery reporting for a laptop with touchscreen MSI
Date: Mon, 23 Feb 2026 17:12:24 +0000 [thread overview]
Message-ID: <bug-220722-215701-6vKuiQL6NK@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220722-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220722
--- Comment #14 from Hans de Goede (hansg@kernel.org) ---
(In reply to ggrundik from comment #12)
> Isn't this a GNOME problem, not a kernel one?
>
> Current PCs can have quite a lot of battery-powered devices, apart of PC
> itself: wireless controllers, mices, keyboards, pens, VR headsets,
> headphones, etc. Most of them can report their battery status. If a desktop
> environment cant separate them apart, and dont understand which is PC itself
> and which is not... Its clearly fault of desktop environment, since its
> quite a common case. KDE, for example, has no problems with that. This bug
> should be reported in GNOME, not in kernel.
GNOME already tells all these different batteries apart. e.g. if my wireless
Logitech mouse battery is getting empty it will throw a "Logitech mouse battery
is getting low warning", not a laptop-empty battery warning which you seem to
think.
And in case of these ELAN touchscreens it throws a "ELAN Touchscreen Stylus
battery low" warning and it does so *all* the time, because upower is telling
it that there is a "ELAN Touchscreen Stylus" battery at 0%.
This is really not a GNOME problem, this needs to be fixed either in upower or
in the kernel. GNOME is just forwarding the info it is receiving from upower
and this works for all those other wireless kbds, mice, game controllers and
headphones you mention.
(In reply to ggrundik from comment #13)
> Best solution could have been to hotplug the stylus battery device when
> stylus comes in range first time, but that would be quite a trick for the
> driver.
And probably also hot unplug it when the stylus goes out of range. I would say
patches welcome.
> Less convenient solution could be to hide this battery readings, if stylus
> is not in use. This is a userspace solution.
Yes, fixing this in upower might also be a solution, see:
https://gitlab.freedesktop.org/upower/upower/-/issues/197
for an existing upower issue.
> But current solution, to hide this battery always and from everyone, seems
> like a worst one.
Patches to properly solve this are welcome. But until there are fixes to upower
telling GNOME that their is a "ELAN Touchscreen Stylus" battery at 0%, the
filtering out of the HID battery reporting on these touchscreens is staying in
place, since it is the least bad option of the bad choices we have atm.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2026-02-23 17:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 16:18 [Bug 220722] New: Non existent battery reporting for a laptop with touchscreen MSI bugzilla-daemon
2025-10-30 15:02 ` [Bug 220722] " bugzilla-daemon
2025-10-30 15:19 ` bugzilla-daemon
2025-10-30 15:38 ` bugzilla-daemon
2025-10-30 15:41 ` bugzilla-daemon
2025-10-30 15:41 ` bugzilla-daemon
2025-10-30 15:45 ` bugzilla-daemon
2025-10-30 15:47 ` bugzilla-daemon
2025-10-30 15:58 ` bugzilla-daemon
2025-10-30 20:05 ` bugzilla-daemon
2025-10-31 11:02 ` bugzilla-daemon
2026-02-22 13:54 ` bugzilla-daemon
2026-02-23 10:45 ` bugzilla-daemon
2026-02-23 16:43 ` bugzilla-daemon
2026-02-23 16:59 ` bugzilla-daemon
2026-02-23 17:12 ` bugzilla-daemon [this message]
2026-02-23 17:37 ` bugzilla-daemon
2026-02-23 18:31 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-220722-215701-6vKuiQL6NK@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.