On 05/07/2014 05:41 PM, David Mansfield wrote:
On 05/02/2014 09:05 AM, Marc-André Lureau wrote:
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
Hi
Thanks a lot for your analysis so far!
Adding David Airlie in CC
- Original Message -
I have an explanation for this, but not a fix. The fix needs to be made
by the owner of this code (Alon or Dave according to the header!)
The bug lies in qxl_display.c:qxl_crtc_mode_set. In
On 05/08/2014 10:59 AM, Marc-André Lureau wrote:
Hi
Thanks a lot for your analysis so far!
Adding David Airlie in CC
- Original Message -
I have an explanation for this, but not a fix. The fix needs to be made
by the owner of this code (Alon or Dave according to the header!)
The
Hi
- Original Message -
On 05/08/2014 10:59 AM, Marc-André Lureau wrote:
Hi
Thanks a lot for your analysis so far!
Adding David Airlie in CC
- Original Message -
I have an explanation for this, but not a fix. The fix needs to be made
by the owner of this code
- Original Message -
I have an explanation for this, but not a fix. The fix needs to be made
by the owner of this code (Alon or Dave according to the header!)
The bug lies in qxl_display.c:qxl_crtc_mode_set. In this method, there
is a conditional termed recreate_primary.
On Wed, Apr 16, 2014 at 06:32:30AM +1000, Lindsay Mathieson wrote:
Monitor resize is handled by the spice-vdagent app in the *guest* system, it
must be installed and running in the guest for that to work. It serves the
same purpose as the guest tools in vmware, virtualbox etc.
With a recent
On 04/16/2014 03:15 AM, Christophe Fergeau wrote:
On Wed, Apr 16, 2014 at 06:32:30AM +1000, Lindsay Mathieson wrote:
Monitor resize is handled by the spice-vdagent app in the *guest* system, it
must be installed and running in the guest for that to work. It serves the
same purpose as the guest
Hi All:
I'd like to be able to trace all events going back and forth between
spice server / client and also between Xorg driver (qxl) and spice
server regarding monitor connect resize etc.
The reason for this is that I'd like to debug why gnome3 works in dual
head setup but other desktop
- Original Message -
Hi All:
I'd like to be able to trace all events going back and forth between
spice server / client and also between Xorg driver (qxl) and spice
server regarding monitor connect resize etc.
The reason for this is that I'd like to debug why gnome3 works in
On 04/15/2014 10:35 AM, David Mansfield wrote:
Hi All:
I'd like to be able to trace all events going back and forth between
spice server / client and also between Xorg driver (qxl) and spice
server regarding monitor connect resize etc.
The reason for this is that I'd like to debug why
On Tue, 15 Apr 2014 10:35:32 AM David Mansfield wrote:
I'd like to be able to trace all events going back and forth between
spice server / client and also between Xorg driver (qxl) and spice
server regarding monitor connect resize etc.
Monitor resize is handled by the spice-vdagent app in
On 04/15/2014 04:32 PM, Lindsay Mathieson wrote:
On Tue, 15 Apr 2014 10:35:32 AM David Mansfield wrote:
I'd like to be able to trace all events going back and forth between
spice server / client and also between Xorg driver (qxl) and spice
server regarding monitor connect resize etc.
Monitor
12 matches
Mail list logo
