cups webpage waits for ever on modify printer make, if authtype is enabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
I use cups on a print server so I configure cups remote through the web front-end. If I set security as low as possible (BrowseAllow All, Allow From All for all other sections and AuthType and AuthClass disabled) I have no problem. I can do (printer is already installed): manage printers --> modify printer --> continue --> continue --> continue --> On the Make/Manufacturer page I want to change the driver so I select the make, continue --> and I get on the page Model/Driver and so on. But when I enhance security with AuthType and AuthClass in cupsd.conf on the sections /admin and /admin/conf, the cups website works as follows: manage printers --> modify printer --> Error page with notification that the page will switch to https --> authentication: username, password, OK --> continue --> continue --> continue --> On the Make/Manufacturer page I want to change the driver so I select the make, continue --> I get an wait for .... and after several minutes I get a white firefox page. This is a bug.
This is my problem investigation: I saw when cups changed to https that my FQDN was missing the root domain (my FQDN is <server>.local.lan) Cups HTTPS redirected me to <server>.local (I will mention this in an other bug report). After disabling avahi-daemon cups HTTPS redirected me to the IP of the server but I still have the same bug. So I tried system-
I use 8.04-1 jeos on KVM for the print server
package cupsys:
Installed: 1.3.7-1ubuntu3.1
Candidate: 1.3.7-1ubuntu3.1
Version table:
*** 1.3.7-1ubuntu3.1 0
500 http://
500 http://
100 /var/lib/
1.3.7-1ubuntu3 0
500 http://
Hello Pva,
Thank you for submitting this bug and reporting a problem with cups and printing. You made this bug report some time ago and Ubuntu has been updated since then.
Could you confirm that this is no longer a problem and that we can close the ticket?
If it is still a problem, are you still interested in finding a solution to this bug?
If you are, could you let us know, and in the current version, run the following (only once):
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this particular issue.
Thank you again for helping make Ubuntu better.
G