Olá Pessoal
After updating the Gnome 42 boxes application on EndeavorOS on today’s date, the crashes started inside and outside the environment. It is only possible to return to the system by turning off the desktop by the button.
Is this a problem with gnome-boxes or gnome-system-monitor?
You could launch them in a terminal and see if you get some error messages.
Also, in order for the forum members who are able to help to have some idea please read the following
article and provide some system info and logs.
Thank you and good luck!
1 Like
Yes, it’s a problem with gnome-boxes.
Monitor was open to see why the high memory consumption.
Here is the requested log:
[edson@edson-p6540br ~]$ /usr/bin/gnome-boxes
(gnome-boxes:8717): Gtk-WARNING **: 11:31:53.164: GtkFlowBox with a model will ignore sort and filter functions
(gnome-boxes:8717): Gtk-WARNING **: 11:31:53.168: GtkListBox with a model will ignore sort and filter functions
Boxes-Message: 11:31:55.303: libvirt-machine.vala:259: Failed to connection to system libvirt: Não foi possível abrir qemu+unix:///system: falha ao conectar o soquete ao ‘/var/run/libvirt/virtqemud-sock-ro’: No such file or directory
(gnome-boxes:8717): GLib-GObject-WARNING **: 11:31:56.808: …/glib/gobject/gsignal.c:2692: handler ‘2843’ of instance ‘0x5565430c0450’ is not blocked
Crashes occur when using any of the created vms. Everything hangs, both when opening when we can open, and when closing the vms.
Note: This did not happen before the update:
Follow the system log.
11:40:33 opera: [7298:7298:0509/114033.624554
chrome_content_verifier_delegate.cc(240)] Corruption detected in extension bkdgflcldnnnapblkhphbgpggdiikppg installed at: /home/edson/.config/opera/Extensions/bkdgflcldnnnapblkhphbgpggdiikppg/2022.4.26_0, from webstore: 1, corruption reason: 1, should be repaired: 0, extension location: kInternal
11:40:33 gnome-shell: Can’t update stage views actor [:0x56546eabe900] is on because it needs an allocation.
11:40:33 systemd: app-gnome-org.manjaro.pamac.manager-0.scope: Consumed 29.306s CPU time.
11:40:32 dbus-daemon: [session uid=1000 pid=1432] Successfully activated service ‘org.gnome.Logs’
11:40:25 gnome-shell: [Blur my Shell] updated background for screenshot’s window selector
11:40:22 systemd: gnome-terminal-server.service: Consumed 2.813s CPU time.
11:40:19 virtqemud: End of file while reading data: Input/output error
11:38:46 kernel: audit: type=1334 audit(1652107126.442:156): prog-id=0 op=UNLOAD
11:38:46 kernel: BPF prog-id=0 op=UNLOAD
11:38:46 kernel: audit: type=1131 audit(1652107126.342:153): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-hostnamed comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
11:38:46 kernel: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-hostnamed comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
11:38:46 systemd: systemd-hostnamed.service: Deactivated successfully.
11:38:32 opera: [7298:7298:0509/113832.369333
11:38:16 systemd: Started Hostname Service.
11:38:16 dbus-daemon: [system] Successfully activated service ‘org.freedesktop.hostname1’
11:38:16 systemd: Starting Hostname Service…
11:38:16 kernel: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-hostnamed comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
11:38:16 kernel: BPF prog-id=40 op=LOAD
11:38:16 kernel: audit: type=1130 audit(1652107096.068:152): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-hostnamed comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
11:38:16 dbus-daemon: [system] Activating via systemd: service name=‘org.freedesktop.hostname1’ unit=‘dbus-org.freedesktop.hostname1.service’ requested by ‘:1.136’ (uid=1000 pid=1853 comm=“/usr/lib/xdg-desktop-portal-gnome”)
11:37:54 opera: [7298:7298:0509/113754.420749
11:37:41 Xorg: (EE) event3 - CHICONY HP USB Multimedia Keyboard: client bug: event processing lagging behind by 36ms, your system is too slow
11:36:57 opera: [7298:7298:0509/113657.776266
11:35:06 kernel: audit: type=1131 audit(1652106906.915:148): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-tmpfiles-clean comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
11:35:06 kernel: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-tmpfiles-clean comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
11:35:06 kernel: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-tmpfiles-clean comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
11:35:06 systemd: Finished Cleanup of Temporary Directories.
11:35:06 opera: [7298:7298:0509/113506.573051
11:33:49 Xorg: (EE) event3 - CHICONY HP USB Multimedia Keyboard: client bug: event processing lagging behind by 34ms, your system is too slow
11:33:31 opera: [7298:7298:0509/113331.781346
11:32:32 gnome-shell: Can’t update stage views actor [:0x56546d91dbe0] is on because it needs an allocation.
11:31:54 kernel: L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details.
11:31:42 systemd: Started VTE child process 8668 launched by gnome-terminal-server process 8637.
11:31:42 dbus-daemon: [session uid=1000 pid=1432] Successfully activated service ‘org.gnome.Terminal’
11:31:42 systemd: Starting GNOME Terminal Server…
11:31:42 dbus-daemon: [session uid=1000 pid=1432] Activating via systemd: service name=‘org.gnome.Terminal’ unit=‘gnome-terminal-server.service’ requested by ‘:1.381’ (uid=1000 pid=8632 comm=“gnome-terminal --window”)
11:31:42 systemd: Started Application launched by gnome-shell.
11:31:17 kernel: audit: type=1334 audit(1652106677.741:146): prog-id=0 op=UNLOAD
11:31:17 kernel: BPF prog-id=0 op=UNLOAD
11:31:17 kernel: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-hostnamed comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
11:31:17 kernel: audit: type=1131 audit(1652106677.661:143): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-hostnamed comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
11:31:17 systemd: systemd-hostnamed.service: Deactivated successfully.
11:31:09 pamac-manager: gdk_window_set_cursor: assertion ‘GDK_IS_WINDOW (window)’ failed
11:31:09 kernel: audit: type=1130 audit(1652106669.477:142): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=pamac-daemon comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
11:31:09 kernel: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=pamac-daemon comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
11:31:09 systemd: Started Pamac Daemon.
11:31:09 dbus-daemon: [system] Successfully activated service ‘org.manjaro.pamac.daemon’
11:31:09 systemd: Starting Pamac Daemon…
11:31:09 dbus-daemon: [system] Activating via systemd: service name=‘org.manjaro.pamac.daemon’ unit=‘pamac-daemon.service’ requested by ‘:1.151’ (uid=1000 pid=8520 comm=“/usr/bin/pamac-manager --gapplication-service”)
11:30:47 kernel: audit: type=1130 audit(1652106647.607:141): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-hostnamed comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
11:30:47 kernel: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-hostnamed comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
Need something else?
What is the output of:
systemctl status virtqemud.socket virtqemud-ro.socket virtqemud-admin.socket
?
1 Like
It’s this:
[edson@edson-p6540br ~]$ systemctl status virtqemud.socket virtqemud-ro.socket virtqemud-admin.socket
○ virtqemud.socket - Libvirt qemu local socket
Loaded: loaded (/usr/lib/systemd/system/virtqemud.socket; disabled; vendor>
Active: inactive (dead)
Triggers: ● virtqemud.service
Listen: /run/libvirt/virtqemud-sock (Stream)
○ virtqemud-ro.socket - Libvirt qemu local read-only socket
Loaded: loaded (/usr/lib/systemd/system/virtqemud-ro.socket; disabled; ven>
Active: inactive (dead)
Triggers: ● virtqemud.service
Listen: /run/libvirt/virtqemud-sock-ro (Stream)
○ virtqemud-admin.socket - Libvirt qemu admin socket
Loaded: loaded (/usr/lib/systemd/system/virtqemud-admin.socket; disabled; >
Active: inactive (dead)
Triggers: ● virtqemud.service
Listen: /run/libvirt/virtqemud-admin-sock (Stream)
lines 1-17/17 (END)
Try enabling and starting them and see if that will resolve the issue:
sudo systemctl enable --now virtqemud.socket virtqemud-ro.socket virtqemud-admin.socket
If this log can help me in something I would appreciate it in advance.
Log EndeavourOS Gnome 42 X11 - journalctl -b -0
OK
The result was the one below and I will check later if the crashes have stopped
[edson@edson-p6540br ~]$ sudo systemctl enable --now virtqemud.socket virtqemud-ro.socket virtqemud-admin.socket
[sudo] senha para edson:
Created symlink /etc/systemd/system/sockets.target.wants/virtqemud.socket → /usr/lib/systemd/system/virtqemud.socket.
Created symlink /etc/systemd/system/sockets.target.wants/virtqemud-ro.socket → /usr/lib/systemd/system/virtqemud-ro.socket.
Created symlink /etc/systemd/system/sockets.target.wants/virtqemud-admin.socket → /usr/lib/systemd/system/virtqemud-admin.socket.
[edson@edson-p6540br ~]$
1 Like
Crashes still occur at some point. @pebcak
I remember that:
When updating gnome-boxes, there was a conflict of qmeu or qemu, I don’t remember for sure, because it was a list and asked to replace and I clicked yes to update gnome-boxes, where I had to confirm. I think that could have been the problem too.
When you force the exit, it does not exit at all. Only by turning off the desktop by the power off button.
See the screenshots of screen crashes that still occur:
No best idea that ask trouble . if computer become un responsive ( stuck ) this better option
EDit… Probably most useful post on forum. imo
3 Likes
The keyboard also freezes, making it impossible to use the aforementioned keys.
Yes the package qemu has been replaced by qemu-desktop. See this thread:
I am not experiencing this issue. Let’s see if other gnome-box users would chime in with their experience.
In the meantime you could still try this:
Open two terminal windows. In one, run journalctl -f. In the other, launch gnome-boxes and start using your VMs. Observe any error messages.
Also run sudo dmesg and look for anything related to gnome-boxes, qemu, libvirtd, etc.
Might not hurt to run a filesystem check as well. Launch your EnOS’ installer usb and run a check on your system partition.
1 Like
Fully up to date, using qemu-desktop now (update that replaced qemu), running Gnome 42.1 and Boxes still works on my end, so it must be a very specific issue here not related to all Gnome users unfortunately.
1 Like
No it doesn’t. As long as the kernel is loaded in the memory, Magic SysRq key will work.
Have you enabled the Magic SysRq key? It won’t work if it is not enabled…
3 Likes
Yes, same here. Not experiencing any issues after the update.
Could be any number of system and configuration specific things.
1 Like
It could be a file system problem. Although the virtqemud error does not appear in the later posted journal log. I wonder why. Is it not the same boot?
Anyway, looking into the pacman log might provide more info about what exactly happened with package upgrade.
I couldn’t see anything too obvious in the journal log.
Unless we see some clearly relevant log message, we are just speculating, which is… fun BTW 
1 Like
as @Kresimir say … keyboard still work , you no see out put on screen of keyboard
1 Like
Seems to have a bit of trouble with metapackages anyway.
From Reddit:
Looks like there are a few issues with the new meta packages.
`qemu-desktop` for example has several packages in its `depends` field that are also included in its `optdepends` field.
Edit 10.5.2022
More information was received on this. Apparently done on purpose.
That is actually on purpose, as there would otherwise be no place to list all available qemu components. That’s why all qemu providers share the same optdepends (even if they require some or most of them), as it allows you to do
pacman -Qi qemuto show the reference of what is currently installed on a system.
1 Like
Not what I could see (only glancing through 
) or am I looking at wrong place?
https://archlinux.org/packages/extra/x86_64/qemu-desktop/
Dependencies (158)
- qemu-audio-alsa
-
qemu-audio-dbus
… - qemu-audio-alsa (optional) - for ALSA audio driver
- qemu-audio-dbus (optional) - for D-Bus audio driver
etc.
2 Likes