Closed
Bug 1190183
Opened 9 years ago
Closed 9 years ago
Firefox does not find the display on Wayland
Categories
(Firefox :: Untriaged, defect)
Firefox
Untriaged
Tracking
()
RESOLVED
DUPLICATE
of bug 635134
People
(Reporter: eldmannen+mozilla, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 Build ID: 20150620063927 Steps to reproduce: Attempted to launch Firefox on Weston, the reference Wayland compositor. $ ./firefox Actual results: Printed out the following in the terminal; Error: no display specified Expected results: Should have started Firefox and shown the Firefox browser window on the screen.
Confirmed. Latest Archlinux and Firefox Nightly from 8-17. Running GDK_BACKEND=wayland ./firefox results in Error: no display specified
Updated•9 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Comment 3•9 years ago
|
||
Was this report about finding the X11 display under Wayland, or about running directly under Wayland? Direct Wayland support is a way off, but it should be possible to make firefox automatically use the X11 GDK_BACKEND, assuming the DISPLAY env var is set.
(In reply to Karl Tomlinson (ni?:karlt) from comment #3) > Was this report about finding the X11 display under Wayland, or about > running directly under Wayland? > > Direct Wayland support is a way off, but it should be possible to make > firefox automatically use the X11 GDK_BACKEND, assuming the DISPLAY env var > is set. This bug was about running directly under Wayland.
You need to log in
before you can comment on or make changes to this bug.
Description
•