Description of problem: After upgrading from Mga5: systemsettings -> personalization -> account details -> kwallet Displays a message: "The shared library is not found" This is reproduced in a new user. I will attach a screen shot of the full message. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
Created attachment 8820 [details] Screenshot Running systemsettings from CLI: [baz@acer ~]$ systemsettings5 org.kde.kcoreaddons: Error loading plugin "kcm_kwallet5" "The shared library was not found." Plugin search paths are ("/usr/lib64/qt5/plugins", "/usr/bin") The environment variable QT_PLUGIN_PATH might be not correctly set Error loading plugin: "The shared library was not found." However urpmf indicates that kwalletmanager provides it at the correct location: kwalletmanager:/usr/lib64/qt5/plugins/kcm_kwallet5.so rpm -q kwalletmanager kwalletmanager-16.12.0-1.mga6 But: [baz@acer ~]$ ll /usr/lib64/qt5/plugins/kcm_kwallet5.so ls: cannot access '/usr/lib64/qt5/plugins/kcm_kwallet5.so': No such file or directory [baz@acer ~]$ ll /usr/lib/qt5/plugins/kcm_kwallet5.so -rwxr-xr-x 1 root root 90136 Dec 26 09:28 /usr/lib/qt5/plugins/kcm_kwallet5.so* [baz@acer ~]$ So it seems that maybe in x86_64 the file is expected in /usr/lib64/qt5/plugins/ but is packaged in /usr/lib/...OR the package installed is the wrong arch. I will check.
The kwalletmanager package installed was i586. After rpm -e --nodeps and re-install of the x86_64 package all is now working normally. I do not know why the wrong arch was installed but if it happened during the upgrade then maybe there is a bug. Both arch repos were enabled as is default, and the upgrade was done using urpmi.
CC: (none) => marja11Assignee: bugsquad => kdeSummary: kwalletmanager says 'The shared library was not found' after upgrade from Mga5 => kwalletmanager says 'The shared library was not found' after upgrade from Mga5 (Upgraded to the wrong arch)
it was an update mga5 -> mga6 ? using isos or mga5 and then urpmi to update to mga6 ?
CC: (none) => mageia
Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Status: NEW => RESOLVEDResolution: (none) => OLD