Re: [PATCH] how can i trace monitor change (etc) events

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi

----- Original Message -----

> > (remote-viewer:12916): GSpice-WARNING **: FIXME: only support monitor
> > config with primary surface 0, but given config surface 5
> >
> > Which seems suspicious to me, given that these are followed
> > immediately by incorrect behavior and don't happen in GNOME3.
> >
> Ok. This is worse than suspicious.  It's the bug.  In the source
> gtk/spice-widget.c, right after this "FIXME" we goto "whole".  Maybe a
> guru can explain why we need to bail out here and display the whole
> framebuffer on the second monitor *on purpose*. However, the following
> patch works for me:

The code goto "whole" when the monitor configuration is invalid, because in this case, we don't know what to display, so we just display the "whole" primary surface 0.

Somebody needs to figure out why the monitor surface is 5, and if the server config is correct, then spice-gtk needs to learn to switch primary surfaces, which is currently not supported.
_______________________________________________
Spice-devel mailing list
Spice-devel@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/spice-devel




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]     [Monitors]