search

microsoft / wslg

Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
MIT License
9.95k stars 300 forks source link

gnome-session not starting. #106

Open shah-xad opened 3 years ago

shah-xad commented 3 years ago

I am trying to start a gnome-session and it gives me this:


shahzad@shahzad-:~$ gnome-session
gnome-session-binary[1868]: WARNING: Using null backend for session tracking
SSH_AUTH_SOCK=/mnt/wslg/runtime-dir/keyring/ssh
SSH_AUTH_SOCK=/mnt/wslg/runtime-dir/keyring/ssh
SSH_AUTH_SOCK=/mnt/wslg/runtime-dir/keyring/ssh
Window manager warning: Unsupported session type
gnome-session-binary[1868]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Window manager warning: Unsupported session type
gnome-session-binary[1868]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
gnome-session-binary[1868]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
gnome-session-binary[1868]: CRITICAL: We failed, but the fail whale is dead. Sorry....
farrsite commented 3 years ago

I am experiencing the same thing.

Ammatarasu commented 3 years ago

I am also experiencing the same issue. I got a different error when doing whats in this https://gist.github.com/Ta180m/e1471413f62e3ed94e72001d42e77e22 guide. it now says: gnome-session-binary[6601]: ERROR: Failed to connect to system bus: Could not connect: No such file or directory aborting... Trace/breakpoint trap

KavyanshJain commented 3 years ago

@spronovo you had labled it Missing-Desktop-Dependencies so what are this missing dependencies, I am also having the same problem.

UGatgithub commented 3 years ago

@KavyanshJain as I understand it, there is a Parent (here gnome-session) to Child (gnome apps) DBUS dependency that wslg does not take care about yet which needs to get solved to become able to run a full blown distro resp. gnome-session under wslg without an additional Xserver / client setup. I think THE PARENT INIT PROCESS AND SHARED DBUS INSTANCE PROBLEM describes it quite well.

Alex6357 commented 2 years ago

I have the same issue. I ran export DISPLAY=$(cat /etc/resolv.conf | grep nameserver | awk '{print $2}'):0 export LIBGL_ALWAYS_INDIRECT=1 in https://gist.github.com/Ta180m/e1471413f62e3ed94e72001d42e77e22 Now when I start gnome-session, I got the same output. But it takes much longer than not running the code above.

gnome-session-binary[1219]: WARNING: Using null backend for session tracking
SSH_AUTH_SOCK=/mnt/wslg/runtime-dir/keyring/ssh
SSH_AUTH_SOCK=/mnt/wslg/runtime-dir/keyring/ssh
SSH_AUTH_SOCK=/mnt/wslg/runtime-dir/keyring/ssh
Window manager warning: Unsupported session type
gnome-session-binary[1219]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Window manager warning: Unsupported session type
gnome-session-binary[1219]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
gnome-session-binary[1219]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
gnome-session-binary[1219]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Hezhexi2002 commented 1 year ago

I have the same issue. I ran export DISPLAY=$(cat /etc/resolv.conf | grep nameserver | awk '{print $2}'):0 export LIBGL_ALWAYS_INDIRECT=1 in https://gist.github.com/Ta180m/e1471413f62e3ed94e72001d42e77e22 Now when I start gnome-session, I got the same output. But it takes much longer than not running the code above.

gnome-session-binary[1219]: WARNING: Using null backend for session tracking
SSH_AUTH_SOCK=/mnt/wslg/runtime-dir/keyring/ssh
SSH_AUTH_SOCK=/mnt/wslg/runtime-dir/keyring/ssh
SSH_AUTH_SOCK=/mnt/wslg/runtime-dir/keyring/ssh
Window manager warning: Unsupported session type
gnome-session-binary[1219]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Window manager warning: Unsupported session type
gnome-session-binary[1219]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
gnome-session-binary[1219]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
gnome-session-binary[1219]: CRITICAL: We failed, but the fail whale is dead. Sorry....

Hi.I also meet the same problem and I follow the link https://blog.csdn.net/DraemSky/article/details/120123595 but it give the output like below: gnome-session-binary[328]: WARNING: Using null backend for session tracking _IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root GNOME_KEYRING_CONTROL=/home/hezhexi2002/.cache/keyring-IJWTU1 GNOME_KEYRING_CONTROL=/home/hezhexi2002/.cache/keyring-IJWTU1 GNOME_KEYRING_CONTROL=/home/hezhexi2002/.cache/keyring-IJWTU1 SSH_AUTH_SOCK=/home/hezhexi2002/.cache/keyring-IJWTU1/ssh Window manager warning: Unsupported session type gnome-session-binary[328]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Window manager warning: Unsupported session type gnome-session-binary[328]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 gnome-session-binary[328]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly gnome-session-binary[328]: CRITICAL: We failed, but the fail whale is dead. Sorry.... so have you solved this error or not?

fdebijl commented 9 months ago

systemd is now available under WSL2, which fixes the issue in the OP https://devblogs.microsoft.com/commandline/systemd-support-is-now-available-in-wsl/

This raises a new issue, where gnome-session cant start because it can't reach the dbus:

** (process:92437): WARNING **: 14:51:48.001: Could not make bus activated clients aware of XDG_CURRENT_DESKTOP=GNOME environment variable: Could not connect: No such file or directory

If you initiate a dbus session manually with dbus-run-session gnome-session a window actually opens, but it's just an error screen: image