Hello dear Maintainers.

I encountered a strange bug with the GNOME Shell.
To reproduce:

1) Set up a debian/devuan testing/sid vm with sysvinit.
2) Install gnome-core
3) Try to launch firefox(-esr) or thunderbird from a GNOME wayland session

Nothing happens. The process opens and terminates instantly. Neither KDE Plasma (wayland) exhibits this bug, nor GNOME on xorg, nor a wayfire session launched
via dbus.
Strangely firefox launches fine when MOZ_ENABLE_WAYLAND=1 is set. ktrip and kgeotag also fail to launch when forced on x11 with QT_QPA_PLATFORM=xcb.
My guess: Some weird xwayland quirk ? Xwayland is running.

Happy to provide more debugging. For now, it can be worked around by explicitly setting said env vars to force wayland
I haven't tested another init system. Sending this from my systemd machine in case you're wondering.

Regards,

Matthias Geiger

Hi Jesse,
Not really. Just the command idly running and nothing happens.
Probably. Starting the GNOME wayland session from sddm instead of gdm3 also doesn't make a difference. Running gdm I did a comparison of the processes and the same ones get executed on systemd:

root         645  0.0  0.0 240512  8576 ?        Ssl  13:42   0:00 /usr/sbin/gdm3
root        1961  0.0  0.0 165496  9384 ?        Sl   13:49   0:00 gdm-session-worker [pam/gdm-password]
werdahi+    2090  0.0  0.0 159456  5632 tty2     Ssl+ 13:49   0:00 /usr/libexec/gdm-wayland-session /usr/bin/gnome-session

I'm happy to provide more logs / get into debugging.

Regards

Matthias