Created attachment 557810 [details] emerge --info output When double-clickingon a VM in the overview, I get the error popup "Connection to <VMNAME> failed." Related log entries are: Dec 15 14:03:39 xps gnome-boxes[7550]: machine.vala:209: display Microsoft Windows 10 disconnected Dec 15 14:03:39 xps gnome-boxes[7550]: (spice-widget.c:2513):update_mouse_mode: code should not be reached The VM itself seems to be fine, I can see in the preview image that the OS is up and running. After some trial-and-error, I found a way to avoid this error: right-click the VM, open the Properties dialog, close it. However, the VM is not displayed, I get a grey window displayed, with the logs not complaining about a failed assertion: Dec 15 14:09:16 xps gnome-boxes[7550]: spice_main_channel_update_display_enabled: assertion 'channel != NULL' failed Dec 15 14:09:16 xps gnome-boxes[7550]: spice_main_channel_update_display: assertion 'channel != NULL' failed Dec 15 14:09:16 xps gnome-boxes[7550]: spice_main_channel_update_display: assertion 'channel != NULL' failed Dec 15 14:10:45 xps wpa_supplicant[441]: wlp2s0: WPA: Group rekeying completed with 24:65:11:9e:16:c4 [GTK=TKIP] Dec 15 14:10:51 xps org.gnome.Shell.desktop[785]: Window manager warning: last_user_time (9964528) is greater than comparison timestamp (9964527). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Dec 15 14:10:51 xps org.gnome.Shell.desktop[785]: Window manager warning: 0x1e00010 (Enter Bug:) appears to be one of the offending windows with a timestamp of 9964528. Working around... Dec 15 14:10:52 xps org.gnome.Shell.desktop[785]: Window manager warning: last_user_time (9964589) is greater than comparison timestamp (9964588). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Dec 15 14:10:52 xps org.gnome.Shell.desktop[785]: Window manager warning: 0x1e00010 (Enter Bug:) appears to be one of the offending windows with a timestamp of 9964589. Working around... The issue doesn't depend on guest OS. This makes the boxes pretty much unusable for me ATM; the workaround right now is to stick with virt-manager.
Can you try a newer version from the official gnome overlay? https://cgit.gentoo.org/proj/gnome.git/tree/gnome-extra/gnome-boxes
Indeed, no errors with =gnome-extra/gnome-boxes-3.26.4! Nice, thanks! Maybe a version bump in the main gentoo repo?
Soon, yes. Good to know only 3.26.4 helps too. That can get in earlier - 3.30 requires tracker-2 work to be concluded for main tree.
Yep, 3.26.4 could be updated immediately without any further changes on my system which has the stable Gnome from main repo running (with the only unstable exception being =gnome-extra/gnome-packagekit-3.24.0, to avoid the issue https://gitlab.gnome.org/GNOME/gnome-shell/issues/369). Both 3.28.5 and 3.30.3 requested unmerging of gnome-extra/nautilus-tracker-tags, so didn't try them out anymore. Thus an update to 3.26.4 was an easy fix.
nautilus-tracker-tags will be last rited soon, but that was a symptom of it pulling in the tracker upgrade (which doesn't provide that package anymore - used to be a split package from tracker tarball), which could break some main tree builds until taken care of.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b99ccc5e6df439ca83895ced05527d738a314a3b commit b99ccc5e6df439ca83895ced05527d738a314a3b Author: Mart Raudsepp <leio@gentoo.org> AuthorDate: 2019-01-23 11:30:50 +0000 Commit: Mart Raudsepp <leio@gentoo.org> CommitDate: 2019-01-23 11:30:50 +0000 gnome-extra/gnome-boxes: bump to 3.26.4 Bug: https://bugs.gentoo.org/673186 Package-Manager: Portage-2.3.52, Repoman-2.3.12 Signed-off-by: Mart Raudsepp <leio@gentoo.org> gnome-extra/gnome-boxes/Manifest | 1 + gnome-extra/gnome-boxes/gnome-boxes-3.26.4.ebuild | 106 ++++++++++++++++++++++ 2 files changed, 107 insertions(+)
So I assume this main tree commit should be fine too, to fix this up. I guess this is a trouble for many people, and we should aim to stabilize at least this version soon, despite the rest of GNOME 3.26 not going to be stabled?
I would propose to close this issue as fixed or obsolete, the issue was gone with the update to 3.26.4 and I did observe no regression after (now) months of using the 3.30.3 from the main tree. No regression also after the today's update of gnome-base/gnome to 3.32.2.
Thank you for following up :)
