Summary: | System Tray applet is not automatically closing on focus loss | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Peter van den Houten <petervdh> |
Component: | System Tray widget | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | materka, nate |
Priority: | NOR | ||
Version: | 5.27.5 | ||
Target Milestone: | 1.0 | ||
Platform: | Debian stable | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Peter van den Houten
2023-07-05 10:21:40 UTC
That's very strange. Some questions for debugging purposes: 1. Does it happen in the Wayland session too, or only on X11? 2. How many screens do you have connected when this happens? 3. Are you using a non-default window activation policy (e.g. focus follows mouse)? 4. Are you using any 3rd-party themes, scripts, or KWin effects? 5. Are you using any window rules? The problem was solved by deleting the default bottom panel and re-creating it. To answer your questions: 1) Have not tried in a Wayland session; will change if the problem re-occurs. 2) Just a laptop screen or with external screen, makes no difference. 3) No - all defaults 4) No - all defaults 5) No - all defaults Thanks Peter On 13/09/2023 20:21, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=471969 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Summary|System Tray applet is not |System Tray applet is not > |automatically minimizing |automatically closing on > | |focus loss > CC| |nate@kde.org > Resolution|--- |WAITINGFORINFO > Status|REPORTED |NEEDSINFO > > --- Comment #1 from Nate Graham <nate@kde.org> --- > That's very strange. Some questions for debugging purposes: > 1. Does it happen in the Wayland session too, or only on X11? > 2. How many screens do you have connected when this happens? > 3. Are you using a non-default window activation policy (e.g. focus follows > mouse)? > 4. Are you using any 3rd-party themes, scripts, or KWin effects? > 5. Are you using any window rules? > Hm, thanks. If you can't reproduce the problem anymore, then unfortunately there is probably no way to debug it after the fact. Please do feel free to re-open this bug report if it happens again, though. |