Doesn't start in VMware - Asked to enter username on Live CD

[press5]

Hi folks,

Using VMWare Fusion Pro 12.1.2 with the live iso manjaro-sway-21.1.0-210820-linux510.iso it seems login with manjaro/manjaro is impossible:

[boredland]

You should not even be seeing that prompt. Will have a look later.

[press5]

Thank you. Let me know if you need more information.

[boredland]

from your screenshot, there may be other things going wrong. I tested with gnome boxes and clearly had the behaviour from https://github.com/Manjaro-Sway/manjaro-sway/issues/56. So I'll fix that up and hope this makes it better for you too.

[boredland]

I can't really wrap my head around this. why would there be a basic login shell on tty2 and why are the credentials not valid. this is booting straight from the live cd?

[boredland]

hmmm. I am getting greetd in vmware, like in gnome boxes (can't loging before setting the variable mentioned in #56 though):

[press5]

@boredland this is booting straight from the iso image, yes.

[press5]

I see a new ISO generated from #56 - will try that and report back.

thank you again :)

[press5]

@boredland if this ever gives up or finishes I'll let you know what happens. :)

EDIT: Looks like it goes in a loop for some time. I stopped it, because it was making my laptop a very efficient warmer :)

[press5]

After playing with this a little more I get the loop behavior if I boot with the opensource option (in hindsight, this kind of makes sense) regardless of the state of 3D acceleration in VMWare.

If I select the proprietary drivers with 3D off, I get the behavior I reported last night (login on tty2, manjaro/manjaro doesn't work). Proprietary drivers & 3D on, it seems to loop here for a while:

Eventually we get to the point where it starts the greeter service (below), but at this point the VM appears to go unresponsive.

[boredland]

For me it doesn't work in VMware either. In Gnome Boxes / Qemu it now works even without 3d acceleration.

BUT: for me it stops at the greetd login, not in plain tty2. This is what I get if I start the current image in VMware player with the default grub setting, opensource drivers:

[boredland]

seems to be an upstream issue in sway on vmware, at least there's people experiencing that in void linux too: https://github.com/swaywm/sway/issues/5834 the oblivious workaround is trying it in a qemu based vm, like gnome boxes.

[boredland]

the iso works fine with vbox and the 3d accelerated graphics adapter by the way, so this seems to be a vmware issue only:

[boredland]

closing in favor of a comment in the readme caveats section