similar to: Fwd: [fprint] libusb-1.0 enters beta

On Mon, Jun 20, 2016 at 05:02:32PM -0400, m.roth at 5-cent.us wrote: > Fred Smith wrote: > > On Mon, Jun 20, 2016 at 04:13:35PM -0400, m.roth at 5-cent.us wrote: > >> Fred Smith wrote: > >> > On Mon, Jun 20, 2016 at 02:59:29PM -0400, Jon LaBadie wrote: > >> >> On Mon, Jun 20, 2016 at 08:58:54AM -0400, Fred Smith wrote: > >> >> > On

Documentation/ext3.txt suggests that the "user_xattr" and "acl" mount options are on by default. This doesn't seem to be the case, as the kernel deduces the default mount options from the filesystem superblock, and mke2fs does not appear to write any default mount options there. This error was spotted by Jacques de Mer. Signed-off-by: Daniel Drake <dsd at

On a 7.2 desktop system I see irregular attempts to start the fingerprint authentication daemon "fprintd". One of the messages is "D-Bus service launched with name: net.reactivated.Fprint" This fails as there is no fingerprint device. fprintd.service is disabled. Without a fingerprint device, is this software needed. Yum removal (aborted) shows no packages dependent on

Hello world, As posted at https://github.com/networkupstools/nut/issues/300#issuecomment-969385505 and https://github.com/networkupstools/nut/issues/300#issuecomment-970243340 in greater detail, during the past weekend I have updated the "libusb-1.0" and "libusb-1.0+0.1" branches in NUT repository, so their proposed changes are integrated over the past few years of

Hello world, As posted at https://github.com/networkupstools/nut/issues/300#issuecomment-969385505 and https://github.com/networkupstools/nut/issues/300#issuecomment-970243340 in greater detail, during the past weekend I have updated the "libusb-1.0" and "libusb-1.0+0.1" branches in NUT repository, so their proposed changes are integrated over the past few years of

On Sun, Dec 14, 2014 at 07:22:01PM -0500, Mark LaPierre wrote: > On 12/14/14 07:29, ken wrote: > > uname -r; rpm -q libusb > > CentOS 6.6 says: > [mlapier at mushroom ~]$ uname -r; rpm -q libusb > 2.6.32-504.1.3.el6.i686 > libusb-0.1.12-23.el6.i686 CentOS 5 has: libusb-0.1.12 CentOS 6 has: libusb-0.1.12 libusb1-1.0.9 CentOS 7 has: libusb-0.1.4 libusbx-1.0.15

Trying to install Canon printer driver package (rpm), I get a dependency error: libusb-1.0.so.0 is needed.... The version currently installed on my 5.9 system is libusb-0.1.12-6.el5 and, AFAIK (per yum), no upgrade to that is available. So question: Do higher centos versions have libusb-1.0.so ? (We could perform a quick inventory with: uname -r; rpm -q libusb Thanks.

CentOS Errata and Bugfix Advisory 2011:1498 Upstream details at : http://rhn.redhat.com/errata/RHBA-2011-1498.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 7d2661ef76a592b0742f34abc20ba700 libusb-0.1.12-6.el5.i386.rpm 565c12782b350526c032d83e362f06b5 libusb-0.1.12-6.el5.x86_64.rpm 6c35a97adc73c5b361b3f56a2c582a45

On Nov 26, 2017, at 3:15 PM, Sam Varshavchik wrote: > > Charles Lepple writes: > >> still looking for volunteers to test the libusb-1.0 code on FreeBSD and other systems. > > On Fedora 27, running commit 2999c95f0: Thanks for checking this. I should have been more clear in the second email in the thread, but commit 2999c95f0 is on the original "libusb-1.0"

Hi, I've been asked to find out some answers from libusb maintainer, so I'm forwarding them: - Why nut uses legacy libusb-0.1 api and not libusb 1.0 ? - Is there any plan to update it to libusb 1.0? Thanks, Michal

I just upgraded the FreeBSD buildbot machine from 6.4 to 8.0, and I ran across some interesting differences. The libusb API that we use (0.1) is available in /usr/include/usb.h and /usr/lib/libusb.* as before, but it seems to be the compatibility layer from libusb 1.0. However, it doesn't include the libusb-config binary. This is from the 'ports' Makefile for NUT: ########## - -

NUT developers, just thought I'd share some notes and ideas on using valgrind against the NUT USB drivers on Linux. Stepping back a bit, I wanted to make sure that the tripplite_usb driver* wasn't using any uninitialized memory, or leaking memory over time. valgrind (specifically, the memcheck tool) runs the code in a special dynamic translator that checks every memory access to see if

I doesn't fix any problems but I think it is nicer code. :-) I don't think we want to call usb_detach_kernel_driver_np unless we claimed the device. $ diff -uw libusb.c.bak libusb.c.new --- libusb.c.bak 2010-05-11 09:35:39.000000000 -0400 +++ libusb.c.new 2010-05-11 09:32:44.000000000 -0400 @@ -206,18 +206,21 @@ upsdebugx(2, "failed to

Hello! I have an UPS made by Powercom company; the model of the UPS is RPT-800A. This UPS has a USB port, which can be used to connect the UPS to a PC and read various data from the UPS (percentage of load, input voltage, output voltage, etc.). So I download the NUT binary package for Windows, install and set it up using manual. Everything works fine for a few hours (I can get the data I

On Thu, Aug 30, 2018 at 03:41:43PM +0800, Daniel Drake wrote: > On Tue, Aug 28, 2018 at 5:57 PM, Peter Wu <peter at lekensteyn.nl> wrote: > > Just to be sure, after "sleep", do both devices report "suspended" in > > /sys/bus/pci/devices/0000:00:1c.0/power/runtime_status > > /sys/bus/pci/devices/0000:01:00.0/power/runtime_status > > > > and

> >> # nut-scanner >> Cannot load USB library (/usr/lib64/libusb-1.0.so.0.1.0) : /usr/lib64/libusb-1.0.so.0.1.0: undefined symbol: usb_get_string_simple. USB search disabled. > > Although I suspect that the USB portion of nut-scanner could probably be replaced with a small shell script that parses the output of lsusb, this shouldn't be too hard to fix. Logged, in case it

Charles Lepple writes: > still looking for volunteers to test the libusb-1.0 code on FreeBSD and > other systems. On Fedora 27, running commit 2999c95f0: # nut-scanner Cannot load USB library (/usr/lib64/libusb-1.0.so.0.1.0) : /usr/lib64/libusb-1.0.so.0.1.0: undefined symbol: usb_get_string_simple. USB search disabled. There's also a bug in the configure script on 64 bit

CentOS Errata and Bugfix Advisory 2011:1498 Upstream details at : http://rhn.redhat.com/errata/RHBA-2011-1498.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 7d2661ef76a592b0742f34abc20ba700 libusb-0.1.12-6.el5.i386.rpm 6c35a97adc73c5b361b3f56a2c582a45 libusb-devel-0.1.12-6.el5.i386.rpm Source:

On 12/14/14 07:29, ken wrote: > uname -r; rpm -q libusb CentOS 6.6 says: [mlapier at mushroom ~]$ uname -r; rpm -q libusb 2.6.32-504.1.3.el6.i686 libusb-0.1.12-23.el6.i686 -- _ ?v? /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ****

Przemysław Kopa reports that since commit b516ea586d71 ("PCI: Enable NVIDIA HDA controllers"), the discrete GPU Nvidia GeForce GT 540M on his 2011 Samsung laptop refuses to runtime suspend, resulting in a power regression and excessive heat. Rivera Valdez witnesses the same issue with a GeForce GT 525M (GF108M) of the same era, as does another Arch Linux user named "R0AR" with