Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 443205 - system-config-printer does not always start from non root login
Summary: system-config-printer does not always start from non root login
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-printer
Version: 9
Hardware: i686
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F9Target
TreeView+ depends on / blocked
 
Reported: 2008-04-19 08:56 UTC by n_k_samal
Modified: 2008-05-19 10:01 UTC (History)
2 users (show)

Fixed In Version: 0.7.82.3-2.fc9
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-05-19 10:01:17 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
screen of system-config-printer as user (deleted)
2008-05-09 11:59 UTC, antonio montagnani 		no flags Details
Screen as root (deleted)
2008-05-09 12:02 UTC, antonio montagnani 		no flags Details
View All

Description n_k_samal 2008-04-19 08:56:50 UTC 
Description of problem:
The root user generally works by logging as ordinary user. In cases of need the 
root user does a "su root" or enters the root password when asked by gui tool 
system-config-printer and carries out necessary configuration changes. Most of 
the time the system does not respond when the root user tries to use the 
graphical gui tool system-config-printer.

Version-Release number of selected component (if applicable):
Fedora-9-Beta-i386

How reproducible:
Log in as root and run the gui tool from system-config-printer from applications

Steps to Reproduce:
1.Log in as ordinary uses
2.Go to applications > printing.
3.Press enter
4.If no response for about 20 seconds log out and re-login again as non root 
user and repeat steps 2 and 3
5. If no response try step 4 once again.
6. After two /three/four trials the system asks to enter root password.
7. Now necessary changes can be made.
  
Actual results:
Most of the times no response.

Expected results:
The system should have asked the non root user to enter root password on the 
first time itself since he does not has the required privilages.

Additional info:
Full system profile is at http://www/smolt.org/show?/uuid=pub_85955a62-7804-
46c3-9010-eb5cf098549a.
No such problem was seen in F7. Every time the graphical GUI tools system-
config-printer was invoked by not root user, the system used to ask for root 
password. Once root password was entered necessary changes could be made.
Comment 1 Tim Waugh 2008-04-21 14:12:17 UTC 
I haven't been able to reproduce this.

Whta does 'rpm -q system-config-printer' say?
Comment 2 antonio montagnani 2008-05-09 08:03:27 UTC 
I have same problem:

If I start as root the graphical tool for printing everything seems o.k, but as
standard user I am not requested for password and I get a message stating:

CUPS server error
HTTP error: not connected
Comment 3 antonio montagnani 2008-05-09 08:04:50 UTC 
system-config-printer-0.7.82.2-4.fc9.i386

I forgot this piece of info
Comment 4 Tim Waugh 2008-05-09 08:20:22 UTC 
I'm a little confused: in the original report it seemed like the problem was
that system-config-printer wouldn't start when logged in as root, but in comment
#2 it looks like the problem only occurs when logged in as a *non-root* user.

When I try this here I don't see any problem at all.

Please attach your /etc/cups/cupsd.conf file.
Comment 5 antonio montagnani 2008-05-09 08:33:35 UTC 
Here it is......

MaxLogSize 0
# Show troubleshooting information in error_log.
LogLevel debug
SystemGroup sys root
# Only listen for connections from the local machine.
Listen localhost:631
Listen /var/run/cups/cups.sock
# Show shared printers on the local network.
Browsing On
BrowseOrder allow,deny
BrowseAllow all
DefaultAuthType Basic
<Location />
  # Restrict access to the server...
  Order allow,deny
</Location>
<Location /admin>
  Encryption Required
  # Restrict access to the admin pages...
  Order allow,deny
</Location>
<Location /admin/conf>
  AuthType Default
  Require user @SYSTEM
  # Restrict access to the configuration files...
  Order allow,deny
</Location>
<Policy default>
  <Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs
Set-Job-Attributes Create-Job-Subscription Renew-Subscription
Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job
Suspend-Current-Job Resume-Job CUPS-Move-Job>
    Require user @OWNER @SYSTEM
    Order deny,allow
  </Limit>
  <Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class
CUPS-Delete-Class CUPS-Set-Default>
    AuthType Default
    Require user @SYSTEM
    Order deny,allow
  </Limit>
  <Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer
Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs
Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer
Startup-Printer Promote-Job Schedule-Job-After CUPS-Accept-Jobs CUPS-Reject-Jobs>
    AuthType Default
    Require user @SYSTEM
    Order deny,allow
  </Limit>
  <Limit Cancel-Job CUPS-Authenticate-Job>
    Require user @OWNER @SYSTEM
    Order deny,allow
  </Limit>
  <Limit All>
    Order deny,allow
  </Limit>
</Policy>
Comment 6 Tim Waugh 2008-05-09 11:48:24 UTC 
Please try running 'system-config-printer' from the GNOME terminal window --
does that make any difference?  What output does it give?
Comment 7 antonio montagnani 2008-05-09 11:59:23 UTC 
Created attachment 304935 [details]
screen of system-config-printer as user

I will submit same screen as root
Comment 8 antonio montagnani 2008-05-09 12:02:22 UTC 
Created attachment 304936 [details]
Screen as root

I apologize for the Italian :-)

It was working fine!!! because sometimes I used to open this window to test if
Bugzilla Bug 439154: Cannot print on a Windows shared printer had been
solved!!!
Comment 9 Tim Waugh 2008-05-09 12:13:14 UTC 
When logged in as the non-root user, what output do these commands give?:

1. ls ~/.cups
2. lpstat -s
3. system-config-printer
Comment 10 antonio montagnani 2008-05-09 12:35:45 UTC 
 ls ~/.cups
ls: impossibile accedere a /home/antonio/.cups: No such file or directory
[antonio@acer ~]$ lpstat -s
destinazione predefinita di sistema: LaserJet_1200
dispositivo per Cups-PDF: cups-pdf:/
dispositivo per LaserJet_1200: smb://WORKGROUP/CELERON/HPLaserJ
dispositivo per LaserJet_12002: smb://WORKGROUP/CELERON/HPLaserJ
[antonio@acer ~]$ system-config-printer

usual error
Comment 11 Tim Waugh 2008-05-09 12:40:35 UTC 
Please try this:

PYCUPS_DEBUG=1 system-config-printer

What output do you get?
Comment 12 antonio montagnani 2008-05-09 12:51:45 UTC 
 PYCUPS_DEBUG=1 system-config-printer
-> Connection_init()
httpConnectEncrypt(...)
<- Connection_init() = 0
-> Connection_getPrinters()
cupsDoRequest("/")
Attribute: printer-is-shared
Added printer-is-shared to dict
Attribute: printer-state
Added printer-state to dict
Attribute: printer-state-message
Added printer-state-message to dict
Attribute: printer-state-reasons
-> build_list_from_attribute_strings()
none
<- build_list_from_attribute_strings()
Added printer-state-reasons to dict
Attribute: printer-type
Added printer-type to dict
Attribute: printer-uri-supported
Added printer-uri-supported to dict
Attribute: printer-name
Attribute: printer-location
Added printer-location to dict
Attribute: printer-info
Added printer-info to dict
Attribute: device-uri
Added device-uri to dict
Attribute: printer-make-and-model
Added printer-make-and-model to dict
Attribute: printer-is-shared
Added printer-is-shared to dict
Attribute: printer-state
Added printer-state to dict
Attribute: printer-state-message
Added printer-state-message to dict
Attribute: printer-state-reasons
-> build_list_from_attribute_strings()
none
<- build_list_from_attribute_strings()
Added printer-state-reasons to dict
Attribute: printer-type
Added printer-type to dict
Attribute: printer-uri-supported
Added printer-uri-supported to dict
Attribute: printer-name
Attribute: printer-location
Added printer-location to dict
Attribute: printer-info
Added printer-info to dict
Attribute: device-uri
Added device-uri to dict
Attribute: printer-make-and-model
Added printer-make-and-model to dict
Attribute: printer-is-shared
Added printer-is-shared to dict
Attribute: printer-state
Added printer-state to dict
Attribute: printer-state-message
Added printer-state-message to dict
Attribute: printer-state-reasons
-> build_list_from_attribute_strings()
none
<- build_list_from_attribute_strings()
Added printer-state-reasons to dict
Attribute: printer-type
Added printer-type to dict
Attribute: printer-uri-supported
Added printer-uri-supported to dict
Attribute: printer-name
Attribute: printer-location
Added printer-location to dict
Attribute: printer-info
Added printer-info to dict
Attribute: device-uri
Added device-uri to dict
Attribute: printer-make-and-model
Added printer-make-and-model to dict
<- Connection_getPrinters() = dict
-> Connection_getClasses()
cupsDoRequest("/")
<- Connection_getClasses() = dict
-> Connection_getFile(/admin/conf/printers.conf, /tmp/tmplW1lLgprinter.conf)
cupsGetFile()
set_http_error: 401
<- Connection_getFile() (error)
-> Connection_init()
httpConnectEncrypt(...)
<- Connection_init() = 0
-> Connection_getFile(/admin/conf/printers.conf, /tmp/tmplW1lLgprinter.conf)
cupsGetFile()
set_http_error: -1
<- Connection_getFile() (error)
httpClose()
Comment 13 Tim Waugh 2008-05-09 13:35:12 UTC 
The exact circumstance this occurs is when a local queue exists that uses an
'smb://...' URI.
Comment 14 Will Woods 2008-05-09 21:29:12 UTC 
Note added to http://fedoraproject.org/wiki/Bugs/F9Common. Moving to F9Target.

Tim, is there a fix for this in the current s-c-printer build for F9 in koji?
Comment 15 Tim Waugh 2008-05-12 08:58:10 UTC 
Yes, system-config-printer-0.7.82.3-1.fc9 has the fix.
Comment 16 Bug Zapper 2008-05-14 09:42:30 UTC 
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Note You need to log in before you can comment on or make changes to this bug.