3DxWare segfault problem

Questions and answers about 3Dconnexion devices on UNIX and Linux.

Moderator: Moderators

Post Reply
simwin
Posts: 10
Joined: Mon Aug 11, 2008 8:35 pm

3DxWare segfault problem

Post by simwin » Mon Aug 11, 2008 9:28 pm

G'Day

I have been using a SpaceTraveller3 USB on a RHEL5u5 x86_64 system.

Today I replaced it with a SpaceNavigator and 3DxWare will no longer load - it segfaults! I have tried upgrading to the latest drivers (from 1.2.17 to 1.3) and plugging the old spaceball back in but it still segfaults.

I can run the driver manually but my application (based on the SDK) stops receiving updates from the spaceball after a short time.

Code: Select all

3DxWareUNIX V1.3.0 ID 3788 log file
Process ID: 3543
 Time: 2008-08-12 13:41:17
Machineinfo 1: Systemname=Linux, Nodename=neil, Release=2.6.18-53.1.21.el5
Machineinfo 2: Version=#1 SMP Tue May 20 09:35:07 EDT 2008, Machine=x86_64
Runlevel-Info:          run-level 5  Aug 12 13:40                   last=S

-----------------------------------

[2008-08-12 13:41:17] uddev.c, 1171: UdDevInit() 0x9bb8010
[2008-08-12 13:41:17] 3dxsrv.c,705: displayname = $DISPLAY set to :0
[2008-08-12 13:41:17] 3dxsrv.c,710: putenv() was successful
[2008-08-12 13:41:17] 3dxsrv.c,712: displayname is now :0
[2008-08-12 13:41:18] auth.c :: authGetUser(), FOUND: user home = "/users/sxw"
[2008-08-12 13:41:18] 3dxsrv.c :: startupInittab(), authGetUser(), user=sxw
[2008-08-12 13:41:18] UdDev: Opening USB device on USB port /proc/bus/usb/003/004
[2008-08-12 13:41:18] UdDev: SpaceNavigator opened
[2008-08-12 13:41:18] UdDev: Opening SpaceNavigator device on USB port /proc/bus/usb/003/004
[2008-08-12 13:41:18] snav_usb.c :: UdDevRezero(): Rezeroing the device
[2008-08-12 13:41:18] 3dxsrv.c,730: UdDevOpen() was successful [SpaceNavigator]
The only part of my configuration that has changed is the Spaceball!

simwin
Posts: 10
Joined: Mon Aug 11, 2008 8:35 pm

Post by simwin » Mon Aug 11, 2008 9:30 pm

I have also tried deleting /etc/3DxWare and ~/.3dx* but this did not help either.

simwin
Posts: 10
Joined: Mon Aug 11, 2008 8:35 pm

Post by simwin » Tue Aug 12, 2008 11:35 pm

I have managed to replicate this bug on another system.

This is an Intel dual-core system running CentOS 5.1 x86_64. It has had a SpaceTraveller3 USB running for over six months with out any configuration changes or software updates. I unplugged the SpaceTraveller yesterday and when I plugged it in again this morning it lit up but the 3DxWare window did not appear. /var/log/messages reveals that the driver began segfaulting when the SpaceTraveller was plugged back in. The driver runs manually but will no longer run from inittab!

The original machine has now had a fresh install of its operating system but 3DxWare will not run from inittab.

Please suggest how I might fix this problem. I am not sure where to go from here.

simwin
Posts: 10
Joined: Mon Aug 11, 2008 8:35 pm

Re: 3DxWare segfault problem

Post by simwin » Tue Aug 12, 2008 11:58 pm

simwin wrote:G'Day

I have been using a SpaceTraveller3 USB on a RHEL5u5 x86_64 system.

Today I replaced it with a SpaceNavigator and 3DxWare will no longer load - it segfaults! I have tried upgrading to the latest drivers (from 1.2.17 to 1.3) and plugging the old spaceball back in but it still segfaults.

I can run the driver manually as root but it wont run from the inittab.

Code: Select all

3DxWareUNIX V1.3.0 ID 3788 log file
Process ID: 3543
 Time: 2008-08-12 13:41:17
Machineinfo 1: Systemname=Linux, Nodename=neil, Release=2.6.18-53.1.21.el5
Machineinfo 2: Version=#1 SMP Tue May 20 09:35:07 EDT 2008, Machine=x86_64
Runlevel-Info:          run-level 5  Aug 12 13:40                   last=S

-----------------------------------

[2008-08-12 13:41:17] uddev.c, 1171: UdDevInit() 0x9bb8010
[2008-08-12 13:41:17] 3dxsrv.c,705: displayname = $DISPLAY set to :0
[2008-08-12 13:41:17] 3dxsrv.c,710: putenv() was successful
[2008-08-12 13:41:17] 3dxsrv.c,712: displayname is now :0
[2008-08-12 13:41:18] auth.c :: authGetUser(), FOUND: user home = "/users/sxw"
[2008-08-12 13:41:18] 3dxsrv.c :: startupInittab(), authGetUser(), user=sxw
[2008-08-12 13:41:18] UdDev: Opening USB device on USB port /proc/bus/usb/003/004
[2008-08-12 13:41:18] UdDev: SpaceNavigator opened
[2008-08-12 13:41:18] UdDev: Opening SpaceNavigator device on USB port /proc/bus/usb/003/004
[2008-08-12 13:41:18] snav_usb.c :: UdDevRezero(): Rezeroing the device
[2008-08-12 13:41:18] 3dxsrv.c,730: UdDevOpen() was successful [SpaceNavigator]
The only part of my configuration that has changed is the Spaceball!

UtaSH
Moderator
Moderator
Posts: 3346
Joined: Mon Nov 27, 2006 10:34 am
Location: Munich, Germany
Contact:

Re: 3DxWare segfault problem

Post by UtaSH » Wed Aug 13, 2008 2:53 am

Hi simwin,

do you have a log file from the 3DxWareUnix? (/tmp/3DxWare.log) It is created if you add the options -debug -E to the entry in the inittab.

Do you have more information there? Do you get a core file?

Uta

simwin
Posts: 10
Joined: Mon Aug 11, 2008 8:35 pm

Re: 3DxWare segfault problem

Post by simwin » Wed Aug 13, 2008 5:39 pm

uludwig wrote:do you have a log file from the 3DxWareUnix? (/tmp/3DxWare.log) It is created if you add the options -debug -E to the entry in the inittab.

Do you have more information there? Do you get a core file?
Both systems produce the same log output which you can see in my original post. The device lights up and then the driver segfaults.

I don't think it created a corefile, where should I be looking? How can I make it produce one when it is being run from inittab?

UtaSH
Moderator
Moderator
Posts: 3346
Joined: Mon Nov 27, 2006 10:34 am
Location: Munich, Germany
Contact:

Re: 3DxWare segfault problem

Post by UtaSH » Thu Aug 14, 2008 2:22 am

From what I see from the log file it looks as if the authorization at the XServer causes problems. Do you see any difference if you do a
  • xhost +
from the command line?

Uta

simwin
Posts: 10
Joined: Mon Aug 11, 2008 8:35 pm

Re: 3DxWare segfault problem

Post by simwin » Thu Aug 14, 2008 8:14 pm

uludwig wrote:From what I see from the log file it looks as if the authorization at the XServer causes problems. Do you see any difference if you do a
  • xhost +
from the command line?

Uta
I tried "xhost +" this morning on both systems but the driver still segfaults. I have installed CentOS 5.2 x86_64 on one of these systems now and it has the same problem with a fresh install!

Code: Select all

3DxWareUNIX V1.3.0 ID 3788 log file
Process ID: 14293
 Time: 2008-08-16 07:31:51
Machineinfo 1: Systemname=Linux, Nodename=test, Release=2.6.18-92.el5
Machineinfo 2: Version=#1 SMP Tue Jun 10 18:51:06 EDT 2008, Machine=x86_64
Runlevel-Info:          run-level 5  Aug 16 07:16                   last=S

-----------------------------------

[2008-08-16 07:31:51] uddev.c, 1171: UdDevInit() 0x1d6ff010
[2008-08-16 07:31:51] 3dxsrv.c,705: displayname = $DISPLAY set to :0
[2008-08-16 07:31:51] 3dxsrv.c,710: putenv() was successful
[2008-08-16 07:31:51] 3dxsrv.c,712: displayname is now :0
[2008-08-16 07:31:52] auth.c :: authGetUser(), FOUND: user home = "/users/test"
[2008-08-16 07:31:52] 3dxsrv.c :: startupInittab(), authGetUser(), user=test
[2008-08-16 07:31:52] UdDev: Opening USB device on USB port /proc/bus/usb/005/004
[2008-08-16 07:31:52] UdDev: SpaceTraveler opened
[2008-08-16 07:31:52] UdDev: Opening SpaceTraveler device on USB port /proc/bus/usb/005/004
[2008-08-16 07:31:52] straveler_usb.c :: UdDevRezero(): Rezeroing the device
[2008-08-16 07:31:52] 3dxsrv.c,730: UdDevOpen() was successful [SpaceTraveler]

simwin
Posts: 10
Joined: Mon Aug 11, 2008 8:35 pm

Post by simwin » Thu Aug 14, 2008 8:17 pm

/var/log/messages

Code: Select all

Aug 16 07:41:55 test kernel: input: USB HID v1.10 Multi-Axis Controller [3Dconnexion SpaceTraveler USB] on usb-0000:00:1d.0-1
Aug 16 07:42:06 test kernel: usb 5-1: usbfs: process 16430 (3dxsrv) did not claim interface 0 before use
Aug 16 07:42:06 test kernel: 3dxsrv[16430]: segfault at 0000000000000010 rip 0000003bb3471966 rsp 00007fff2b14ceb0 error 6
Aug 16 07:42:07 test kernel: usb 5-1: usbfs: process 16437 (3dxsrv) did not claim interface 0 before use
Aug 16 07:42:07 test kernel: 3dxsrv[16437]: segfault at 0000000000000010 rip 0000003bb3471966 rsp 00007fff6f146eb0 error 6
Aug 16 07:42:08 test kernel: usb 5-1: usbfs: process 16458 (3dxsrv) did not claim interface 0 before use
Aug 16 07:42:08 test kernel: 3dxsrv[16458]: segfault at 0000000000000010 rip 0000003bb3471966 rsp 00007fff4715dec0 error 6
Aug 16 07:42:09 test kernel: usb 5-1: usbfs: process 16468 (3dxsrv) did not claim interface 0 before use
Aug 16 07:42:09 test kernel: 3dxsrv[16468]: segfault at 0000000000000010 rip 0000003bb3471966 rsp 00007fff1dc03960 error 6
Aug 16 07:42:10 test kernel: usb 5-1: usbfs: process 16478 (3dxsrv) did not claim interface 0 before use
Aug 16 07:42:10 test kernel: 3dxsrv[16478]: segfault at 0000000000000010 rip 0000003bb3471966 rsp 00007fff0f3450b0 error 6
Aug 16 07:42:11 test kernel: usb 5-1: usbfs: process 16488 (3dxsrv) did not claim interface 0 before use
Aug 16 07:42:11 test kernel: 3dxsrv[16488]: segfault at 0000000000000010 rip 0000003bb3471966 rsp 00007fff12bfd960 error 6
Aug 16 07:42:12 test kernel: usb 5-1: usbfs: process 16498 (3dxsrv) did not claim interface 0 before use
Aug 16 07:42:12 test kernel: 3dxsrv[16498]: segfault at 0000000000000010 rip 0000003bb3471966 rsp 00007fff6a41f180 error 6
Aug 16 07:42:13 test kernel: usb 5-1: usbfs: process 16508 (3dxsrv) did not claim interface 0 before use
Aug 16 07:42:13 test kernel: 3dxsrv[16508]: segfault at 0000000000000010 rip 0000003bb3471966 rsp 00007fff113460b0 error 6
Aug 16 07:42:14 test kernel: usb 5-1: usbfs: process 16518 (3dxsrv) did not claim interface 0 before use
Aug 16 07:42:14 test kernel: 3dxsrv[16518]: segfault at 0000000000000010 rip 0000003bb3471966 rsp 00007fffbce1fb80 error 6
Aug 16 07:42:15 test kernel: usb 5-1: usbfs: process 16527 (3dxsrv) did not claim interface 0 before use
Aug 16 07:42:15 test kernel: 3dxsrv[16527]: segfault at 0000000000000010 rip 0000003bb3471966 rsp 00007fffa3d99b00 error 6
Aug 16 07:42:15 test init: Id "3d" respawning too fast: disabled for 5 minutes

UtaSH
Moderator
Moderator
Posts: 3346
Joined: Mon Nov 27, 2006 10:34 am
Location: Munich, Germany
Contact:

Re: 3DxWare segfault problem

Post by UtaSH » Tue Aug 19, 2008 9:12 am

Hi,

do you see any difference when you create a new user?

Or when you delete the .Xauthority file?
  • echo $XAUTHORITY

simwin
Posts: 10
Joined: Mon Aug 11, 2008 8:35 pm

Re: 3DxWare segfault problem

Post by simwin » Tue Aug 19, 2008 8:28 pm

uludwig wrote:do you see any difference when you create a new user?
These computers use a network login so it is possible that the process launched from inittab is unable to access the X authority file. I will try and test this.

As of this morning, the driver is loading on my workstation again. I am not sure why so I will have to try and get it to fail again.

Post Reply