This bug was fixed in the package xserver-xorg-input-synaptics -
1.6.2-1ubuntu1~precise1
---
xserver-xorg-input-synaptics (1.6.2-1ubuntu1~precise1) precise-proposed;
urgency=low
* Fixes memory corruption by driver (LP: #941953) FDo #49439
* Fixes 'Coasting Direction is incorrect
Fixes the memory corruption I was seeing in valgrind.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/9
** Branch linked: lp:ubuntu/precise-proposed/xserver-xorg-input-
synaptics
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/941953
Title:
Xorg crashed with SIGSEGV in Write
Hello Scott, or anyone else affected,
Accepted xserver-xorg-input-synaptics into precise-proposed. The package
will build now and be available at http://launchpad.net/ubuntu/+source
/xserver-xorg-input-synaptics/1.6.2-1ubuntu1~precise1 in a few hours,
and then in the -proposed repository.
Please
** Changed in: xserver-xorg-input-synaptics (Ubuntu Precise)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/941953
Title:
Xorg
** Changed in: xserver-xorg-input-synaptics (Ubuntu Precise)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/941953
Title:
Xorg cras
** Description changed:
- This crash occurred on resume from suspend (to RAM) on a precise box up-
- to-date as of Feb 24.
+ [Impact]
+ Crash bug and silent memory corruption due to out of bounds access that may
not be noticed until much much later, in which case it's fatal.
+
+ [Test Case]
+ Th
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Assignee: Chase Douglas (chasedouglas) => Maarten Lankhorst (mlankhorst)
** Changed in: xserver-xorg-input-synaptics (Ubuntu Precise)
Assignee: Chase Douglas (chasedouglas) => Maarten Lankhorst (mlankhorst)
--
You received this bug n
** Changed in: xserver-xorg-input-synaptics
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/941953
Title:
Xorg crashed with SIGS
commit 55fc42e7c9b4948cadd4f98ef7b6a3b12e268e3e
Author: Chase Douglas
Date: Mon May 14 10:20:01 2012 -0700
Ignore pre-existing touches
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.la
I had that patch as a workaround locally, but since I didn't understand
the problem well enough, I didn't want to accept it as real solution.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.lau
** Branch linked: lp:ubuntu/xserver-xorg-input-synaptics
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/941953
Title:
Xorg crashed with SIGSEGV in WriteToClient() with bu
This bug was fixed in the package xserver-xorg-input-synaptics -
1.6.1-1ubuntu1
---
xserver-xorg-input-synaptics (1.6.1-1ubuntu1) quantal; urgency=low
* Merged from Debian unstable
* Refreshed patches for indentation changes
- 101_resolution_detect_option.patch
- 118_quell
Ok looks like it should be fixed upstream now.
Since this bug was attached to freedesktop.org I tried rebuilding
synaptics locally with the fixes and it seems to fix the corruption I
personally was seeing upstream.
Does
http://people.canonical.com/~mlankhorst/synaptics-rebuild/xserver-xorg-input-
http://patchwork.freedesktop.org/patch/10230/
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/941953
Title:
Xorg crashed with SIGSEGV in WriteToClient() with buf = 0x1
I can't reproduce using a magic trackpad. Maybe the issue is a bad
kernel driver for a different device?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/941953
Title:
Xorg
Launchpad has imported 2 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=49439.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
There appears to be a bug where the number of touches goes negative.
This leads to buffer overrun issues.
** Package changed: xorg-server (Ubuntu) => xserver-xorg-input-synaptics
(Ubuntu)
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Confirmed => Triaged
** Changed in: xser
#12 0x7f5ca64128e2 in WriteToClient (who=0x7f5caa9a46f0, count=4,
__buf=0x1) at /usr/include/x86_64-linux-gnu/bits/string3.h:58
oc = 0x7f5caa904180
oco = 0x7f5caa90a700
padBytes =
buf = 0x1
buf looks wrong here.
** Summary changed:
- Xorg cr
** Description changed:
This crash occurred on resume from suspend (to RAM) on a precise box up-
to-date as of Feb 24.
+ => 0x7f5ca44a42bc : mov-0x8(%rdi),%rax
+0x7f5ca44a42c0 : lea-0x10(%rdi),%rsi
+0x7f5ca44a42c4 : test $0x2,%al
+0x7f5ca44a42c6 : jne0x7f5ca44a
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/941953
Title:
Xorg crashed with SIGSEGV in WriteToClient()
To manage notifications about this bug go to:
h
21 matches
Mail list logo
