Bug 2086539 - avrdude crashes due to missing libhidapi-libusb.so.0 after upgrade from f35
Summary: avrdude crashes due to missing libhidapi-libusb.so.0 after upgrade from f35
Keywords:
Status: CLOSED COMPLETED
Alias: None
Product: Fedora
Classification: Fedora
Component: avrdude
Version: 36
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Hans Ulrich Niedermann
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-16 11:51 UTC by nilskemail
Modified: 2023-05-26 17:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-25 19:31:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description nilskemail 2022-05-16 11:51:10 UTC
Description of problem:

Running avrdude directly aborts due to missing the shared library "libhidapi-libusb.so.0"


Version-Release number of selected component (if applicable):

6.4-3.fc36


How reproducible:

Always


Steps to Reproduce:

1. Run avrdude


Actual results:

avrdude: error while loading shared libraries: libhidapi-libusb.so.0: cannot open shared object file: No such file or directory


Expected results:

A help page should be shown


Additional info:

Manually installing the hidapi package fixes the error however this is not pulled in for me automatically. Reinstalling the package also does not result in this dependency being installed.
Installing avrdude in a podman container however correctly pulls in the hidapi requirement. I recently upgraded my machine from Fedora 35 though that *should* not cause such behaviour. As upgrading from any 2 previous releases should be save I filed a bug.

Comment 1 Hans Ulrich Niedermann 2022-05-17 00:14:15 UTC
So... the F36 avrdude package depends on libhidapi-libusb.so.0:

    $ rpm -q avrdude
    avrdude-6.4-3.fc36.x86_64
    $ rpm -q --requires avrdude
    […]
    libhidapi-libusb.so.0()(64bit)
    […]
    $ ldd /usr/bin/avrdude  | grep hidapi
	libhidapi-libusb.so.0 => /lib64/libhidapi-libusb.so.0 (0x00007f50f914b000)
    $ _

How did you upgrade from F35 to F36?

It appears that this upgrade method has ignored that avrdude-6.4-3.fc36 depends on libhidapi-libusb.so.0.

Comment 2 nilskemail 2022-05-17 20:42:13 UTC
I upgraded using the dnf-plugin-system-upgrade as explained in the fedora docs: https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/

The above rpm commands also correctly show the dependency however somehow this dependency is ignored by dnf.
Even after reinstalling either of avrdude and hidapi they are still unconnected.
Removing e.g. libftdi correctly prompts that avrdude would be removed too but hidapi does not do that.

Comment 3 Hans Ulrich Niedermann 2022-05-18 06:01:20 UTC
Weird.

I cannot reproduce this on my F36 fresh install:

    $ rpm -q avrdude hidapi
    avrdude-6.4-3.fc36.x86_64
    hidapi-0.11.2-2.fc36.x86_64
    $ sudo dnf remove hidapi
    Dependencies resolved.
    ==============================================================================================
     Package                   Architecture   Version                      Repository        Size
    ==============================================================================================
    Removing:
     hidapi                    x86_64         0.11.2-2.fc36                @fedora          115 k
    Removing dependent packages:
     avrdude                   x86_64         6.4-3.fc36                   @updates         2.4 M
     hidapi-devel              x86_64         0.11.2-2.fc36                @fedora           19 k
    […]

I will try and find a F35-to-F36 with "dnf system-upgrade" to reproduce.

Comment 4 nilskemail 2022-06-15 19:57:55 UTC
A similar problem occurred to me for qBittorent which seems to be missing 'libQt6Widgets.so.6' after the upgrade.

Comment 5 Ben Cotton 2023-04-25 18:24:16 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 6 Ludek Smid 2023-05-25 19:31:40 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 7 nilskemail 2023-05-26 17:51:54 UTC
I took a bit of time to see if I could reproduce it again and finally found the fault. For both dependencies ('libhidapi-libusb.so.0()(64bit)' and 'libQt6Widgets.so.6()(64bit)') I had another 3rd party package providing them. I guess the maintainer of that package fixed the building process in the meanwhile as after upgrading that package everything else now sees to be detected properly🎉. I changed the status from EOL to COMPLETED as well.


Note You need to log in before you can comment on or make changes to this bug.