You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
(2) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(4) |
Feb
(19) |
Mar
(5) |
Apr
(5) |
May
|
Jun
(3) |
Jul
(21) |
Aug
(27) |
Sep
|
Oct
(5) |
Nov
(4) |
Dec
(3) |
2002 |
Jan
(27) |
Feb
(33) |
Mar
(25) |
Apr
(40) |
May
(58) |
Jun
(25) |
Jul
(39) |
Aug
(23) |
Sep
(15) |
Oct
(26) |
Nov
(75) |
Dec
(35) |
2003 |
Jan
(29) |
Feb
(13) |
Mar
(24) |
Apr
(58) |
May
(27) |
Jun
(21) |
Jul
(11) |
Aug
(24) |
Sep
(6) |
Oct
(6) |
Nov
(30) |
Dec
(71) |
2004 |
Jan
(125) |
Feb
(47) |
Mar
(31) |
Apr
(29) |
May
(53) |
Jun
(29) |
Jul
(43) |
Aug
(19) |
Sep
(69) |
Oct
(38) |
Nov
(38) |
Dec
(37) |
2005 |
Jan
(59) |
Feb
(92) |
Mar
(32) |
Apr
(54) |
May
(29) |
Jun
(27) |
Jul
(34) |
Aug
(46) |
Sep
(47) |
Oct
(43) |
Nov
(63) |
Dec
(112) |
2006 |
Jan
(99) |
Feb
(117) |
Mar
(68) |
Apr
(59) |
May
(66) |
Jun
(32) |
Jul
(65) |
Aug
(85) |
Sep
(44) |
Oct
(113) |
Nov
(334) |
Dec
(42) |
2007 |
Jan
(64) |
Feb
(147) |
Mar
(245) |
Apr
(427) |
May
(229) |
Jun
(66) |
Jul
(56) |
Aug
(58) |
Sep
(82) |
Oct
(109) |
Nov
(196) |
Dec
(78) |
2008 |
Jan
(143) |
Feb
(79) |
Mar
(85) |
Apr
(126) |
May
(405) |
Jun
(259) |
Jul
(218) |
Aug
(118) |
Sep
(116) |
Oct
(135) |
Nov
(105) |
Dec
(79) |
2009 |
Jan
(196) |
Feb
(146) |
Mar
(60) |
Apr
(180) |
May
(229) |
Jun
(206) |
Jul
(126) |
Aug
(155) |
Sep
(276) |
Oct
(160) |
Nov
(120) |
Dec
(185) |
2010 |
Jan
(685) |
Feb
(581) |
Mar
(460) |
Apr
(650) |
May
(495) |
Jun
(567) |
Jul
(375) |
Aug
(518) |
Sep
(531) |
Oct
(487) |
Nov
(269) |
Dec
(461) |
2011 |
Jan
(524) |
Feb
(457) |
Mar
(385) |
Apr
(316) |
May
(229) |
Jun
(480) |
Jul
(302) |
Aug
(243) |
Sep
(411) |
Oct
(158) |
Nov
(171) |
Dec
(269) |
2012 |
Jan
(117) |
Feb
(177) |
Mar
(225) |
Apr
(251) |
May
(150) |
Jun
(228) |
Jul
(127) |
Aug
(74) |
Sep
(128) |
Oct
(106) |
Nov
(47) |
Dec
(73) |
2013 |
Jan
(83) |
Feb
(224) |
Mar
(69) |
Apr
(182) |
May
(118) |
Jun
(52) |
Jul
(180) |
Aug
(43) |
Sep
(43) |
Oct
(54) |
Nov
(18) |
Dec
(43) |
2014 |
Jan
(40) |
Feb
(78) |
Mar
(138) |
Apr
(85) |
May
(65) |
Jun
(81) |
Jul
(56) |
Aug
(116) |
Sep
(123) |
Oct
(60) |
Nov
(74) |
Dec
(99) |
2015 |
Jan
(120) |
Feb
(126) |
Mar
(176) |
Apr
(133) |
May
(124) |
Jun
(60) |
Jul
(54) |
Aug
(92) |
Sep
(134) |
Oct
(75) |
Nov
(48) |
Dec
(78) |
2016 |
Jan
(94) |
Feb
(89) |
Mar
(109) |
Apr
(33) |
May
(25) |
Jun
(64) |
Jul
(54) |
Aug
(26) |
Sep
(59) |
Oct
(30) |
Nov
(77) |
Dec
(16) |
2017 |
Jan
(37) |
Feb
(22) |
Mar
(25) |
Apr
(7) |
May
(36) |
Jun
(10) |
Jul
(64) |
Aug
(39) |
Sep
(22) |
Oct
(26) |
Nov
(27) |
Dec
(14) |
2018 |
Jan
(10) |
Feb
(31) |
Mar
(15) |
Apr
(35) |
May
(20) |
Jun
(13) |
Jul
(10) |
Aug
(6) |
Sep
(22) |
Oct
(13) |
Nov
(52) |
Dec
(23) |
2019 |
Jan
(25) |
Feb
(17) |
Mar
(30) |
Apr
(34) |
May
(12) |
Jun
(10) |
Jul
(26) |
Aug
(13) |
Sep
(24) |
Oct
(12) |
Nov
(9) |
Dec
(5) |
2020 |
Jan
(24) |
Feb
(12) |
Mar
(40) |
Apr
(20) |
May
(12) |
Jun
(10) |
Jul
(41) |
Aug
(20) |
Sep
(24) |
Oct
(4) |
Nov
(6) |
Dec
(38) |
2021 |
Jan
(34) |
Feb
(33) |
Mar
(10) |
Apr
(12) |
May
(10) |
Jun
(49) |
Jul
(49) |
Aug
(17) |
Sep
(43) |
Oct
(11) |
Nov
(2) |
Dec
(13) |
2022 |
Jan
(14) |
Feb
(14) |
Mar
(1) |
Apr
(6) |
May
(6) |
Jun
(10) |
Jul
|
Aug
(3) |
Sep
(6) |
Oct
(19) |
Nov
(9) |
Dec
(5) |
2023 |
Jan
(4) |
Feb
(9) |
Mar
(30) |
Apr
(17) |
May
(5) |
Jun
|
Jul
(39) |
Aug
(7) |
Sep
(3) |
Oct
(6) |
Nov
|
Dec
(3) |
2024 |
Jan
(2) |
Feb
|
Mar
(17) |
Apr
(16) |
May
(14) |
Jun
(13) |
Jul
(7) |
Aug
(3) |
Sep
(8) |
Oct
(19) |
Nov
(1) |
Dec
|
2025 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Tormod V. <lis...@gm...> - 2025-03-19 09:14:14
|
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 |
From: Tormod V. <lis...@gm...> - 2025-03-06 22:40:55
|
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 |
From: Romain G. <rom...@bo...> - 2024-11-20 08:47:41
|
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 |
From: Swati A. <swa...@qt...> - 2024-10-25 06:41:28
|
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 |
From: Swati A. <swa...@qt...> - 2024-10-25 06:02:18
|
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...> |
From: Tim R. <ti...@pr...> - 2024-10-24 18:36:47
|
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... |
From: David G. <dav...@gm...> - 2024-10-24 16:17:07
|
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 > > |
From: Swati A. <swa...@qt...> - 2024-10-24 08:59:14
|
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 |
From: Swati A. <swa...@qt...> - 2024-10-24 08:10:50
|
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 |
From: Swati A. <swa...@qt...> - 2024-10-24 07:20:57
|
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...> |
From: David G. <dav...@gm...> - 2024-10-24 07:13:49
|
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 > |
From: Tim R. <ti...@pr...> - 2024-10-24 07:06:28
|
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... |
From: Swati A. <swa...@qt...> - 2024-10-24 05:43:23
|
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 |
From: Fourcade, P. <Pie...@sm...> - 2024-10-18 15:27:04
|
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. |
From: Tim R. <ti...@pr...> - 2024-10-16 17:37:14
|
Fourcade, Pierre wrote: > Hello, > We are indeed using an isochronous endpoint in our alternate setting. > We are working on a USB 5 Gb/s connection, and the endpoint is > configured as follows: > > * Maximum packet size: 1024 > * Burst size: 12 > * Number of iso-packets: 3 > * Service interval: 1 uFrame > > Theoretical throughput is then around 2.4 Gb/s, so we should be within > the allowed bandwidth. 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... Providenza & Boekelheide, Inc. |
From: Fourcade, P. <Pie...@sm...> - 2024-10-16 09:37:53
|
Hello, We are indeed using an isochronous endpoint in our alternate setting. We are working on a USB 5 Gb/s connection, and the endpoint is configured as follows: * Maximum packet size: 1024 * Burst size: 12 * Number of iso-packets: 3 * Service interval: 1 uFrame Theoretical throughput is then around 2.4 Gb/s, so we should be within the allowed bandwidth. Additionally, no other USB devices (besides a mouse and a keyboard) are connected. The issue is that if it were asking for more than the possible bandwidth, this should happen systematically and be reproducible. Here, it is basically that one day we will just plug in a new device, and the issue will be present. Even previous devices that were correctly accessed are now presenting the issue. ________________________________ On 10/15/24 1:45 AM, Fourcade, Pierre wrote: Regarding the issue: “Randomly”, with our custom USB device, libusb reports a systematic failure when attempting to set the device to a specific alternate setting. When setting the log levels to debug, the following issue is reported: “libusb: error [winusbx_set_interface_altsetting] SetCurrentAlternateSetting failed: Insufficient system resources exist to complete the requested service.” I have looked into existing topics regarding this issue but found none answered, at least related to USB. Usually, the issue appears to be more observable on computers that are not often turned off, but we have had the issue at least once on every computer using Windows. What are the endpoints are in your alternate settings? Usually, this error means that your alternate setting contains an isochronous or interrupt endpoint, and the reservation you asked for exceeded the reservation limit for the bus. For example, if you try to start two video cameras on a USB 2 bus that's already running USB audio, that will exceed the limit. -- Tim Roberts, ti...@pr...<mailto:ti...@pr...> Providenza & Boekelheide, Inc. |
From: Tim R. <ti...@pr...> - 2024-10-15 15:00:55
|
On 10/15/24 1:45 AM, Fourcade, Pierre wrote: > Regarding the issue: “Randomly”, with our custom USB device, libusb > reports a systematic failure when attempting to set the device to a > specific alternate setting. When setting the log levels to debug, the > following issue is reported: “libusb: error > [winusbx_set_interface_altsetting] SetCurrentAlternateSetting failed: > Insufficient system resources exist to complete the requested > service.” I have looked into existing topics regarding this issue but > found none answered, at least related to USB. Usually, the issue > appears to be more observable on computers that are not often turned > off, but we have had the issue at least once on every computer using > Windows. What are the endpoints are in your alternate settings? Usually, this error means that your alternate setting contains an isochronous or interrupt endpoint, and the reservation you asked for exceeded the reservation limit for the bus. For example, if you try to start two video cameras on a USB 2 bus that's already running USB audio, that will exceed the limit. -- Tim Roberts,ti...@pr... Providenza & Boekelheide, Inc. |
From: Fourcade, P. <Pie...@sm...> - 2024-10-15 14:22:05
|
Dear libusb community, I am reaching out for help regarding an unexpected error we have encountered using libusb on Windows. First of all, I believe this issue is probably more related to Windows and WinUSB itself, and I also intend to seek help from their side. However, I am trying my luck here to see if this is a known issue and if there might be some workaround. Regarding the issue: “Randomly”, with our custom USB device, libusb reports a systematic failure when attempting to set the device to a specific alternate setting. When setting the log levels to debug, the following issue is reported: “libusb: error [winusbx_set_interface_altsetting] SetCurrentAlternateSetting failed: Insufficient system resources exist to complete the requested service.” I have looked into existing topics regarding this issue but found none answered, at least related to USB. Usually, the issue appears to be more observable on computers that are not often turned off, but we have had the issue at least once on every computer using Windows. What has been tested/verified: * It is apparently not linked to our USB firmware since the same device plugged into two different computers (one with the issue, the other without) has different behavior. * Despite the libusb error, our USB device correctly detects the setting of the alternate setting and behaves correctly. * We have tried with libusb version 1.0.24 and the latest version 1.0.27 without any change in the issue. * The only solution found to fix the issue is to manually uninstall all the devices in Windows Device Manager and restart the computer afterward. After this, the problem is no longer present. * The issue is not reproducible (making it more fun). * USB enumeration and USB properties on Windows report no issue when the problem occurs. If this rings any bells or if you think we could try anything to fix this issue, please do not hesitate! Thank you for your time and consideration. Best regards. |
From: Daniel G. <dg...@de...> - 2024-10-09 19:51:53
|
I'm using the synchronous interface, and can do everything I want to do in 2.0 mode (with a 2.0 cable plugged into the device) When the device is plugged directly into a 3.0 port, I can get the list, find the device, release the default driver, claim the driver, open the port, but then when I call the libusb_bulk_transfer(), it times out. From: Tim Roberts <ti...@pr...> Sent: Tuesday, October 8, 2024 3:11 PM To: lib...@li... Subject: Re: [libusb] LIBUSB-1.0.27.11882 MAC OS works on a 2.0 port not a 3.0 port CAUTION: **** This email was sent from an external sender **** Please exercise caution and do not open attachments or click links from unknown senders or unexpected email. Daniel Gill via libusb-devel wrote: I have developed a LIBUSB program to send locate/claim/open a USB reader/card and send a few commands to the drive and retrieve the data. This works fine when the drive is plugged in with a 2.0 cable adapter, but if straight in to 3.1, then it times out. Times out where, exactly? On which call? Are you able to open the device and claim the interface? Have you disabled the default operating system driver? -- Tim Roberts, ti...@pr...<mailto:ti...@pr...> Providenza & Boekelheide, Inc. |
From: Tim R. <ti...@pr...> - 2024-10-08 22:10:42
|
Daniel Gill via libusb-devel wrote: > > I have developed a LIBUSB program to send locate/claim/open a USB > reader/card and send a few commands to the drive and retrieve the data. > > This works fine when the drive is plugged in with a 2.0 cable adapter, > but if straight in to 3.1, then it times out. > Times out where, exactly? On which call? Are you able to open the device and claim the interface? Have you disabled the default operating system driver? -- Tim Roberts,ti...@pr... Providenza & Boekelheide, Inc. |
From: Ludovic R. <lud...@gm...> - 2024-10-08 20:16:15
|
Le mar. 8 oct. 2024 à 21:41, Daniel Gill via libusb-devel < lib...@li...> a écrit : > > > Hello, > > Hello Daniel, > I have developed a LIBUSB program to send locate/claim/open a USB > reader/card and send a few commands to the drive and retrieve the data. > What kind of card? Something like a SD card or microSD card? Bye -- Dr. Ludovic Rousseau |
From: Daniel G. <dg...@de...> - 2024-10-08 19:38:32
|
Hello, I have developed a LIBUSB program to send locate/claim/open a USB reader/card and send a few commands to the drive and retrieve the data. This works fine when the drive is plugged in with a 2.0 cable adapter, but if straight in to 3.1, then it times out. Same code works under Linux for both 2.0 and 3.0 ports. Is there any updates to the MACOS version that might help fix my problem? Thanks, dan [cid:image001.png@01DB1979.22961540] Dan Gill dg...@de...<mailto:dg...@de...> Director of Engineering 858.391.1234x115 Delkin Devices Inc. 13350 Kirkham Way Poway, CA 92064-7117 www.delkin.com<http://www.delkin.com/> |
From: Tim R. <ti...@pr...> - 2024-09-24 00:36:54
|
Aaron Gomez | Rother Industries & Technology wrote: > > I know my device under test only has one class, but by "multi-class" I > mean that it is a device that can recognize different device classes > (standard classes registred by USB). > I still don't know what you mean by that. It's darned near impossible to write a driver that handles multiple device classes, because the protocols are all entirely different. (A libusb app is essentially a user-mode driver.) -- Tim Roberts, ti...@pr... Providenza & Boekelheide, Inc. |
From: Ларионов Д. <scu...@ya...> - 2024-09-20 19:59:59
|
> If you can use c++, there is a great library for discovering and > communicating with serial devices called QSerialPort That's... a stretch, to put it mildly. QSerialPort is a class which is a part of Qt, which in turn is an utterly gargantuan framework. Personally I find it (Qt) great and almost exclusively use it all the time instead of STL, but even I wouldn't blanket-endorse it for all situations. > On 2024-09-20 13:55, Tim Roberts wrote: > >>> How to know the ttyUSBx/ttyACMx/... name with libusb? I could see that when I >>> connect the device in the path dev/serial/by-id/ a file >>> is created where its name is the components of string >>> descriptor and it is linked with the ttyUSBx/ttyACMx/... >>> (path: /dev/tty...) file which I need to open this file >>> descriptor and start the communication. >> >> Well, hang on. If you have a ttyXXX device, then that means >> you already have a driver that is converting the USB device into >> a serial device. You cannot use libusb to talk to a /dev/ttyXXX >> device. /dev/ttyXXX speaks serial protocol, not USB protocol. > > If you can use c++, there is a great library for discovering and > communicating with serial devices called QSerialPort > > Jon |
From: drwho <dr...@in...> - 2024-09-20 18:33:23
|
On 2024-09-20 13:55, Tim Roberts wrote: >> >> How to know the ttyUSBx/ttyACMx/... name with libusb? I could see >> that when I connect the device in the path dev/serial/by-id/ a file >> is created where its name is the components of string descriptor and >> it is linked with the ttyUSBx/ttyACMx/... (path: /dev/tty...) file >> which I need to open this file descriptor and start the communication. >> > Well, hang on. If you have a ttyXXX device, then that means you > already have a driver that is converting the USB device into a serial > device. You cannot use libusb to talk to a /dev/ttyXXX device. > /dev/ttyXXX speaks serial protocol, not USB protocol. > If you can use c++, there is a great library for discovering and communicating with serial devices called QSerialPort <https://doc.qt.io/qt-6/qserialport.html> Jon |