Bug 505767
| Summary: | root unable to configure printer | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Daniel Qarras <dqarras> | ||||||
| Component: | cups | Assignee: | Tim Waugh <twaugh> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 11 | CC: | twaugh | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2009-06-17 12:36:18 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 347747 [details]
cups error log
You don't need to become root to use system-config-printer. Just use it from your user account. PolicyKit denies access to the root user as a matter of course (see bug #447266). *** This bug has been marked as a duplicate of bug 447266 *** |
Created attachment 347746 [details] cups access log Description of problem: I logged in as an ordinary user, used "su -" and launched system-config-printer from the command line as root. Seemed to work ok except a) can't access Server->Settings and b) when adding a new printer applying the changes fails due to privilege error. Version-Release number of selected component (if applicable): cups-1.4-0.b2.18.fc11.i586 How reproducible: Always. Steps to Reproduce: 1. Log in as an ordinary user 2. su - 3. system-config-printer 4. Server->Settings 5. Try to add a new printer Actual results: Permission denied for the super user(!). Expected results: root is able to do his will. Additional info: I'm attaching access_log and error_log after such an attempt.