Bug 710689 - CUPS does not start after upgrading system from F14 to F15
Summary: CUPS does not start after upgrading system from F14 to F15
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: cups
Version: 15
Hardware: i686
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-04 03:30 UTC by Javier Perez
Modified: 2011-07-18 11:54 UTC (History)
2 users (show)

Fixed In Version: cups-1.4.6-19.fc15
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-18 11:54:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Javier Perez 2011-06-04 03:30:57 UTC
Description of problem:
CUPS does not start after upgrading system from F14 to F15.

When I try to start it using systemctl, I get the following message:

[root@bloody cups]# systemctl status cups.service
cups.service - LSB: The CUPS scheduler
          Loaded: loaded (/etc/rc.d/init.d/cups)
          Active: failed since Fri, 03 Jun 2011 05:52:30 -0500; 10s ago
         Process: 1394 ExecStart=/etc/rc.d/init.d/cups start (code=exited, status=1/FAILURE)
          CGroup: name=systemd:/system/cups.service

/var/log/messages shows the following messages:
Jun  3 05:52:30 bloody systemd[1]: cups.service: control process exited, code=exited status=1
Jun  3 05:52:30 bloody systemd[1]: Unit cups.service entered failed state.

If I try to start cups by itself in foreground mode, I get the following messages:
[root@bloody ~]# cupsd -f
process 1461: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3524.
This is normally a bug in some application using the D-Bus library.
  D-Bus not built with -rdynamic so unable to print a backtrace
Aborted

And the cups error_log shows the following message:

[root@bloody cups]# cat error_log
I [03/Jun/2011:06:50:25 -0500] Listening to ::1:631 (IPv6)
I [03/Jun/2011:06:50:25 -0500] Listening to 127.0.0.1:631 (IPv4)
I [03/Jun/2011:06:50:25 -0500] Listening to /var/run/cups/cups.sock (Domain)
I [03/Jun/2011:06:50:25 -0500] Remote access is disabled.
D [03/Jun/2011:06:50:25 -0500] Added auto ServerAlias bloody.pphm
D [03/Jun/2011:06:50:25 -0500] Added auto ServerAlias bloody
I [03/Jun/2011:06:50:25 -0500] Loaded configuration file "/etc/cups/cupsd.conf"
I [03/Jun/2011:06:50:25 -0500] Using default TempDir of /var/spool/cups/tmp...
I [03/Jun/2011:06:50:25 -0500] Configured for up to 100 clients.
I [03/Jun/2011:06:50:25 -0500] Allowing up to 100 client connections per host.
I [03/Jun/2011:06:50:25 -0500] Using policy "default" as the default!
I [03/Jun/2011:06:50:25 -0500] Full reload is required.
I [03/Jun/2011:06:50:25 -0500] Loaded MIME database from "/usr/share/cups/mime" and "/etc/cups": 35 types, 45 filters...
D [03/Jun/2011:06:50:25 -0500] Loading printer Canon_IP3000...
D [03/Jun/2011:06:50:25 -0500] load_ppd: Loading /var/cache/cups/Canon_IP3000.ipp4...
D [03/Jun/2011:06:50:25 -0500] Calling DeleteDevice(cups-Canon_IP3000)


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

cups 1.4.6-15.fc15
cups-bjnp 0.5.5-3.fc15
cups-libs 1.4.6-15.fc15
cups-pk-helper 0.1.2-1.fc15

How reproducible:
Always

Steps to Reproduce:
1. Update from F14 to F15. Upon boot you will get a message that cups did not start.
2. Run systemctl start cups.service 
3. Run cupsd -f
  
Actual results:
cups does not start

Expected results:
cups should have started as a service

Additional info:

Comment 1 Javier Perez 2011-06-04 05:27:49 UTC
I tried cups 1.4.6-19.fc15 and it solved the problem.

http://koji.fedoraproject.org/koji/buildinfo?buildID=246196


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