Consistently getting 'battery health charging install check timed out'

[Chinychon]

I have tried to use the sudo instead of pkexec workaround as well as the workaround script, but without any luck. I'm on fedora (wayland), and I noticed my system is listed as a known non-affected system. I'm not really a technical user, just wanted to report that I've been experiencing this bug. I essentially have to just disable and reenable to plugin every time I wake from suspension.

[maniacx]

Can you give some details.

Laptop make model
Kernel version
Fedora detail (example 42 Workstation/ silver blue. Etc)

journalctl -f -o cat /usr/bin/gnome-shell

Open terminal/ console and run the above command.
This will show some logs. Disable/ re enable it and post the log here.

[Chinychon]

❯ hostnamectl
Static hostname: Pilgrim
Hardware Vendor: Lenovo
Hardware Model: ThinkPad P1 Gen 3
Operating System: Fedora Linux 43 (Workstation Edition)
Kernel: Linux 6.18.13-200.fc43.x86_64

❯ journalctl -f -o cat /usr/bin/gnome-shell
Can't find input for stream-id 417
meta_dbus_session_manager_uninhibit: assertion 'priv->inhibit_count > 0' failed
meta_dbus_session_manager_uninhibit: assertion 'priv->inhibit_count > 0' failed
meta_dbus_session_manager_uninhibit: assertion 'priv->inhibit_count > 0' failed
libinput error: event5 - Razer Razer Viper Mini: client bug: event processing lagging behind by 24ms, your system is too slow
Battery Health Charging: Exceeded timeout for command: sudo /usr/local/bin/batteryhealthchargingctl-gabrielchin CHECKINSTALLATION /home/gabrielchin/.local/share/gnome-shell/extensions/Battery-Health-Charging@maniacx.github.com/resources gabrielchin
g_signal_handler_disconnect: assertion 'handler_id > 0' failed
g_signal_handler_disconnect: assertion 'handler_id > 0' failed
g_signal_handler_disconnect: assertion 'handler_id > 0' failed
Overwriting existing binding of keysym 61 with keysym 61 (keycode 26).
Source ID 5540230 was not found when attempting to remove it
g_signal_handler_disconnect: assertion 'handler_id > 0' failed
g_signal_handler_disconnect: assertion 'handler_id > 0' failed
Overwriting existing binding of keysym 61 with keysym 61 (keycode 26).
g_signal_handler_disconnect: assertion 'handler_id > 0' failed
libinput error: event5 - Razer Razer Viper Mini: client bug: event processing lagging behind by 24ms, your system is too slow

[maniacx]

Just curious, Why did you install the extension as system extension?
It is not meant to be used as a system extension.
You need to install it as a user extension.

Remove / Uninstall the extension as system extension. And install it back again as user extension.

[maniacx]

Just curious, Why did you install the extension as system extension? It is not meant to be used as a system extension. You need to install it as a user extension.

Remove / Uninstall the extension as system extension. And install it back again as user extension.

Sorry My mistake. It is not installed as system extension. I am sleepy I guess.

Can you please test these 2 command in terminal / console and post the output.

time sudo /usr/local/bin/batteryhealthchargingctl-gabrielchin CHECKINSTALLATION /home/gabrielchin/.local/share/gnome-shell/extensions/Battery-Health-Charging@maniacx.github.com/resources gabrielchin

time pkexec /usr/local/bin/batteryhealthchargingctl-gabrielchin CHECKINSTALLATION /home/gabrielchin/.local/share/gnome-shell/extensions/Battery-Health-Charging@maniacx.github.com/resources gabrielchin

[neildarlow]

The OP wasn't clear about where this timeout is occurring but I'm experiencing the same error immediately after login.

Polkit presents an authentication dialog for the /usr/local/bin script but I don't have time to enter my password before it times-out.

System details:

System Details Report

---

Report details

• Date generated: 2026-04-24 14:21:34

Hardware Information:

• Hardware Model: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X421EAY_S413EA
• Memory: 16.0 GiB
• Processor: 11th Gen Intel® Core™ i5-1135G7 × 8
• Graphics: Intel® Iris® Xe Graphics (TGL GT2)
• Disk Capacity: (null)

Software Information:

• Firmware Version: X421EAY.308
• OS Name: Fedora Linux 44.20260424.n.0 (Silverblue)
• OS Build: (null)
• OS Type: 64-bit
• GNOME Version: 50
• Windowing System: Wayland
• Kernel Version: Linux 6.19.10-300.fc44.x86_64

[maniacx]

@neildarlow

pkexec /usr/local/bin/batteryhealthchargingctl-$USER CHECKINSTALLATION /home/$USER/.local/share/gnome-shell/extensions/Battery-Health-Charging@maniacx.github.com/resources $USER
echo $?

Can you test this command?
It should not ask for a password / Polkit authentication dialog

[neildarlow]

Battery Health Charging: checking rules !
Battery Health Charging: checking ctl !
Battery Health Charging: installation is up to date
0

That looks OK. It just seems to be too-short of a timeout for the initial check.

[neildarlow]

I spoke too soon. Logging-out and back in again presents the authentication dialog again which times-out as before,

[neildarlow]

Re. your earlier request to check the pkexec command, it does present a PolKit Authentication dialog.

[maniacx]

@neildarlow
Just tested on extension on the latest fedora SilberBlue on a VM to check if something changed in silver blue.
It works out of the box. It doesn't ask for password which means polkit rules for extension applied correctly.

How are you installing the extension?
Did you make changes to shell environment or polkit rules configuration?

[neildarlow]

Interesting. The extension install was a new one:

1. From extensions.gnome.org using Chromium with GNOME extensions integration
2. There were no polkit-1/rules.d entries before the installation
3. My environment additions are just for PIPEWIRE_LATENCY and FLATPAK_ENABLE_SDK_EXTENSIONS

The polkit rules are being installed correctly but, it seems, pkexec is prompting for authentication always which, I believe, is default behaviour unless measures are taken to prevent it.

The only other thing I can think of is that I use Ptyxis as my GNOME terminal. I had used this extension a while back without any of these issues so, unless the installation check is a new thing or has been changed, it must be a difference in Silverblue.

I'll take another look after official fedora 44 release when updates start flowing freely again but, for now, I can't use the extension.

I guess you'll have to mark this as "works for me".

[maniacx]

Try to debug polkit rules.
Check if the installation of polkit rules are correct

sudo -s
ls /etc/polkit-1/rules.d/

You should see a file 10-dem.batteryhealthcharging.setthreshold-${your_username}.rules

Example. My username is maniacx.

10-dem.batteryhealthcharging.setthreshold-maniacx.rules

view content of file

cat /etc/polkit-1/rules.d/10-dem.batteryhealthcharging.setthreshold-maniacx.rules

Expected

polkit.addRule(function(action, subject) {
    if (action.id === "org.freedesktop.policykit.exec" &&
        action.lookup("program") === "/usr/local/bin/batteryhealthchargingctl-maniacx" &&
        subject.user === "maniacx")
    {
        return polkit.Result.YES;
    }
});

Check if this action lookup program path is correct /usr/local/bin/batteryhealthchargingctl-maniacx and matches the path of ctl installed.
Also check if subject.user is your username.

[neildarlow]

Yes. Verified all that as correct. The installation is obviously correct it's errant runtime behaviour.

[maniacx]

@neildarlow

Ok. I made a mistake. I was not aware, SilverBlue had a beta version and that you were using beta version.
My earlier testing was on SilverBlue 43. But later I realized that I am not on Gnome 50 but 49. And digging a bit found out that there was a beta version with Gnome 50.

Anyways I found the issue with SilverBlue 44. Now I am not sure if it is an bug or intentional. I created a new issue. Let discuss further here. #194