Your message dated Wed, 16 Jun 2021 12:30:08 +0200
with message-id <[email protected]>
and subject line Re: Bug#641138: Really old bug, Garmin hardware not mentioned.
has caused the Debian Bug report #641138,
regarding gpsbabel: Command line option "-f usb:1" causes segmentation fault.
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
641138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641138
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gpsbabel
Version: 1.4.2-3
Severity: normal
Dear Maintainer,
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
# gpsbabel -t -i garmin -f usb:1 -o gpx -F test.gpx
Speicherzugriffsfehler
# gpsbabel -i garmin -f usb:1
Speicherzugriffsfehler
# gpsbabel -f usb:1
No valid input type specified
# gpsbabel -i garmin -f usb:0
Claim interfaced failed: could not claim interface 0: Device or resource busy
# gpsbabel -i garmin -f usb:
Claim interfaced failed: could not claim interface 0: Device or resource busy
# tail /var/log/syslog
Sep 10 19:04:50 localhost kernel: usb 6-2: USB disconnect, device number 7
Sep 10 19:04:50 localhost kernel: garmin_gps ttyUSB1: Garmin GPS usb/tty
converter now disconnected from ttyUSB1
Sep 10 19:04:50 localhost kernel: garmin_gps 6-2:1.0: device disconnected
Sep 10 19:04:59 localhost kernel: usb 6-2: new full speed USB device number 8
using uhci_hcd
Sep 10 19:05:00 localhost kernel: usb 6-2: New USB device found, idVendor=091e,
idProduct=0003
Sep 10 19:05:00 localhost kernel: usb 6-2: New USB device strings: Mfr=0,
Product=0, SerialNumber=0
Sep 10 19:05:00 localhost kernel: garmin_gps 6-2:1.0: Garmin GPS usb/tty
converter detected
Sep 10 19:05:00 localhost kernel: usb 6-2: Garmin GPS usb/tty converter now
attached to ttyUSB1
Sep 10 19:05:00 localhost kernel: usb 6-2: USB disconnect, device number 8
Sep 10 19:05:00 localhost kernel: garmin_gps ttyUSB1: Garmin GPS usb/tty
converter now disconnected from ttyUSB1
Sep 10 19:05:00 localhost kernel: garmin_gps 6-2:1.0: device disconnected
Sep 10 19:05:10 localhost kernel: usb 6-2: new full speed USB device number 9
using uhci_hcd
Sep 10 19:05:10 localhost kernel: usb 6-2: New USB device found, idVendor=091e,
idProduct=0003
Sep 10 19:05:10 localhost kernel: usb 6-2: New USB device strings: Mfr=0,
Product=0, SerialNumber=0
Sep 10 19:05:10 localhost kernel: garmin_gps 6-2:1.0: Garmin GPS usb/tty
converter detected
Sep 10 19:05:10 localhost kernel: usb 6-2: Garmin GPS usb/tty converter now
attached to ttyUSB1
....
Sep 10 19:39:48 localhost kernel: gpsbabel[17737]: segfault at 0 ip
00007f1d10eb6594 sp 00007fff7ce42470 error 4 in
libusb-0.1.so.4.4.4[7f1d10eb3000+7000]
Sep 10 19:41:04 localhost kernel: gpsbabel[17787]: segfault at 0 ip
00007f15b0724594 sp 00007fff81cc4ba0 error 4 in
libusb-0.1.so.4.4.4[7f15b0721000+7000]
* What was the outcome of this action?
Speicherzugriffsfehler = Segmentation fault
* What outcome did you expect instead?
Download of track data or a proper error message.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to de_DE.utf8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gpsbabel depends on:
ii libc6 2.13-18
ii libexpat1 2.0.1-7
ii libusb-0.1-4 2:0.1.12-19
ii zlib1g 1:1.2.3.4.dfsg-3
Versions of packages gpsbabel recommends:
pn gpsbabel-doc <none>
gpsbabel suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Robert,
* Robert Lipe <[email protected]> [2021-06-15 01:48]:
Please close this issue.
Done.
Suggestion: mark this as closed. the error message was improved and the
fixes were deliver a long, long time ago. No devices using Garmin comm
protocol (current ones mount as mass storage devices and you basically copy
GPX files to/from them) since about 2008 or so. The libusb path is so
inconsequential it's being strongly considered for removal upstream because
of disuse and churn at the libusb api level.
Do you mean deprecating: gpsbabel -i garmin -f usb: ? That would be
really sad, I still have a working device where I use that from time to
time.
Cheers Jochen
signature.asc
Description: PGP signature
--- End Message ---
