Bug 374651 - Tray based app cannot run properly
Summary: Tray based app cannot run properly
Status: RESOLVED UPSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-wayland (show other bugs)
Version: 5.8.5
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-06 19:19 UTC by Szymon Łągiewka
Modified: 2019-01-03 23:14 UTC (History)
4 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 Szymon Łągiewka 2017-01-06 19:19:02 UTC
I use MEGA (also known as MEGAsync, mega.nz) cloud synchronization. The app is set to autostart. On Wayland session the app will always notify about it not being able to find a system tray and that it will not function properly. The program keeps running (/usr/bin/megasync process is alive) but the tray icon is missing. Spawning MEGAsync from krunner opens the app's window but it's aligned all the way to the left whereas it should be opened nearby the tray. My tray is located on the right. The panel is on top edge of the screen.

When the process is killed manually, the app can be started with the icon in the tray. It's functional - clicking spawns the app's windows (again on the left, though).

Nearly all dialogs given by the application cannot be read and there's nothing I can do with them. It may be related to the screen being HiDPI (3200x1800 with 2x scaling). The dialogs are tiny and nearly no text is visible. I cannot take any actions. This includes:
- opening the app's windows selecting Syncs->Add sync->Dialog cannot be seen,
- opening a file share link (example from my cloud https://mega.nz/#!ZgQgHDZL!OeKVISti6vfcvBh85Z0rOj1jwi1fP0AZ9Jhx548T9Fc) and using Download with MEGAsync -> dialog is nowhere near being operational,
- settings menu

Under X - none of those issues happen.
Comment 1 Martin Flöser 2017-01-09 07:12:05 UTC
Is the app using native Wayland or Xwayland?
Comment 2 Szymon Łągiewka 2017-01-12 20:24:42 UTC
Error message had an X icon, so I presume it's running XWayland. Today I updated XWayland to 1.19 - same issues. Although without scaling on I can see more inside the windows.
Comment 3 Szymon Łągiewka 2017-06-09 23:09:01 UTC
Update with Plasma 5.10.1.

I stopped using the MEGA sync app on startup, but for the sake of this issue I wanted to test what is happening now.

Probably due to changes in scaling and forcing DPI for fonts, I can now see the entire error dialog: http://imgur.com/a/R1hTu.

And besides that - nothing changed. I need to kill the app process and start it again in order for it to appear in the tray and be accessible for any interaction.
Comment 4 Alexander Mentyu 2017-08-18 07:02:45 UTC
Confirming this bug in:

Distribution: Netrunner Rolling
KDE Plasma Version: 5.10.4
KDE Frameworks Version: 5.36.0
Qt Version: 5.9.1
Kernel Version: 4.9.43-1-MANJARO
OS Type: 64-bit
xorg-server-xwayland 1.19.3-3
wayland 1.14.0-1
wayland-protocols 1.10-1

Also i noticed that MEGAsync's settings window doesn't have KWin decoration and MEGAsync's settings window is displaying not with MEGAsync logo but with default Wayland icon in task manager.
Comment 5 Martin Flöser 2017-12-07 19:38:22 UTC
So the fact that it shows Qt window decorations says a lot. The application seems to ship it's own Qt and due to that our integration doesn't work. This could also explain why it doesn't find the systray.

If system Qt would be used, the app would work fine. My suggestion is to force the application to use xcb, then it should also find the systray.
Comment 6 David Edmundson 2019-01-03 23:14:20 UTC
If it bundles its own Qt, there's not much we can do.

Once they upgrade they'll get a Qt with built in SNI support.
Comment 7 David Edmundson 2019-01-03 23:14:54 UTC
We also don't force QT_QPA_PLATFORM anymore, so older Qt will use XCB by default anyway.