Bug 468264

Created attachment 321334 [details]
dmesg

Created attachment 321336 [details]
messages

Created attachment 321337 [details]
xorg.conf

Created attachment 321338 [details]
Xorg.0.log

I'm giving this to linuxwacom for now since it is only triggered by wacom  tablets.
If you can manage to get a backtrace in the logs, that'd be much appreciated. Also, doing at least one run with the nv driver instead of nvidia may be helpful too.

i tried the nv driver and the same thing happened. you can find Xorg.0.log attached. i found sth interesting:

Oct 27 21:23:29 teru kernel: usb 3-2: USB disconnect, address 4
Oct 27 21:23:31 teru bonobo-activation-server (teru-4222): could not associate with desktop session: Failed to connect to socket /tmp/dbus-0YLBGi0xFL: Połączenie odrzucone (Connection rejected)

it appeared in /var/log/messages when X crashed.

is there anything else i can do to help you?

Created attachment 321642 [details]
xorg_log_nv

that error appearted most likely after the server crashed (and the client thus couldn't connect to it anymore). You can ignore it.

*** Bug 471351 has been marked as a duplicate of this bug. ***

Here's the stack trace...

Program received signal SIGSEGV, Segmentation fault.
xf86WcmDevProc (pWcm=0x2497f80, what=2) at ./xf86Wacom.c:956
956	./xf86Wacom.c: No such file or directory.
	in ./xf86Wacom.c
(gdb) bt
#0  xf86WcmDevProc (pWcm=0x2497f80, what=2) at ./xf86Wacom.c:956
#1  0x0000000002160c55 in xf86WcmUninit (drv=<value optimized out>, local=0x2497d30, flags=0) at ./wcmConfig.c:375
#2  0x0000000000490e1b in DeleteInputDeviceRequest (pDev=<value optimized out>) at xf86Xinput.c:496
#3  0x000000000045ff0e in remove_device (dev=0x2497f80) at hal.c:72
#4  0x000000000045ff9f in device_removed (ctx=<value optimized out>, udi=<value optimized out>) at hal.c:90
#5  0x00000038d580bd29 in ?? () from /usr/lib64/libhal.so.1
#6  0x000000345e80ef7b in dbus_connection_dispatch () from /lib64/libdbus-1.so.3
#7  0x000000345e80f33b in ?? () from /lib64/libdbus-1.so.3
#8  0x000000000045fbbb in wakeup_handler (data=0x7b6620, err=<value optimized out>, read_mask=0x0) at dbus-core.c:58
#9  0x000000000044a42b in WakeupHandler (result=-1, pReadmask=0x7dbf20) at dixutils.c:417
#10 0x00000000004e4c5f in WaitForSomething (pClientsReady=0x2490fa0) at WaitFor.c:239
#11 0x00000000004465af in Dispatch () at dispatch.c:375
#12 0x000000000042ccdd in main (argc=8, argv=0x7fff2fdbb828, envp=<value optimized out>) at main.c:441

(gdb) print *pWcm
$2 = {public = {devicePrivate = 0x24b0200, processInputProc = 0x345f76da60 <main_arena+96>, realInputProc = 0x5541f0 <ProcessKeyboardEvent>, enqueueInputProc = 0x44f100 <EnqueueEvent>, on = 0}, next = 0x0, grabTime = {
    months = 0, milliseconds = 578173}, startup = 1, deviceProc = 0x2157c20 <xf86WcmDevProc>, inited = 1, enabled = 0, coreEvents = 4, grab = 0x0, sync = {frozen = 0, state = 0, other = 0x0, event = 0x0, evcount = 0}, 
  type = 213, name = 0x2495b60 "??Q\002", id = 2 '\002', activatingKey = 0 '\0', fromPassiveGrab = 0, activeGrab = {next = 0x0, resource = 0, device = 0x0, window = 0x0, ownerEvents = 0, keyboardMode = 0, pointerMode = 0, 
    coreGrab = 0, coreMods = 0, type = 0 '\0', modifiersDetail = {exact = 0, pMask = 0x0}, modifierDevice = 0x0, detail = {exact = 0, pMask = 0x0}, confineTo = 0x0, cursor = 0x0, eventMask = 0}, 
  ActivateGrab = 0x452b90 <ActivateKeyboardGrab>, DeactivateGrab = 0x452aa0 <DeactivateKeyboardGrab>, key = 0x0, valuator = 0x2498370, button = 0x24981d0, focus = 0x2498310, proximity = 0x24981b0, absolute = 0x0, 
  kbdfeed = 0x24b0400, ptrfeed = 0x2498340, intfeed = 0x0, stringfeed = 0x0, bell = 0x0, leds = 0x24b04d0, xkb_interest = 0x0, 
  config_info = 0x2440630 "hal:/org/freedesktop/Hal/devices/usb_device_56a_42_noserial_if0_logicaldev_input", devPrivates = 0x2498140, nPrivates = 0, unwrapProc = 0x1a0}

This bug is not present in linuxwacom-0.8.1-6 when compiled as:

CFLAGS="-ggdb3 -Wall -O0" ./configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info && make && sudo make install

Jeremy,
please give the scratch build 
   http://koji.fedoraproject.org/koji/taskinfo?taskID=933860
a try and let me know how it goes.

0.8.0.3-5 does not cause a crash on device removal.

it's commited and tagged, but I guess I won't be able to build it now.

linuxwacom-0.8.0.3-6.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/linuxwacom-0.8.0.3-6.fc10

linuxwacom-0.8.0.3-6.fc10 has been pushed to the Fedora 10 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update linuxwacom'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/f10/FEDORA-2008-10000

This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

linuxwacom-0.8.0.3-6.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.