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 16:43:51 +0000 [thread overview]
Message-ID: <bug-220722-215701-8mvpdiGdKy@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 #12 from ggrundik@gmail.com ---
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.
Blocking some device metrics in a kernel, just because some specific userspace
program incorrectly handles that in a weird way does not seems like a wise
solution. It is a perfectly functional, correct and useful metric.
This touchscreen is has two sensor layers: one for fingers plus one for stylus,
and it does report battery status of stylus. Communications between stylus and
the drawing surface can happen only when stylus is in range of touchscreen, its
a hardware limitation. So touchscreen does not have any information about
stylus until this communication happens at least once, but this does not means
that there are no stylus at all, or it is never in use. But after this
communication happens, touchscreen remembers last known status, and its
correctly shown as a battery level.
Before this change was made, this touchscreen was working as good as hardware
could. Now there are no pen battery status not only in GNOME, but nowhere.
--
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 16:43 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 [this message]
2026-02-23 16:59 ` bugzilla-daemon
2026-02-23 17:12 ` bugzilla-daemon
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-8mvpdiGdKy@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.