https://bugzilla.novell.com/show_bug.cgi?id=443861 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Factory |Beta4 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=443861 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=443861#c3 --- Comment #3 from Stefan Dirsch 2008-11-12 06:58:20 MST --- (In reply to comment #2 from Stanislav Brabec)

gpsbabel -i mtk,erase=0 -f /dev/ttyUSB0 -o mtkbin -F log.bin works for me.

According to http://www.gpsbabel.org/os/Linux_Hotplug.html using the garmin kernel module is not recommended. This is also what Robert Lipe recently stated on the gpsbabel-misc mailing list. Date: Tue, 11 Nov 2008 10:57:10 -0600 From: Robert Lipe To: Mishustin Alexey Cc: gpsbabel-misc@lists.sourceforge.net Subject: Re: [Gpsbabel-misc] How to upload tracks with all trackpoints [...] "Remove the kernel driver (which works badly for a large number of people) and use "usb:" instead of "/dev/ttyUSB0"." [...]

=> It may be a problem of libusb usage

I don't think people will care about such an argument, when they suddently notice that their favorite applications no longer work. I simply don't understand why we introduced this compatibility layer, when we need to ship both library versions anyway. I see only regressions and no benefits at all here. I also didn't see any FATE request or bugreport to introduce such a compatibility layer instead of keeping the old implementation as it is (working). Also libusb 1.0 is still considered BETA.

As you have beta4, I guess that you have latest version of libusb-compat:

rpm -q --changelog libusb-0_1-4 | grep -A4 meissner@suse.de * Wed Oct 08 2008 meissner@suse.de - handle case where usb_init() failed (ctx NULL), so we do not crash. bnc#432129 - added more NULL ptr checks, where older libusb were more graceful and did not crash. bnc#432129

Sure I have including this change * Properly obsolete old implementation of the library (bnc#437768). I even builded every older versions of this package and rebuilded gpsbabel against it. Same problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=443861 User sbrabec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=443861#c5 --- Comment #5 from Stanislav Brabec 2008-11-12 07:40:06 MST ---

...

=> It may be a problem of libusb usage

I don't think people will care about such an argument, when they suddently notice that their favorite applications no longer work

Well, there are slight differences between behavior of libusb-0_1-4 and libusb-compat. In some situations, where libusb-0_1-4 behavior is "possibly crash", the behavior of libusb-compat is EINVAL (e. g. bug 432129 - double usb_close). "Possibly crash" may mean "it actually works" and EINVAL means "it stopped to work" and then user could see a regression. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=443861 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=443861#c7 --- Comment #7 from Stefan Dirsch 2008-11-12 07:49:10 MST --- Thanks for explanation, Stanislav. I now understand why we introduced this compat library. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=443861 User sbrabec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=443861#c9 Stanislav Brabec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #9 from Stanislav Brabec 2008-11-12 10:01:26 MST --- libusb-compat seems to be bug incompatible with libusb0. Reverting to libusb0. Applications can still be built against libusb-1.0 using libusb-compat-devel instead of libusb-devel. Please report failures of these packages to upstream: libusb-devel@lists.sourceforge.net For 11.1, only packages explicitly testing libusb-1.0 support will use libusb-1.0. After 11.1, working packages can be migrated to libusb-1.0. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=443861 User sbrabec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=443861#c11 --- Comment #11 from Stanislav Brabec 2008-11-12 10:37:12 MST --- See bug 439574 and bug 432129 for more regressions. Upstream report: http://sourceforge.net/mailarchive/forum.php?thread_name=1226510657.1845.60.camel%40hammer.suse.cz&forum_name=libusb-devel opensuse-factory announce: http://lists.opensuse.org/opensuse-factory/2008-11/msg00456.html -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=443861 User meissner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=443861#c13 --- Comment #13 from Marcus Meissner 2008-11-19 09:39:02 MST --- run with export USB_DEBUG=255 to get lots of debugging output -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.