Description of problem: after update of cauldron x86 and reboot- due to updating other versions on unit, unable to launch MCC from icon, or from any Mageia welcome link. these are packages that were installed: see attached file Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
Created attachment 7291 [details] update list
Summary: Cauldron Mga6: MCC will not launch from icon, launches from konsole as root => Cauldron Mga6: regression MCC will not launch from icon, launches from konsole as root,
Created attachment 7292 [details] attempting to check system updates from Mageia Welcome link
latest updates appear to have resolved issue
Status: NEW => RESOLVEDResolution: (none) => FIXED
and back again after updates today
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
running from terminal [launching from Mageia Welcome]: >>> "run drakrpm-update" ['drakrpm-update'] Error executing command as another user: Not authorized This incident has been reported. direct from terminal: $ drakrpm-update Error executing command as another user: Not authorized This incident has been reported. as root, launches correctly
Summary: Cauldron Mga6: regression MCC will not launch from icon, launches from konsole as root, => [Mga6-dev1]: regression MCC will not launch from icon, launches from konsole as root,Whiteboard: (none) => Mga6-dev1
I've seen in cauldron, too, that some tools that could be started as user in the past, after which the root password was asked, did now not start as user at all. I cannot check now whether this is still wrong, last time I hit it was ± a week ago. Assigning to drakxtools maintainer.
CC: (none) => marja11Assignee: bugsquad => thierry.vignaudSummary: [Mga6-dev1]: regression MCC will not launch from icon, launches from konsole as root, => [Mga6-dev1]: regression MCC will not launch as user (after which root password is asked)
I fail to reproduce this. Anyway, auth is handled by polkit
CC: (none) => mageia
It works fine now, here, too. Could the "Error executing command as another user: Not authorized" error" also have been caused by a crashing authentication pop-up? Wondering because just closing the pop-up results in that error, too. @ Ben Does it work fine for you again, too, now?
Keywords: (none) => NEEDINFO
(In reply to Marja van Waes from comment #8) > @ Ben > > Does it work fine for you again, too, now? yes, currently
Status: REOPENED => RESOLVEDResolution: (none) => FIXED