#VMWare Workstation - Post install & first boot up error "Xsession: unable to launch"

35 messages ยท Page 1 of 1 (latest)

silent elk
#

Hey there. I have been trying to get Vanilla OS to run in VMWare Workstation 17.6.3 but keep encountering the same error, when loading into the OS for first time after install:

"Xsession: unable to launch "env GNOME_SHELL_SESSION_MODE=firstsetup gnome-session -- session=firstsetup" X session --- "env GNOME_SHELL_SESSION_MODE=firstsetup gnome-session -- session=firstsetup" not found; falling back to default session."

The install ran & completed just fine, prompted me to reboot, load into "Current Stats - A" but gives this error when starts to load desktop.
Any help please?

VM Specs:
Normal VanillaOS install option
4GB memory
2 Processors
100GB VHD
Hardware acceleration - off

silent elk
#

They there. I am still looking for help with this is anybody can lend a hand please. Many thanks ๐Ÿ™

mortal marsh
#

I have vmware workstation 17, I will give this a try and update you here in a bit.

patent valley
silent elk
#

I am checking the site again but not seeing a VM download option. Only the iso

patent valley
patent valley
silent elk
silent elk
#

I can"t see it

patent valley
#

You're gonna need to boot the installer again, and select Install Custom Image (Advanced).
When it asks for the image, specify ghcr.io/vanilla-os/vm:main (edit: corrected x2)

patent valley
silent elk
#

great thanks ๐Ÿ™ I will try this

patent valley
#

Seems to be installing now. The URL is ghcr.io/vanilla-os:vm

coral oasis
#

I don't think that will fix the issue.

patent valley
coral oasis
patent valley
silent elk
patent valley
#

I can't confirm that it worked for me because my VM is still busy installing

silent elk
#

Oki doki ๐Ÿ‘Œ Maybe it takes longer to install via the custom install with URL method

patent valley
# silent elk

same actually. I might still have the url wrong ๐Ÿซ 

silent elk
#

no worries. If it doesn't work it doesn't work . Thanks anyways with the advice ๐Ÿ™

patent valley
#

Did the installer show you the 'Do you want to install VM Tools' screen at all? @silent elk

silent elk
#

I gave up on the install - Didn't progress any further .
I had the yellow bar at bottom when I first booted the VM with "Install your OS as you usually would ...(blah blah blah) I didn't remember if that was for the VMware tools

patent valley
patent valley
coral oasis
#

Not sure, I think the issue is with the graphics driver for the hardware accelleration of the VM being used.

It's trying to use the X session instead of the default wayland session for some reason.

#

Since we got rid of the custom session in the new first setup it should work just fine in the next upgrade.

patent valley
#

Alright, first:
Did some more trail and error. I figured out the reason for the hang is indeed a wrong custom-image url, so the correct url for the vm image is ghcr.io/vanilla-os/vm:main (<registry>/<org>/<package>:<tag>). Massive skill issue on my end. Since I didn't know of the VM-check in installer, this info is rather useless now because it will change to that image for you, if you choose to install VM Tools.
Second:
I spent waaay too much time to install VMware Workstation... to specifically install Vanilla... ๐Ÿคฃ
Anyways, I installed Workstation because I was using Hyper-V previously so I could eliminate the variable of the Hypervisor being the issue. I attached my .vmx config file if someone wants to recreate the VM, but I don't have anything to report other than 'It just worked'. I got through all installer steps, on both desktop and vm, and Wayland just works.
One thing was giving me troubles: booting the .iso without UEFI.
Anyways for graphics configs I...

  • enabled Accelerate 3D graphics
  • set VRAM to 512MB

Edit: I should add:

  • I was using the latest Workstation version 17.6.3-24583834 (and the latest VM Compatibility version)
  • The latest available Vanilla .iso (20250220)
  • No VMware Tools, just open-vm-tools in case of vanilla-os/vm
  • Debian 12 64-bit as my OS target
  • Used UEFI boot (I tried BIOS for science and it just hangs everywhere)
  • Was forced to run with side-channel migrations
  • Didn't try the Xorg session
  • Windows 11 as the Host OS