Bug 447052 - cups won't start because of ldap linking problem
Summary: cups won't start because of ldap linking problem
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: cups
Version: 9
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-17 13:16 UTC by Luis Villa
Modified: 2008-05-17 17:18 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-05-17 15:56:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Luis Villa 2008-05-17 13:16:51 UTC
[louie@towel ~]$ sudo /etc/init.d/cups start
Starting cups: cupsd: error while loading shared libraries: libldap-2.3.so.0:
cannot open shared object file: No such file or directory
                                                           [FAILED]

Note that symlinking libldap-2.4.so.2 to libldap-2.3.so.0 allows cups to start,
but then I get an authentication message from system-config-printer that I've
never seen before- possibly that is because of ldap? Dunno. (This is a purely
local setup, I have never used ldap in my life :)

Version info:
[louie@towel ~]$ rpm -qi cups
Name        : cups                         Relocations: (not relocatable)
Version     : 1.3.7                             Vendor: Fedora Project
Release     : 2.fc8                         Build Date: Fri 09 May 2008 06:57:21
AM EDT
...

[louie@towel ~]$ rpm -qi openldap
Name        : openldap                     Relocations: (not relocatable)
Version     : 2.4.8                             Vendor: Fedora Project
Release     : 3.fc9                         Build Date: Wed 05 Mar 2008 08:04:24
AM EST

Comment 1 Tim Waugh 2008-05-17 15:56:24 UTC
Looks like you haven't applied the updates.  There is a cups-1.3.7-2.fc9 update,
which is newer than your F-8 package.

Comment 2 Luis Villa 2008-05-17 17:18:00 UTC
Yum says there are no updates; must be a residual problem from preupgrade. Funfun.


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