** Changed in: xorg-server
Status: Confirmed => 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/956071
Title:
Xorg crashed with SIGSEGV in XIGetDeviceP
*** Bug 54283 has been marked as a duplicate of this bug. ***
--
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/956071
Title:
Xorg crashed with SIGSEGV in XIGetDevicePropert
** Branch unlinked: 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/956071
Title:
Xorg crashed with SIGSEGV in XIG
Is this bug tracker actually used?
--
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/956071
Title:
Xorg crashed with SIGSEGV in XIGetDeviceProperty()
To manage notification
Fixes for that are in synaptics 1.8 and 1.7.6. It was caused by missing
SYN_DROPPED handling.
You'll need libevdev 1.2 or later, iirc to get rid of the bug in
synaptics 1.8.
Otherwise, the commit on the 1.7 branch was:
http://cgit.freedesktop.org/xorg/driver/xf86-input-synaptics/commit/?h=synapt
I can still produce this bug on Debian stable. It requires me to run a
process that does a lot of random io in a a large file, such that some
swap is consumed.
I also had an instance of X crashing as a result:
[ 84441.029] BUG: triggered 'if (priv->num_active_touches > priv->num_slots)'
[ 84441.0
I'm seeing this on an Lenovo T420. I frequently see it when coming out
of hibernation (because my system is still swapping in).
I can "recover" by suspending to memory and then unresponding. At that
point the touchpad works again just fine without restarting X.
Debian Wheezy:
xserver-xorg-input-s
Have not yet seen this bug in xserver-xorg-input-synaptics
1.6.2-1ubuntu6 (Raring).
--
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/956071
Title:
Xorg crashed with SIGSEGV
right, that was the one and it hasn't been reverted, it just got
integrated into upstream 1.13.1 so we don't need the patch anymore. back
to the drawing board.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu
Hmm, Peter, can you confirm that patch is already in Fedora 18. It seems to
have been merged as part of:
* Tue Oct 30 2012 Peter Hutterer 1.13.0-6
- Add touchscreen fixes (including pointer emulation) #871064
So unless it was reverted by a later patch (at 1.13.2-1 now), this is
not it (unless th
My eeepc running mint has suddenly (after an update) also started to
exhibit this bug. It is starting to get annoying! I will try the patch
mentioned in the coming days (but confirmation can take some time, I
only hit this once a week or less).
--
You received this bug notification because you ar
There are suggestions that http://lists.x.org/archives/xorg-
devel/2012-October/034149.html helps with this issue, but unconfirmed so
far.
--
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.launch
I have not encountered this bug after upgrading to Raring.
--
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/956071
Title:
Xorg crashed with SIGSEGV in XIGetDeviceProperty()
*** Bug 55821 has been marked as a duplicate of this bug. ***
--
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/956071
Title:
Xorg crashed with SIGSEGV in XIGetDevicePropert
FWIW this bug only happens to me when unlocking the screen saver,
usually though not always after a resume from suspend. I think it
happens when I start typing a password quickly and right away. (The
crash does not happen immediately—a few seconds later.)
If I take care to wait a moment until the
I am not sure if it is still the same issue, but the last comments in
this bug are very similar to what is reported in bug 55821.
A reproducible test case I could not find. It just happens during normal
use, though a heavy load (suspend/resume) may trigger it quicker. It is
hard to be really sure
** Changed in: xorg-server
Status: Fix Released => Confirmed
--
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/956071
Title:
Xorg crashed with SIGSEGV in XIGetDeviceP
Hard to read the backtrace without symbols, but please try to find a
reproducible test-case. The number of fingers on the touchpad at suspend
time vs at resume time is almost certainly the trigger for this, but I
haven't found a reliable trigger yet.
--
You received this bug notification because
A couple of weeks ago I experienced a similar bug once or twice (at
least a similar backtrace as in comment 16), but I also did not have
symbols installed.
However, it may be noteworthy that I did not trigger it by a resume, but
by putting very heavy load on the machine. I have not done so since,
1.6.2-1ubuntu1~precise2 which I think has this patch, and also 1.5.99,
continue to crash for me with this SEGV on occasion, shortly but not
immediately after unlocking the screen (not necessarily after resume
from suspend). No clear way to reproduce. Anything that can be done to
help? (Any all-in-o
Although this patch makes the situation much better, it looks like a
similar bug is present elsewhere. Using git commit On git rev
3cb14dcccf5574366d90e24f351e3ad04b35e35f, I see an occasional crash
after several days of using a laptop with ~10 suspensions per day.
The following diagnostic messag
1.6.2-1ubuntu1~precise2 still occasionally crashing for me with what
seems to be the same SIGSEGV, under similar conditions as before (as in
comment #6—unlocking screen after longish period of inactivity).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscr
** Changed in: xorg-server (Debian)
Status: Confirmed => 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/956071
Title:
Xorg crashed with SIGSEGV in XIG
** Changed in: oem-priority
Status: Fix Committed => 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/956071
Title:
Xorg crashed with SIGSEGV in XIGetDe
** Changed in: oem-priority/precise
Status: Fix Committed => 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/956071
Title:
Xorg crashed with SIGSEGV in
Romano: disable it from the software center (edit - app sources -
updates)
--
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/956071
Title:
Xorg crashed with SIGSEGV in XIGet
Great. Is there any instruction on how to undo the - proposal activation
? I used the method described in the wiki to add only this package (the
trick with priorities), is deselecting the proposed repository
sufficient? Thanks!
--
You received this bug notification because you are a member of Ubu
the hotkey bug for thinkpads at least is bug 804109
--
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/956071
Title:
Xorg crashed with SIGSEGV in XIGetDeviceProperty()
To ma
The hotkey bug is a separate issue and needs to be tracked elsewhere.
It's likely reported already, so if someone knows the master bug for it,
please add a link here. Otherwise I'll file it and do the same.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subsc
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
This bug was fixed in the package xserver-xorg-input-synaptics -
1.6.2-1ubuntu1~precise2
---
xserver-xorg-input-synaptics (1.6.2-1ubuntu1~precise2) precise-proposed;
urgency=low
* Added 130_reset-num_active_touches-on-deviceoff.patch (LP: #956071)
-- Timo AaltonenThu, 30 Aug 2
** Description changed:
[Impact]
Causes crashes in the xserver usually on resume from suspend.
[Test Case]
- Put one or more fingers to the touchpad
- - Send the computer to standby, or disable the pad if hotkey exists with the
finger(s) still on the pad
+ - Send the computer to
i installed the update a few days ago and have only had one crash since
(and it was the same day as the update).. i use to have them almost
consistently everytime i went out of suspend (at least 4 times a day).
--
You received this bug notification because you are a member of Ubuntu-X,
which is s
Touchpad works now. I tried downgrading and upgrading with logout or
reboot, but I cannot reproduce thus far. ~precise2 hasn't crashed yet.
--
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.launc
My findings so far (with my T420s):
- disabling the touchpad with 'xinput disable/enable' works as many times as I
like
- disabling the touchpad with the hotkey fails to enable it, even though the
logfile gets a new "touchpad found" entry, and the same with the old driver
version... Logging out
Well, I could not trigger the bug, but had crashes every few hours.
Since when updating to the proposed package, I had no more crashes -
can't be 100% sure it's fixed, given the random nature of the thing, but
it seems ok, and it's for sure much better than before.
--
You received this bug notifi
Adding a regression-proposed tag for now to prevent migration until we
can get some more feedback as to how this is better (no crashing sounds
good) or worse (it seems some touchpads don't work when they previously
did?) than the previous version.
** Tags added: regression-proposed
--
You receiv
@Scott: I never noticed this problem when I was on
1.6.2-1ubuntu1~precise1. I now run 1.6.2-1ubuntu1~precise1 since it was
released to proposed and I have only noticed the touchpad problem twice
since. Right now it's working fine even though I have done several
suspend / resumes. So I cannot reprod
I can confirm that 1.6.2-1ubuntu1~precise2 doesn't completely fix the
bug on Lenovo T420s.
While I have not seen any random crashes for some time, the touchpad can
still be killed by the test described in #81. After some cycles of
disabling it by hotkey with fingers on and reenabling with fingers
Still broken.
Using a Lenovo t410 - Intel ® Integrated Graphics and NVIDIA® NVS3100M
Discrete Graphics
Bubmblebee is installed.
I can confirm that this does not happen without bumblebee.
For me, logoff occurs immediately after returning from suspend. I then
get this message:
"An problem has be
Thomas: Is the touchpad problem fixed if you downgrade back to the
previous package?
--
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/956071
Title:
Xorg crashed with SIGSEG
System is doing fine on 1.6.2-1ubuntu1~precise2 regarding crashes.
However, touchpad does not work OK! That little red pointer-thing (on
my Lenovo) works though. Also scrolling on the touchpad works.
Ubuntu developers: Are you going to reset bug status to confirmed or
whatever or do we need to o
I tried 1.6.2-1ubuntu1~precise2. No crashes, but the touchpad doesn't
work either. It worked briefly, then stopped working even after reboot.
--
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
Since updating to the fixed package, no more crashes whatsoever. Very
happy;)
--
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/956071
Title:
Xorg crashed with SIGSEGV in XI
In my case, I get a similar crash (same title in Apport than in this
bug) but it happens on both supsend/resume and cold boot. Not sure if I
should test the fix in -proposed or open a different bug report. My
machine is a Vostro V131 running 12.04. Please let me know what you
think I should do.
--
Marking verification-done based on comment #84
In response to comment #85, it's probably not useful for you to test
proposed unless you can reliabley reproduce with the -updates package
_or_ you know that this bug triggers frequently enough that when you
install the new package you know it's fixed
** Changed in: xorg-server
Status: Confirmed => 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/956071
Title:
Xorg crashed with SIGSEGV in XIGetDeviceP
commit a245d42f53096b1ae81e6702729f97ca508e5b5b
Author: Peter Hutterer
Date: Thu Aug 30 16:38:38 2012 +1000
Reset num_active_touches on DeviceOff (#52496)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubu
thanks for the patch, fixed it for me!
--
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/956071
Title:
Xorg crashed with SIGSEGV in XIGetDeviceProperty()
To manage notifica
Thanks! that really helped finding the issue
http://patchwork.freedesktop.org/patch/11873/
--
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/956071
Title:
Xorg crashed with
The method for triggering the bug explained in #81 does not work for me.
Is still useful to test the package from -proposed?
--
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
No crashes in 4 days from the package in precise-proposed, looks good so
far.
--
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/956071
Title:
Xorg crashed with SIGSEGV in XI
This affects me on a T410i with integrated graphics:
Backtrace:
[ 8987.859] 0: /usr/bin/X (xorg_backtrace+0x37) [0xb76a2627]
[ 8987.859] 1: /usr/bin/X (0xb751a000+0x18c3aa) [0xb76a63aa]
[ 8987.859] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb74f740c]
[ 8987.859] 3: /usr/bin/X (XIGetDeviceProperty
The fix does not work for me. It crashed again.
--
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/956071
Title:
Xorg crashed with SIGSEGV in XIGetDeviceProperty()
To manage
** Description changed:
- Crash on resume in xserver-xorg-input-synaptics. Version
- 1.5.99.902-0ubuntu5 works, the workaround is to downgrade to that
- version.
+ [Impact]
+
+ Causes crashes in the xserver usually on resume from suspend.
+
+ [Test Case]
+
+ - Put one or more fingers to the tou
If I understand the fix right, there may be a method to reliable
reproduce this error with the buggy version, and thus check the fix
after updating:
- Put two or more fingers to the touchpad
- Send the computer to standby, or disable the pad if hotkey exists with the
fingers still on the pad
- Re
** 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/956071
Title:
Xorg crashed with SIGSEGV in XIGet
Hello Jonatan, 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~precise2 in a few hours,
and then in the -proposed repository.
Pleas
** Changed in: oem-priority/precise
Status: Confirmed => In Progress
** Changed in: oem-priority
Status: Confirmed => 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.
tested the patch locally with precise and it works
** Changed in: xserver-xorg-input-synaptics (Ubuntu Precise)
Status: Incomplete => 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.
http
** 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/956071
Title:
Xorg crashed with SIGSEGV in XIGetDeviceProperty()
This bug was fixed in the package xserver-xorg-input-synaptics -
1.6.2-1ubuntu5
---
xserver-xorg-input-synaptics (1.6.2-1ubuntu5) quantal; urgency=low
* Added 130_reset-num_active_touches-on-deviceoff.patch (LP: #956071)
-- Timo AaltonenThu, 30 Aug 2012 20:13:39 +0300
** Chang
While downgrading has solved this crash fo me I also occasionaly still get the
freeze described in post 68. Anyone have an idea what this might be related to?
Instead of a hard reboot you can use ctr-alt-f1 to get a teminal, login and
issue the command 'pkill -KILL -t tty7' which should send you
The "except for scrolling" phrase from ThomasNovin really caught my
attention because, on two laptops using xserver-xorg-input-synaptics
1.5.99.902, I have seen the touchpad become inoperable except for
scrolling. I have both configured for two-finger scrolling, and when
this happens, it switches
** Changed in: xorg-server
Status: Incomplete => Confirmed
--
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/956071
Title:
Xorg crashed with SIGSEGV in XIGetDevicePro
After suspending/resuming I notice this error repeated a whole lot of times
on xorg 1.13rc4 + synaptics 1.6.2 (with finger on touchpad while
suspending/resuming by closing lid and pressing power button to wake up):
==3097== Invalid write of size 4
==3097== at 0xAEBFE95: UpdateTouchState.isra.12 (
I can confirm the exact behavior that ThomasNovin describes, using
1.5.99.902-0ubuntu5 on my Lenovo W520.
--
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/956071
Title:
Xor
I have had one crash on 1.5.99.902-0ubuntu5. That is the crash log in
post #70.
With this older version my touchpad never works after resuming from
suspend.
If I reboot and login, it works but after suspend / resume it's dead..
except for scrolling!
--
You received this bug notification because
Me too had no crashes since downgrading to 1.5.99.902-ubuntu5 .
For all those who also downgraded, please check again if you downgraded
to that version or earlier, and that the packaged is 'locked' after the
old version is forced to prevent it being upgraded again. Also there
where some reports th
I have been reproducing this on my Acer Aspire 1410-2285 (year 2009) for
several weeks now. Graphics processor is Intel GMA 4500MHD. I will
report back after further testing. (Have to suspend now, and not sure
my browser will survive the resume.)
--
You received this bug notification because y
Had a crash today after resuming even with the downgraded xorg
synaptics.
Attaching my Xorg.0.log.old.
** Attachment added: "Xorg.0.log.old"
https://bugs.launchpad.net/debian/+source/xorg-server/+bug/956071/+attachment/3278776/+files/Xorg.0.log.old
--
You received this bug notification beca
Upgrading to critical:
This is a bug that meets all of the following:
"A bug which has a severe impact on a large portion of Ubuntu users
Causes data corruption
Crashes the entire operating system
Renders the system temporarily or permanently unusable
Severely affects applications
I am experiencing some crashes again after resuming from suspend. The
xserver-xorg-input-synaptics is indeed at the prior version, and for at
least a few weeks this seemed to solve the issues (to reveiw, for me at
least on my Thinkpad T520 the problem occurred in me being kicked out to
the login s
Can also confirm that downgrading the package solves the issue.
Also found a way to reproduce the bug (on a Lenovo T420s):
1. Boot, set the cursor to an empty space on the desktop
2. Quickly toggle the touchpad enable/disable button (Fn+F8) while
simultaneously tapping the touchpad
3. The bug
Noted that Ubuntu 12.04.1 was released today. Unless xserver-xorg-input-
synaptics was downgraded for this release, very non-serious to have a
bug of this significance in such release. A bug that is probable to lead
to data loss should be of the highest importance?
--
You received this bug notifi
Argh! Lost data today from a Xorg-crash because xserver-xorg-input-
synaptics had been upgraded even though locked in Synaptic. It seems
unattended-upgrades don't care about that version lock.
This solves that, create /etc/apt/apt.conf.d/99unattended-upgrades with
this content:
// List of package
I can also confirm that downgrading to xserver-xorg-input-
synaptics=1.5.99.902 appears to have solved the problem.
--
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/956071
Ti
*** Bug 53686 has been marked as a duplicate of this bug. ***
--
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/956071
Title:
Xorg crashed with SIGSEGV in XIGetDevicePropert
sorry, still can't reproduce this and I can't see any change between 902
and 1.6.2 that could have introduced this bug. Are you still on server
1.12.1.902 or have you updated the server as well?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xse
I have upgraded xorg server quite a while ago and it had not resolved
the issue at that time. Just for the completness:
/var/log/dpkg.log.1:2012-07-03 09:53:04 status installed xserver-xorg:amd64
1:7.6+13
/var/log/dpkg.log.1:2012-07-03 09:53:04 status installed xorg:amd64 1:7.6+13
/var/log/dpkg.
Also no crashes for four days using 1.5.99. Maybe the update center
could roll back to this version while the problem is being investigated?
$ sudo apt-get install xserver-xorg-input-synaptics=1.5.99.902-0ubuntu5
&& echo 'xserver-xorg-input-synaptics hold' | sudo dpkg --set-selections
&& dpkg -s x
I get 2 different corruptions right now it seems on xorg 1.13rc4, with
--free-file=df:
First one is synaptics out of bounds..
==3097== Invalid write of size 4
==3097==at 0xAEBFE95: UpdateTouchState.isra.12 (synaptics.c:3132)
==3097==by 0xAEC1532: HandleState (synaptics.c:3224)
==3097==
Happens for mo on Lenovo G560, with kubuntu 12.04 latest updates.
When I manually sleep, the bug does not occur (at least, so far)
--
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
I have this problem onan Asus EEE-PC with Atom N280
Ocasionally, but not always, after the crah when I use shutdown/restart
it just logsout again.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://b
I have similar issue, ThinkPad T420s. System randomly but constantly
crashes when suspending after closing the lid for a couple of weeks now.
My xserver-xorg-input-synaptics is 1.6.2-1ubuntu1~precise1.
I did not went down the road of downgrading this one, but I tried
suspending by hand before clos
Just to chime in about 1.5.99.902-0ubuntu5.
No crashes for 3 days.
--
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/956071
Title:
Xorg crashed with SIGSEGV in XIGetDevicePr
** Changed in: xorg-server (Debian)
Status: Unknown => Confirmed
--
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/956071
Title:
Xorg crashed with SIGSEGV in XIGetDev
I have been running xserver-xorg-input-synaptics version
1.6.0-0ubuntu1~precise1 for about a week and have not experienced the X
server crash reported here.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
h
ok -- downgrade to xserver-xorg-input-synaptics 1.5.99.902-1 (debian
package) built with -O0 -- no crashes within a week -- so I guess it is
indeed synaptics to blame. If I find a chance I will "upgrade" to 1.6.0
and see if crash comes back... I would hate to do such silly bisection
but I guess it
The downgrade also is working for me. No crash since I downgraded and
locked xserver-xorg-input-synaptics to 1.5.99.902.
--
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/95607
I did a downgrade of xserver-xorg-input-synaptics to 1.5.99.902 and have
not had a crash since. I have a Lenovo t420s.
--
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/956071
(In reply to comment #6)
> yaroslav: could you try reverting the synaptics driver to, say, 1.5.99.902 or
> .903 and test if you can reproduce the crash? A similar crash has been filed
> on
> ubuntu, and there it was discovered that reverting to that version stopped the
> crashes.
yes -- I saw tho
yaroslav: could you try reverting the synaptics driver to, say,
1.5.99.902 or .903 and test if you can reproduce the crash? A similar
crash has been filed on ubuntu, and there it was discovered that
reverting to that version stopped the crashes.
--
You received this bug notification because you a
Disregard comment #46. The package had been upgraded again during the following
update.
I have now locked the version to 1.5.99.902 and will see how that behaves.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ub
@Daniel: Did you reboot?
--
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/956071
Title:
Xorg crashed with SIGSEGV in XIGetDeviceProperty()
To manage notifications about th
Downgrading xserver-xorg-input-synaptics to version 1.5.99.902 did not fix the
issue for me.
I just opened the lid after a suspend of approximately 40 minutes and got
kicked out to lightdm
about 30 seconds later.
--
You received this bug notification because you are a member of Ubuntu-X,
which
Timo or Jonatan,
Can either of you comment on "how" the crash happens? My issue (and I
think several others) was that I was kicked out to lightdm. If you are
getting actual freezes then this does seem separate.
If that is the case, maybe it is best to "separate the bug reports" and
mark the oth
I have still been followin this bug report, but I have been busy lately,
so I haven't been able to participate.
The problem is still occuring, but I am not sure if it's the same bug as other
posters.
Also, as the outcome of both bugs seems to be the same, makes me uncertain if
the original bug
I lied, just got this with my T420s. It was my wife's session that
crashed, my own was fine. Not directly related to suspend I think,
there's a VT change involved when changing user sessions (mine was the
active one). Synaptics seems to reprobe itself after the VT change ->
(occasional) boom.
It's
I agree that it does appear that this bug report was possibly "hijacked"
as the OP issues arose before. A majority of the comments are after
July 18, with nothing between March and July.
But as the OP hasn't been involved since March, it is hard to know what
the status of the "original bug" is.
1 - 100 of 154 matches
Mail list logo
