Battery icon not displaying on Manjaro Linux
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
On Manjaro Linux, when I load up any menu driver that shows the battery icon, that icon doesn't show up upon having the setting enabled in User Interface
Expected behavior
Battery level appears next to Date and Time
Actual behavior
It only shows Date and Time
Bisect Results
This is after installing Linux on my machine, the battery icon displays fine when I loaded Retroarch on Windows, but not Linux.
My Windows partition currently has Lenovo Vantage installed, with the battery threshold enabled, which appears to still be active even upon booting into Linux.
Going into sys/class/power_supply/BAT/unevent shows this
https://cdn.discordapp.com/attachments/469974542299955210/711661681423679639/Screenshot_from_2020-05-17_12-28-45.png
I believe it is either some dependencies that are missing or Vantage is causing a conflict, though I do not know which one.
#Steps I took
- Confirm Battery level is set to enable in Retroarch
- Confirm if it occurs on battery power or AC (It occurs on both)
Version/Commit
- RetroArch: 1.8.6
- Snap Build: https://snapcraft.io/retroarch
Environment information
- OS: Manjaro Liux 5.6.11.1 Cinnamon
- Compiler: Snap
- Hardware: Lenovo Thinkpad 420
- Other Software: Lenovo Power Vantage (Windows), TLP, ACPI_Call (Linux)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the missing battery icon on Manjaro Linux 5.6.11.1 Cinnamon with RetroArch 1.8.6 from the Snap build and the reported settings. Inspect the reported sys/class/power_supply/BAT/unevent path and compare behavior on battery and AC power; done means identifying whether the cause is RetroArch, a missing dependency, or the listed power-management software.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- frontend, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100