Open Bug 1599556 Opened 5 years ago Updated 3 years ago

[wayland] Using the wayland backend for nightly causes it to run as named 'firefox' not the nightly.

Categories

(Core :: Widget: Gtk, defect)

72 Branch
x86_64
Linux
defect

Tracking

()

UNCONFIRMED

People

(Reporter: shchurgood, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:72.0) Gecko/20100101 Firefox/72.0

Steps to reproduce:

Set MOZ_WAYLAND_ENABLE=1 in my environment allowing nightly to run with wayland as a backend. Then I started the program.

Actual results:

Nightly runs but it's program name is set as 'firefox', resulting in no icon if 'firefox' is not installed (since I only have nightly). It also shows up as firefox in all references to it.

Expected results:

Nightly should have its name set as 'nightly' or something of equivalent. This is what happens when nightly runs in X11 mode.

As a note, I am on Arch 5.3.13-arch1-1, nightly is 72.0a1 (2019-10-24). Gnome 3.34.1 is running under wayland. Using xprop to get the properties of x11 windows does not work on firefox, nor other Wayland windows as expected; however it does trigger on windows running under xWayland, showing that firefox is indeed in Wayland mode.

Severity: normal → minor
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
Summary: Using the wayland backend for nightly causes it to run as named 'firefox' not the nightly. → [wayland] Using the wayland backend for nightly causes it to run as named 'firefox' not the nightly.

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core
Severity: minor → S4
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: