Discussion:
Bug#837499: virt-viewer & virt-manager's Spice viewer crash on first mouse click on GNOME+Wayland
intrigeri
2016-09-12 00:08:57 UTC
Permalink
Package: virt-viewer
Version: 4.0-1
Severity: normal

Hi,

on current Debian sid, running GNOME on Wayland, I start a Debian sid
desktop VM with libvirt/QEMU. It boots fine up to the graphical
interface, but as soon as I click somewhere it crashes. The exact
error message depends on how exactly I display the VM locally:

* using virt-manager's own Spice viewer:

python2: ../../../../src/cairo-surface.c:928: cairo_surface_reference: Assertion `(_cairo_atomic_int_get (&(&surface->ref_count)->ref_count) > 0)' failed.

* running a standalone virt-viewer:

../../../../src/cairo-surface.c:953: cairo_surface_destroy: Assertion `(_cairo_atomic_int_get (&(&surface->ref_count)->ref_count) > 0)' failed.

I've also seen in the Journal, around the time of the crash:

gnome-shell[11969]: (wayland/meta-wayland-surface.c:424):meta_wayland_surface_ref_buffer_use_count: runtime check failed: (surface->buffer_ref.buffer->resource)

Running virt-manager with GDK_BACKEND=x11 fixes this problem.

I've found no corresponding bug in upstream bug tracker
(https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&classification=Community&product=Virtualization%20Tools&query_format=advanced),
so I wonder if that's a known issue or something specific to my setup.

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages virt-viewer depends on:
ii libatk1.0-0 2.21.90-2
ii libc6 2.24-2
ii libcairo-gobject2 1.14.6-1+b1
ii libcairo2 1.14.6-1+b1
ii libgdk-pixbuf2.0-0 2.35.4-4
ii libglib2.0-0 2.49.6-1
ii libgovirt2 0.3.4-2
ii libgtk-3-0 3.21.5-3
ii libgtk-vnc-2.0-0 0.6.0-1
ii libgvnc-1.0-0 0.6.0-1
ii libpango-1.0-0 1.40.2-1
ii libpangocairo-1.0-0 1.40.2-1
ii librest-0.7-0 0.8.0-1
ii libsoup2.4-1 2.55.90-1
ii libspice-client-glib-2.0-8 0.32-1
ii libspice-client-gtk-3.0-5 0.32-1
ii libvirt-glib-1.0-0 0.2.3-2
ii libvirt0 2.2.0-1
ii libxml2 2.9.4+dfsg1-1+b1

virt-viewer recommends no packages.

Versions of packages virt-viewer suggests:
ii netcat-openbsd [netcat] 1.105-7
ii netcat-traditional [netcat] 1.10-41

-- no debconf information
--
intrigeri
Guido Günther
2016-09-12 19:48:10 UTC
Permalink
Post by intrigeri
Package: virt-viewer
Version: 4.0-1
Severity: normal
Hi,
on current Debian sid, running GNOME on Wayland, I start a Debian sid
desktop VM with libvirt/QEMU. It boots fine up to the graphical
interface, but as soon as I click somewhere it crashes. The exact
python2: ../../../../src/cairo-surface.c:928: cairo_surface_reference: Assertion `(_cairo_atomic_int_get (&(&surface->ref_count)->ref_count) > 0)' failed.
../../../../src/cairo-surface.c:953: cairo_surface_destroy: Assertion `(_cairo_atomic_int_get (&(&surface->ref_count)->ref_count) > 0)' failed.
gnome-shell[11969]: (wayland/meta-wayland-surface.c:424):meta_wayland_surface_ref_buffer_use_count: runtime check failed: (surface->buffer_ref.buffer->resource)
Running virt-manager with GDK_BACKEND=x11 fixes this problem.
I've found no corresponding bug in upstream bug tracker
(https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&classification=Community&product=Virtualization%20Tools&query_format=advanced),
so I wonder if that's a known issue or something specific to my setup.
I don't know about any such issues so it might be worth reporting this
upstream. Do we have a Waylland session available via gdm3 nowadays or
is there a specific setup required?
Cheers,
-- Guido
intrigeri
2016-09-12 20:20:41 UTC
Permalink
Hi,
Post by Guido Günther
I don't know about any such issues so it might be worth reporting this
upstream.
OK, I'll try to do that next time I try to switch to Wayland again (my
only other identified blocker is also related to
virt-{viewer,manager}, not reported yet). Thanks!
Post by Guido Günther
Do we have a Waylland session available via gdm3 nowadays
Yes :)

Cheers,
--
intrigeri
Guido Günther
2016-09-16 12:44:43 UTC
Permalink
control: tags -1 +help
Post by intrigeri
Hi,
Post by Guido Günther
I don't know about any such issues so it might be worth reporting this
upstream.
OK, I'll try to do that next time I try to switch to Wayland again (my
only other identified blocker is also related to
virt-{viewer,manager}, not reported yet). Thanks!
Post by Guido Günther
Do we have a Waylland session available via gdm3 nowadays
Yes :)
Great news! I just tried to reproduce and I don't see any crashes.

Cheers,
-- Guido

Loading...