Red Hat Bugzilla – Bug 318251
samba failed to start because of missing cups-libs
Last modified: 2007-11-30 17:12:17 EST
Description of problem:
I installed some kind of minimal system (server class) and this machine should
only provide file services, so I decided not to install printing support and
"unchecked" it in the installation. Everything went fine, but samda did not
start, even if printing was explicite not configured.
After installing cups-libs, samba started perfectly.
Version-Release number of selected component (if applicable):
just tried once
Steps to Reproduce:
1. install fedora 7 without "printing support", but including "samba"
2. try to start samba service
the smbd did not start properly
either installation should have installed cups-libs or the samba smbd binary
should load the lib dynamically if needed via some kind of module system.
The samba packages requires libcups.so.2 which is provided by cups-libs.
Have you installed all dependencies? or have you forced the installation of the
samba package with --nodeps ?
I just made a "normal" installation without any possibility to force
installation of packages.
I don't know if this is a bug in "Requires" or in anaconda which in fact
installed the package.
an 'rpm -q --requires samba' should return you libcups.so.2 in the output, can
you confirm ?
Yes, the package seems to have libcups.so.2 listed in requires.
But installation dates on the machine are:
samba: september 26th, 10:38
cups-libs: september 27th, 14:48
(I installed cups-libs after samba failed to start.)
I just found out, that the original installation installed cups-libs-1.2.10 and
now 1.2.12 is installed. Maybe the original cups-libs package was broken?
Could be, what samba version do you have?
As I stated already:
now (working) is 1.2.12
previous (not working) was 1.2.10 (original installation version)
But I asked you about the samba version, not the cups version :-)
currently installed is 3.0.26a, previously installed was 3.0.25-2
So I think that one of the installation packages had bad dependencies which are
Ok then I'll close this as fixed in current release,