Bug 1836342 Comment 5 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Snap sets GDK_BACKEND=wayland by default on Wayland. Firefox' launch script currently `unset`s it.
$ sudo snap install gnome-terminal --edge
$ printenv | grep GDK_BACKEND
(=nothing)
$ snap run gnome-terminal -- bash -c "printenv | grep GDK_BACKEND; sleep 5"
> GDK_BACKEND=wayland
Revision 1 by
on 
Snap sets GDK_BACKEND=wayland by default on Wayland. Firefox' launch script currently `unset`s it.
$ sudo snap install gnome-terminal --edge
$ printenv | grep GDK_BACKEND
(=nothing)
$ snap run gnome-terminal -- bash -c "printenv | grep GDK_BACKEND; sleep 5"
> GDK_BACKEND=wayland

Edit:
So far I'm only aware of bug 1522780. Which child processes that doesn't support Wayland should Firefox try to launch inside the Firefox Snap?
Revision 2 by
on 
Snap sets GDK_BACKEND=wayland by default on Wayland. Firefox' launch script currently `unset`s it.
$ sudo snap install gnome-terminal --edge
$ printenv | grep GDK_BACKEND
(=nothing)
$ snap run gnome-terminal -- bash -c "printenv | grep GDK_BACKEND; sleep 5"
> GDK_BACKEND=wayland

Edit:
So far I'm only aware of bug 1522780. Which child processes that don't support Wayland should Firefox try to launch inside the Firefox Snap?

Back to Bug 1836342 Comment 5