[PATCH] Set a flag property on the root window to say if the X server VT is active

An X11 client may need to know whether the X server virtual terminal is currently the active one. This change adds a root window property which provides that information. Intended interface user: the VirtualBox Guest Additions. Signed-off-by: Michael Thayer michael.tha...@oracle.com --- This is

[PATCH xf86-input-mouse] Do not drop the result of protocol detection

In MousePickProtocol() with protocol PROT_AUTO we probe for the protocol to use but drop the result in most cases. This was causing DEVICE_INIT and DEVICE_ON to fail to be called with the VUID protocol. Git history suggests that this code was originally meant to cover both PS/2 auto-detection

[PATCH] Add a return value to load_cursor_argb() to allow it to report failure

load_cursor_argb() may need to be able to fail and have the server fall back to a software cursor in at least the following circumstances. 1) The hardware can only support some ARGB cursors and this does not just depend on cursor size. 2) Virtual hardware may not wish to pass through a cursor to

Re: [PATCH libxtrans] Increase UNIX socket buffer size

Hi, On 03/29/2014 11:51 PM, Mark Kettenis wrote: From: Mark Kettenis kette...@openbsd.org Some systems provide a really small default buffer size for UNIX sockets. Bump it up to 64k if necessary such that large transfers (such as XGetImage() on a 8-megapixel image) don't take tens of

[ANNOUNCE] xtrans 1.3.4

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi All, I'm happy to announce xtrans-1.3.4 Hans de Goede (2): configure: Also add -D_DEFAULT_SOURCE to .pc cflags to shut up glibc warnings xtrans 1.3.4 Mark Kettenis (1): Increase UNIX socket buffer size Thomas Klausner (2):

[PATCH] Add pScreen-NameWindowPixmap hook

This hook allows drivers to be notified when a pixmap gains a new ID. (ABI break.) Signed-off-by: Daniel Stone dani...@collabora.com --- composite/compext.c | 6 ++ include/scrnintstr.h | 3 +++ 2 files changed, 9 insertions(+) Is this in time for the ABI break? It's for quite a niche

Re: [PATCH] config by seat

2014-03-28 15:41 GMT-03:00 Laércio de Sousa lbsous...@gmail.com: You'll need to take care with ServerLayout section. I've detected a small problem with your patch in a very particular situation: Consider a machine with two seats, seat0 and seat1. Suppose you only have a file

[PATCH xinit v3 3/3] startx: Under Linux start X on the current VT

When we let X allocate a new VT, systemd-logind will not recognize any processes running on this VT as belonging to a valid session (since there was no pam session opened on that tty). This causes problems like PolicyKit denials for these processes. ConsoleKit under Linux has been deprecated for

[PATCH xinit v3 1/3] Bump required util-macros version to 1.19

Signed-off-by: Hans de Goede hdego...@redhat.com --- configure.ac | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/configure.ac b/configure.ac index 3d5ea79..37eabfa 100644 --- a/configure.ac +++ b/configure.ac @@ -31,10 +31,10 @@ AC_CONFIG_HEADERS([config.h])

[PATCH xinit v3 2/3] Drop Replace $RAWCPPFLAGS with $TRADITIONALCPPFLAGS when processing cpp files

Various .cpp files containt things like #ifdef __APPLE__ and #ifdef __linux__ these have been broken (all #ifdef-s always seen as false) since: http://cgit.freedesktop.org/xorg/util/macros/commit/?id=d690e4a9febd07988d149a967791c5629c17b258 This commit makes these work again. Signed-off-by: Hans

[PATCH xinit v3 0/3] startx: Under Linux start X on the current VT

Hi All, Here is v3 of my patchset to make startx start X on the current VT under Linux. New in v3 is a patch to require version 1.19 of util-macros. If there are no objections I'll push this in a couple of days. Changelog: v2: -Use new $TRADITIONALCPPFLAGS to replace $RAWCPPFLAGS v3: -Drop:

Re: [PATCH] Xephyr: restore initial window resize lost in xcb conversion

On Wed, Mar 26, 2014 at 22:37:04 -0700, Keith Packard wrote: Julien Cristau jcris...@debian.org writes: The XResizeWindow call wasn't replaced by the xcb equivalent, so we were no longer setting the initial window size, only wm size hints. Regression from commit a2b73da Xephyr: start

Re: [PATCH] dix/dispatch: DoGetImage: Use a single buffer

On Sat, 2014-03-29 at 17:53 +0800, Daniel Kurtz wrote: Since we are now allocating from the heap, there should no longer be necessary, or desirable to chop up the DoGetImage() buffer. Maybe not necessary, but probably still desirable. In the PutImage direction we have a similar phenomenon:

Re: [PATCH] dix/dispatch: DoGetImage: Use a single buffer

On 03/29/14 02:53, Daniel Kurtz wrote: DoGetImage chops up an image into IMAGE_BUFSIZE strips. This predates commit [0] (a pull from XFree86 to X.Org), at which time IMAGE_BUFSIZE was 8k. Back then the immediate buffers were allocated with ALLOCATE_LOCAL(), so it made sense to try to keep them

[PATCH] dri3: Allow asynchronous implementation for dri3_open

By passing the client pointer to the dri3_open implementation, we allow the clients to implement the open callback asynchronously. If the client ignore count is positive after returning from dri3_open, we assume that authentication is in progress and doesn't send the reply. The code to send the

Re: [PATCH] dix/dispatch: DoGetImage: Use a single buffer

Aaron Plattner aplatt...@nvidia.com writes: Can't the max image size be multiple gigabytes? That seems a little large to describe as close to running out of heap space. The problem is that we're going to buffer that in memory anyway, down in the OS layer. The only alternative is to block