Closed Bug 1588129 Opened 5 years ago Closed 5 years ago

MOZ_ENABLE_WAYLAND=0 and MOZ_ENABLE_WAYLAND=1 do the same

Categories

(Core :: Widget: Gtk, defect)

69 Branch
Unspecified
Linux
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: stanislavgeyko, Assigned: sawyerbergeron)

References

(Blocks 1 open bug)

Details

Attachments

(1 obsolete file)

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

Steps to reproduce:

  1. Launch Firefox on Linux using the command env MOZ_ENABLE_WAYLAND=1 firefox
  2. Launch Firefox on Linux using the command env MOZ_ENABLE_WAYLAND=0 firefox

Actual results:

  1. Firefox runs on Wayland
  2. Firefox runs on Wayland

Expected results:

  1. Firefox runs on Wayland
  2. Firefox runs on X11 (Xwayland)

I tested this behaviour on Gnome Shell.

Blocks: wayland
Component: Untriaged → Widget: Gtk
OS: Unspecified → Linux
Product: Firefox → Core

Source code seems to match the description.

    // Make X11 backend the default one unless MOZ_ENABLE_WAYLAND or
    // GDK_BACKEND are specified.
    disableWayland = (PR_GetEnv("GDK_BACKEND") == nullptr) &&
                     (PR_GetEnv("MOZ_ENABLE_WAYLAND") == nullptr);

Yes, please use "unset MOZ_ENABLE_WAYLAND" to disable it.

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX

(In reply to Martin Stránský [:stransky] from comment #2)

Yes, please use "unset MOZ_ENABLE_WAYLAND" to disable it.

I use "MOZ_ENABLE_WAYLAND" to launch Firefox on Wayland. However, when I want Firefox to use X11, I don't use this variable. It just seems illogical that both values do the same job. It might be a good idea to implement a new variable like MOZ_BACKEND for setting a needed backend.

Assignee: nobody → sawyerbergeron
Attachment #9197600 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: