cups-1.5.4-18.fc17 & /etc/cups/cups-files.conf

Gregory P. Ennis PoMec at PoMec.Net
Wed Mar 6 18:20:03 UTC 2013

On Tue, 2013-03-05 at 19:40 -0600, Gregory P. Ennis wrote:
> The f17 update of cups to cups-1.5.4-18.fc17 on Feb 25th caused cups to
> fail to start.  This update had some security updates with a creation of
> a new file /etc/cups/cups-files.conf that apparently can not be written
> to by cupsd.
> Log errors demonstrated that the lack ssl certificates on this unit
> caused cupsd to fail.  I commented the certificates out of
> the /etc/cups-files.conf file, and got cups to start, but I still could
> not get it to communicate with the cups print server on the network.  

It would be fantastic if you could file a bug report against cups,
including the log messages you saw.



I usually check the list first to see if someone else has solved the
problem, or to get an idea if the problem was caused by me.

I ave created a bug report for it.

It is interesting in that I have other F17 and F18 units that were
updated on latter dates than the 26th of February that did not develop
the problem.  

If there are others that have the problem all I did to solve it was to
comment out the last lines of the cups-files.conf file that were added
by the RPM package.

# End of "$Id$".

# Settings automatically moved from cupsd.conf by RPM package:
#LogFilePerm 0600
#Printcap /etc/printcap
#ServerCertificate /etc/cups/ssl/server.crt
#ServerKey /etc/cups/ssl/server.key

The other Desktop units in our network related to F17 and F18 did not
add these lines to the cups-files.conf file with yum updates, and cups
functioned normally on those units.  


More information about the users mailing list