| Summary: | Root passwd visable when openning mcc & (polkit update) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | martyn vidler <martynvidler> |
| Component: | RPM Packages | Assignee: | Colin Guthrie <mageia> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | martynvidler, thierry.vignaud |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
martyn vidler
2013-10-10 23:19:02 CEST
martyn vidler
2013-10-10 23:19:30 CEST
CC:
(none) =>
martynvidler
David Walser
2013-10-10 23:21:47 CEST
Component:
Security =>
RPM Packages Also as a user with sudo mcc & wont start, But sudo mcc starts ok As root mcc & works ok polkit adaptation is Colin's work CC:
(none) =>
thierry.vignaud Regarding backgrounding processes that need user input, but this pretty much expected. You are putting the application in the background and returning control to the shell, so whatever you type is going into the shell itself just as with any other command you type... simply don't use & here. Ultimately this issue can probably be avoided if E17 had an appropriate polkit authorisation agent running. Perhaps it has one but it's not configured to run at login or installed (i.e. not (yet) one of the required packages). When a proper authorisation agent is running the password will be asked for via a GUI popup, not via the CLI and thus you can put the app into the background quite happily. In theory, the only time you should be asked for a pass via the console is when you are launching in text mode, and in that case you really cannot use & to put it into the background anyway :) Summary:
Root passwd visable when openning mcc & =>
Root passwd visable when openning mcc & (polkit update) This isn't a bug as it was ultimately user error (backgrounding something on a terminal which wanted to control terminal). Status:
NEW =>
RESOLVED |