[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Michael Thayer, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
up
** Changed in: xorg-server (Ubuntu)
Status: Expired = New
--
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/767159
Title:
udevadm trigger --action=change crashes X.Org Server
To
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Just tested again. I no longer see this on bare metal (I think I did
before, but it was so long ago...) I do see it in VirtualBox (Oneiric
VM) with and without Guest Additions installed. I will take fifteen
minutes to see if I can debug it.
--
You received this bug notification because you
I note that in
(gdb) p handlers[i]
$2 = {BlockHandler = 0x9604b0, WakeupHandler = 0x9605e0,
blockData = 0x8fd06f8, deleted = 1}
the value of deleted is 1. WakeupHandler() actually checks that - some
concurrency issue?
--
You received this bug notification because you are a member of
pInfo-read_input - EvdevReadInput - EvdevMBEmuFinalize -
RemoveBlockAndWakeupHandlers - handlers[i].deleted = TRUE;
Do I recall correctly that read_input is called from the SIGIO handler
in the X server?
--
You received this bug notification because you are a member of Ubuntu-X,
which is
My first instinct would be to try the following patch. Looking at the
server source code I don't think that read_input will be called in a
loop if it returns without doing anything, and I would assume that the
server will get notification from udev on a separate path to trigger
device removal
I intercepted this in gdb, with the following result (unfortunately I
couldn't find a debug symbol package for the evdev driver):
Program received signal SIGSEGV, Segmentation fault.
0x00960600 in ?? () from /usr/lib/xorg/modules/input/evdev_drv.so
(gdb) bt
#0 0x00960600 in ?? () from
Hey michael-thayer,
You filed this bug report against natty, but I see it's still open and
doesn't appear to have much activity recently. So, now that oneiric
is released and stable, this may be a good point for you to upgrade
and re-test if this issue is still present there.
If it's solved in
--
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/767159
Title:
udevadm trigger --action=change crashes X.Org Server
___
Mailing list:
12 matches
Mail list logo
