libusb-devel Mailing List for libusb

On 16 Apr 2026, at 8:17, Rob Davidson via libusb-devel wrote:

> however I need to use a release

Why?  How about using the 1.0.30-rc1 "release"?

Sean

It doesn't make sense to discuss bugs already fixed on the master branch.
Open source software very often requires patches to work on niche
platforms.  You should build from a commit on master since it works for
you. Alternatively, use "git bisect" to efficiently find which specific
commit on the master branch fixes your issue, and then apply it as a patch
to v1.0.29 in your build process.

--David

On Thu, Apr 16, 2026 at 3:53 PM Rob Davidson via libusb-devel <
lib...@li...> wrote:

> Hello,
>
>
>
> I was able to checkout master and build it (Win32 or x64), however I need
> to use a release and cannot get the tag for v 1.0.29 to build in either
> Win32 or x64 configurations.  My end goal is to re-target libusb for use on
> a Snapdragon/ARM64 processor.  Can someone verify the tag for 1.0.29 builds
> correctly in VS2022?  If needed, I can provide more details (unfortunately,
> I’ve already deleted it, but I can recreate – all I did was create a local
> branch off of the tag for v 1.0.29, open 2022 and try to build it).  Note,
> I have the necessary C++ development installed and MSVC v143 as well.
>
>
>
> On a side note, since Microsoft is leaning towards the Snapdragon
> processors for Windows 11 based laptops and tablets, are there any plans to
> provide libusb binaries for that architecture?  That would be a great idea
> to put on the list for the next release or soon after.
>
>
>
> Regards,
>
> Rob Davidson
>
>
>
>
>
>
> _______________________________________________
> libusb-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-devel
>

Hello,

I was able to checkout master and build it (Win32 or x64), however I need to use a release and cannot get the tag for v 1.0.29 to build in either Win32 or x64 configurations.  My end goal is to re-target libusb for use on a Snapdragon/ARM64 processor.  Can someone verify the tag for 1.0.29 builds correctly in VS2022?  If needed, I can provide more details (unfortunately, I've already deleted it, but I can recreate - all I did was create a local branch off of the tag for v 1.0.29, open 2022 and try to build it).  Note, I have the necessary C++ development installed and MSVC v143 as well.

On a side note, since Microsoft is leaning towards the Snapdragon processors for Windows 11 based laptops and tablets, are there any plans to provide libusb binaries for that architecture?  That would be a great idea to put on the list for the next release or soon after.

Regards,
Rob Davidson

Hello libusb mailing list,

I’m a vulnerability analyst at VulnCheck <https://www.vulncheck.com/>, an
exploit intelligence company and research CVE Numbering Authority (CNA),
where I'm one of several folks who manage our coordinated vulnerability
disclosure (CVD) program.

An external security researcher recently reported
<https://www.vulncheck.com/advisories/report> a vulnerability
impacting the libusb
<https://github.com/libusb/libusb>codebase (discovered when testing against
version 1.0.29), and VulnCheck is acting as the intermediary and
coordinator.

VulnCheck follows a 120-day disclosure policy
<https://www.vulncheck.com/vulnerability-disclosure-policy>, meaning we
afford vendors/maintainers up to 120 days from the time of receiving the
report to address the issue before publication of a CVE record and
third-party advisory. For this vulnerability, that 120-day deadline falls
on *August 7 2026*.

We have provisionally reserved the following CVE ID, which have been shared
with the researcher but will remain private until public disclosure:
*CVE-2026-23679*

Please be aware that none of this information is public at this moment and
all parties involved are considered under embargo. The researcher has
provided us with a comprehensive technical report including reproduction
steps. Once an appropriate medium and point of contact are identified, we'd
be happy to share those materials with your team.

If interested in VulnCheck's previous disclosures, you may find those here
<https://www.vulncheck.com/advisories>.

Let us know if you have any questions for us about the CVD process or for
the researcher regarding the reported vulnerability.

Best regards,

<https://www.vulncheck.com/>

Wade Sparks III
VulnCheck
Senior Vulnerability Analyst

Unfortunately this is an area which very few people are familiar with.

We do not have a good example either.
https://github.com/libusb/libusb/issues/816

You may want to try your luck to comment on the above issue or open a
new discussion in github libusb project.
https://github.com/libusb/libusb/discussions

--
Xiaofan

On Mon, Mar 2, 2026 at 5:15 PM Praveena G via libusb-devel
<lib...@li...> wrote:
>
> Hi Everyone,
>
> I hope you’re doing well. I’m following up on my earlier email regarding performance considerations for sending SCSI commands using libusb vs. the UAS driver stack with io_uring.
>
> We would greatly appreciate and value any insights that you can share. Thanks in advance for your guidance.
>
> Best regards,
> Praveena G
>
>
> From: Praveena G
> Sent: Thursday, February 19, 2026 3:55 PM
> To: 'lib...@li...' <lib...@li...>
> Cc: Mayank Mishra <May...@sa...>; Vijay Mhapsekar <Vij...@sa...>; Rushabha Jain <rus...@sa...>; Hrithik Raj <hri...@sa...>
> Subject: Seeking Guidance on High-Speed SCSI Command Execution in Linux: libusb vs UAS Driver/IO_uring Performance Implications
>
> Hi Everyone,
>
> I hope this email finds you well. We are currently working on developing a solution in Linux to
> send SCSI commands in UAS and BOT mode, with our primary goal being to achieve
> high-speed performance. So far, we have explored a couple of promising approaches: one using libusb and the other leveraging the internal UAS driver stack in combination with io_uring.
>
> We have successfully implemented a proof of concept (POC) using libusb, which allows us to continuously send all SCSI commands. To achieve asynchronous transfer, we are utilizing the `libusb_fill_bulk_stream_transfer()` and `libusb_handle_events_completed()` APIs.
>
> However, we have a query regarding the performance implications of libusb operating in user space. Specifically, for each command, there are three context switches between the kernel and user space to provide callbacks for the command phase, data phase, and status phase. We are concerned that these context switches might slow down the overall performance.
>
> On the other hand, we understand that the underlying UAS driver stack can be directly accessed and used to send commands with a single API call, thereby reducing context switches. Additionally, the io_uring approach, which utilizes a shared ring buffer between user space and the kernel, minimizes system call overhead and could potentially offer faster performance.
>
> Given these considerations, we are curious about the potential advantages of using libusb in this scenario. Could you please help us understand the benefits of libusb and guide us on the best approach to achieve high-speed performance? We would greatly appreciate any suggestions or insights you could provide to help us improve our solution.
>
> Thank you in advance for your assistance and expertise.
>
> Best regards,
>
> Praveena G

Hi Everyone,

I hope you're doing well. I'm following up on my earlier email regarding performance considerations for sending SCSI commands using libusb vs. the UAS driver stack with io_uring.

We would greatly appreciate and value any insights that you can share. Thanks in advance for your guidance.

Best regards,
Praveena G


From: Praveena G
Sent: Thursday, February 19, 2026 3:55 PM
To: 'lib...@li...' <lib...@li...>
Cc: Mayank Mishra <May...@sa...>; Vijay Mhapsekar <Vij...@sa...>; Rushabha Jain <rus...@sa...>; Hrithik Raj <hri...@sa...>
Subject: Seeking Guidance on High-Speed SCSI Command Execution in Linux: libusb vs UAS Driver/IO_uring Performance Implications

Hi Everyone,

I hope this email finds you well. We are currently working on developing a solution in Linux to send SCSI commands in UAS and BOT mode, with our primary goal being to achieve high-speed performance. So far, we have explored a couple of promising approaches: one using libusb and the other leveraging the internal UAS driver stack in combination with io_uring.

We have successfully implemented a proof of concept (POC) using libusb, which allows us to continuously send all SCSI commands. To achieve asynchronous transfer, we are utilizing the `libusb_fill_bulk_stream_transfer()` and `libusb_handle_events_completed()` APIs.

However, we have a query regarding the performance implications of libusb operating in user space. Specifically, for each command, there are three context switches between the kernel and user space to provide callbacks for the command phase, data phase, and status phase. We are concerned that these context switches might slow down the overall performance.

On the other hand, we understand that the underlying UAS driver stack can be directly accessed and used to send commands with a single API call, thereby reducing context switches. Additionally, the io_uring approach, which utilizes a shared ring buffer between user space and the kernel, minimizes system call overhead and could potentially offer faster performance.

Given these considerations, we are curious about the potential advantages of using libusb in this scenario. Could you please help us understand the benefits of libusb and guide us on the best approach to achieve high-speed performance? We would greatly appreciate any suggestions or insights you could provide to help us improve our solution.

Thank you in advance for your assistance and expertise.

Best regards,
Praveena G

This is the first release candidate for libusb 1.0.30.

Please help with testing the RC on various platforms and with as many
applications and devices as possible. We have a test tracker at
https://github.com/libusb/libusb/issues/1757 to track what has been
tested.

The RC source code tarball can be downloaded here:
https://github.com/libusb/libusb/releases/download/v1.0.30-rc1/libusb-1.0.30-rc1.tar.bz2

An archive of Windows binaries can be downloaded here:
https://github.com/libusb/libusb/releases/download/v1.0.30-rc1/libusb-1.0.30-rc1.7z

Note that the RC tarball includes a configure script so unlike a git
checkout it is not necessary to bootstrap it with autoconf. The
"check" target will run a number of tests:
  tar jxvf libusb-1.0.30-rc1.tar.bz2
  cd libusb-1.0.30-rc1
  ./configure --enable-tests-build --enable-examples-build
  make check

The current ChangeLog:
* Add hotplug support on Microsoft Windows
* Add RAW_IO support in WinUSB backend
* Work around a macOS 26 Tahoe compatibility breakage due to Apple
changing kUSBHostPortPropertyPortNumber
* Add new API libusb_get_device_string() to access device strings
without opening the device
* Add new API libusb_get_session_data() which returns the OS-specific handle
* On Android, fix intermittent failures in get_usbfs_fd()
* On Windows, fix bus number assignment for root hub device,
preventing duplicate bus number assignments
* Fix compilation with Microsoft Visual Studio 2026
* Fix various compiler warnings, improved tests and examples

Since 1.0.29, 51 commits by 19 contributors (10 new)

There is now optional support for hotplug on Windows. There are still
issues with e.g. composite devices, so it is not enabled by default,
and must be enabled at build time. The 7z archive with Windows
binaries includes both hotplug and default build variants.

Tormod

Hi Everyone,

I hope this email finds you well. We are currently working on developing a solution in Linux to send SCSI commands in UAS and BOT mode, with our primary goal being to achieve high-speed performance. So far, we have explored a couple of promising approaches: one using libusb and the other leveraging the internal UAS driver stack in combination with io_uring.

We have successfully implemented a proof of concept (POC) using libusb, which allows us to continuously send all SCSI commands. To achieve asynchronous transfer, we are utilizing the `libusb_fill_bulk_stream_transfer()` and `libusb_handle_events_completed()` APIs.

However, we have a query regarding the performance implications of libusb operating in user space. Specifically, for each command, there are three context switches between the kernel and user space to provide callbacks for the command phase, data phase, and status phase. We are concerned that these context switches might slow down the overall performance.

On the other hand, we understand that the underlying UAS driver stack can be directly accessed and used to send commands with a single API call, thereby reducing context switches. Additionally, the io_uring approach, which utilizes a shared ring buffer between user space and the kernel, minimizes system call overhead and could potentially offer faster performance.

Given these considerations, we are curious about the potential advantages of using libusb in this scenario. Could you please help us understand the benefits of libusb and guide us on the best approach to achieve high-speed performance? We would greatly appreciate any suggestions or insights you could provide to help us improve our solution.

Thank you in advance for your assistance and expertise.

Best regards,
Praveena G

We are happy to announce the release of libusb 1.0.29.

This is a follow-up release with selected important changes and
regression fixes. All users and distributions are recommended to
upgrade from 1.0.28 to 1.0.29.

Note I forgot to bump the LIBUSB_API_VERSION macro in 1.0.28 although
we had added new functions, so using this macro to check for the
availability of these functions will only work with 1.0.29.

The macOS regression in 1.0.28 affected some devices (typically slower
devices/systems).

ChangeLog with most important changes since previous release 1.0.28:
* Fix regression on macOS leading to timeouts in enumeration
* LIBUSB_API_VERSION bump for the new functions in 1.0.28
* Fix xusb regression displaying wrong error on claim failure

The source code tarball can be downloaded here:
https://github.com/libusb/libusb/releases/download/v1.0.29/libusb-1.0.29.tar.bz2

An archive of Windows binaries can be downloaded here:
https://github.com/libusb/libusb/releases/download/v1.0.29/libusb-1.0.29-binaries.7z

Note that the release tarball includes a configure script so unlike a
git checkout it is not necessary to bootstrap with autoconf.

On behalf of the libusb development community,
Tormod


--

$ git shortlog v1.0.28..v1.0.29

Oleksand Radovenchyk (1):
      chore: Remove broken or stale build badges from README

Tormod Volden (5):
      docs: Refer to Topics instead of Modules
      Bump LIBUSB_API_VERSION
      xusb: Fix error reporting on interface claim
      docs: Document SuperSpeedPlus device capability functions
      libusb 1.0.29

Zeng Guang (1):
      darwin: Fix regression causing re-enumeration timeout

On Wed, Apr 30, 2025 at 6:31 AM McKenzie, Eric via libusb-devel
<lib...@li...> wrote:
>
> Hi,
> I'd like to check out the source for libusbdotnet that matches NuGet version 2.2.75.
> I can't seem to find the link between the nuget version and the source code in github.
>  (https://github.com/LibUsbDotNet/LibUsbDotNet)
>
> Any help would be appreciated, thank you.

I believe it is corresponding to the following commit.
https://github.com/LibUsbDotNet/LibUsbDotNet/commit/2d7289ab5d4059ac9bfbde666cfb0d4825d89814

Please go to the following issue and comment there.
https://github.com/LibUsbDotNet/LibUsbDotNet/issues/230

--
Xiaofan

Hi,
I'd like to check out the source for libusbdotnet that matches NuGet version 2.2.75.   I can't seem to find the link between the nuget version and the source code in github.   (https://github.com/LibUsbDotNet/LibUsbDotNet)

Any help would be appreciated, thank you.


  *
Eric



Eric McKenzie | Principal Software Engineer | Excelitas Technologies
1 Fortune Drive | Billerica, MA 01821 | *: 978-439-3455 |  Cell: 781-572-5135

*: Eri...@Ex...<mailto:Eri...@Ex...>

We are happy to announce the final release of libusb 1.0.28.

This is a rather small maintenance release with a few bug and build
fixes in addition to one new API function.

ChangeLog with most important changes since previous release 1.0.27:
* New libusb_get_ssplus_usb_device_capability_descriptor API
  for query of SuperSpeed+ Capability Descriptors
* API support for reporting USB 3.2 Gen2x2 speeds
* macOS: Fix Zero-Length Packet for multiple packets per frame
* Windows: Base HID device descriptor on OS-cached values
* Build fixes for Haiku and SunOS
* Many code correctness fixes

The source code tarball can be downloaded here:
https://github.com/libusb/libusb/releases/download/v1.0.28/libusb-1.0.28.tar.bz2

An archive of Windows binaries can be downloaded here:
https://github.com/libusb/libusb/releases/download/v1.0.28/libusb-1.0.28.7z

Note that the release tarball includes a configure script so unlike a
git checkout it is not necessary to bootstrap with autoconf.

The 1.0.28 release was made possible by the contributions from all
patch submitters (see below git shortlog with 64 commits from 12
contributors, of which 6 new) plus everyone who contributed with issue
reporting, discussions and testing.

On behalf of the libusb development community,
Tormod


--

Adrien Destugues (1):
      haiku: Use gcc atomic builtins to fix build

Fabien Sanglard (5):
      Add support for SuperSpeed+ Capability Descriptors
      SuperSpeedPlus: Fix typo mantisa -> mantissa in struct field
      Cosmetic cleanup of SuperSpeedPlus comments
      docs: Document internal_ssplus_capability_descriptor
      macos: Fix Zero-Length Packet for multiple packets per frame

Francis Hart (1):
      windows: Restore behaviour of skipping malformed device GUIDs

Harry Mallon (1):
      Add API support for LIBUSB_SPEED_SUPER_PLUS_X2 20Gbps USB 3.2 gen 2x2

Jesse Taube (1):
      CI: Remove build job for MSYS clang32

Jon Beniston (1):
      Emscripten: Avoid uncaught TypeError on browsers without USB support

Matthijs Lavrijsen (1):
      winusb: Fix winusb_get_device_list() failing to find port numbers

Radu Vele (1):
      Enable linux netlink event monitoring for Android OS platform services

Sean McBride (32):
      Add clang-tidy config file
      xusb: Avoid warning about implicit switch fallthrough
      Fix most warnings about implicit sign conversion
      darwin: Correct interpretation of COM-style Release() return value
      xcode: Enable several additional warnings in the Xcode project
      darwin: Fix clang static analyzer warning about a variable
that's never read
      darwin: Suppress false positive warning with an assert
      Increase usbi_get_tid() size from int to long
      darwin: Cleanup of usbi_backend structure
      descriptor: Replace parse_descriptor() function
      descriptor: Defer potentially truncating cast to last minute
      descriptor: Restore implicitly casted-away const
      descriptor: Fix potential offsetting of pointer by too much
      descriptor: Small clarifications with no behaviour change
      descriptor: Avoid buffer over-increment in parse_iad_array function
      examples/ezusb: Replace rewind with fseek, to check for errors
      examples/fxload: Eliminate all reserved C identifiers (leading
underscores)
      examples/xusb: Make all macro replacement lists parenthesized
      examples/xusb: Make some parameters const where possible
      examples/xusb: Match size of loop index to what is iterated
      darwin: Always use uppercase literal suffixes for improved readability
      darwin: Explicitly compare string compare function results to -1, 0, or 1
      darwin: Fix multiplication overflow by better matching type sizes
      Avoid assignments within `if` statements
      descriptor: Eliminate all duplicate branch bodies, as they are bug-prone
      descriptor: Fix addition overflow by correcting casts
      libusb.h: Match parameter names in declaration and definition
      clang-tidy: Stop suppressing readability-misleading-indentation warnings
      Replace atoi() with strtol() which allows error checking
      examples/ezusb: Fix error checking regression in recent commit
      xcode: Adjust file indentation settings
      descriptor: Fix clang -Wimplicit-int-conversion warnings

Sylvain Fasel (2):
      hotplug_exit: Remove parents recursively
      hotplug_exit: Mutex protection of context device list while cleaning it

Tormod Volden (17):
      sunos: Fix typos breaking build
      emscripten: Remove superfluous capability
      linux: Fix type of open() flags argument
      linux: ioctl() request number is unsigned long
      xusb: Only retrieve BOS descriptor for bcdUSB 0x0201 or higher
      windows: Downgrade get_guid DeviceInterfaceGUID message to debug level
      Consistent use of C-style comment markers
      Add KEYS file for release files verification
      netbsd: Debug print all errors
      openbsd: Use default clause in _errno_to_libusb()
      windows: Base HID device descriptor on cached values
      docs: Hide internal descriptor.c structure from doxygen
      docs: Fix broken doxygen references
      libusb 1.0.28-rc1
      core: Avoid infinite recursion on invalid LIBUSB_DEBUG value
      configure.ac: Bump libtool library version
      libusb 1.0.28

Yiwei Lin (1):
      xusb: Define proper exit status

This is the first release candidate for libusb 1.0.28.

Please help with testing the RC on various platforms and with as many
applications and devices as possible. We have a test tracker at
https://github.com/libusb/libusb/issues/1615 to track what has been
tested.

Download:
https://github.com/libusb/libusb/releases/download/v1.0.28-rc1/libusb-1.0.28-rc1.tar.bz2

Note that the RC tarball includes a configure script so unlike a git
checkout it is not necessary to bootstrap it with autoconf. The
"check" target will run a number of tests:
  tar jxvf libusb-1.0.28-rc1.tar.bz2
  cd libusb-1.0.28-rc1
  ./configure --enable-tests-build --enable-examples-build
  make check

The current ChangeLog:
* New libusb_get_ssplus_usb_device_capability_descriptor API
  for query of SuperSpeed+ Capability Descriptors
* API support for reporting USB 3.2 Gen2x2 speeds
* macOS: Fix Zero-Length Packet for multiple packets per frame
* Windows: Base HID device descriptor on OS-cached values
* Build fixes for Haiku and SunOS
* Many code correctness fixes

Since 1.0.27, 61 commits by 12 contributors (6 new!)

This is a rather small maintenance release with a few bug and build
fixes in addition to the new API function.

Tormod

Hi everyone,

Are there currently any plans on getting pull request #1521 merged?

As a reminder, this fixes a Windows corner case where the same bus number can
get assigned to multiple different root hubs. This is quite an annoying bug to 
work around, and I think it's quite important to fix it.

Of course, I'd be happy to address any concerns or requests regarding the pull
request itself.

Link to the pull request: https://github.com/libusb/libusb/pull/1521

Best Regards,

-- 
Romain Gantois, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Thank you @David Grayson<mailto:dav...@gm...>!!

You are correct, My ubuntu system itself is somewhat broken as update command is also not working.

sudo apt-get  update
apt-get: error while loading shared libraries: libcgmanager.so.0: cannot open shared object file: No such file or directory

Regards,
Swati

From: David Grayson <dav...@gm...>
Sent: Thursday, October 24, 2024 9:47 PM
To: Swati Agarwal <swa...@qt...>
Cc: Tim Roberts <ti...@pr...>; lib...@li...
Subject: Re: [libusb] Need help in installing libusb library


WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
Your problem has nothing to do with libusb.  Your Ubuntu system is broken.  You might have to reinstall it, or maybe you can find a copy of that library from a different *trusted* system and copy it over.  --David

On Thu, Oct 24, 2024 at 1:59 AM Swati Agarwal <swa...@qt...<mailto:swa...@qt...>> wrote:
Hi,


Output of ldd /usr/bin/apt-get in which it says libcgmanager.so.0 => not found

        linux-vdso.so.1 (0x00007fffc7572000)
        libapt-private.so.0.0 => /lib/x86_64-linux-gnu/libapt-private.so.0.0 (0x00007f0b8a228000)
        libapt-pkg.so.6.0 => /lib/x86_64-linux-gnu/libapt-pkg.so.6.0 (0x00007f0b8a061000)
        libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f0b89e35000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f0b89e15000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f0b89bec000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f0b89bce000)
        libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x00007f0b89bbb000)
        liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f0b89b90000)
        liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1 (0x00007f0b89b70000)
        libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x00007f0b89aa1000)
        libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x00007f0b89800000)
        libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x00007f0b89739000)
        libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007f0b895fb000)
        libxxhash.so.0 => /lib/x86_64-linux-gnu/libxxhash.so.0 (0x00007f0b89a8a000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f0b89514000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f0b8a2b4000)
        libcgmanager.so.0 => not found
        libnih.so.1 => not found
        libnih-dbus.so.1 => not found
        libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007f0b89a3a000)
        librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f0b89a35000)
        libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x00007f0b89a2a000)
        libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007f0b894ee000)

Regards,
Swati

From: Swati Agarwal
Sent: Thursday, October 24, 2024 1:04 PM
To: David Grayson <dav...@gm...<mailto:dav...@gm...>>; Tim Roberts <ti...@pr...<mailto:ti...@pr...>>
Cc: lib...@li...<mailto:lib...@li...>
Subject: RE: [libusb] Need help in installing libusb library

Hi David,

I tried this as well but getting similar error

sudo apt-get install libusb-1.0-0-dev
apt-get: error while loading shared libraries: libcgmanager.so.0: cannot open shared object file: No such file or directory

The question still boil out to , if ubuntu version is 22.04, what are the ways to install libcgmanager.

Regards,
Swati

From: David Grayson <dav...@gm...<mailto:dav...@gm...>>
Sent: Thursday, October 24, 2024 12:43 PM
To: Tim Roberts <ti...@pr...<mailto:ti...@pr...>>
Cc: lib...@li...<mailto:lib...@li...>
Subject: Re: [libusb] Need help in installing libusb library


WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

Instead of downloading libusb's source just install it with apt-get:

sudo apt-get install libusb-1.0-0-dev

--David

On Thu, Oct 24, 2024, 12:09 AM Tim Roberts <ti...@pr...<mailto:ti...@pr...>> wrote:

On 10/23/24 10:11 PM, Swati Agarwal via libusb-devel wrote:

getting below error while installing it---

error while loading shared libraries: libcgmanager.so.0: cannot open shared object file: No such file or directory

sudo apt-get install libcgmanager
apt-get: error while loading shared libraries: libcgmanager.so.0: cannot open shared object file: No such file or directory

Did you search for this at all before asking?  You need to install the libcgmanager0 package:

https://askubuntu.com/questions/715714/error-loading-shared-libraries-libcgmanager-so-0-no-such-file-or-directory
--

Tim Roberts, ti...@pr...<mailto:ti...@pr...>
_______________________________________________
libusb-devel mailing list
lib...@li...<mailto:lib...@li...>
https://lists.sourceforge.net/lists/listinfo/libusb-devel

Its throwing similar error.

sudo apt install libcgmanager0

apt: error while loading shared libraries: libcgmanager.so.0: cannot open shared object file: No such file or directory

Regards,
Swati
From: Tim Roberts <ti...@pr...>
Sent: Friday, October 25, 2024 12:06 AM
To: lib...@li...
Subject: Re: [libusb] Need help in installing libusb library


WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
Swati Agarwal wrote:
Hi Tim,

As mentioned below, I tried to install it


  1.  sudo apt-get install libcgmanager -- apt-get: error while loading shared libraries: libcgmanager.so.0: cannot open shared object file: No such file or directory

I don't think you read my message at all.  The APT package is called "libcgmanager0" with a trailing 0.

--

Tim Roberts, ti...@pr...<mailto:ti...@pr...>

Swati Agarwal wrote:
>
> Hi Tim,
>
> As mentioned below, I tried to install it
>
>  1. sudo apt-get install libcgmanager -- apt-get: error while loading
>     shared libraries: libcgmanager.so.0: cannot open shared object
>     file: No such file or directory
>
I don't think you read my message at all.  The APT package is called 
"libcgmanager0" with a trailing 0.

-- 
Tim Roberts,ti...@pr...

Your problem has nothing to do with libusb.  Your Ubuntu system is broken.
You might have to reinstall it, or maybe you can find a copy of that
library from a different *trusted* system and copy it over.  --David

On Thu, Oct 24, 2024 at 1:59 AM Swati Agarwal <swa...@qt...>
wrote:

> Hi,
>
>
>
>
>
> Output of ldd /usr/bin/apt-get in which it says libcgmanager.so.0 => not
> found
>
>
>
>         linux-vdso.so.1 (0x00007fffc7572000)
>
>         libapt-private.so.0.0 =>
> /lib/x86_64-linux-gnu/libapt-private.so.0.0 (0x00007f0b8a228000)
>
>         libapt-pkg.so.6.0 => /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
> (0x00007f0b8a061000)
>
>         libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6
> (0x00007f0b89e35000)
>
>         libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
> (0x00007f0b89e15000)
>
>         libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f0b89bec000)
>
>         libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f0b89bce000)
>
>         libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0
> (0x00007f0b89bbb000)
>
>         liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5
> (0x00007f0b89b90000)
>
>         liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1
> (0x00007f0b89b70000)
>
>         libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1
> (0x00007f0b89aa1000)
>
>         libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1
> (0x00007f0b89800000)
>
>         libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0
> (0x00007f0b89739000)
>
>         libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20
> (0x00007f0b895fb000)
>
>         libxxhash.so.0 => /lib/x86_64-linux-gnu/libxxhash.so.0
> (0x00007f0b89a8a000)
>
>         libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f0b89514000)
>
>         /lib64/ld-linux-x86-64.so.2 (0x00007f0b8a2b4000)
>
>         libcgmanager.so.0 => not found
>
>         libnih.so.1 => not found
>
>         libnih-dbus.so.1 => not found
>
>         libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3
> (0x00007f0b89a3a000)
>
>         librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f0b89a35000)
>
>         libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2
> (0x00007f0b89a2a000)
>
>         libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0
> (0x00007f0b894ee000)
>
>
>
> Regards,
>
> Swati
>
>
>
> *From:* Swati Agarwal
> *Sent:* Thursday, October 24, 2024 1:04 PM
> *To:* David Grayson <dav...@gm...>; Tim Roberts <ti...@pr...
> >
> *Cc:* lib...@li...
> *Subject:* RE: [libusb] Need help in installing libusb library
>
>
>
> Hi David,
>
>
>
> I tried this as well but getting similar error
>
>
>
> sudo apt-get install libusb-1.0-0-dev
>
> apt-get: error while loading shared libraries: libcgmanager.so.0: cannot
> open shared object file: No such file or directory
>
>
>
> The question still boil out to , if ubuntu version is 22.04, what are the
> ways to install libcgmanager.
>
>
>
> Regards,
>
> Swati
>
>
>
> *From:* David Grayson <dav...@gm...>
> *Sent:* Thursday, October 24, 2024 12:43 PM
> *To:* Tim Roberts <ti...@pr...>
> *Cc:* lib...@li...
> *Subject:* Re: [libusb] Need help in installing libusb library
>
>
>
> *WARNING:* This email originated from outside of Qualcomm. Please be wary
> of any links or attachments, and do not enable macros.
>
> Instead of downloading libusb's source just install it with apt-get:
>
> sudo apt-get install libusb-1.0-0-dev
>
> --David
>
>
>
> On Thu, Oct 24, 2024, 12:09 AM Tim Roberts <ti...@pr...> wrote:
>
> On 10/23/24 10:11 PM, Swati Agarwal via libusb-devel wrote:
>
>
>
> getting below error while installing it---
>
>
>
> error while loading shared libraries: libcgmanager.so.0: cannot open
> shared object file: No such file or directory
>
>
>
> sudo apt-get install libcgmanager
>
> apt-get: error while loading shared libraries: libcgmanager.so.0: cannot
> open shared object file: No such file or directory
>
> Did you search for this at all before asking?  You need to install the
> libcgmanager0 package:
>
>
> https://askubuntu.com/questions/715714/error-loading-shared-libraries-libcgmanager-so-0-no-such-file-or-directory
>
> --
>
> Tim Roberts, ti...@pr...
>
> _______________________________________________
> libusb-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-devel
>
>

Hi,


Output of ldd /usr/bin/apt-get in which it says libcgmanager.so.0 => not found

        linux-vdso.so.1 (0x00007fffc7572000)
        libapt-private.so.0.0 => /lib/x86_64-linux-gnu/libapt-private.so.0.0 (0x00007f0b8a228000)
        libapt-pkg.so.6.0 => /lib/x86_64-linux-gnu/libapt-pkg.so.6.0 (0x00007f0b8a061000)
        libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f0b89e35000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f0b89e15000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f0b89bec000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f0b89bce000)
        libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x00007f0b89bbb000)
        liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f0b89b90000)
        liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1 (0x00007f0b89b70000)
        libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x00007f0b89aa1000)
        libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x00007f0b89800000)
        libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x00007f0b89739000)
        libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007f0b895fb000)
        libxxhash.so.0 => /lib/x86_64-linux-gnu/libxxhash.so.0 (0x00007f0b89a8a000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f0b89514000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f0b8a2b4000)
        libcgmanager.so.0 => not found
        libnih.so.1 => not found
        libnih-dbus.so.1 => not found
        libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007f0b89a3a000)
        librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f0b89a35000)
        libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x00007f0b89a2a000)
        libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007f0b894ee000)

Regards,
Swati

From: Swati Agarwal
Sent: Thursday, October 24, 2024 1:04 PM
To: David Grayson <dav...@gm...>; Tim Roberts <ti...@pr...>
Cc: lib...@li...
Subject: RE: [libusb] Need help in installing libusb library

Hi David,

I tried this as well but getting similar error

sudo apt-get install libusb-1.0-0-dev
apt-get: error while loading shared libraries: libcgmanager.so.0: cannot open shared object file: No such file or directory

The question still boil out to , if ubuntu version is 22.04, what are the ways to install libcgmanager.

Regards,
Swati

From: David Grayson <dav...@gm...<mailto:dav...@gm...>>
Sent: Thursday, October 24, 2024 12:43 PM
To: Tim Roberts <ti...@pr...<mailto:ti...@pr...>>
Cc: lib...@li...<mailto:lib...@li...>
Subject: Re: [libusb] Need help in installing libusb library


WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

Instead of downloading libusb's source just install it with apt-get:

sudo apt-get install libusb-1.0-0-dev

--David

On Thu, Oct 24, 2024, 12:09 AM Tim Roberts <ti...@pr...<mailto:ti...@pr...>> wrote:

On 10/23/24 10:11 PM, Swati Agarwal via libusb-devel wrote:

getting below error while installing it---

error while loading shared libraries: libcgmanager.so.0: cannot open shared object file: No such file or directory

sudo apt-get install libcgmanager
apt-get: error while loading shared libraries: libcgmanager.so.0: cannot open shared object file: No such file or directory

Did you search for this at all before asking?  You need to install the libcgmanager0 package:

https://askubuntu.com/questions/715714/error-loading-shared-libraries-libcgmanager-so-0-no-such-file-or-directory
--

Tim Roberts, ti...@pr...<mailto:ti...@pr...>
_______________________________________________
libusb-devel mailing list
lib...@li...<mailto:lib...@li...>
https://lists.sourceforge.net/lists/listinfo/libusb-devel

Hi David,

I tried this as well but getting similar error

sudo apt-get install libusb-1.0-0-dev
apt-get: error while loading shared libraries: libcgmanager.so.0: cannot open shared object file: No such file or directory

The question still boil out to , if ubuntu version is 22.04, what are the ways to install libcgmanager.

Regards,
Swati

From: David Grayson <dav...@gm...>
Sent: Thursday, October 24, 2024 12:43 PM
To: Tim Roberts <ti...@pr...>
Cc: lib...@li...
Subject: Re: [libusb] Need help in installing libusb library


WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

Instead of downloading libusb's source just install it with apt-get:

sudo apt-get install libusb-1.0-0-dev

--David

On Thu, Oct 24, 2024, 12:09 AM Tim Roberts <ti...@pr...<mailto:ti...@pr...>> wrote:

On 10/23/24 10:11 PM, Swati Agarwal via libusb-devel wrote:

getting below error while installing it---

error while loading shared libraries: libcgmanager.so.0: cannot open shared object file: No such file or directory

sudo apt-get install libcgmanager
apt-get: error while loading shared libraries: libcgmanager.so.0: cannot open shared object file: No such file or directory

Did you search for this at all before asking?  You need to install the libcgmanager0 package:

https://askubuntu.com/questions/715714/error-loading-shared-libraries-libcgmanager-so-0-no-such-file-or-directory
--

Tim Roberts, ti...@pr...<mailto:ti...@pr...>
_______________________________________________
libusb-devel mailing list
lib...@li...<mailto:lib...@li...>
https://lists.sourceforge.net/lists/listinfo/libusb-devel

Hi Tim,

As mentioned below, I tried to install it


  1.  sudo apt-get install libcgmanager -- apt-get: error while loading shared libraries: libcgmanager.so.0: cannot open shared object file: No such file or directory


  1.  ldconfig -p | grep -i 'cgmanager' – its not present



  1.  sudo find / -iname 'libcmanager.so’* --- getting permission denied error, even with su


I need to know how to install libcgmanager that will help ininstalling libusb library

Regards,
Swati

From: Tim Roberts <ti...@pr...>
Sent: Thursday, October 24, 2024 12:36 PM
To: lib...@li...
Subject: Re: [libusb] Need help in installing libusb library


WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

On 10/23/24 10:11 PM, Swati Agarwal via libusb-devel wrote:

getting below error while installing it---

error while loading shared libraries: libcgmanager.so.0: cannot open shared object file: No such file or directory

sudo apt-get install libcgmanager
apt-get: error while loading shared libraries: libcgmanager.so.0: cannot open shared object file: No such file or directory

Did you search for this at all before asking?  You need to install the libcgmanager0 package:

https://askubuntu.com/questions/715714/error-loading-shared-libraries-libcgmanager-so-0-no-such-file-or-directory
--

Tim Roberts, ti...@pr...<mailto:ti...@pr...>

Instead of downloading libusb's source just install it with apt-get:

sudo apt-get install libusb-1.0-0-dev

--David

On Thu, Oct 24, 2024, 12:09 AM Tim Roberts <ti...@pr...> wrote:

> On 10/23/24 10:11 PM, Swati Agarwal via libusb-devel wrote:
>
>
>
> getting below error while installing it---
>
>
>
> error while loading shared libraries: libcgmanager.so.0: cannot open
> shared object file: No such file or directory
>
>
>
> sudo apt-get install libcgmanager
>
> apt-get: error while loading shared libraries: libcgmanager.so.0: cannot
> open shared object file: No such file or directory
>
> Did you search for this at all before asking?  You need to install the
> libcgmanager0 package:
>
>
> https://askubuntu.com/questions/715714/error-loading-shared-libraries-libcgmanager-so-0-no-such-file-or-directory
> --
>
> Tim Roberts, ti...@pr...
>
> _______________________________________________
> libusb-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-devel
>

On 10/23/24 10:11 PM, Swati Agarwal via libusb-devel wrote:

> getting below error while installing it---
>
> error while loading shared libraries: libcgmanager.so.0: cannot open 
> shared object file: No such file or directory
>
> sudo apt-get install libcgmanager
>
> apt-get: error while loading shared libraries: libcgmanager.so.0: 
> cannot open shared object file: No such file or directory
>
Did you search for this at all before asking?  You need to install the 
libcgmanager0 package:

https://askubuntu.com/questions/715714/error-loading-shared-libraries-libcgmanager-so-0-no-such-file-or-directory

-- 

Tim Roberts,ti...@pr...

Hi,

I want to compile libuvc application----  https://libuvc.github.io/libuvc/

For that libusb<https://libusb.info/> 1.0+ is needed. I downloaded libusb-1.0.27.tar.bz2<https://github.com/libusb/libusb/releases/download/v1.0.27/libusb-1.0.27.tar.bz2> from the releases.

Following below steps for installing it.

tar jxvf libusb-1.0.27-rc2.tar.bz2
cd libusb-1.0.27-rc2
./configure --enable-tests-build --enable-examples-build
make check

getting below error while installing it---

error while loading shared libraries: libcgmanager.so.0: cannot open shared object file: No such file or directory

sudo apt-get install libcgmanager
apt-get: error while loading shared libraries: libcgmanager.so.0: cannot open shared object file: No such file or directory

Basically, I not able to install this library.

I am working on ubuntu version --- Ubuntu 22.04.4 LTS

Regards,
Swati

Our device is the only one demanding on the USB bus, so nothing else should be using more than 100 MB/s.
The issue occurred on various computers with different USB ports and controllers. However, I can check if there’s another USB controller on the computer that’s currently failing. If it works on that one, I could assume the issue is with the controller. Do you know if there’s a way, either through libusb or Windows, to access the available resources of the USB bus? This would allow me to see if there’s indeed an inability to lock our 300 MB/s.

________________________________


Well, mostly.  You're asking for 300 MB/s.  The total bus capacity after encoding is about 500 MB/s, but only 80% of that bandwidth is allowed to be allocated to reservations for interrupt and isochronous pipes.  Mice and keyboards also have reservations, although USB 2 traffic travels on different wires from USB 3 traffic.


It could just be a host controller failure.  Do these errors happen on the same types of computers?

--
Tim Roberts, ti...@pr...<mailto:ti...@pr...>
Providenza & Boekelheide, Inc.