Description of problem: double entry of Mageia Control Center in Mageia 5 Alpha 1 MateDesktop. Please have a look on the screenshot. How reproducible: Install Mageia 5 Alpha 1 with Mate-Desktop Reproducible: Steps to Reproduce:
Created attachment 5275 [details] Screenshot Mate Menu - Double Entry
I see it too in Mate, on a system where I installed 5a1 with all DEs Assigned to the package maintainer. (Please set the status to 'assigned' if you are working on it)
Keywords: (none) => TriagedCC: (none) => marja11Assignee: bugsquad => tarakbumbaSource RPM: (none) => mate-menus-1.8.0-1.mga5
That comes from mate-control-center package. I' ve added a mate-mcc.desktop to solve a problem for both mintmenu and gnome-main-menu. You see, mintmenu and gnome-main-menu have Mageia Control Center entry. But it never worked due to famous "double forking" issue. mageia-drakconf.desktop file and relevant launcher script /usr/bin/drakconf which comes with drakconf package raised "double forking" issue. So, /usr/bin/drakconf script is unlike other mageia tools scripts like /usr/bin/rpmdrake launcher script uses perl and does not work with mintmenu and gnome-main-menu. So, i added another script and .desktop file to workaround this problem temporarily. I should ask for this to tv but forgot. Will see what we can do this about. I'm asking this at dev-ml right now. Stay tune...
Status: NEW => ASSIGNEDHardware: x86_64 => AllSource RPM: mate-menus-1.8.0-1.mga5 => mate-control-center-1.8.1-2.mga5
Thanks to tv, double forking issue is fixed in drakconf package. So, i have removed all mate-drakconf instances from both mintmenu, gnome-main-menu and mate-control-center. Updates should be arrived to mirrors soon. Please test and if you see this issue is fixed then please inform me, or better close this bug report. Thanks.
yes, it's fixed, thx Atilla and Thierry @ Björn I'm closing this report, because I can't imagine that the fix doesn't work for you. However, feel free to reopen if needed.
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED
Hi @all, I can confirm that the problem is fixed. Thank you.