Startup WM Class Wayland
Categories
(Core :: Widget: Gtk, defect, P2)
Tracking
()
People
(Reporter: scott.palmer, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0
Steps to reproduce:
Start Firefox 70.0b14 in Gnome-Shell 3.34 Wayland session.
Actual results:
Firefox started but the window that appears is not recognized as belonging to Firefox. A new entry is created on my dash with no icon.
Expected results:
The window should show up and be attached to Firefox.
in .desktop file: Startup WM Class=Firefox Beta
Window association works fine in Xorg session.
Comment 1•6 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
| Reporter | ||
Comment 2•6 years ago
|
||
You can see how I get one blank icon per tab.
In the example shown here. I have 2 tabs in one window and 1 tab in another window.
Comment 3•4 years ago
|
||
I can clearly state that this is fixed, running Nightly on Wayland under Ubuntu 21.10 with GNOME 40.
Comment 4•4 years ago
|
||
(In reply to Alexandre LISSY :gerard-majax from comment #3)
I can clearly state that this is fixed, running Nightly on Wayland under Ubuntu 21.10 with GNOME 40.
Is this really fixed?
I tried Nightly on Debian unstable.
WM_CLASS is still "firefox".
Anyway this seems to be duplicate of bug 1694928.
Comment 5•4 years ago
|
||
(In reply to Hideo Oshima from comment #4)
(In reply to Alexandre LISSY :gerard-majax from comment #3)
I can clearly state that this is fixed, running Nightly on Wayland under Ubuntu 21.10 with GNOME 40.
Is this really fixed?
I tried Nightly on Debian unstable.
WM_CLASS is still "firefox".
Anyway this seems to be duplicate of bug 1694928.
Here:
$ cat ~/.local/share/applications/Firefox-Nightly.desktop
[Desktop Entry]
Encoding=UTF-8
Version=1.0
Type=Application
Exec=env MOZ_ENABLE_WAYLAND=1 $HOME/bin/firefox/firefox %u
Icon=$HOME/bin/firefox/browser/chrome/icons/default/default128.png
Name=Firefox Nightly
Comment=Firefox Web Browser
StartupWMClass=firefox
X-Desktop-File-Install-Version=0.26
And I have no problem with the icon. Changing StartupWMClass to some other value, I have the problem.
So it sounds to me it is fixed. If it's not the case, then either we need to dupe it against this other bug, or it needs more infos.
Comment 6•4 years ago
|
||
(In reply to Alexandre LISSY :gerard-majax from comment #5)
(In reply to Hideo Oshima from comment #4)
(In reply to Alexandre LISSY :gerard-majax from comment #3)
I can clearly state that this is fixed, running Nightly on Wayland under Ubuntu 21.10 with GNOME 40.
Is this really fixed?
I tried Nightly on Debian unstable.
WM_CLASS is still "firefox".
Anyway this seems to be duplicate of bug 1694928.Here:
$ cat ~/.local/share/applications/Firefox-Nightly.desktop [Desktop Entry] Encoding=UTF-8 Version=1.0 Type=Application Exec=env MOZ_ENABLE_WAYLAND=1 $HOME/bin/firefox/firefox %u Icon=$HOME/bin/firefox/browser/chrome/icons/default/default128.png Name=Firefox Nightly Comment=Firefox Web Browser StartupWMClass=firefox X-Desktop-File-Install-Version=0.26And I have no problem with the icon. Changing
StartupWMClassto some other value, I have the problem.So it sounds to me it is fixed. If it's not the case, then either we need to dupe it against this other bug, or it needs more infos.
Sorry. My information was insufficient.
$ cat /usr/share/applications/nighlty.desktop
[Desktop Entry]
Type=Application
Name=Firefox Nightly
GenericName=Web Browser
X-GNOME-FullName=Firefox Nightly Browser
Comment=Browse World Wide Web
Exec=/home/hideo/firefox/firefox %u
Icon=/home/hideo/firefox/browser/chrome/icons/default/default128.png
Terminal=false
X-MultipleArgs=false
Categories=Network;WebBrowser;
MimeType=text/html;text/xml;application/xhtml_xml;application/x-mimearchive;x-scheme-handler/http;x-scheme-handler/https;
StartupNotify=true
StartupWMClass=Nightly
I set Nightly as StartupWMClass but actual WM_CLASS is firefox not Nighlty.
So I think this is not fixed.
Updated•4 years ago
|
Comment 7•4 years ago
|
||
(In reply to Hideo Oshima from comment #4)
Anyway this seems to be duplicate of bug 1694928.
Indeed.
Description
•