X86 platform drivers
 help / color / mirror / Atom feed
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 10:45:51 +0000	[thread overview]
Message-ID: <bug-220722-215701-rHFNRz1INf@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 #11 from Hans de Goede (hansg@kernel.org) ---
(In reply to ggrundik from comment #10)
> As I stated in https://bugzilla.kernel.org/show_bug.cgi?id=221118, its not
> the fake battery, its the pen battery. All you need is just use the pen,
> touch the screen by it, and this battery level will update according to the
> pen battery.
> 
> So now you removed that feature, and pen battery is no longer showing.

The problem is that without pen nearby the HID battery reports 0 charge instead
of not-present. This results in GNOME showing an low battery warning every time
the user logs into a session which is very annoying.

So until we've some better fix we need to choose between many users getting the
annoying low battery warning all the time; or the few users who actually use a
pen with these touchscreens (which is quite rare) not having battery info.

Having the chose at all between this is not ideal, but until we've a better fix
just hiding the broken battery reporting is the best we can do.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2026-02-23 10:45 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 [this message]
2026-02-23 16:43 ` bugzilla-daemon
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-rHFNRz1INf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox