Package: libticables3 Version: 3.9.6-5 Severity: important (Note: Another bug that may actually be against TiLP. Reassign if so.)
(Note 2: I've marked this and the previous bug as important because as far as I can tell, they completely break support for the by far most common connector cables nowadays. If you think the severity should be lower, feel free to change it.) Hrm... Further adventures after dealing with bug #351863. Okay... so it didn't work as a regular user... what about as root? Trying to get things running as root results in a different error. This time, the dialog complained "Msg: Error occurred while initializing the libusb. Cause: Check that your cable is connected or not stalled. Check your libusb and usbfs, too. System: Device or resource busy (errno = 16)" And the log reads ticables: getting method from resources (automatic): ticables: check for tiusb usability: ticables: using devfs: no ticables: node /dev/tiusb0: does not exists ticables: => you will have to create the node. ticables: warning: can't use IO_TIUSB ticables: check for lib-usb usability: ticables: usb filesystem (/proc/bus/usb): mounted ticables: node /proc/bus/usb/devices: exists ticables: permissions/user/group: -r--r--r-- root root ticables: is user can r/w on device: yes ticables: mapping I/O... ticables: registering cable... ticables: list of settings: ticables: cable: SilverLink ticables: port: USB port #1 ticables: method: user mode (ioctl) ticables: device name: /dev/tiusb0 ticables: delay value: 10 tifiles : settings: tifiles : calc type: TI89 ticalcs : settings: ticalcs : calc type: TI89 ticables: Found <SilverLink>. ticables: err: usb_set_configuration (could not set config 1: Device or resource busy) (Once again, it interestingly tries to open /proc/bus/usb/devices r/w even though the permissions don't allow that. However, as the superuser root, the permissions don't mean anything, and it gets its wish.) The interesting thing for this bug report, though, is the "device name: /dev/tiusb0" line; after having rejected tiusb earlier, it's now trying it again. A "cat /proc/bus/usb/devices" yields the following clause which I think is relevant: T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0451 ProdID=e001 Rev= 1.03 S: Manufacturer=Texas Instruments Incorporated S: Product=TI-GRAPH LINK USB C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=usbfs E: Ad=81(I) Atr=02(Bulk) MxPS= 32 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 32 Ivl=0ms This leads me to believe the real file you want to connect to is /dev/bus/usb/002/003. And in fact... [EMAIL PROTECTED]:~$ ls -l /dev/bus/usb/002/003 crw-rw---- 1 root tilp 189, 130 2006-02-07 19:16 /dev/bus/usb/002/003 [EMAIL PROTECTED]:~$ Indeed, the permissions on this file seems to be working just fine. (This may be relevant information for the other bug as well.) Anyway, hopefully these reports are detailed enough; feel free to ask for more information if you need it. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-2-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages libticables3 depends on: ii libc6 2.3.5-12.1 GNU C Library: Shared libraries an ii libusb-0.1-4 2:0.1.11-4 userspace USB programming library Versions of packages libticables3 recommends: ii udev [hotplug] 0.084-3 /dev/ and hotplug management daemo -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
