| Summary: | mgaapplet crashed (Typelib file for namespace 'StatusNotifier', version '1.0' not found) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Gilles Langlais <gillou33> |
| Component: | RPM Packages | Assignee: | Mageia tools maintainers <mageiatools> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | magicandsave, rene, thierry.vignaud |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | mgaonline-3.20-1.mga6 | CVE: | |
| Status comment: | |||
|
Description
Gilles Langlais
2017-03-14 12:31:58 CET
This might be because you updated your Cauldron at a time where somehow your Core 32-bit Release repo was more up-to-date than Core Release (64-bit), so you likely ended up with the 32-bit version of libstatusnotifier-gir1.0. If so, you can fix the issue with: # urpmi lib64statusnotifier-gir1.0 # urpme libstatusnotifier-gir1.0 libstatusnotifier1 Assignee:
bugsquad =>
mageiatools Merci, le problème est résolu... resolved , best regards... Status:
NEW =>
RESOLVED @ Thierry: Those bugs are happening because mgaonline and drakx-net are noarch and have a dependency on `typelib(StatusNotifier)`, which is provided by both lib64statusnotifier-gir1.0 (64-bit) and libstatusnotifier-gir1.0 (32-bit). It seems that in some situations, urpmi will use the 32-bit variant to resolve the dependency, which is obviously bogus. That might be worth discussing in a specific issue/on the dev ML, but I'm not sure how we can fix this issue. A simple workaround would be to make mgaonline and drakx-net archful, but can't we do better? CC:
(none) =>
thierry.vignaud (In reply to Rémi Verschelde from comment #1) > This might be because you updated your Cauldron at a time where somehow your > Core 32-bit Release repo was more up-to-date than Core Release (64-bit), so > you likely ended up with the 32-bit version of libstatusnotifier-gir1.0. > > If so, you can fix the issue with: > > # urpmi lib64statusnotifier-gir1.0 > # urpme libstatusnotifier-gir1.0 libstatusnotifier1 Worked for my Cauldron-VM. Boot without earlier reported error-messages. 4.9.14-desktop-1.mga6 CC:
(none) =>
isis2000 I doubt that noarch has anything to do with that. A lot of noarch packages are pulling typelib() like requires and everything wors fine. I suspect the affected users might have used dnf instead of urpmi... (In reply to Thierry Vignaud from comment #6) > I doubt that noarch has anything to do with that. > A lot of noarch packages are pulling typelib() like requires and everything > wors fine. > I suspect the affected users might have used dnf instead of urpmi... PLUS reply to isadora ... @ Thierry: NOPE - just regular update via update applet ... @isadora: Manual Work around works OK - temporary solution confirmed. (In reply to Thierry Vignaud from comment #6) > I doubt that noarch has anything to do with that. > A lot of noarch packages are pulling typelib() like requires and everything > wors fine. > I suspect the affected users might have used dnf instead of urpmi... I doubt that's the issue. I see two potential culprits: - If Core Release is lagging behind and Core 32-bit Release is more up-to-date, the newer package would be pulled from the 32-bit repo by urpmi/MageiaUpdate. - If both repos are in sync and urpmi still picks the package from the 32-bit repo, then we have some big issue... |