Errors trying i-gotU utilities on Linux (64 bit Opensuse)

Asked by Graham Dicker

A long while back I tried to get the i-gotU software to work on my Opensuse 32bit system but gave up because I could not figure out how to get round the errors like "QThread: Destroyed while thread is still running". Having just built myself a swish new 64 bit computer I thought I would try it again. No joy I'm afraid. Same problems and error messages as before. Is it possible that the author (or anyone else) has a small test program I could use to diagnose the problem? I did try to hack the original program to try to find out whether I could get a very simple command to work but the full program is just too massive and complex to be of any use as a diagnostic tool. With a little 3 line, 10 line or even 50 line program maybe I could understand it and figure out what the problem is.

Thanks

Graham

Question information

Language:
English Edit question
Status:
Expired
For:
igotu2gpx Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Michael Hofmann (mh21) said :
#1

Hi Graham,

could you specify where it goes wrong?

For troubleshooting, that is what I do:
- connect the tracker, check 'dmesg' output to see that it is recognized correctly, should be sth like

[10910.008800] usb 2-1.5: new full-speed USB device number 8 using ehci-pci
[10910.103216] usb 2-1.5: New USB device found, idVendor=0df7, idProduct=0900
[10910.103220] usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[10910.103223] usb 2-1.5: Product: i-gotU
[10910.103225] usb 2-1.5: Manufacturer: Mobile Action
[10910.104101] navman 2-1.5:1.0: navman converter detected
[10910.104219] usb 2-1.5: navman converter now attached to ttyUSB0

- try to run it as sudo igotu2gpx info, should give sth like

Downloading configuration...
Serial number: xxxxxxx
Firmware version: 3.09
Model: GT-200e
Number of points: 4032
Schedule date: woensdag 7 juli 2010
Schedule date offset: 0 day(s)
Schedule table: disabled
Log interval: 15 s
Interval change: disabled
LEDs: enabled
Button: enabled
Security version: 0
Password: disabled, []

- try to reconnect it a couple of times if it does not work :-)

Now, there should be verbose output with --verbose which shows the commands used, but I can't get it to work right now.

For debugging, https://www.kernel.org/doc/Documentation/usb/usbmon.txt is also really helpful:
- mount -t debugfs none_debugs /sys/kernel/debug
- modprobe usbmon
- ls /sys/kernel/debug/usb/usbmon
- find the bus with the device on it and do
  cat /sys/kernel/debug/usb/usbmon/*u

Let me know where it goes wrong. I could create a test program but because of the different backends (serial/libusb/libusb10) and the general weirdness of the devices I never tried.

Cheers
  Michael

PS: There is another project, maybe that one works?: http://www.sunaga-lab.com/hgrepos/pygotu

Revision history for this message
Graham Dicker (graham-dicker) said :
#2

Output from dmesg

[ 9715.631332] usb 3-11: new full-speed USB device number 5 using xhci_hcd
[ 9715.797549] usb 3-11: New USB device found, idVendor=0df7, idProduct=0900
[ 9715.797552] usb 3-11: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 9715.797553] usb 3-11: Product: Logger
[ 9715.797555] usb 3-11: Manufacturer: Mobile Action
[ 9716.833387] usbcore: registered new interface driver usbserial
[ 9716.833402] usbcore: registered new interface driver usbserial_generic
[ 9716.833413] usbserial: USB Serial support registered for generic
[ 9716.850292] usbcore: registered new interface driver navman
[ 9716.850302] usbserial: USB Serial support registered for navman
[ 9716.850311] navman 3-11:1.0: navman converter detected
[ 9716.850360] usb 3-11: navman converter now attached to ttyUSB0

mozart:~ # igotu2gpx info
Downloading configuration...
QThread: Destroyed while thread is still running
Segmentation fault

igotu2gpx --verbose info
Downloading configuration...
Interface 0 already claimed by kernel driver, detaching
Command: 930101030000000000000000000000
Device error: Device responded with error code: -1
Command: 930101030000000000000000000000
Result:
Command: 930a00000000000000000000000000
Result: d70e050003180001000c
Command: 9305040003019f0000000000000000
Result: c22015
Command: 930b03001d00000000000000000000
Result: 004d32
Command: 930507100004030000000000000000
Result: 01156f20ff0fff3c00f1ffffffff

after this crash dmesg says:

[10384.499824] navman ttyUSB0: navman converter now disconnected from ttyUSB0
[10384.499832] navman 3-11:1.0: device disconnected
[10384.985517] usb 3-11: usbfs: process 11400 (QThread) did not claim interface 0 before use

If I do (after plugging in the igotu):

cat /dev/ttyUSB0

then the IMEA data is printed out OK

Revision history for this message
Graham Dicker (graham-dicker) said :
#3

cat /sys/kernel/debug/usb/usbmon/3u
ffff880223fafa00 1960246807 S Ii:3:013:1 -115:1 16 <
ffff88021a60cdc0 1960246857 S Co:3:013:0 s 21 09 0200 0000 0008 8 = 93010103 00000000
ffff88021a60cdc0 1960247053 C Co:3:013:0 0 8 >
ffff880223fafa00 1960247505 C Ii:3:013:1 0:1 16 = 3331352c 2c2c4e2a 34390d0a 2c313630
ffff880223fafa00 1960247538 S Ii:3:013:1 -115:1 16 <
ffff880223fafa00 1960248496 C Ii:3:013:1 0:1 3 = 930000
ffff880223fafa00 1960248529 S Ii:3:013:1 -115:1 16 <
ffff88021bd5bf40 1960267183 S Co:3:013:0 s 21 09 0200 0000 0008 8 = 00000000 00000068
ffff88021bd5bf40 1960267414 C Co:3:013:0 0 8 >
ffff880223fafa00 1960267537 C Ii:3:013:1 0:1 3 = 930000
ffff880223fafa00 1960267612 S Ii:3:013:1 -115:1 16 <
ffff88021a60c700 1960287697 S Co:3:013:0 s 21 09 0200 0000 0008 8 = 930a0000 00000000
ffff88021a60c700 1960287932 C Co:3:013:0 0 8 >
ffff880223fafa00 1960288497 C Ii:3:013:1 0:1 3 = 930000
ffff880223fafa00 1960288574 S Ii:3:013:1 -115:1 16 <
ffff8800b2ca6d00 1960308167 S Co:3:013:0 s 21 09 0200 0000 0008 8 = 00000000 00000063
ffff8800b2ca6d00 1960308389 C Co:3:013:0 0 8 >
ffff880223fafa00 1960308512 C Ii:3:013:1 0:1 13 = 93000ad7 0e050003 1800010b 0c
ffff880223fafa00 1960308587 S Ii:3:013:1 -115:1 16 <
ffff880223fafdc0 1960328669 S Co:3:013:0 s 21 09 0200 0000 0008 8 = 93050400 03019f00
ffff880223fafdc0 1960328870 C Co:3:013:0 0 8 >
ffff880223fafa00 1960329482 C Ii:3:013:1 0:1 3 = 930000
ffff880223fafa00 1960329555 S Ii:3:013:1 -115:1 16 <
ffff8800955ba7c0 1960349094 S Co:3:013:0 s 21 09 0200 0000 0008 8 = 00000000 000000c1
ffff8800955ba7c0 1960349294 C Co:3:013:0 0 8 >
ffff880223fafa00 1960349486 C Ii:3:013:1 0:1 3 = 930003
ffff880223fafa00 1960349555 S Ii:3:013:1 -115:1 16 <
ffff880223fafa00 1960350482 C Ii:3:013:1 0:1 3 = c22015
ffff880223fafa00 1960350551 S Ii:3:013:1 -115:1 16 <
ffff880223faf700 1960369536 S Co:3:013:0 s 21 09 0200 0000 0008 8 = 930b0300 1d000000
ffff880223faf700 1960369737 C Co:3:013:0 0 8 >
ffff880223fafa00 1960370482 C Ii:3:013:1 0:1 3 = 930000
ffff880223fafa00 1960370554 S Ii:3:013:1 -115:1 16 <
ffff880223faf7c0 1960389961 S Co:3:013:0 s 21 09 0200 0000 0008 8 = 00000000 00000042
ffff880223faf7c0 1960390165 C Co:3:013:0 0 8 >
ffff880223fafa00 1960390482 C Ii:3:013:1 0:1 3 = 930003
ffff880223fafa00 1960390509 S Ii:3:013:1 -115:1 16 <
ffff880223fafa00 1960391482 C Ii:3:013:1 0:1 3 = 004d32
ffff880223fafa00 1960391508 S Ii:3:013:1 -115:1 16 <
ffff880223fafa00 1960392482 C Ii:3:013:1 0:1 3 = 004d32

Revision history for this message
Michael Hofmann (mh21) said :
#4

Hi Graham,

this all seems pretty ok actually. Could you run it in gdb and give the backtrace for the crash?

gdb igotu2gpx
r --verbose info
<crash>
bt

Cheers
  Michael

Revision history for this message
Graham Dicker (graham-dicker) said :
#5

mozart:~ # gdb --args igotu2gpx --verbose info
GNU gdb (GDB; openSUSE 13.2) 7.8
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://bugs.opensuse.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...

warning: /etc/gdbinit.d/gdb-heap.py: No such file or directory
Reading symbols from igotu2gpx...done.
(gdb) run
Starting program: /usr/local/bin/igotu2gpx --verbose info
Got object file from memory but can't read symbols: File truncated.
Missing separate debuginfos, use: zypper install glibc-debuginfo-2.19-16.9.1.x86_64
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7ffff3a71700 (LWP 3615)]
[New Thread 0x7fffeb5a4700 (LWP 3616)]
Downloading configuration...
[New Thread 0x7fffeada3700 (LWP 3617)]
Interface 0 already claimed by kernel driver, detaching
[New Thread 0x7fffea5a2700 (LWP 3618)]
Command: 930101030000000000000000000000
Protocol violated : Invalid response packet: 332c2c
Command: 930101030000000000000000000000
Result:
Command: 930a00000000000000000000000000
Device error: Device responded with error code: -2
Command: 930a00000000000000000000000000
Result: d70e0500031800010b0c
Command: 9305040003019f0000000000000000
Result: c22015
Command: 930b03001d00000000000000000000
Result: 004d32
Command: 930507100004030000000000000000
Result: 01156f20ff0fff3c00f1ffffffffffffffffffffffffffffffffffffffffffffffffffffffff
e200bb00171e001c08080404020202020000200f1601a00c280000000000000000000000000005000500
0000590130e05d01fcf51200040f917c8610917cdb01917c07c4c27718110000ffffff..............

<lots of gobbledegook deleted here>

................00000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000102030405060708090a0b0c0d0e0f
Command: 930101000000000000000000000000
Result:
QThread: Destroyed while thread is still running

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffea5a2700 (LWP 3618)]
0x00007ffff2e5a582 in ?? () from /usr/lib64/libusb-1.0.so.0
Missing separate debuginfos, use: zypper install fontconfig-debuginfo-2.11.1-2.1.2.x86_64 glibc-locale-debuginfo-2.19-16.9.1.x86_64 libICE6-debuginfo-1.0.9-2.1.3.x86_64 libSM6-debuginfo-1.2.2-4.1.2.x86_64 libX11-6-debuginfo-1.6.2-5.1.2.x86_64 libXau6-debuginfo-1.0.8-5.1.2.x86_64 libXcursor1-debuginfo-1.1.14-5.1.2.x86_64 libXext6-debuginfo-1.3.3-2.1.2.x86_64 libXfixes3-debuginfo-5.0.1-4.1.2.x86_64 libXi6-debuginfo-1.7.4-2.1.2.x86_64 libXinerama1-debuginfo-1.1.3-4.1.2.x86_64 libXrandr2-debuginfo-1.4.2-4.1.2.x86_64 libXrender1-debuginfo-0.9.8-4.1.2.x86_64 libboost_program_options1_54_0-debuginfo-1.54.0-10.1.3.x86_64 libexpat1-debuginfo-2.1.0-14.1.2.x86_64 libffi4-debuginfo-4.8.3+r212056-2.2.4.x86_64 libfreetype6-debuginfo-2.5.3-2.1.3.x86_64 libgcc_s1-debuginfo-4.8.3+r212056-2.2.4.x86_64 libglib-2_0-0-debuginfo-2.42.1-5.1.x86_64 libgobject-2_0-0-debuginfo-2.42.1-5.1.x86_64 libicu53_1-debuginfo-53.1-2.3.2.x86_64 libpcre1-debuginfo-8.35-3.2.3.x86_64 libpng16-16-debuginfo-1.6.13-2.4.1.x86_64 libqt4-debuginfo-4.8.6-4.4.1.x86_64 libqt4-x11-debuginfo-4.8.6-4.4.1.x86_64 libstdc++6-debuginfo-4.8.3+r212056-2.2.4.x86_64 libudev1-debuginfo-210-25.12.1.x86_64 libusb-1_0-0-debuginfo-1.0.19-2.1.2.x86_64 libuuid1-debuginfo-2.25.1-13.1.x86_64 libxcb1-debuginfo-1.11-2.1.2.x86_64 libz1-debuginfo-1.2.8-5.1.2.x86_64
(gdb) bt
#0 0x00007ffff2e5a582 in () at /usr/lib64/libusb-1.0.so.0
#1 0x00007ffff2e550fb in () at /usr/lib64/libusb-1.0.so.0
#2 0x00007ffff2e55d03 in libusb_handle_events_timeout_completed () at /usr/lib64/libusb-1.0.so.0
#3 0x00007ffff2e55dcf in libusb_handle_events () at /usr/lib64/libusb-1.0.so.0
#4 0x00007ffff30684f5 in WorkerThread::run() (this=0x7fffe4004740) at libusb10connection.cpp:136
#5 0x00007ffff74c379f in () at /usr/lib64/libQtCore.so.4
#6 0x00007ffff722d0a4 in start_thread () at /lib64/libpthread.so.0
#7 0x00007ffff674306d in clone () at /lib64/libc.so.6
(gdb)

Revision history for this message
Graham Dicker (graham-dicker) said :
#6

I hope I did this debug run correctly. My gdb command line syntax seems slightly different. Do I need to install glibc-debuginfo-2.19-16.9.1.x86_64? Is that why it said it couldn't load the symbols?

Revision history for this message
Graham Dicker (graham-dicker) said :
#7

Michael, did the above debug transcript help to diagnose the problem please?

Revision history for this message
Michael Hofmann (mh21) said :
#8

Sorry I didn't have time to look into it. I will only have time in the weekend :-(

Revision history for this message
Launchpad Janitor (janitor) said :
#9

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Graham Dicker (graham-dicker) said :
#10

I would still like to fix this if possible please

Revision history for this message
Launchpad Janitor (janitor) said :
#11

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Graham Dicker (graham-dicker) said :
#12

I would still like to fix this if possible please. I am learning how to communicate with another USB device (a camera) and as part of that project I have learned how to record a USB trace using usbmon. Would a USB trace of the igotu be of help?

Revision history for this message
Launchpad Janitor (janitor) said :
#13

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Graham Dicker (graham-dicker) said :
#14

I would still like to fix this please.

Revision history for this message
Launchpad Janitor (janitor) said :
#15

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Graham Dicker (graham-dicker) said :
#16

I would still like to fix this please.

Revision history for this message
Launchpad Janitor (janitor) said :
#17

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Graham Dicker (graham-dicker) said :
#18

I would still like to fix this please.

Revision history for this message
Launchpad Janitor (janitor) said :
#19

This question was expired because it remained in the 'Open' state without activity for the last 15 days.