[willfish]

The battery applet previously exited when UPower reported no battery. #1370 changed the no-battery path to keep the applet alive so non-battery controls, including brightness controls and power profiles, remain accessible.

That exposed a follow-up UI problem: when no battery was present and no brightness control was available, the panel indicator fell back to the generic battery icon. On desktops without battery hardware this looked like a stray battery indicator, even though the applet still had useful power controls.

Use the existing plugged-into-power-symbolic icon as the no-battery fallback instead of showing a battery icon or hiding the applet. Display brightness and keyboard brightness icons still take priority when those controls are available, and battery systems continue to use the battery level icon.

Test plan

• Ran cargo fmt --check
• Ran cargo check -p cosmic-applet-battery
• Ran cargo clippy -p cosmic-applet-battery --all-targets
• Ran git diff --check

Note: the repo flake currently provides Rust 1.87, while current dependencies require Rust 1.93+. I ran the Rust commands with Fenix latest (rustc 1.98.0-nightly) inside the repo dev shell, with systemd.dev added for libudev.pc.

---

• I have disclosed use of any AI generated code in my commit messages.
  • If you are using an LLM, and do not fully understand the changes it is making to the code base, do not create a PR.
  • In our experience, AI generated code often results in overly complex code that lacks enough context for a proper fix or feature inclusion. This results in considerably longer code reviews. Due to this, AI authored or partially authored PRs may be closed without comment.
• I understand these changes in full and will be able to respond to review comments.
• My change is accurately described in the commit message.
• My contribution is tested and working as described.
• I have read the Developer Certificate of Origin and certify my contribution under its conditions.

[willfish]

@wash2, you look like the best person to sanity-check this area. Do these changes seem suitable for the battery applet behavior, or is there a better direction you would prefer?

[wash2]

@pop-os/ux just to confirm, is this alright?

[willfish]

@jklgrasso would you be able to take a look at this when you have a chance? It has been sitting for a while and already has a maintainer approval, so I would appreciate a review or guidance on what is needed to move it forward.