You are not logged in.
Hello,
I've been having this problem for quite some time now, and Google doesn't seem to help either so I assume the problem must be on my end.
I use KDE Plasma, and any program I run on Wine (Staging) that has a system tray icon, does not react at all when I right click it. Double left click gives me nothing either. This only happens with Wine applications. Example of such programs: Steam or Ultracopier. This happens in both 32-bit and 64-bit Wine prefixes. I wasn't able to test it in a different Desktop Environment.
Using journalctl -f, I'm able to observe what happens when I run Ultracopier portable under a 64-bit prefix (http://files.first-world.info/ultracopi … .4.1.3.zip)
Sep 23 19:34:32 arch plasmashell[958]: QQuickItem::stackAfter: Cannot stack StatusNotifierItem_QMLTYPE_258(0x7fa8980131c0, parent=0x5628317f04e0, geometry=0,0 0x0) after StatusNotifierItem_QMLTYPE_258(0x562833f8baf0), which must be a sibling
And this is the message I get if I right click Ultracopier tray icon:
Sep 23 19:34:50 arch plasmashell[958]: Could not find DBusMenu interface, falling back to calling ContextMenu()
And after that nothing happens. If I keep right clicking it, the journal gets spammed with the above message.
Unfortunately, Google only gave me some old bug reports (that were already fixed) about these messages. In case someone is wondering, these are the libindicator libraries I have installed:
$ pacman -Qn | grep indicator
lib32-libappindicator-gtk2 12.10.0-9
lib32-libindicator-gtk2 12.10.1-6
lib32-libindicator-gtk3 12.10.1-6
libappindicator-gtk2 12.10.0-12
libappindicator-gtk3 12.10.0-12
libindicator-gtk2 12.10.1-7
libindicator-gtk3 12.10.1-7
Any help is appreciated. Thank you!
Last edited by guihkx (2019-12-18 21:44:15)
Offline
I have exactly the same problem too, for all wine apps (haven't seen any wine app that does not have this problem so far).
Killing/restarting xembedsniproxy does not help.
Last edited by hexchain (2018-09-29 11:50:55)
Offline
Do you happen to be using KDE as well? It appears to be the only desktop environment affected. For me it doesn't happen with vanilla wine though, only with staging. I've opened a bug report here:
https://bugs.winehq.org/show_bug.cgi?id=45899
Last edited by guihkx (2018-09-29 12:17:08)
Offline
Yes, I am also using KDE.
Offline
I guess I've found what the problem is. Please try the following :
1. Disable the KWin compositor (Alt+Shift+F12)
2. Launch any program using Wine that uses the system tray
3. Re-enable KWin (Alt+Shift+F12)
3. Try to interact with the tray icon (right clicking, left clicking) and see if it works now
That fixed the problem for me, but obviously it's not too much of a good solution.
Last edited by guihkx (2018-09-29 12:39:53)
Offline
That also fixed the problem for me.
So the problem just got even more interesting - now it has something to do with that patch in wine-staging and kwin compositing.
Last edited by hexchain (2018-09-29 12:25:28)
Offline
Yep. If you (or anyone else) is interested in fixing the wine-staging package yourself by disabling the patches that introduced this issue, follow these steps:
1. Install the asp package so you can get the wine-staging PKGBUILD:
sudo pacman -S asp
2. Export the wine-staging package:
asp export wine-staging
3. Navigate to the wine-staging directory you've just exported and disable the patch that introduces this problem:
cd wine-staging/
sed -i.old 's/--all/-W user32-Mouse_Message_Hwnd/' PKGBUILD
4. (Optional) To make compilation time less painful, you can specify the number of concurrent jobs that make will spawn to compile wine-staging faster.
I'd say an "okay" value is the number of threads your CPU has. In my case it's 4:
export MAKEFLAGS="-j4"
6. Now compile wine-staging and install the package afterwards:
makepkg -si
P.S. If you get an error message regarding missing PGP keys, you must import them to your local keyring by running:
gpg --recv-keys <key>
Last edited by guihkx (2018-10-02 15:18:14)
Offline
5. (Optional) To make compilation time less painful, you can specify the number of jobs that make will spawn to compile wine-staging faster.
I'd say an ok value is the number of threads your CPU has. In my case it's 4, so go ahead and append -j4 (or -j<a number>) to both lines 147 and 161.
https://wiki.archlinux.org/index.php/Ma … pile_times
that change works much better in makepkg.conf
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
Thanks! I've edited my post to include that. Once this bug gets fixed upstream, I'll mark this thread as [SOLVED] as well.
Offline