[SOLVED] Reverting back to Wayland after ujust setup-virtualization
I set up virtualization and enabled VFIO, but later learned that it's difficult to GPU passthrough on my laptop. So I went and disabled VFIO using the ujust command, but every time I reboot/login, it starts in an X11 session rather than Wayland. I'd like to keep virt-manager/kvm/qemu etc and Wayland at the same time.
Solution:Jump to solution
Maybe the trick was the full poweroff. All the other attempts were restarts
46 Replies
The X11 session rather than Wayland is an option that you choose at login, enabling virtualisation shouldn't change that at all. In your login screen, in the bottom left hand corner select "Plasma" instead of "Plasma (X11)" for KDE and bottom right hand corner in Gnome.
Note that if you have an Nvidia GPU might might have some issues such as flickering etc if you use Wayland until the Nvidia 555 drivers move to stable release
i don't get that bottom right hand corner button on the gnome login screen
That's really odd, are you perhaps using a custom login skin/theme? Where are you seeing that you are in an X11 session rather than Wayland?
i'm on bazzite-gnome-nvidia
no custom login skin, and i see it in settings, system details
do you not have a user password?
i do have a password
gear icon should be bottom right of the login screen after picking your user
one second
that is extremly weird
It's also weird that you have X11 available at all, you have an AMD GPU. What image are you using? could you please run
rpm-ostree status?amd igpu, nvidia dgpu
Ah ok, makes sense why you have X11 available but no clue why you cannot select Wayland. There was a ticket a while back where someone also couldn't select wayland due to bios setting of custom udev rule. Let me see if I can find it
Have a look as M2's answer in this ticket https://discord.com/channels/1072614816579063828/1237406854863130714/1238104694304280678 either way looks like your machine is falling back on to X11 for some reason
there isn't a no-wayland file in /run/gdm
If you try restarting is the wayland option also not there? In the login I mean. In the other ticket, the Wayland option was sometimes there and sometimes not
when i restarted the option wasn't there
no idea why the wayland option is gone as vfio does not touch that.
also there is a 90% chance the nvidia gpu is a 3D controller and not a VGA controller, meaning passthrough would never be possible anyway.
and if it was a VGA controller, you would only get the passthrough output using an external monitor (or dummy plug+looking-glass)
the only thing i can think of is maybe compare the gdm config from
/etc with the one from /usr/etc? see if it has been changed somehow 🤔 /usr/etc should contain the originalokay, something weird, i shut down the laptop last night and went to sleep. after i powered it on it is now in the wayland session
weird laptop being weird
i restarted this laptop like 4-5 times last night
Solution
Maybe the trick was the full poweroff. All the other attempts were restarts
oh
New problem. Ever since I've set up virtualization. It seems like some programs randomly crash the session. I launched Dolphin and it crashed, I launched Spotify, also crashed.
Now the gear in the corner of the login screen lets me choose GNOME or GNOME on Xorg
it appears now, unlike before
you using dolphin in gnome?
yeah
ah ok
I'm on wayland now
idk about that since i dont use gnome myself but dolphin and everything works fine with virtualization enabled
shouldnt affect anything
seems to be random apps randomly crashing the session
make a new user and see if it happens on that too
i launched my bottles shortcut for foobar2000 for example and it crashed the session
that would be my first step to debug random apps crashing
is it a system problem or a user homefolder config problem
dolphin crashes the session for the other user
not the KDE file manager but the emulator
might be a gnome specific issue then 🤔 but nobody else has reported anything similar
i disabled vfio earlier, is there any remnants that could be interfering?
I noticed in flatseal dolphin had X11 windowing system enabled by default
Setting it to Wayland causes dolphin not to start, and enabling fallback to X11 does the same
Enabling X11 and disabling Wayland causes the session to crash
Noticing a pattern. Seems like flatpaks with X11 by default crash the session, where flatpaks with all 3 options or both X11/Wayland don't crash
switching to X11 seems more stable.
dolphin works under x11 session
nope its part of the kernel, just disabled by default
i have no idea what to do, it feels like ever since i ran those commands my system became less stable
well all the vfio command does is create the file
/etc/dracut.conf.d/vfio.conf with the list of drivers to load
and removing it deletes it
your problem is caused by something elseCould the "initramfs: regenerate" cause any issues? It gets enabled by one of the ujust virtualisation commands.
can disable that with
rpm-ostree initramfs --disable
but i highly doubt that is the cause as it doesnt do anything but include dracut stuff@SMNFXCN do me a favor and update
Let me know if it still happens
it works. i don't have the issue of x11 apps crashing on wayland anymore
Sweet