Bug 112835 - When configuring cups with printconf a incorrect configuration is generated.
Summary: When configuring cups with printconf a incorrect configuration is generated.
Alias: None
Product: Fedora
Classification: Fedora
Component: cups
Version: 1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
Keywords: Security
Depends On:
TreeView+ depends on / blocked
Reported: 2004-01-03 15:15 UTC by Nicolai Langfeldt
Modified: 2007-11-30 22:10 UTC (History)
0 users

Clone Of:
Last Closed: 2004-05-13 12:52:49 UTC

Attachments (Terms of Use)

Description Nicolai Langfeldt 2004-01-03 15:15:20 UTC
Description of problem:

When creating a queue and then sharing it, restricting it to specific
IP addresses the generatet config contains "Listen"
instead of Allow from The host in question's ip-address is

Version-Release number of selected component (if applicable):


How reproducible:

Steps to Reproduce:
1. be root
2. printconf
3. select a queue
4. select menu: action -> sharing...
5. In dialog tab Queue click for "This queue is available to other
6. Remove the "All hosts" line from the Allowed hosts
7. Add/Single IP address/ (the address should not be one of
the addresses of your computer) and click ok.
8. click ok in the "Sharing properties" dialog
9. click apply in the printer configuration main window

This is highly bogus and when I add 
Actual results:

Inspect the cupsd.conf file genrated and at the very end find "Listen".

When cups is then _restarted_ instead of just reconfigured it bails
out with this in the messages file:

Jan  3 16:16:10 roke cupsd: cupsd: Child exited with status 99!

Expected results:

Only the Allow from lines generated earlier in the file.  And perhaps
a "Port" command for listening to the network in general, or some
Listen commands for each local address of the computer.

Additional info:

Comment 1 Tim Waugh 2004-01-05 17:00:54 UTC
Please try these experimental packages:


Let me know if that helps or not.

Comment 2 Tim Waugh 2004-01-12 11:24:07 UTC

Comment 3 Tim Waugh 2004-01-19 15:50:44 UTC

Please respond so that I know if this fixes the problem you were seeing.

Comment 4 Nicolai Langfeldt 2004-02-02 22:58:45 UTC
Sorry.  I was busy writing a book to a deadline.  Yes.  It's much
better like this, the Listen statements stick to the hosts own
addresses and adding new addresses only adds Allow from statements:

<Location /printers/otak>
Order Deny,Allow
Deny From All
Allow From
AuthType None
Allow from
Allow from
Allow from

To me this appears to be resolved.


Note You need to log in before you can comment on or make changes to this bug.