© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
I was about to file this same bug. After a few days of research, I found the following similar or related bug reports:
https:/
https:/
https:/
http://
Note, the issue begins in 1.4.x versions of cups, <=1.3 should work fine, so a downgrade might be your desired course of action if that's a possibility for you.
None of the solutions provided in those helped. In case you find this via google, let me save you some time and enumerate them here:
-In cups.conf, add (or uncomment, or modify) a line at the end to read:
ServerAlias *
-In cups.conf, add (or uncomment, or modify) the entry for "<Location /admin>" to:
Allow from all
or
Allow from [some ip here]
-In cups.conf, add a line that reads:
Listen 192.168.1.1:631
or
Listen *:631
(or whatever port you want to use instead of 631)
(with the IP you want to allow access to)
The problem shows up as lines similar to the following in your cups error_log file:
E [23/Nov/
The most relevant link was:
https:/
which traces the problem to this patch:
https:/
(direct link to msg: https:/
Which was submitted to solve:
https:/
So with that info, I downloaded the sources on my fedora (fc17) machine, modified them, rebuilt the packages and installed, and everything works now as (I) intended.
I have attached the patch I wrote which solves it for me,
WARNING: this might introduce some security issues (related to CVE-2009-0164), which I didn't delve too deeply to know whether they do or not.
So, USE AT YOUR OWN RISK.
Read this too:
http://
When running the patched version, you still need to have the proper Listen and ServerAlias entries, of course.