Closed
Bug 1706480
Opened 4 years ago
Closed 4 years ago
Nightly 90 can only use XWayland
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1706452
People
(Reporter: hikaph+mozilla, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:87.0) Gecko/20100101 Firefox/87.0
Steps to reproduce:
I restarted Nightly to run with a newer build. My system runs Fedora 34 with MOZ_ENABLE_WAYLAND=1
set whenever launching Firefox.
Actual results:
- Nightly started with "window protocol" under
about:support
set toxwayland
(as opposed towayland
). - Nightly will actually fail to start if
${DISPLAY}
is unset in the environment.
Expected results:
I expect Nightly to start with direct Wayland support (and not via XWayland).
Reporter | ||
Comment 1•4 years ago
|
||
mozregression
suggests these three changes:
12:40.43 INFO: No more integration revisions, bisection finished.
12:40.43 INFO: Last good revision: 30af8f80e2754783f1981485dd911a2e341d9afd
12:40.43 INFO: First bad revision: f8eb1926bfdbb630b4aa17e064c3472c4a32709e
12:40.43 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=30af8f80e2754783f1981485dd911a2e341d9afd&tochange=f8eb1926bfdbb630b4aa17e064c3472c4a32709e
Comment 2•4 years ago
|
||
Possible duplicate of bug 1706452.
Reporter | ||
Comment 3•4 years ago
|
||
Reading over bug 1706452, it's definitely a dupe — thanks for pointing it out.
Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•