https://bugs.kde.org/show_bug.cgi?id=504025
--- Comment #3 from Arcisse <mahamoudarciss...@gmail.com> --- Subject: Battery Detection Issue on MacBook Pro 2017 with Garuda Linux (KDE Plasma 6.3.5) Hello, I am reaching out to report an issue I am experiencing with my MacBook Pro 2017 running Garuda Linux with KDE Plasma 6.3.5. Issue Description: The battery is not being detected correctly by the system: - The indicator remains constantly at 0%, even when the laptop is connected to a power source. - No information about the charging state or estimated battery life is displayed. - The system seems to completely ignore the battery, even after multiple reboots. Diagnostics Performed: - applesmc and mbpfan modules are installed. - The apple-smc-dkms module is not available during installation from AUR. - The command upower -i /org/freedesktop/UPower/devices/battery_BAT0 shows no relevant information. - lsmod | grep -i smc confirms that applesmc is loaded correctly. - dmesg | grep -i battery does not return any visible errors. Resolution Attempts: - Installed mbpfan for fan control: works as expected. - Activated applesmc: no changes in battery detection. - Looked for alternative drivers for battery management: no success. Additional Information: - Dual-boot setup with macOS Ventura (battery is detected properly under macOS). - Kernel version: Linux 6.14.5-zen1-1-zen. - Power management: TLP is used instead of power-profiles-daemon. I am available to provide additional logs or perform tests if needed. Thank you in advance for your assistance. Best regards, Arcisse On Tue, 13 May 2025 at 23:15 Arcisse Mahamoud <mahamoudarciss...@gmail.com> wrote: > I solved it. But now I am having issue with battery… > > On Tue, 13 May 2025 at 22:38 Nate Graham <bugzilla_nore...@kde.org> wrote: > >> https://bugs.kde.org/show_bug.cgi?id=504025 >> >> Nate Graham <n...@kde.org> changed: >> >> What |Removed |Added >> >> ---------------------------------------------------------------------------- >> CC| |n...@kde.org >> Resolution|--- |DOWNSTREAM >> Status|REPORTED |RESOLVED >> >> --- Comment #1 from Nate Graham <n...@kde.org> --- >> You're using a wide variety of 3rd-party theming systems and themes, plus >> an >> unsupported login manager; there's no real way to be sure that the issue >> in >> question wasn't caused by the theme itself changing in a way you find >> undesirable, or a bug in the theme or Kvantum, or something else. I'm >> afraid we >> can't help with this unless you can do some debugging yourself and >> demonstrate >> that the issue was caused by a flaw in any KDE code. >> >> Thanks for understanding! >> >> -- >> You are receiving this mail because: >> You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
