| Summary: | High CPU, even at idle, when Hide automatically for Panel | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Ingemar <reach.ingemar> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | nate |
| Priority: | NOR | ||
| Version First Reported In: | 6.3.5 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
attachment-2045207-0.html
attachment-2078022-0.html attachment-2684773-0.html |
||
Title:
High CPU usage when Panel set to “Hide Automatically” in Plasma — panel edge pixel triggers redraw
Product: Plasma Workspace
Component: KWin / Panel
Version: Plasma 6.3.5, KWin 6.3.5
OS: Arch Linux (kernel 6.14.7-5-cachyos)
Summary:
When the desktop panel is configured to “Hide Automatically,” CPU usage spikes from under 2% idle to around 12–15%. The issue appears related to a 1-pixel strip of the panel remaining visible at the screen edge, causing KWin to continuously redraw or poll input events.
Steps to Reproduce:
Set Panel style to “Hide Automatically”
Observe CPU usage at idle with e.g., top or htop
Workarounds include:
Pressing the Meta key (opening and closing the app launcher) resets CPU usage to normal
Cloning the current panel, placing it elsewhere, then deleting the original also resets the condition
Expected Result:
Panel hides fully without leaving a visible pixel strip, and CPU usage stays low when idle.
Actual Result:
A tiny visible pixel strip triggers continuous compositor activity and high CPU usage.
Additional Notes:
Occurs consistently on Arch Linux with Plasma/KWin 6.3.5 and kernel 6.14.7-5-cachyos.
Suspect compositor or panel hiding logic does not fully hide the panel or fails to notify KWin of state changes.
Some questions: 1. Does this happen in the X11 session, the Wayland session or both? 2. Does the issue reproduce in a new clean user account on the same machine, with the only customization being to configure the panel to auto-hide? Created attachment 181617 [details] attachment-2045207-0.html Hi, 1. On X11 for sure, not sure about Wayland, dont run that as much. 2. Yes, on new as well as used systems. (You can easily see the CPU load drop as soon as you go down to the Panel (and it drops up) or use Meta key) Ingemar Den ons 21 maj 2025 kl 18:09 skrev Nate Graham <bugzilla_noreply@kde.org>: > https://bugs.kde.org/show_bug.cgi?id=504617 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|REPORTED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > CC| |nate@kde.org > > --- Comment #2 from Nate Graham <nate@kde.org> --- > Some questions: > 1. Does this happen in the X11 session, the Wayland session or both? > 2. Does the issue reproduce in a new clean user account on the same > machine, > with the only customization being to configure the panel to auto-hide? > > -- > You are receiving this mail because: > You reported the bug. Created attachment 181622 [details] attachment-2078022-0.html and 3. Mostly, the bug/ situation will be introduced after a reboot. Then, as mentioned, you can make it go away by cloning the panel, then deleting it, and continuing when the new one. Den ons 21 maj 2025 kl 18:14 skrev Ingemar Åström <reach.ingemar@gmail.com>: > Hi, > > 1. On X11 for sure, not sure about Wayland, dont run that as much. > 2. Yes, on new as well as used systems. (You can easily see the CPU load > drop as soon as you go down to the Panel (and it drops up) or use Meta key) > > Ingemar > > Den ons 21 maj 2025 kl 18:09 skrev Nate Graham <bugzilla_noreply@kde.org>: > >> https://bugs.kde.org/show_bug.cgi?id=504617 >> >> Nate Graham <nate@kde.org> changed: >> >> What |Removed |Added >> >> ---------------------------------------------------------------------------- >> Status|REPORTED |NEEDSINFO >> Resolution|--- |WAITINGFORINFO >> CC| |nate@kde.org >> >> --- Comment #2 from Nate Graham <nate@kde.org> --- >> Some questions: >> 1. Does this happen in the X11 session, the Wayland session or both? >> 2. Does the issue reproduce in a new clean user account on the same >> machine, >> with the only customization being to configure the panel to auto-hide? >> >> -- >> You are receiving this mail because: >> You reported the bug. > > Aha, it's actually Bug 487895. *** This bug has been marked as a duplicate of bug 487895 *** Created attachment 181654 [details] attachment-2684773-0.html Nate, Aha, ok, thank's. Ingemar Den tors 22 maj 2025 kl 17:36 skrev Nate Graham <bugzilla_noreply@kde.org>: > https://bugs.kde.org/show_bug.cgi?id=504617 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Resolution|WAITINGFORINFO |DUPLICATE > Status|NEEDSINFO |RESOLVED > > --- Comment #5 from Nate Graham <nate@kde.org> --- > Aha, it's actually Bug 487895. > > *** This bug has been marked as a duplicate of bug 487895 *** > > -- > You are receiving this mail because: > You reported the bug. |
Title: High CPU usage when Panel set to “Hide Automatically” in Plasma — panel edge pixel triggers redraw Product: Plasma Workspace Component: KWin / Panel Version: Plasma 6.3.5, KWin 6.3.5 OS: Arch Linux (kernel 6.14.7-5-cachyos) Summary: When the desktop panel is configured to “Hide Automatically,” CPU usage spikes from under 2% idle to around 12–15%. The issue appears related to a 1-pixel strip of the panel remaining visible at the screen edge, causing KWin to continuously redraw or poll input events. Steps to Reproduce: Set Panel style to “Hide Automatically” Observe CPU usage at idle with e.g., top or htop Workarounds include: Pressing the Meta key (opening and closing the app launcher) resets CPU usage to normal Cloning the current panel, placing it elsewhere, then deleting the original also resets the condition Expected Result: Panel hides fully without leaving a visible pixel strip, and CPU usage stays low when idle. Actual Result: A tiny visible pixel strip triggers continuous compositor activity and high CPU usage. Additional Notes: Occurs consistently on Arch Linux with Plasma/KWin 6.3.5 and kernel 6.14.7-5-cachyos. Suspect compositor or panel hiding logic does not fully hide the panel or fails to notify KWin of state changes.