Bug 12014 - drakconf upgrading from previous Mageia versions breaks drakconf launcher icon
Summary: drakconf upgrading from previous Mageia versions breaks drakconf launcher icon
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Damien Lallement
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 11979
  Show dependency tree / graph
 
Reported: 2013-12-16 15:04 CET by David Walser
Modified: 2013-12-17 21:04 CET (History)
2 users (show)

See Also:
Source RPM: drakconf-12.45-1.mga4.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description David Walser 2013-12-16 15:04:35 CET 
The default desktop configuration (at least in KDE) in Mageia includes a drakconf icon in the panel.  After upgrading to Cauldron, this launcher will no longer work.  It is called "mageia-drakconf.desktop" and is missing the icon, and clicking it says that file:///usr/share/applications/mageia-drakconf.desktop does not exist.

Reproducible: 

Steps to Reproduce:
David Walser 2013-12-16 15:04:56 CET

Blocks: (none) => 11979

David Walser 2013-12-16 15:11:32 CET

CC: sysadmin-bugs => (none)
Component: Release (media or process) => RPM Packages

Comment 1 Thierry Vignaud 2013-12-16 16:39:14 CET 
Reassigning to the one that did the change:
http://svnweb.mageia.org/packages/cauldron/drakconf/current/SPECS/drakconf.spec?r1=452132&r2=452133&

CC: (none) => mageia
Assignee: thierry.vignaud => mageia

Comment 2 Damien Lallement 2013-12-17 01:59:06 CET 
Fixed in drakconf-12.45-2.mga4.

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

Comment 3 Jani Välimaa 2013-12-17 19:51:15 CET 
This latest change b0rked Xfce menu (as it was modified after previous change). Maybe a better option would have been fixing it in KDE config?

CC: (none) => jani.valimaa

Comment 4 David Walser 2013-12-17 21:04:31 CET 
It's not a matter of "KDE config," it's user configs already existing from previous releases, and unless there's a way to fix those, it's better to leave this how it was for mga3 and earlier.
Note You need to log in before you can comment on or make changes to this bug.