Bug 471969 - System Tray applet is not automatically closing on focus loss
Summary: System Tray applet is not automatically closing on focus loss
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: System Tray widget (show other bugs)
Version: 5.27.5
Platform: Debian stable Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-05 10:21 UTC by Peter van den Houten
Modified: 2023-09-14 18:45 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter van den Houten 2023-07-05 10:21:40 UTC
SUMMARY

The System Tray applet is not automatically minimizing after being clicked on and popping up. After any applet entry has been clicked on, the entry will pop up and display the relevant information, e.g. Networks will show the network information, Disks & Devices will show the attached drives.

The applet works OK but when finished viewing the information and clicking on the desktop or whatever program is running, the applet does not minimize back top the tray automatically - it used to, then something happened and it no longer functions correctly. Now, one has to click on the applet entry once again to minimize to the tray, otherwise it will stay on the screen.

STEPS TO REPRODUCE
1. Click on system tray applet (any entry)
2. Entry selected pops up correctly
3. Click on desktop, menu, running program, or anywhere else.

OBSERVED RESULT

System tray applet does not minimize after clicking elsewhere, only when clicking on applet entry again.

EXPECTED RESULT

System tray applet should minimize to tray when user has clicked elsewhere.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Debian GNU/Linux 12 - kernel 6.1.0-9-amd64 (64-bit)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION

Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz
Memory: 16 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4000
Comment 1 Nate Graham 2023-09-13 18:21:53 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?
Comment 2 Peter van den Houten 2023-09-14 08:32:24 UTC
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?
>
Comment 3 Nate Graham 2023-09-14 18:45:15 UTC
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.