Dear \[Support Team/Developer], I am writing to report an issue I encountered after performing an update and reinstallation of the `garuda-dr460nized` package on my **Garuda Linux** system. ### **Before the Update:** * OS: Garuda Linux x86\_64 * KDE Plasma Version: 6.3.4 * Window Manager: KWin (Wayland) * Login Manager: **cddm 0.21.0 (Wayland)** * Shell: Fish 4.0.2 * Color Themes: **Dr460nized (Sweet)** \[Qt], **Sweet-Dark** \[GTK2/3/4] ### **After the Update:** * OS: Garuda Linux x86\_64 * KDE Plasma Version: 6.3.5 * Window Manager: KWin (Wayland) * Login Manager: **sddm 0.21.0 (Wayland)** * Shell: Fish 4.0.2 * Color Themes: **Sweet \[Qt], Breeze-Dark \[GTK2], Breeze \[GTK3]** * Icons: **BeautyLine** \[Qt], **BeautyLine** \[GTK2/3/4] * System Fonts: **Fira Sans (10pt)** \[Qt], **Fira Sans (10pt)** \[GTK2/3/4] ### **Problem Description:** After the update and reinstallation of `garuda-dr460nized`, my color themes and certain desktop configurations were changed unexpectedly: * The **Dr460nized (Sweet)** theme was replaced with **Sweet \[Qt]** and **Breeze-Dark** for GTK2 and GTK3. * The login manager switched from **cddm** to **sddm**. * My previous settings and customization seem to have been overridden. I attempted to manually change the settings back using **Kvantum Manager** and **Appearance Settings**, but the issue persists. Konsole no longer reflects the Dr460nized theme properly. ### **System Information:** * Device: MacBook Pro 2017 (Mac-CAD6701F7CEA0921) * CPU: Intel Core i5-7267U @ 3.50 GHz * GPU: Intel Iris Plus Graphics 650 @ 1.05 GHz * Display: 2560x1600 @ 60 Hz Would you be able to provide guidance on how to restore the original **Dr460nized (Sweet)** configuration? Is there a way to safely revert to the previous theme and color settings without affecting the system stability? I appreciate any assistance you can provide. Thank you. Best regards, **Arcisse**
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!
Created attachment 181253 [details] attachment-1381476-0.html I solved it. But now I am having issue with battery… On Tue, 13 May 2025 at 22:38 Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=504025 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |nate@kde.org > Resolution|--- |DOWNSTREAM > Status|REPORTED |RESOLVED > > --- Comment #1 from Nate Graham <nate@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.
Created attachment 181276 [details] attachment-1662148-0.html 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 <mahamoudarcisse24@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_noreply@kde.org> wrote: > >> https://bugs.kde.org/show_bug.cgi?id=504025 >> >> Nate Graham <nate@kde.org> changed: >> >> What |Removed |Added >> >> ---------------------------------------------------------------------------- >> CC| |nate@kde.org >> Resolution|--- |DOWNSTREAM >> Status|REPORTED |RESOLVED >> >> --- Comment #1 from Nate Graham <nate@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. > >
bugs.kde.org is for reporting individual bugs in KDE software; it's not a support ticket system. If you've got a new issue, it needs a new bug report. In this case that sounds like an issue deeper in the software stack, and not in KDE code. So I would encourage you to reach out to your distro about it. Thanks for understanding!