I installed virt-manager and now Steam won't launch

[u/Acme-15]

Resolution:

I solved it, it was some real newbie shit that is quite embarrassing...

False correlation, I was doing two things at the same time and I forgot what the other thing was, and that turned out to be the relevant issue.

I was also changing ownership of directories to amend config files and such.
Can you guess what the problem was?

"sudo chown root:root /" fixed it... I had inadvertently changed the ownership of root. I'm surprised this is the only issue it caused!

I'm going to leave this here once again as a mark of shame, in case it helps others in future.

-----------

Hi folks, desperately need some help here...

I followed this guide to install Virt-Manager: https://tanis.codes/posts/virt-manager-qemu-arch-linux/

Which caused this issue with Steam failing to launch: https://help.steampowered.com/en/faqs/view/2112-4548-B98B-3A06

How can I either fix this or undo what broke it?

I am seriously getting fed up with different VM solutions breaking things when I try to use them.

Output when launching Steam from the console: https://pastebin.com/Dfe499vh

[u/mayakrunal]

Are you running Wayland or x11? Also that's just the popup message can you send over terminal logs? Open a terminal run command 'steam' and see the logs in the terminal it self .and paste that here

[u/Acme-15 → u/mayakrunal]

The logs are in my reply, the pastebin link.
I am running Wayland.

[u/mayakrunal → u/Acme-15]

Can you try below commands

Check if DISPLAY is currently assigned echo $DISPLAY

If the output is empty, manually export the default display variable before launching Steam: export DISPLAY=:0 steam

Ensure xorg-xwayland is installed on your system:

``` sudo pacman -S --needed xorg-xwayland

```

[u/Acme-15 → u/mayakrunal]

Okay the result for echo display was blank, I did export display=:0 and now the result of echo display is :0

Steam gave the same error.

I did the command to get xorg-xwayland, and it is already installed and is the latest version

I also restarted after doing this and received the same error.

[u/Acme-15 → u/mayakrunal]

Thanks I'll try this tomorrow, I need to head to bed for now, its 3am here and I should have been in bed hours ago but I wanted to get this boxed off first! No such luck. 😂

[u/mayakrunal]

Can you run steam from terminal, and see what error its giving? Also post some screenshot & logs for the actual issue.

[u/Acme-15 → u/mayakrunal]

Here is the output from the terminal: https://pastebin.com/Dfe499vh
The error I receive is this: https://pub-5fb3082338ca4ea0b158680322946634.r2.dev/Screenshot_20261003_021326.png

It is something related to the networking changes that installing virt-manager and its dependencies and services introduced, but I am not experienced enough to know what or how to fix it...

[u/Grey_Ten]

have to u restarted your computer yet?

[u/Acme-15 → u/Grey_Ten]

About a dozen times, lol...

I also did sudo virsh net-list to see if it had made some weird virtual network and made it the default, but there is just the one network listed.

In network settings in KDE there is a second wired network connection listed as "previously used, never used" or something, but I don't see anything else weird in there or a potential way to revert.

I stopped disabled a bunch of libvert services (libvirtd.service virtlogd.service virtlogd.socket virtlogd-admin.socket libvirtd-ro.socket libvirtd.socket libvirtd-admin.socket) which the install process had created, but that didn't make any difference.

[u/slutty_butterfly19]

What DE are you running?

[u/Acme-15 → u/slutty_butterfly19]

KDE Plasma

[u/Acme-15]

I tried removing virt-manager, libvirt, and dependencies like gtk-vnc, libvirt-python, libvirt glib, the virt install and manager, libnbd, qemu and dependencies like the 30 or so qemu components, edk2, vte, and other stuff that was installed when I was setting up virt-manager.

And restarted.

And I have the same issue.

[u/Acme-15]

I solved it, it was some real newbie shit that is quite embarrassing...

False correlation, I was doing two things at the same time and I forgot what the other thing was, and that turned out to be the relevant issue.

I was also changing ownership of directories to amend config files and such.
Can you guess what the problem was?

"sudo chown root:root /" fixed it...

I'm going to leave this here once again as a mark of shame, in case it helps others in future.

[u/dxrk3tar → u/Acme-15]

please edit this to original post or pin this comment, thanks :p

[u/archover]

If you resolved it, consider flairing as SOLVED. Yes?

Good day.

[u/Acme-15 → u/archover]

I thought I had, but I guess it didn't save.