Muvm : X application authorization protocol error

Our Neighbors Asahi Linux Ask Asahi
1

hello
It was announced recently a very nice capability to run a small vm. However I can’t figure how to set it up.

muvm is able to start terminal related applications. I have tried htop, cmus, or directly sh and they are working as expected. But with all X applications, something goes wrong, an Authorization is missing

$ muvm – xclock
Failed to set the new pressure in the guest: could not connect to muvm server: Connection refused (os error 111)
No IPv6 nameserver available for NDP/DHCPv6
Using default interface naming scheme ‘v255’.
/usr/lib/udev/rules.d/90-alsa-restore.rules:16 GOTO=“alsa_restore_std” has no matching label, ignoring.
/usr/lib/udev/rules.d/90-alsa-restore.rules:16 The line has no effect any more, dropping.
/usr/lib/udev/rules.d/90-alsa-restore.rules:20 GOTO=“alsa_restore_std” has no matching label, ignoring.
/usr/lib/udev/rules.d/90-alsa-restore.rules:20 The line has no effect any more, dropping.
Authorization required, but no authorization protocol specified
Error: Can’t open display: :1
“xclock” process exited with status code: 1

1 Like
2

ok, the short answer was a missing permission to launch X application

xhost +SI:localuser:$(whoami)

2 Likes
3

if you’re using GNOME this should be fixed by muvm-0.2.0-2, GNOME handles XAUTHORITY differently, see Commit - rpms/rust-muvm - 8c01f90c3c3926e5440305bb0d2e05289c76a81b - src.fedoraproject.org

If muvm-0.2.0-2doesn’t fix the issue and you’re using a different compositor / window manager please provide the output of xauth list on the host.