** Changed in: xorg-server (Ubuntu Precise)
Status: Fix Committed => Invalid
--
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/943880
Title:
Xorg crashed with SIGABRT in
** Changed in: xorg-server (Ubuntu)
Status: Invalid => Fix Released
** Changed in: xorg-server (Ubuntu Precise)
Status: Invalid => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Should have been fixed in 1.6.2-1ubuntu1~precise2, which has been in
precise-updates for some time. Dupe of some other bug .:)
** Also affects: xserver-xorg-input-synaptics (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xorg-server (Ubuntu)
Status: Confirmed = Invalid
I worked around this bug in the end by adding the following script
into /etc/pm/sleep.d directory. I created this script in July, and
have never seen the problem recur since. I'm using an Acer 1810tz
laptop.
#! /bin/sh
rfkills=$(ls /sys/class/rfkill)
#echo $rfkills
case $1 in
I was curious about the dialog i receive often about some internal error
after startup, or while using the system, and looked at the details.
After that i found this bug.
The fact that in the last comments the touchpad is mentioned, and the
base report is loenovo x220 related, I can only provide
This is really making me look for alternatives, Do we have some
workaround for this ? Does disabling synaptic help ?
--
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/943880
Title:
Xorg
I'm using the mainstream kernel for now. It's rock solid. It just
doesn't have VMWare, or full apparmor support, or ipv6.
On Tue, Jun 12, 2012 at 9:29 PM, Aneesh Kumar K.V
aneesh.ku...@gmail.com wrote:
This is really making me look for alternatives, Do we have some
workaround for this ? Does
Does disabling synaptic help ?
aneesh-kumar,
if you disable Synaptics driver, then you'll probable need to use an external
mouse instead of your touchpad.
---
I'm using the mainstream kernel for now. It's rock solid.
hughperkins,
Xorg (and its drivers) have nothing to do with Linux kernel.
--
Please test. :)
--
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/943880
Title:
Xorg crashed with SIGABRT in __libc_message() from malloc_printerr()
via XIDestroyDeviceProperty
To manage
Hi Maarten,
I installed the synaptics driver, and rebooted into the standard
kernel, and the standard kernel was really unstable so I rebooted back
into mainstream kernel. I'm a bit concerned about the security
implications of running an old mainstream kernel, but at least the
mainstream kernel
Hey,
There's no need to change kernel for testing, the bug was specifically
abourt X.org crashing in a specific way. I was simply asking if the
attached deb fixed that crash or not. It's a X.org driver not a kernel
driver.
Cheers,
~Maarten
--
You received this bug notification because you are
Thanks a lot.
2012/6/7 Maarten Lankhorst maarten.lankho...@canonical.com:
Please test. :)
--
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/943880
Title:
Xorg crashed with SIGABRT in
mlankhorst,
BTW, your version of 'xserver-xorg-input-synaptics' is
'1.5.99.902-0ubuntu5.1+fixes', and the version in 'precise-updates' is
'1.6.0-0ubuntu1~precise1'.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
I didn't notice at least 1 time touchpad self-disabling, now that bug
report window doesn't appear. Should I try that package anyway?
By the way, touchpad disables every time I type anything (even accidental
arrow keystrokes) during kernel/modules (don't know exactly) load while
system startup.
** Tags added: metabug
--
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/943880
Title:
Xorg crashed with SIGABRT in __libc_message() from malloc_printerr()
via XIDestroyDeviceProperty
To
Well there was a corruption occuring in synaptics that could trigger
every time the touchpad was disabled, for example with syndaemon. It was
fixed in a newer version, and might be what you're experiencing here.
Could you try the appropriate i386/amd64 deb from
What all these bugs have in common is that synaptics driver is used, but
the only thing I see that looks suspicious is that BOOL is redefined as
char for X, the common definition is int. However that seems to be done
consistently so not likely to be a problem, sizeof(BOOL) = 1 inside
synaptics,
In case it's useful in any way, I've started using the mainstream
kernel 3.4.0-030400rc2-generic-pae #201204072235 , which doesn't have
the psmouse-working-after-suspend bug I get in the ubuntu kernel, and
therefore I don't get a crash.
But I suspect this is because I don't have to unload
** Also affects: xorg-server (Ubuntu Precise)
Importance: High
Status: Confirmed
--
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/943880
Title:
Xorg crashed with SIGABRT in
Valgrind how to: https://wiki.ubuntu.com/Valgrind
--
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/943880
Title:
Xorg crashed with SIGABRT in __libc_message() from malloc_printerr()
via
@penalvch: step 3 seems to need some specific clarification, given that
the process in question is the X server. At least: I'm not sure how to
start the X server in valgrind.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
I just figure out today how to get what I believe is a full unity
session up and running in a valgrind X:
1. Log out, we're going to stop the current X session.
2. Switch to a VT (ctrl+alt+fn2)
3. Log in
4. $ sudo stop lightdm
5. $ sudo valgrind Xorg :0 21 | tee /tmp/log
6. Switch to another VT
@Bryce
I ran into this over the weekend, and it was quite easy to reproduce
using the Disable-Touchpad ( Fn-F8 ) on my Thinkpad T410s. I haven't
been able to reproduce since.
That said, my Disable-Touchpad function key now seems completely broken
( but crashes at least ).
--
You received this
(Note: For the Valgrind bit, maybe the easiest thing could be to post
instructions for running valgrind, then if someone gets a moment it's
easy to just run it. Or maybe there are some licensing issues
involved?)
--
You received this bug notification because you are a member of Ubuntu-X,
which
My experience:
- after suspend, my touchpad mouse doesn't work (this itself is a new bug)
- I do 'sudo rmmod psmouse' then 'sudo modprobe psmouse' to reactive the mouse
- ... except, recently, when I do 'sudo rmmod psmouse', X crashes with the bug
in this bug report
--
You received this bug
(by the way, I'm using gnome classic (no effects), fully updated, as of
yesterday/this morning)
--
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/943880
Title:
Xorg crashed with SIGABRT in
I can reproduce it fairly reliably by doing:
- suspend
- after suspend, 'sudo rmmod psmouse'
Sometimes, it's enough to just do 'sudo rmmod psmouse' (obviously if
this fails, you will need to 'sudo modprobe psmouse' before trying the
first method, using suspend)
--
You received this bug
** Summary changed:
- Xorg crashed with SIGABRT in __libc_message() from XIDestroyDeviceProperty
+ Xorg crashed with SIGABRT in __libc_message() from malloc_printerr() via
XIDestroyDeviceProperty
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
28 matches
Mail list logo
