Bug 12865 - MCC does not launch from KDE Task Manager
Summary: MCC does not launch from KDE Task Manager
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-23 22:29 CET by Gerald
Modified: 2015-05-21 18:51 CEST (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:

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

Description Gerald 2014-02-23 22:29:53 CET 
Description of problem:

In my KDE desktop, I've replaced the (default) Icon-Only Task Manager with the Task Manager v2.0 (author Eike Hein). Next I added a launcher for MCC in the Task Manager. When I click on the MCC launcher, nothing seems to happen. MCC does not launch from the Task Manager.

I can launch every other application from this Task Manager, only MCC fails to launch. 

Version-Release number of selected component (if applicable):

Mageia 4, default KDE installation.

How reproducible:

Every time I click the MCC launcher in the Task Manager.

Steps to Reproduce:

1. Unlock widgets 
2. Open Panel toolbox 
3. Remove default Icon-Only Task Manager
4. Add widget Task Manager v2.0  to panel
5. Lock widgets
6. Start MCC from Application Launcher Menu
7. Enable "Show a launcher when not running" 
8. Close MCC -> launcher icon is added in Task Manager
9. Click MCC launcher -> MCC does not launch



Reproducible: 

Steps to Reproduce:
Thierry Vignaud 2014-02-24 01:31:24 CET

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

Comment 1 Colin Guthrie 2014-02-24 10:06:25 CET 
This is because this launcher does something called "double forking". This means that security systems such as polkit cannot properly audit the process and refuse to offer root-privilege elevation.

There are two solutions to this.

1. The application is patched/updated to not double fork (can you tell me it's SRPM name).
2. We change the drakx code to not use exec and thus always keep a parent process alive.

The 2nd option is probably most universal as we had to patch a whole bunch of different desktops and launchers in the run up to MGA4 release.

It should be fairly easy to update drakx on this front.
Comment 2 Anderson Carvalho 2014-03-03 16:14:59 CET 
The same problem happens with IconTasks in my MGA4.

CC: (none) => frateraec

Comment 3 Gerald 2015-05-21 18:46:45 CEST 
Since quite a long time it works fine now, I can launch MCC from the Task Manager.
Does anybody object to closing this bugreport as fixed?
Comment 4 Remco Rijnders 2015-05-21 18:51:33 CEST 
Thanks for your patience Gerald and thank you for reporting that it's been fixed. I assume one of the drakx updates that have been released will have fixed this. Should anyone still be plagued by this problem, please reopen this report.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.