Hi,
On 14 September 2016 at 11:47, Daniel Stone wrote:
> RedirectKey() action had been broken by commit 2e6190.
> A dropped check caused over-intense autorepeat of keysyms enriched
> with the action.
>
> Previous to this commit, the check wrapped the entire switch() block,
On 14.09.2016 12:07, Hans de Goede wrote:
Hi,
On 13-09-16 17:42, Michael Thayer wrote:
Currently if modesetting ever fails to set a hardware cursor it will
switch
to using a software cursor and never go back. Change this to try a
hardware
cursor first every time a new one is set. This is
From: Mihail Konev
RedirectKey() action had been broken by commit 2e6190.
A dropped check caused over-intense autorepeat of keysyms enriched
with the action.
Previous to this commit, the check wrapped the entire switch() block,
which was dropped with the move to a separate
Hi,
Here's the notes from Mihail, which I'd accidentally dropped whilst
passing this on.
Cheers,
Daniel
-- Forwarded message --
From: Mihail Konev
Date: 14 September 2016 at 07:45
Subject: [PATCH v2 xserver] xkb: fix turbo-repeat of RedirectKey-ed keysyms
To:
wl_display_flush() can fail with EAGAIN and Xwayland would make this a
fatal error.
When this happens, it means that Xwayland has flooded the Wayland file
descriptor, either because the Wayland compositor cannot cope or more
likely because of a deadlock situation where the Wayland compositor is
Hi,
On 14-09-16 15:53, Michael Thayer wrote:
On 14.09.2016 12:07, Hans de Goede wrote:
Hi,
On 13-09-16 17:42, Michael Thayer wrote:
Currently if modesetting ever fails to set a hardware cursor it will
switch
to using a software cursor and never go back. Change this to try a
hardware
cursor
On 09/07/16 17:15, Hans de Goede wrote:
> Hi,
>
> On 07-09-16 15:08, Laszlo Ersek wrote:
>> The new platform bus code and the old PCI bus code overlap. Platform bus
>> can handle any type of device, including PCI devices, whereas the PCI
>> code
>> can only handle PCI devices. Some drivers only
On 08/09/16 10:24 PM, Qiang Yu wrote:
> This fix is for the following xorg.conf can work:
>
> Section "ServerFlags"
> Option "AutoAddGPU" "off"
> EndSection
>
> Section "Device"
> Identifier "Amd"
> Driver "ati"
> BusID "PCI:1:0:0"
> EndSection
>
> Section
Hi,
On 13-09-16 17:45, Adam Jackson wrote:
On Tue, 2016-09-13 at 12:53 +0200, Hans de Goede wrote:
The following changes since commit 35c4e96ed1d372dd161480be8cddcd2d4549e449:
randr: Fix crtc_bounds when using rotation combined with reflection
(2016-09-13 10:27:30 +0200)
are available
Hi,
On 13-09-16 17:42, Michael Thayer wrote:
Currently if modesetting ever fails to set a hardware cursor it will switch
to using a software cursor and never go back. Change this to try a hardware
cursor first every time a new one is set. This is needed because hardware
may be able to handle
On Tue, 13 Sep 2016 12:04:14 -0400 (EDT)
Olivier Fourdan wrote:
> Hi Pekka,
>
> - Original Message -
> > Hi Olivier,
> >
> > I don't have any solution for you. The interactions between the Wayland
> > compositor and Xwayland are known to be very easily deadlockable
On Mon, Jun 13, 2016 at 03:31:13PM +1000, Peter Hutterer wrote:
> On Fri, Jun 10, 2016 at 04:32:19PM +0200, Stefan Dirsch wrote:
> > Bump up the vmmouse driver to 70, so it get's preferred over libinput, which
> > was dropped down to 60. This is only relevant for older kernels, which do
> > not
>
Keith Packard writes:
> [ Unknown signature status ]
>
> Following the 'release early and often' mantra, we should probably get
> 1.19 out the door and let people start using the new code.
>
> I'd like to propose that we figure out what remaining non-bug changes
> we'd like to
The dbus teardown code is called when the server fatal errors even if
that is before dbus has ever been initialized. By statically
initializing the value of bus_info.fd, we avoid calling RemoveNotifyFd
on stdin.
Signed-off-by: Keith Packard
---
config/dbus-core.c | 2 +-
1
14 matches
Mail list logo