Summary: | defect when clicking icon in systray | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | old_man999 |
Component: | System Tray widget | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | answer2019, bugseforuns, karl.mistelberger, kde, kyle413 |
Priority: | NOR | Flags: | old_man999:
Wayland-
old_man999: Brainstorm- old_man999: Translation_missing- |
Version: | 5.13.2 | ||
Target Milestone: | 1.0 | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Notification area settings
wrong applet openend Empty System Tray Entries |
Description
old_man999
2018-06-28 12:16:27 UTC
Recreating systray per Drag'n drop temporary resolves the issue. This obviuosly is triggered when I try to set some icons (indicators) to be shown always. I'm a bit confused, can you add some screenshots Created attachment 113645 [details]
Notification area settings
Set some notification to be shown always
Created attachment 113646 [details]
wrong applet openend
After some time the area with the hidden icons does not close properly.
When clicking on the speaker icon (or any non third party) the area with the hidden icon appears but nonfuntional. (I pinned it just for it to be captured by the screenshot)
Created attachment 113823 [details]
Empty System Tray Entries
I think I have the same issue. Expand system tray > click on any icon > Nothing happens. Expect to have applet related to icon load (i.e click on Networks > Available network connection load in applet).
Running plasmashell from shell shows the following error when hovering or clicking on any of System Tray icons.
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/items/AbstractItem.qml:84: TypeError: Type error
While issue is occurring right click System Tray > System Tray Settings > Entries is empty about 50% of the time. (see attachment)
Changing Settings > Entries > Visibility > Always triggers the bug. *** This bug has been marked as a duplicate of bug 396153 *** |