Description of problem: drakconf fails to start from the menu. Running drakconf from the command line produces this error message: Error executing command as another user: Not authorized This incident has been reported. Version-Release number of selected component (if applicable): How reproducible: Every time I attempt to run drakconf Steps to Reproduce: 1. /bin/drakconf 2. See the error message above. Expected result: A window pops up in which I can type a password. After giving my password, the drakconf window pops up. /bin/drakconf is a perl script which runs /usr/bin/pkexec on either /usr/libexec/drakconf or /usr/libexec/drakxconf I can run pkexec on various commands in /bin (eg bash, ls etc.) but not on commands in /usr/libexec (eg mgaapplet-config) Googling the error message produced various results: including a suggestion to add the user to the "wheel" group, which I have tried. Reproducible: Steps to Reproduce:
Assignee: bugsquad => mageia
I have two very similar systems, one has a graphics card and is working fine, the other uses motherboard graphics and has a tuner card and shows the above problem. It was working fine until the upgrade to Mageia 4. Both systems were installed with Mageia 3 and upgraded to Mageia 4. If someone could suggest where to look for differences between the two machines, then that would help to track down the problem!
is polkit (and an agent) running ?
The following are running: /usr/lib/polkit-1/polkitd --no-debug /usr/lib64/kde4/libexec/polkit-kde-authentication-agent-1 This is the same as the working system.
Do you still experience this? We are more who see it now, on Mageia 5, see Bug 16396 - MCC won't start after logging out/in to KDE session
CC: (none) => fri
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
(In reply to Morgan Leijström from comment #4) > We are more who see it now, on Mageia 5, see Bug 16396 > - MCC won't start after logging out/in to KDE session Please do not intermingle such issues, Martin could be affected by a totally different issue. @Martin: Please retry with Mageia 5, and provide the output of the following commands: cat /run/systemd/users/$(id -u) ps -ef|grep -v grep|grep polkit systemctl status polkit.service -a And please describe shortly how you start your X session, and if you login only once, or maybe ifyou login/logout from your X session with your user during one boot.
Status: NEW => ASSIGNEDCC: (none) => doktor5000, mageiaAssignee: mageia => doktor5000
Closing as OLD, in case it still happens with Mageia 5 please reopen and update the bug as mentioned in comment 5 and 6.
Status: ASSIGNED => RESOLVEDResolution: (none) => OLD