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

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

 



Hi

> 
> FYI: I have been running with the attached patch (not the inline above)
> to spice-gtk for one week now, and so has my colleague.  Dual monitor
> works perfectly.  There is one other crash scenario (xorg in guest
> crashes and won't restart) which sometimes happens consistently upon
> logging in.  This can be "fixed" by removing the file
> ~/.config/monitors.xml (in the guest).
> 
> I recommend strongly that the attached fix be included. I understand it
> is a "band-aid" but so is "fixme: goto whole" (see source code) which is
> broken by definition.

You are basically ignoring the surface_id from the monitor config with this patch. This isn't helping much, most probably this point out to invalid config, so I'd rather not do that and keep displaying the whole surface instead. Did you manage to trace back to where that surface id was generated? That's what I would do. It could be corrupted memory...

> I'm going to open a bug now on bugzilla with all my collected
> information - I can proceed no further with this without any assistance.

Yes, please.
_______________________________________________
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]