Ubuntu
libusb package

Replace libusb-0.1 with libusb-compat-0.1

Bug #991004 reported by Marius B. Kotsbak on 2012-04-29

This bug affects 6 people

Affects		Status	Importance	Assigned to	Milestone
	libusb (Debian)	New	Unknown	debbugs #731424
	libusb (Ubuntu)	Confirmed	Wishlist	Unassigned

Bug Description

See http://www.libusb.org/wiki/libusb-compat-0.1

From http://www.libusb.org/:

"However, if you have installed libusb-1.0 then we strongly recommend to use libusb-compat-0.1 instead of the ancient libusb-0.1 code, so that programs which use both the 0.1 API and the 1.0 API in different parts of the program, or in different libraries used by the program, will both end up using libusb-1.0 for actual device access. This is important to avoid potential conflicts between libusb-1.0 and libusb-0.1 being used by the same process."

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: libusb-0.1-4 2:0.1.12-20
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
Uname: Linux 3.2.0-24-generic-pae i686
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
Date: Sun Apr 29 12:23:48 2012
EcryptfsInUse: Yes
ProcEnviron:
LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
TERM=xterm
PATH=(custom, user)
LANG=nb_NO.UTF-8
SHELL=/bin/bash
SourcePackage: libusb
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Marius B. Kotsbak (mariusko) wrote on 2012-04-29:

Dependencies.txt Edit (448 bytes, text/plain; charset="utf-8")

Revision history for this message

Marius B. Kotsbak (mariusko) wrote on 2012-04-29:

As a workaround, here is how to replace it manually:

* Download libusb-compat from here: http://www.libusb.org/wiki/libusb-compat-0.1
* sudo aptitude install libusb-1.0-0-dev
* ./configure
* make
* sudo dpkg -r --force-all libusb-0.1-4
* make install

Revision history for this message

Marek Kalnik (wdev) wrote on 2012-09-18:

Hi,

I'm trying to install gphoto2 with libgphoto-2.5.0. On cofigure I get a message:
* Fatal: libgphoto2 port access library by default requires libusb >= 0.1.5 to build.

Possible solutions:
* - if you have libusb >= 1.0 installed, you must also install
* either the libusb0 compat library or a libusb 0.x version

It would be nice to have the libusb-compat available (or even installed by default), it works well for me.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-01-24:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in libusb (Ubuntu):
status:	New → Confirmed

Revision history for this message

Bart Swinnen (saribro) wrote on 2013-02-15:

I'd like to add my voice to this request.

We have a commercial application which relies on libusb. On Windows we have built/packaged libusb-0 ourselves and have no issues. On Linux we rely on the system's libusb. This showed no issues on Fedora (our main Linux platform), which ships libusb-compat. We've semi-recently added Ubuntu builds, but we run into problems due to the libusb-0 package.
Applying Marius' manual replacement solves our application problems, but of course the update manager will try to reinstall the libusb-0 package. It's a little tricky to communicate this situation to customers.
Also, as the bug description mentions, we could run into 0.1 and 1.0 mingling when a customer uses our SDK in their own application.
Availability of a libusb-compat package would be a great help.

Dylan Aïssi (daissi) on 2014-07-27

no longer affects:

libusb

Bug Watch Updater (bug-watch-updater) on 2014-07-27

Changed in libusb (Debian):
status:	Unknown → New

Mathew Hodson (mhodson) on 2015-11-29

Changed in libusb (Ubuntu):
importance:	Undecided → Wishlist

Revision history for this message

Martinique (martinique) wrote on 2020-01-18:

IMO this should be above "wishlist" importance, because the lcdproc project had to disable a lot of display drivers (such as hd44780-lcd2usb) still relying on libusb 0.1 API, while libusb-compat-0.1 probably would've solved their issues easily. An LCD that worked perfectly with Ubuntu 16.04 is now dead in 18.04.

I fail to see why Debian maintainers are so worried about introducing some corner case bugs while things are breaking completely without the compatibility wrapper. Apparently it's just a matter of packaging libusb-compat-0.1 and making it conflict with libusb-0.1 so that only either one can be used.