Bug 449841

Summary:	Interactive area of 3rd party tray icons stay on the left on Wayland
Product:	[Plasma] plasmashell	Reporter:	ryu.ketsueki
Component:	XembedSNIProxy	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	materka, mvourlakos, nate
Priority:	NOR	Keywords:	regression, wayland
Version:	5.24.0
Target Milestone:	1.0
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description ryu.ketsueki 2022-02-09 11:38:50 UTC

SUMMARY
A bit of a breakdown to explain it better. I use a Latte Panel on the top, with the system tray plasmoid on the right. Whenever a program like AnyDesk, ATLauncher or another one that displays a custom system tray icon is open before Latte, which happens often with autostart programs, the icon's interactive area stays on the first position it is rendered instead of the place it is visually. In my example of AnyDesk, it will be on the top left of the screen, even though the system tray and icons are close to the top right of the screen. This only happens if Latte starts after the said program is open. If it is the opposite, the interactive area of the icon is where it is meant to be. My guess is that the dock and panels appear on screen much before they are "unsquashed" to their right places.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20220206
KDE Plasma Version: 5.24.0
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.16.4-1-default (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-7020U CPU @ 2.30GHz
Memory: 11.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 620

Comment 1 Michail Vourlakos 2022-02-09 13:38:29 UTC

1. I can not understand, please provide a screenshot with more details
2. dont you have the same issue with plasma panels and systray? Latte does not change the behavior of applets

Comment 2 ryu.ketsueki 2022-02-09 16:44:36 UTC

(In reply to Michail Vourlakos from comment #1)
> 1. I can not understand, please provide a screenshot with more details
> 2. dont you have the same issue with plasma panels and systray? Latte does
> not change the behavior of applets

I hope this recording can clear things up. One update, however. I noticed it always happens regardless if the app started before or after latte. At least it does with the apps I could test with, AnyDesk and ATLauncher. Also seem to happen the same thing with Wine apps, in my case, the Battle.net Launcher. It may be related to how all those programs render their own form of tray icons. At the same time, programs like OBS Studio and Elisa, which use a more server-side kind of tray icon, are unaffected by this bug.

Recording of the bug:
https://youtu.be/Dz-OreC2EIM

Comment 3 ryu.ketsueki 2022-02-09 17:01:10 UTC

Actually, my bad. After testing this further, I noticed it's unrelated to Latte. I thought it was latte because I noticed how, at startup, it seems Latte does not render completely, with the components focused on one side of the screen. But it seem to be related to Wayland and the system tray applet itself. I'll correct the bug report now

Comment 4 Michail Vourlakos 2022-02-09 19:03:51 UTC

that looks like related to Plasma and Wayland and not Latte.

To confirm that this is not Latte fault:
1. Close Latte
2. Add a plasma default panel that contains a plasma systray by default
3. Check again with your apps, same issue will probably appear

Comment 5 ryu.ketsueki 2022-02-09 19:28:16 UTC

(In reply to Michail Vourlakos from comment #4)
> that looks like related to Plasma and Wayland and not Latte.
> 
> To confirm that this is not Latte fault:
> 1. Close Latte
> 2. Add a plasma default panel that contains a plasma systray by default
> 3. Check again with your apps, same issue will probably appear

That's what I did and I already changed the bug report away from latte. Sorry for that

Comment 6 Konrad Materka 2022-02-14 22:44:04 UTC

This is a duplicate of 433079. AnyDesk uses deprecated XEmbed which is currently not supported on Wayland (even on X11 it is supported in very "hacky" way).

For workaround please check:
https://bugs.kde.org/show_bug.cgi?id=448050#c4

*** This bug has been marked as a duplicate of bug 433079 ***