-
69cf5e40
by Christophe Fergeau
at 2017-02-08T15:23:56+01:00
Xspice: Use print("") instead of print ""
This allows Xspice to run when using python3 instead of python2
-
b9955a35
by Christophe Fergeau
at 2017-02-08T17:07:39+01:00
Xspice: Remove extra space before assignment
-
9a7eb40f
by Christophe Fergeau
at 2017-02-08T17:08:27+01:00
Xspice: Fix Python3 str() vs bytes() confusion
With python3, without universal_newlines=True, Popen().stdout.read()
will return a byte array, while find(str) expects to operate on a
string.
I've checked that this still works with python2 as well.
-
eaefd19b
by Francois Gouget
at 2017-04-06T10:42:33-05:00
Spelling fixes in the READMEs and configuration samples
Signed-off-by: Francois Gouget <fgouget@codeweavers.com>
Acked-by: Jonathon Jongsma <jjongsma@redhat.com>
-
aa4359f8
by Francois Gouget
at 2017-04-06T10:42:38-05:00
Spelling and typo fixes in some comments
Signed-off-by: Francois Gouget <fgouget@codeweavers.com>
Acked-by: Jonathon Jongsma <jjongsma@redhat.com>
-
0e86e9d2
by Frediano Ziglio
at 2017-04-07T18:35:44+02:00
Make some function static
Signed-off-by: Frediano Ziglio <fziglio@redhat.com>
Acked-by: Christophe Fergeau <cfergeau@redhat.com>
-
0728e085
by Frediano Ziglio
at 2017-04-07T18:35:46+02:00
Make some variables static
Signed-off-by: Frediano Ziglio <fziglio@redhat.com>
Acked-by: Christophe Fergeau <cfergeau@redhat.com>
-
78abd522
by Adam Jackson
at 2017-06-13T09:29:28-04:00
modesetting: Validate the atom for enum properties
The client could have said anything here, and if what they said doesn't
actually name an atom NameForAtom() will return NULL, and strcmp() will
be unhappy about that.
[copied from xserver d4995a3936ae283b9080fdaa0905daa669ebacfc]
Signed-off-by: Adam Jackson <ajax@redhat.com>
-
ee8f904a
by Dave Airlie
at 2017-06-19T11:18:35+02:00
qxl: call provider init
This prevents crashes when multiple QXL devices are configured in a VM.
https://bugzilla.redhat.com/show_bug.cgi?id=1428340
-
505a8bb0
by Jonathon Jongsma
at 2018-11-13T10:45:12+01:00
Make output name numbering 1-based
The QXL driver names its outputs starting at 0 (e.g. Virtual-0,
Virtual-1, etc). This code was presumably copy/pasted from a different
driver, and is not necessary for the QXL driver. Other drivers simply
use the kernel connector_type_id which starts at 1. For example, the
modesetting driver changed from 0-based names to 1-based names for the
same reason in xserver commit 139e36dd.
This will help to make it easier to identify which xrandr outputs belong
to which drm connector without requiring as many driver-specific
special-cases.
This change might effect custom xorg configurations that references a
specific output name. But the same change was made in modesetting driver
despite that possibility.
Signed-off-by: Jonathon Jongsma <jjongsma@redhat.com>
Acked-by: Frediano Ziglio <fziglio@redhat.com>
-
64cb597c
by Jonathon Jongsma
at 2018-11-13T10:55:03+01:00
Make output names match modesetting driver
The xrandr output name used by the QXL driver is based on the drm
connector type, but the names do not match the kernel names (see
/drivers/gpu/drm/drm_connector.c) or the modesetting driver names (see
hw/xfree86/drivers/modesetting/drmmode_display.c). Making these more
consistent will require less driver-specific special-case code if a user
wants to match an xrandr output to a drm connector.
Note that this patch should not actually change any behavior, since the
QXL driver only uses the 'Virtual' connector type, so this is done only
for consistency.
Signed-off-by: Jonathon Jongsma <jjongsma@redhat.com>
Acked-by: Frediano Ziglio <fziglio@redhat.com>
-
cf2254c1
by Victor Toso
at 2018-11-16T17:48:09+01:00
qxl: Initialize prev field while dup surface list
Otherwise we will can hit a segfault qxl_surface_kill()
│717 void
│718 qxl_surface_kill (qxl_surface_t *surface)
│719 {
│720 struct evacuated_surface_t *ev = surface->evacuated;
│721
│722 if (ev)
│723 {
│724 /* server side surface is already destroyed (via reset), don't
│725 * resend a destroy. Just mark surface as not to be recreated */
│726 ev->pixmap = NULL;│
│727 if (ev->image)│
│728 pixman_image_unref (ev->image);
│729 if (ev->next)
│730 ev->next->prev = ev->prev;
│731 if (ev->prev)
>│732 ev->prev->next = ev->next;
│733 free(ev);
│734 surface->evacuated = NULL;
│735 return;
│736 }
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1641793
Signed-off-by: Victor Toso <victortoso@redhat.com>
-
d92e9a8f
by Alan Coopersmith
at 2018-11-18T13:40:44-08:00
Update README for gitlab migration
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
-
e2981166
by Alan Coopersmith
at 2018-12-06T15:55:07-08:00
Update configure.ac bug URL for gitlab migration
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
-
922ec516
by Jeremy White
at 2019-04-06T08:09:31+01:00
Correct a long standing led state bug in XSpice.
The CtrlProc for our keyboard driver incorrectly mapped
the device private to a SpiceKbd* intead of to a InputInfoPtr.
That resulted in led state being written into the driver name
for our driver structure, instead of into the led state.
That, in turn, led to a cool bug where if you pressed caps lock,
the two second sync timer in the spice server would cause it to
attempt to correct the state by pressing caps lock to get the
states to match. Since the states will never match, the caps
lock effectively cycles on and off every two seconds.
Signed-off-by: Jeremy White <jwhite@codeweavers.com>
Acked-by: Victor Toso <victortoso@redhat.com>
-
52c421c6
by Adam Jackson
at 2020-02-05T12:59:48-05:00
qxl: Include only the dpms headers we need
dpms.h is provided by libXext, but nothing in our configure.ac is
verifying that we have libXext's headers. Fortunately we only need the
definitions in dpmsconst.h (which dpms.h included for us), which is in
xorgproto and thus implied by having an xserver DDK to build against.
And we're even trying to include dpmsconst.h when we think we have it,
meaning when HAVE_XEXTPROTO_71 is defined, but while many other drivers
define that macro in their configure.ac, we for no particularly good
reason do not. Oops. But since xextproto is about ten years old by now
we can probably just safely include it unconditionally.
-
1d8c0645
by Timo Aaltonen
at 2020-03-31T07:53:33+03:00
control: Migrate to x11proto-dev.
-
8600bd25
by Timo Aaltonen
at 2020-03-31T08:00:31+03:00
control: Migrate to debhelper-compat, bump to 12.
-
45a05a60
by Timo Aaltonen
at 2020-03-31T09:40:16+03:00
Build with python3.
-
48af07b3
by Timo Aaltonen
at 2020-03-31T09:40:30+03:00
Merge branch 'upstream-unstable' into debian-unstable
-
d90b17ec
by Timo Aaltonen
at 2020-03-31T09:41:15+03:00
bump version
-
93e5c199
by Timo Aaltonen
at 2020-03-31T10:03:52+03:00
python3.diff: Fix shebangs etc for python3.
-
35ea7bf0
by Timo Aaltonen
at 2020-03-31T10:03:58+03:00
Drop generated upstrean changelog, it wasn't shipped anyway.
-
b3399f31
by Timo Aaltonen
at 2020-03-31T10:40:11+03:00
docs: Updated.
-
01f4120d
by Timo Aaltonen
at 2020-03-31T12:03:13+03:00
control: Bump policy to 4.5.0.
-
818424dc
by Timo Aaltonen
at 2020-03-31T12:05:44+03:00
release to sid