Bug 472003 - Clicking on apps' systray icons have no effect (regular applets work fine)
Summary: Clicking on apps' systray icons have no effect (regular applets work fine)
Status: RESOLVED UPSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: System Tray (show other bugs)
Version: master
Platform: Neon Linux
: NOR major
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL: https://codereview.qt-project.org/c/q...
Keywords: qt6
: 470583 471876 474642 (view as bug list)
Depends on:
Blocks:
 
Reported: 2023-07-06 12:35 UTC by Patrick Silva
Modified: 2023-09-19 20:04 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.5.3

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2023-07-06 12:35:21 UTC 
STEPS TO REPRODUCE
1. open any app with a systray icon, like Discord, OBS Studio, VLC player and others
2. click on the systray icon of the used app with any button
3. 

OBSERVED RESULT
nothing happens

EXPECTED RESULT
clicks produce an effect

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.240.0
Qt Version: 6.5.1
Graphics Platform: Wayland
Comment 1 Nate Graham 2023-07-15 17:29:22 UTC 
Cannot reproduce. Can you reproduce it with today's git master, Patrick?
Comment 2 Patrick Silva 2023-07-26 12:42:10 UTC 
The bug persists.
Comment 3 Nate Graham 2023-07-26 18:55:49 UTC 
*** Bug 470583 has been marked as a duplicate of this bug. ***
Comment 4 Nate Graham 2023-07-26 18:56:01 UTC 
*** Bug 471876 has been marked as a duplicate of this bug. ***
Comment 5 Nate Graham 2023-07-26 18:57:15 UTC 
Still cannot reproduce. Can you run `journalctl -f` in a terminal window and paste any output that appears there right after you click on any of these System Tray icons that aren't working?
Comment 6 Patrick Silva 2023-07-27 12:13:50 UTC 
the journal log does not print anything after reproducing the bug.
Comment 7 Nate Graham 2023-07-28 20:49:53 UTC 
Not sure how to proceed here without either a reproducible test case or any logs.
Comment 8 Kai Uwe Broulik 2023-08-01 18:38:00 UTC 
Cannot reproduce on KDE neon dev unstable with Qt 6.6 on today’s git master. Tried with discover notifier and various versions of VLC in both panel and hidden popup.
Comment 9 Patrick Silva 2023-08-01 19:54:23 UTC 
Weird. I have even created a bootlable usb flash drive with neon-unstable-20230730-1119.iso and I can reproduce using mouse and touchpad.
Clipboard and Media Player applets are unusable too - none of their buttons respond to clicks.
Comment 10 Yuking 2023-08-13 13:59:42 UTC 
The same problem exists in today's git codes. Kill xembedsniproxy, the clicks will works.
Comment 11 Patrick Silva 2023-08-13 14:18:05 UTC 
On neon unstable xembedsniproxy process restarts itself after being killed.
Comment 12 Yuking 2023-08-14 13:37:07 UTC 
(In reply to Patrick Silva from comment #11)
> On neon unstable xembedsniproxy process restarts itself after being killed.

Try Moving xembedsniproxy to a new place (not in PATH) and then killing it.
Comment 13 Yuking 2023-08-14 13:49:44 UTC 
(In reply to Patrick Silva from comment #11)
> On neon unstable xembedsniproxy process restarts itself after being killed.

Maybe it is only for wine programs.
Comment 14 Patrick Silva 2023-08-15 12:10:05 UTC 
Wine is not installed on my system. Plasma does not even start after moving /usr/bin/xembedsniproxy. It crashes repeatedly instead.
Comment 15 Nate Graham 2023-08-17 12:39:08 UTC 
Apparently caused by https://codereview.qt-project.org/c/qt/qtdeclarative/+/490152.
Comment 16 Kai Uwe Broulik 2023-08-17 21:31:34 UTC 
Qt bug, potential fix submitted at https://codereview.qt-project.org/c/qt/qtdeclarative/+/497473
Comment 17 Yuking 2023-08-19 14:00:36 UTC 
(In reply to Kai Uwe Broulik from comment #16)
> Qt bug, potential fix submitted at
> https://codereview.qt-project.org/c/qt/qtdeclarative/+/497473

Solved with this patch. THX.
Comment 18 Nate Graham 2023-09-19 20:04:06 UTC 
*** Bug 474642 has been marked as a duplicate of this bug. ***