| Summary: | kde systemsettings software manager does not start because libapper.so is not found | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Angelo Naselli <anaselli> |
| Component: | RPM Packages | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | anaselli, davidwhodgins, sysadmin-bugs |
| Version: | 5 | Keywords: | validated_update |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | MGA5-64-OK advisory | ||
| Source RPM: | apper-0.9.1-1.mga5.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Angelo Naselli
2015-06-10 16:04:01 CEST
Released on svn a fixing, let's wait for mga5 official release to provide an official update. Status:
NEW =>
ASSIGNED
Samuel Verschelde
2015-06-10 17:37:37 CEST
Whiteboard:
(none) =>
MGA5TOO submitted apper-0.9.1-1.1.mga5 to update testing. I will write an advisory later. apper-0.9.1-2.mga6 is on cauldron as well. I have uploaded a patched package for Mageia 5. You can test this bug by following the steps to reproduce it as explained in comment #0. Note for testers, the Software manager behaviour is not completely working due to some pacakgekit issues, i'm still working on with the help of tv, but that should not be related to apper. Software manager, at least, can be started and used once every packagekit restarting. Suggested advisory: ======================== Updated apper package fix the libapper.so library position into file system in order to be found by kde system setting. Without this fixing KDE software manager cannot be executed. ======================== Updated packages in core/updates_testing: apper-0.9.1-1.1.mga5 Source RPMs: apper-0.9.1-1.1.mga5.src.rpm
Angelo Naselli
2015-06-21 11:52:19 CEST
CC:
(none) =>
anaselli Fixed and tested on x86_64 arch
Rémi Verschelde
2015-06-21 12:02:57 CEST
Version:
Cauldron =>
5 Advisory committed to svn. Someone from the sysadmin team please push 16104.adv to updates. Keywords:
(none) =>
validated_update An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGAA-2015-0058.html Status:
ASSIGNED =>
RESOLVED |