WM_CLASS not set up correctly when running as native Wayland client
Tor Browser uses
--class "Tor Browser" parameter to identify itself from plain Firefox windows, and this parameter doesn't work when running as native Wayland client.
The windows class is
firefox rather than expected
Steps to reproduce:
start-tor-browser.deskktopentry to include
MOZ_ENABLE_WAYLAND=1environment variable, in order to prefer Wayland client
start-tor-browser.desktopinto corresponding directory
- Start Tor Browser
What is the current bug behavior?
Tor Browser is started as native Wayland client, but the icon is a generic Wayland icon instead of Tor Browser's own. Furthermore, under certain desktop environments, window grouping and start new instance doesn't work at all, because the running Tor Browser isn't identified / linked to the desktop entry.
What is the expected behavior?
The running Tor Browser should be linked to the desktop entry.
Tor Browser should display its own icon, window grouping and start new instance should work.
windows class should be
- OS: Fedora Kinoite 36
- DE: KDE Plasma 5.24.5, Wayland session
- Software distribution: Downloaded directly from torproject.org (tor-browser-linux64-11.0.13_en-US.tar.xz)
This issue also occurs in unofficial distribution torbrowser-launcher, relevant issue
Relevant logs and/or screenshots
X11 client (under Wayland session, through XWayland)
A hotfix was implemented in tor-browser-build!466 (closed)