| Summary: | drakconf (kde) launcher created in mga3 fails in mga4 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Barry Jackson <zen25000> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | davidwhodgins, mageia |
| Version: | Cauldron | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | drakconf-12.42-1.mga4 | CVE: | |
| Status comment: | |||
| Attachments: | patch to add symlink | ||
|
Description
Barry Jackson
2013-09-22 17:16:57 CEST
Created attachment 4370 [details]
patch to add symlink
isn't this something like this bug https://bugs.mageia.org/show_bug.cgi?id=11304 ? Keywords:
(none) =>
NEEDINFO (In reply to Manuel Hiebel from comment #2) > isn't this something like this bug > https://bugs.mageia.org/show_bug.cgi?id=11304 ? I really don't understand that bug after reading 3 times :\ (yes it's hard to read franglish) have you a message if you run drakconf from the terminal ? (In reply to Manuel Hiebel from comment #4) > (yes it's hard to read franglish) > > have you a message if you run drakconf from the terminal ? No it's fine. In mga4: which drakconf /usr/bin/drakconf In mga3: which drakconf /sbin/drakconf A KDE launcher created in Mga3 does not know about this, but creating a symlink during drakconf package installation in mga4 is a workaround which is much better than a broken icon on the panel. On my Mageia 3 x86_64 system $ which drakconf /usr/bin/drakconf So the question is what happened to /usr/bin/drakconf on that system? CC:
(none) =>
davidwhodgins (In reply to Dave Hodgins from comment #6) > On my Mageia 3 x86_64 system > > $ which drakconf > /usr/bin/drakconf > > So the question is what happened to /usr/bin/drakconf on that system? Nothing - it is there, but the Mga3 version of drakconf has this in the spec which is missing in Mga4: ln -sf %_bindir/drakconf %buildroot/%_sbindir/drakconf For some reason when KDE creates a launcher in Mga3 it uses the symlink rather than the real path, so when that launcher is used in Mga4 it fails. I now realize that my workaround is almost identical to replacing the missing line back in the spec. Ah... Author: colin Date: Sun Sep 1 15:12:46 2013 UTC (3 weeks, 5 days ago) Changed paths: 1 Log Message: Do not include unneeded symlink in /usr/sbin/ CC:
(none) =>
mageia On my Mageia 4 x86-64 system, installed from the pre-release alpha3 kde live dvd iso, $ which drakconf /usr/bin/drakconf And mcc starts ok from clicking on the icon in the kde panel. In comment 5, it indicates it's Mageia 3 where the problem exists. I'm not able to recreate the problem either in Mageia 3 or 4 kde. (In reply to Dave Hodgins from comment #8) > On my Mageia 4 x86-64 system, installed from the pre-release alpha3 kde live > dvd > iso, > $ which drakconf > /usr/bin/drakconf > > And mcc starts ok from clicking on the icon in the kde panel. > > In comment 5, it indicates it's Mageia 3 where the problem exists. > > I'm not able to recreate the problem either in Mageia 3 or 4 kde. Are you using the same home for both mga3 and mga4 after creating the panel icon for drakconf in mga3? I have re-checked by removing any drakconf icons and symlinks in both installs, re-installed (--replacepkgs --replacefiles) drakconf in both systems and then added the panel icon in mga3 only. When running mga4 the launcher fails "KDEInit could not launch '/usr/sbin/drakconf' which is reasonable since the symlink is not there. I agree that this may be an issue with the icon creation in mga3. Yeah, for upgrades I'll make a note of keeping compatibility symlinks. Fixed in drakconf-12.43.2 Status:
NEW =>
RESOLVED |