Bug 28959 - plasma-discover-update crash at startup complaining about missing libDiscoverCommon.so
Summary: plasma-discover-update crash at startup complaining about missing libDiscover...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-22 18:35 CEST by Cyril Levet
Modified: 2024-08-22 23:01 CEST (History)
1 user (show)

See Also:
Source RPM: discover-5.20.4-3.1.mga8.src.rpm
CVE:
Status comment:


Attachments

Description Cyril Levet 2021-05-22 18:35:25 CEST
Description of problem: Trying to launch plasma-discover-update gives :
plasma-discover-update: error while loading shared libraries: libDiscoverCommon.so: cannot open shared object file: No such file or directory

ldd /usr/bin/plasma-discover-update
        linux-vdso.so.1 (0x00007ffe29575000)
        libDiscoverCommon.so => not found
        libKF5I18n.so.5 => /lib64/libKF5I18n.so.5 (0x00007f13d5e3c000)
        libQt5Widgets.so.5 => /lib64/libQt5Widgets.so.5 (0x00007f13d57bd000)
        libQt5Gui.so.5 => /lib64/libQt5Gui.so.5 (0x00007f13d5109000)
        libKF5CoreAddons.so.5 => /lib64/libKF5CoreAddons.so.5 (0x00007f13d5073000)
        libQt5Core.so.5 => /lib64/libQt5Core.so.5 (0x00007f13d4b06000)
        libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f13d4934000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f13d477a000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f13d4637000)
        libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f13d461d000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f13d45fd000)
        libGL.so.1 => /lib64/libGL.so.1 (0x00007f13d4577000)
        libpng16.so.16 => /lib64/libpng16.so.16 (0x00007f13d4519000)
        libz.so.1 => /lib64/libz.so.1 (0x00007f13d44fc000)
        libharfbuzz.so.0 => /lib64/libharfbuzz.so.0 (0x00007f13d4415000)
        libmd4c.so.0 => /lib64/libmd4c.so.0 (0x00007f13d4403000)
        libfam.so.0 => /lib64/libfam.so.0 (0x00007f13d43f9000)
        libsystemd.so.0 => /lib64/libsystemd.so.0 (0x00007f13d4348000)
        libdouble-conversion.so.3 => /lib64/libdouble-conversion.so.3 (0x00007f13d4336000)
        libicui18n.so.68 => /lib64/libicui18n.so.68 (0x00007f13d4030000)
        libicuuc.so.68 => /lib64/libicuuc.so.68 (0x00007f13d3e4a000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f13d3e45000)
        libpcre2-16.so.0 => /lib64/libpcre2-16.so.0 (0x00007f13d3dba000)
        libzstd.so.1 => /lib64/libzstd.so.1 (0x00007f13d3cdf000)
        libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007f13d3bb1000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f13d5ead000)
        libGLdispatch.so.0 => /lib64/libGLdispatch.so.0 (0x00007f13d3af9000)
        libGLX.so.0 => /lib64/libGLX.so.0 (0x00007f13d3ac5000)
        libfreetype.so.6 => /lib64/libfreetype.so.6 (0x00007f13d3a14000)
        libgraphite2.so.3 => /lib64/libgraphite2.so.3 (0x00007f13d39f0000)
        librt.so.1 => /lib64/librt.so.1 (0x00007f13d39e3000)
        liblzma.so.5 => /lib64/liblzma.so.5 (0x00007f13d39b2000)
        liblz4.so.1 => /lib64/liblz4.so.1 (0x00007f13d398f000)
        libgcrypt.so.20 => /lib64/libgcrypt.so.20 (0x00007f13d386c000)
        libicudata.so.68 => /lib64/libicudata.so.68 (0x00007f13d3869000)
        libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f13d37f5000)
        libX11.so.6 => /lib64/libX11.so.6 (0x00007f13d36b6000)
        libbz2.so.1 => /lib64/libbz2.so.1 (0x00007f13d36a3000)
        libgpg-error.so.0 => /lib64/libgpg-error.so.0 (0x00007f13d367d000)
        libxcb.so.1 => /lib64/libxcb.so.1 (0x00007f13d3655000)
        libXau.so.6 => /lib64/libXau.so.6 (0x00007f13d364e000)
        libXdmcp.so.6 => /lib64/libXdmcp.so.6 (0x00007f13d3646000)
        libbsd.so.0 => /lib64/libbsd.so.0 (0x00007f13d362c000)

However, this library exists : 
locate libDiscoverCommon.so
/usr/lib64/plasma-discover/libDiscoverCommon.so

And comes from discover package :
 urpmf -f libDiscoverCommon.so
discover-5.20.4-3.mga8.x86_64:/usr/lib64/plasma-discover/libDiscoverCommon.so
discover-5.20.4-3.1.mga8.x86_64:/usr/lib64/plasma-discover/libDiscoverCommon.so

It works fine on Cauldron. May be related to the impossibility to update Mageia 8 through discover. 

In Cauldron, plasma-discover-update does not crash at startup and plasma-discover can find Mageia updates.

Version-Release number of selected component (if applicable): discover-5.20.4-3.1.mga8


How reproducible: Always


Steps to Reproduce:
1. Install discover
2. Launch plasma-discover-update
Comment 1 Aurelien Oudelet 2021-05-22 19:18:29 CEST
Confirmed.

$ plasma-discover-update 
plasma-discover-update: error while loading shared libraries: libDiscoverCommon.so: cannot open shared object file: No such file or directory

Meanwhile, the Update applet seems to run OK in systray...
But, yes, there is no any Updates that come from DNF PackageKit Backend.
There are some lines in system journal but not relevant to this.
Moreover, if I look for a package, I only get a flatpak one... no any RPM from Mageia repo.

DNF repositories seems correctly enabled...

CC: (none) => ouaurelien
Assignee: bugsquad => kde

Cyril Levet 2022-10-02 12:49:32 CEST

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=30925

Comment 2 Marja Van Waes 2024-08-22 23:01:27 CEST
We stopped supporting Mageia 8 almost 8 months ago 
https://blog.mageia.org/en/2023/12/30/mageia-8-end-of-life/

That means we also stopped fixing Mageia 8 bugs and that this bug report needs to be closed, regardless of whether it was fixed for Mageia 8 or not.

If this particular bug did not get fixed for Mageia 8, then we do regret that.

If this issue is still present in Mageia 9 or cauldron, then please reopen this report, write a comment and adjust the "Version:" field.

If you are not yet a member of one or our teams, then please consider becoming one. https://wiki.mageia.org/en/Contributing
Mageia is a community project, meaning that we, the users, make Mageia together.

The more active contributors we have, the more bug reports will get fixed.
Besides, being active in a team can be very rewarding. It was and is certainly rewarding to me :-D

Status: NEW => RESOLVED
Resolution: (none) => OLD


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