Bug 784542 - spicy crashes when run on a machine using Xinerama
Summary: spicy crashes when run on a machine using Xinerama
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: spice-gtk
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Christophe Fergeau
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-25 10:16 UTC by Hans de Goede
Modified: 2012-02-01 11:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-01 11:37:06 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Hans de Goede 2012-01-25 10:16:43 UTC
I hit this while testing the new spice-gtk-0.8 under a multi monitor RHEL-6 guest (yes I was testing spicy under a spice using vm ...). I believe this is caused by this setup using Xinerama since multi monitor Spice Linux guests are using Xinerama.

Simply starting spicy from such a vm causes it to crash immediately:
[hans@localhost ~]$ spicy -h 192.168.1.100 -p 5932
Xlib:  extension "RANDR" missing on display ":0.0".

(spicy:8177): GSpice-WARNING **: (spicy.c:1694):main: runtime check failed: (rrscreen != NULL)

(spicy:8177): GSpice-CRITICAL **: gnome_rr_screen_list_outputs: assertion `GNOME_IS_RR_SCREEN (screen)' failed
Segmentation fault (core dumped)

Comment 2 Marc-Andre Lureau 2012-01-25 12:31:02 UTC
Hans, can we move that bug to fdo, as spicy isn't really something we support and develop, rather an experimental client.

Comment 3 Hans de Goede 2012-02-01 11:37:06 UTC
Done:
https://bugs.freedesktop.org/show_bug.cgi?id=45489

Closing this one (see comment#2).


Note You need to log in before you can comment on or make changes to this bug.