Bug#412149: marked as done (general: "usb:" stopped working in both gpsbabel and jpilot)
Your message dated Fri, 23 Feb 2007 17:05:45 -0800
with message-id <20070224010545.GE10104@mauritius.dodds.net>
and subject line Bug#412149: general: "usb:" stopped working in both gpsbabel and jpilot
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: general
Severity: normal
A few days ago, jpilot stopped syncing my USB PalmPilot. I had been using
libusb (i.e. "usb:" as the port). A reboot and a different cable didn't help,
but un-blacklisting the visor module and changing the port to /dev/pilot --
i.e. using the kernel visor module instead of libusb, reversing the procedure
suggested in #399878 -- and now sycning works fine.
Similarly, gpsbabel, which also uses libusb, no longer speaks to my GPS unit:
4 [~]$ gpsbabel -r -i garmin -f usb: -o gpx -F /tmp/foo
usb_set_configuration failed, probably because kernel driver ''
is blocking our access to the USB device.
For more information see http://www.gpsbabel.org/os/Linux_Hotplug.html
dmesg output for both the pilot and the GPS are along the lines of:
ohci_hcd 0000:00:02.0: wakeup
usb 1-3: new full speed USB device using ohci_hcd and address 11
usb 1-3: configuration #1 chosen from 1 choice
usb 1-3: USB disconnect, address 11
Also, the GPS works fine in mass storage mode -- again, no libusb.
The following are the packages I upgraded between working and non-working USB:
2007-02-20 21:36:24 status installed dhcp3-common 3.0.4-13
2007-02-20 21:36:29 status installed dhcp3-server 3.0.4-13
2007-02-20 21:36:29 status installed module-init-tools 3.3-pre4-1
2007-02-20 21:36:38 status installed linux-sound-base 1.0.13-4
2007-02-20 21:36:39 status installed alsa-base 1.0.13-4
2007-02-20 21:36:47 status installed libexpat1 1.95.8-3.4
2007-02-20 21:36:47 status installed libexpat1-dev 1.95.8-3.4
2007-02-20 21:36:47 status installed apache2-utils 2.2.3-3.3
2007-02-20 21:36:47 status installed busybox 1:1.1.3-4
2007-02-20 21:36:47 status installed libklibc 1.4.34-1
2007-02-20 21:36:47 status installed klibc-utils 1.4.34-1
2007-02-20 21:36:47 status installed libgphoto2-port0 2.2.1-16
2007-02-20 21:36:50 status installed libgphoto2-2 2.2.1-16
2007-02-20 21:36:51 status installed libpango1.0-common 1.14.8-5
2007-02-20 21:36:51 status installed libpango1.0-0 1.14.8-5
2007-02-20 21:36:51 status installed libpango1.0-dev 1.14.8-5
2007-02-20 21:36:51 status installed libscrollkeeper0 0.3.14-13
2007-02-20 21:36:52 status installed openoffice.org-common 2.0.4.dfsg.2-5
2007-02-20 21:37:04 status installed ttf-opensymbol 2.0.4.dfsg.2-5
2007-02-20 21:37:04 status installed openoffice.org-core 2.0.4.dfsg.2-5
2007-02-20 21:37:07 status installed python-uno 2.0.4.dfsg.2-5
2007-02-20 21:37:07 status installed openoffice.org-writer 2.0.4.dfsg.2-5
2007-02-20 21:37:07 status installed openoffice.org-draw 2.0.4.dfsg.2-5
2007-02-20 21:37:07 status installed openoffice.org-gtk 2.0.4.dfsg.2-5
2007-02-20 21:37:09 status installed scrollkeeper 0.3.14-13
2007-02-20 21:37:09 status installed ttf-dejavu 2.14-2
2007-02-20 21:37:10 status installed ttf-freefont 20060501cvs-10
2007-02-20 21:37:11 status installed update-inetd 4.27-0.3
2007-02-20 21:37:19 status installed x-ttcidfont-conf 25.1
I'm not sure for which package this bug report is appropriate. libusb seems a
likely candidate, but I haven't upgraded that package since October and
haven't touched the configuration in a while.
Any help would be greatly appreciated. Please let me know what further
information would be useful.
Thanks,
Reid
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.18-3-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
--- End Message ---
--- Begin Message ---
On Fri, Feb 23, 2007 at 06:27:01PM -0600, Reid Priedhorsky wrote:
> The following are the packages I upgraded between working and non-working USB:
<snip>
> 2007-02-20 21:36:47 status installed libgphoto2-port0 2.2.1-16
> 2007-02-20 21:36:50 status installed libgphoto2-2 2.2.1-16
<snip>
> I'm not sure for which package this bug report is appropriate. libusb seems a
> likely candidate, but I haven't upgraded that package since October and
> haven't touched the configuration in a while.
This latest libgphoto update fixed a security hole whereby libgphoto's udev
rules would wrongly grant access to the plugdev group on all usb devices
instead of just those related to cameras. An interesting possibility here
is that your use of libusb depended on libgphoto's bug. :)
This was bug #405006. A comment from this bug log:
> What class of USB devices are ending up under group plugdev that
> shouldn't?
It concerns the raw USB devices, in /dev/bus/usb/, used by libusb for
userland drivers.
So I would say this isn't a bug at all, but that you need to set up
additional permissions on /dev/bus/usb/* for your use.
Cheers,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
vorlon@debian.org http://www.debian.org/
--- End Message ---
Reply to: