Arch Linux

archuser38013

Member

Registered: 2024-01-27

Posts: 96

[Solved] (virt-viewer:4895): GLib-GObject-CRITICAL; error after system

I make a vm in virt-manager using the wizard. I am using a livecd and all stock settings. The error seems to be related to gstreamer +/or spice. I looked for the error message online but could not find any solution so far.

Happened after full system update recently.

Full error after loading in virt-manager and it crashing the viewer and then retrying to view in sudo on command line

$  sudo virt-viewer vm

(virt-viewer:4895): GLib-GObject-CRITICAL **: 12:26:02.341: g_object_get_is_valid_property: object class 'GstAutoAudioSink' has no property named 'volume'

(virt-viewer:4895): GLib-GObject-CRITICAL **: 12:26:02.360: g_object_get_is_valid_property: object class 'GstAutoAudioSrc' has no property named 'volume'
Illegal instruction

Last edited by archuser38013 (2024-01-27 15:49:35)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,304

Re: [Solved] (virt-viewer:4895): GLib-GObject-CRITICAL; error after system

You're out of date, this has already been fixed

archuser38013

Member

Registered: 2024-01-27

Posts: 96

Re: [Solved] (virt-viewer:4895): GLib-GObject-CRITICAL; error after system

You're out of date, this has already been fixed

Thanks that did the trick.

Do you mind telling me what was at issue. Here is my update list and did not see any obvious packages pertaining to the problem. My guess would be coreutils.

:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (17) coreutils-9.4-3  gnupg-2.4.4-1  lib32-mesa-1:23.3.4-2
              lib32-vulkan-icd-loader-1.3.276-1  lib32-xz-5.4.6-1  libwpe-1.14.2-1
              mesa-1:23.3.4-2  orc-0.4.36-1  pacman-contrib-1.10.2-1  pangomm-2.48-2.50.2-1
              protobuf-25.2-1  python-jaraco.functools-4.0.0-1  python-markupsafe-2.1.4-1
              python-protobuf-25.2-1  vulkan-headers-1:1.3.276-1
              vulkan-icd-loader-1.3.276-1  xz-5.4.6-1

Last edited by archuser38013 (2024-01-27 15:50:32)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,874

Re: [Solved] (virt-viewer:4895): GLib-GObject-CRITICAL; error after system

The orc package got support for AVX2 optimised instructions, but that got erroneously enabled for systems that only support AVX and not AVX2, which is what got fixed by the update.

archuser38013

Member

Registered: 2024-01-27

Posts: 96

Re: [Solved] (virt-viewer:4895): GLib-GObject-CRITICAL; error after system

The orc package got support for AVX2 optimised instructions, but that got erroneously enabled for systems that only support AVX and not AVX2, which is what got fixed by the update.

Thanks. For future reference where do I go to check such information? Is it on the news page as stated in the wiki?

toblin

Member

Registered: 2025-01-03

Posts: 2

Re: [Solved] (virt-viewer:4895): GLib-GObject-CRITICAL; error after system

Hi there, I'm getting this issue which appears similar lately on a fresh install. I wondering if anyone any debugging tips?

$ sudo virt-viewer
[ALSOFT] (EE) Failed to connect PipeWire event context (errno: 112)

(virt-viewer:33627): GLib-GObject-CRITICAL **: 19:00:55.785: g_object_get_is_valid_property: object class 'GstAutoAudioSink' has no property named 'volume'

(virt-viewer:33627): GLib-GObject-CRITICAL **: 19:00:55.789: g_object_get_is_valid_property: object class 'GstAutoAudioSrc' has no property named 'volume'

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,874

Re: [Solved] (virt-viewer:4895): GLib-GObject-CRITICAL; error after system

Taken at face value, you probably lack pipewire-alsa, however you should configure a more apt audio backend like pipewire directly, and maybe also see: https://wiki.archlinux.org/title/Libvir … m_instance

Should the issue persist open a new thread, your issue has no relation to what the issue used to be in this.

toblin

Member

Registered: 2025-01-03

Posts: 2

Re: [Solved] (virt-viewer:4895): GLib-GObject-CRITICAL; error after system

Thanks for the tips! For anyone else who ever stumbles across this issue, the solution was to not run virt-viewer with sodu.
It works like this...

virt-viewer -c qemu:///system --your-vm-name-here--

Other notes:
When running virt-viewer from the CLI, it would only open the GUI with its 'found' VMs if i ran it with sudo. Without sudo it would not open the GUI and would instead open an error pop-up with "Failed to connect: No running virtual machine found".
However (as seen above) if you connect to the vm directly using the CLI it works a treat!

Thanks again for helping out V1del