Commit 37d956e3ac9513 initializes compat_output to -1, so
xf86CompatOutput would do config-output[-1] when not initialized.
This happens in xf86OutputSetEDID for example, before compat_output is set.
Signed-off-by: Maarten Lankhorst maarten.lankho...@canonical.com
---
diff --git
stopping acpid before Xorg with valgrind --free-fill=df results in this crash
backtrace:
==2670== Invalid read of size 8
==2670==at 0x1B9CB0: xf86Wakeup (xf86Events.c:276)
==2670==by 0x1687B2: WakeupHandler (dixutils.c:423)
==2670==by 0x334793: WaitForSomething (WaitFor.c:224)
On 14 Aug 2012, Andy Ritger told this:
* PATCH 1 changes long standing behavior in xrandr(1). While the patch
makes the semantics consistent with xgamma(1) and xorg.conf options,
maybe it would be better to keep the existing behavior and just document
that behavior in the man page
Peter Hutterer peter.hutte...@who-t.net writes:
Peter Hutterer (1):
xfree86: add xf86UpdateDesktopDimensions()
Merged.
09f1e5b..0a75bd6 master - master
--
keith.pack...@intel.com
pgpV0hh5mfIme.pgp
Description: PGP signature
___
Dave Airlie airl...@gmail.com writes:
On Fri, Oct 5, 2012 at 12:53 PM, Keith Packard kei...@keithp.com wrote:
Maybe I should just all in and try and submit the full-on impedance
layer it just struck me it might be easier to start with something
that just pushes drawables as far down as
Maarten Lankhorst maarten.lankho...@canonical.com writes:
Commit 37d956e3ac9513 initializes compat_output to -1, so
xf86CompatOutput would do config-output[-1] when not initialized.
This happens in xf86OutputSetEDID for example, before compat_output is
set.
Seems like compat_output should
Maarten Lankhorst maarten.lankho...@canonical.com writes:
Taking a pointer to ih-next before calling the event handler fixes
this.
Yay, more open coded lists. Any way we could encourage you to replace it
with a struct xorg_list instead?
--
keith.pack...@intel.com
pgpfPo6ljIsMX.pgp
On 10/08/2012 10:54 AM, Keith Packard wrote:
* PGP Signed by an unknown key
Maarten Lankhorst maarten.lankho...@canonical.com writes:
Taking a pointer to ih-next before calling the event handler fixes
this.
Yay, more open coded lists. Any way we could encourage you to replace it
with a
Hi,
I'm trying to debug a few issues that I suspect are ultimately the
result of wacom touch screens having a resolution different from the
screen resolution [1], and I realized I don't even know what is supposed
to happen when a relative device is used after a touch. The two
possible behaviors
UngrabAllDevices(Bool kill_client):
If we are not going to kill the client (kill_clients false),
we need to deactivate grabs of active clients, too.
(If we are going to kill the client,
no need to deactivate the grab,
as this will be done as part of the client kill.)
Fixes: X.Org Bug 55785
10 matches
Mail list logo