Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 155872 - "yum update" on april 22 destroys my cups configuration
Summary: "yum update" on april 22 destroys my cups configuration
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: cups
Version: 3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-04-25 06:14 UTC by Joachim Backes
Modified: 2014-01-21 22:51 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-04-25 16:31:50 UTC


Attachments (Terms of Use)

Description Joachim Backes 2005-04-25 06:14:16 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050416 Fedora/1.0.3-1.3.1 Firefox/1.0.3

Description of problem:
When updating my system on friday, april 22, with "yum update", the cups config file /etc/cups/cupsd.conf will be corrupt: there is a config line inserted with the contents:

Listen 127.0.0.1:631

This forbids contacts from other hosts.

Version-Release number of selected component (if applicable):
yum-2.2.0-0.fc3

How reproducible:
Always

Steps to Reproduce:
1.see description
2.
3.
  

Actual Results:  contacts from outside are rejected.

Expected Results:  printing possible from hosts other than the cups server.

Additional info:

Removing the Listen line solves my problem.

Comment 1 Seth Vidal 2005-04-25 12:29:22 UTC
This has nothing to do with yum. Refiling against cups

Comment 2 Tim Waugh 2005-04-25 16:31:50 UTC
If you are not using system-config-printer to configure cups, you *must* remove
system-config-printer.


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