Firefox 82 uses "xwayland" Window Protocol instead of "wayland/drm"
Categories
(Core :: Graphics, defect)
Tracking
()
People
(Reporter: victor, Unassigned)
References
Details
Attachments
(1 file)
4.63 KB,
application/x-javascript
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0
Steps to reproduce:
- MOZ_ENABLE_WAYLAND=1
- Upgrade from firefox 81.0.2 to firefox 82
- Check Window Protocol in about:support
Actual results:
Firefox 82 uses "xwayland" as Window Protocol
Expected results:
Firefox 82 uses "wayland/drm" as Window Protocol. 81.0.2 did.
Comment 1•4 years ago
|
||
I am having a hard time reproducing this issue.
Can you help in expanding the steps to reproduce a little? I might be mistaking.
- Download Release v81.0.2.
- Open build folder in terminal.
- input:
MOZ_ENABLE_WAYLAND=1 firefox
and tap ENTER. - check about:support
I may be hitting another issue because, believe it or not, I am seeing version v82.0 on a v81.0.2 build if I open with it with MOZ_ENABLE_WAYLAND=1;
and I see 81.0.2 if I open it normally.
Can you please correct my steps to reproduce?
(In reply to Bodea Daniel [:danibodea] from comment #1)
I am having a hard time reproducing this issue.
Can you help in expanding the steps to reproduce a little? I might be mistaking.
- Download Release v81.0.2.
- Open build folder in terminal.
- input:
MOZ_ENABLE_WAYLAND=1 firefox
and tap ENTER.- check about:support
I may be hitting another issue because, believe it or not, I am seeing version v82.0 on a v81.0.2 build if I open with it with MOZ_ENABLE_WAYLAND=1;
and I see 81.0.2 if I open it normally.Can you please correct my steps to reproduce?
Thanks for picking this up :)
I don't have the resources to effectively compile firefox myself so i use the Nix package manager (but I don't think it matters much) and my steps are:
- install firefox 81.0.2
- MOZ_ENABLE_WAYLAND=1 firefox
- see in about:support that it selected "wayland/drm"
- upgrade to firefox 82
- MOZ_ENABLE_WAYLAND=1 firefox
- see in about:support that it has selected "xwayland"
Comment 3•4 years ago
|
||
The severity field is not set for this bug.
:jimm, could you have a look please?
For more information, please visit auto_nag documentation.
I can't reproduce this on firefox 83 fortuneately, so I am closing this :)
Updated•3 years ago
|
Comment 5•3 years ago
|
||
I am having the same issue on openSUSE Tumbleweed. It was fine while I run "Full Wayland" session but because of massive incompatibility issues I selected "Wayland" session instead. Wayland is available as I can see from KDE System Information. I have put MOZ_ENABLE_WAYLAND=1 to /etc/environment and just to make sure I have tried 'MOZ_ENABLE_WAYLAND=1 firefox' in a shell. No change at all. This is Firefox 88.0.1 on openSUSE TW.
Description
•