[Pkg-electronics-devel] Bug#880092: Bug#880092: Error: libusb_open() failed with LIBUSB_ERROR_ACCESS

[Ivan Sergio Borgonovo]

Hi,

Everything was working fine before update, I was able to upload firmware 
to an stm32 and debug with an olimex arm-usb-ocd-h.

The user was already in plugdev.

I sincerely can't remember for sure if I had 60-openocd.rules in my 
/etc/udev/rules.d directory before but I presume I didn't have it and 
everything was working.
But I've had openocd working on my system for so long I don't remember 
if I had to do some manual setup, so I can't assure I manually copied 
any rule 2 years ago.

After upgrade I surely didn't have an 60-openocd.rules there.
After downgrade I still didn't have it there.

So last upgrade deleted it or something else started to require it.

/lib/udev/rules.d/60-openocd.rules

just contains the string

contrib/60-openocd.rules

In the openocd binary package I can't find any udev rule other than the 
"empty" one above.
In the openocd_0.10.0.orig.tar.bz2 there is a contrib/60-openocd.rules 
and that's the one I copied and placed in /etc/udev/rules.d

I've upgraded openocd at least a couple of times in the past, and I 
can't see many updates in Debian changelog. According to the aptitude 
logs I still have on my system the oldest openocd I had installed was

0.9.0-1+b2

but it is not listed in the debian changelog.

Thanks

On 10/29/2017 01:42 PM, Jonathan McDowell wrote:
> On Sun, Oct 29, 2017 at 01:12:27PM +0100, Ivan Sergio Borgonovo wrote:
>> Package: openocd
>> Version: 0.10.0-2
>>
>> After a cycle of upgrades listed below I got
>> Error: libusb_open() failed with LIBUSB_ERROR_ACCESS
>> using openocd
> 
> Was it working before the upgrade (presumably on version 0.10.0-1+b1
> from your log below)? Is the user in question in the plugdev group?
> 
>> I downgraded to the previous version without improvement.
>>
>> Googled and find a reference to udev rules.
>> Nor the old neither the new openocd package copy any rule in
>> /etc/udev/rules.d
>> Binary package contains /lib/udev/rules.d/60-openocd.rules
>>
>> cat /lib/udev/rules.d/60-openocd.rules
>> contrib/60-openocd.rules
>>
>> Downloaded openocd debian source package and copied
>>
>> 60-openocd.rules
>>
>> in /etc/udev/rules.d
> 
> Is there any difference between the file you put in /etc/udev/rules.d/
> and the shipped file in /lib/udev/rules.d/ ? The file from contrib/ in
> the source package is exactly the same as what's installed in
> /lib/udev/rules.d/ for me, and when I plug in a JTAG device it's
> correctly assigned to the plugdev group. /lib/udev/rules.d/ is the
> appropriate directory for a system shipped set of udev rules.
> 
>> Things started to work again.
>> I'm not sure to which of the below upgraded packages I can attribute the
>> problem.
>>
>> thanks
>>
>> [REMOVE, NOT USED] libbind9-140:amd64 1:9.10.3.dfsg.P4-12.6
>> [REMOVE, NOT USED] libdns-export162:amd64 1:9.10.3.dfsg.P4-12.6
>> [REMOVE, NOT USED] libdns162:amd64 1:9.10.3.dfsg.P4-12.6
>> [REMOVE, NOT USED] libisc-export160:amd64 1:9.10.3.dfsg.P4-12.6
>> [REMOVE, NOT USED] libisc160:amd64 1:9.10.3.dfsg.P4-12.6
>> [REMOVE, NOT USED] libisccfg140:amd64 1:9.10.3.dfsg.P4-12.6
>> [INSTALL, DEPENDENCIES] libbind9-141:amd64 1:9.10.6+dfsg-4
>> [INSTALL, DEPENDENCIES] libdns-export190:amd64 1:9.10.6+dfsg-4
>> [INSTALL, DEPENDENCIES] libdns190:amd64 1:9.10.6+dfsg-4
>> [INSTALL, DEPENDENCIES] libisc-export189:amd64 1:9.10.6+dfsg-4
>> [INSTALL, DEPENDENCIES] libisc189:amd64 1:9.10.6+dfsg-4
>> [INSTALL, DEPENDENCIES] libisccfg144:amd64 1:9.10.6+dfsg-4
>> [INSTALL, DEPENDENCIES] libjaylink0:amd64 0.1.0-1
>> [UPGRADE] appstream:amd64 0.11.6-2 -> 0.11.7-1
>> [UPGRADE] autotools-dev:amd64 20161112.1 -> 20161112.1+nmu1
>> [UPGRADE] bind9-host:amd64 1:9.10.3.dfsg.P4-12.6 -> 1:9.10.6+dfsg-4
>> [UPGRADE] dnsutils:amd64 1:9.10.3.dfsg.P4-12.6 -> 1:9.10.6+dfsg-4
>> [UPGRADE] fonts-arphic-uming:amd64 0.2.20080216.2-9 -> 0.2.20080216.2-10
>> [UPGRADE] freerdp2-wayland:amd64 2.0.0~git20170725.1.1648deb+dfsg1-4 ->
>> 2.0.0~git20170725.1.1648deb+dfsg1-5
>> [UPGRADE] gir1.2-gtk-3.0:amd64 3.22.24-2 -> 3.22.24-3
>> [UPGRADE] gtk-update-icon-cache:amd64 3.22.24-2 -> 3.22.24-3
>> [UPGRADE] init:amd64 1.50 -> 1.51
>> [UPGRADE] init-system-helpers:amd64 1.50 -> 1.51
>> [UPGRADE] isc-dhcp-client:amd64 4.3.5-3 -> 4.3.5-3+b1
>> [UPGRADE] isc-dhcp-common:amd64 4.3.5-3 -> 4.3.5-3+b1
>> [UPGRADE] libappstream4:amd64 0.11.6-2 -> 0.11.7-1
>> [UPGRADE] libappstreamqt2:amd64 0.11.6-2 -> 0.11.7-1
>> [UPGRADE] libexttextcat-2.0-0:amd64 3.4.4-2+b1 -> 3.4.5-1
>> [UPGRADE] libexttextcat-data:amd64 3.4.4-2 -> 3.4.5-1
>> [UPGRADE] libfreerdp-client2-2:amd64 2.0.0~git20170725.1.1648deb+dfsg1-4 ->
>> 2.0.0~git20170725.1.1648deb+dfsg1-5
>> [UPGRADE] libfreerdp2-2:amd64 2.0.0~git20170725.1.1648deb+dfsg1-4 ->
>> 2.0.0~git20170725.1.1648deb+dfsg1-5
>> [UPGRADE] libfreetype6:amd64 2.8-0.2 -> 2.8.1-0.1
>> [UPGRADE] libgd3:amd64 2.2.5-3 -> 2.2.5-4
>> [UPGRADE] libgtk-3-0:amd64 3.22.24-2 -> 3.22.24-3
>> [UPGRADE] libgtk-3-bin:amd64 3.22.24-2 -> 3.22.24-3
>> [UPGRADE] libgtk-3-common:amd64 3.22.24-2 -> 3.22.24-3
>> [UPGRADE] libisccc140:amd64 1:9.10.3.dfsg.P4-12.6 -> 1:9.10.6+dfsg-4
>> [UPGRADE] libjs-sphinxdoc:amd64 1.6.4-2 -> 1.6.5-1
>> [UPGRADE] liblwres141:amd64 1:9.10.3.dfsg.P4-12.6 -> 1:9.10.6+dfsg-4
>> [UPGRADE] libnet-http-perl:amd64 6.16-1 -> 6.17-1
>> [UPGRADE] libnm0:amd64 1.8.4-3 -> 1.8.4-4
>> [UPGRADE] libuwac0-0:amd64 2.0.0~git20170725.1.1648deb+dfsg1-4 ->
>> 2.0.0~git20170725.1.1648deb+dfsg1-5
>> [UPGRADE] libvisio-0.1-1:amd64 0.1.5-4+b1 -> 0.1.6-1
>> [UPGRADE] libwinpr2-2:amd64 2.0.0~git20170725.1.1648deb+dfsg1-4 ->
>> 2.0.0~git20170725.1.1648deb+dfsg1-5
>> [UPGRADE] network-manager:amd64 1.8.4-3 -> 1.8.4-4
>> [UPGRADE] openocd:amd64 0.10.0-1+b1 -> 0.10.0-2
>> [UPGRADE] qt-at-spi:amd64 0.4.0-5 -> 0.4.0-6
>> [UPGRADE] wxmaxima:amd64 17.10.0-3 -> 17.10.1-1
> 
> J.
> 

-- 
Ivan Sergio Borgonovo
http://www.webthatworks.it http://www.borgonovo.net