cupsd: Child exited with status 2!

[John Graddy]

On Wed, 2007-03-14 at 15:17 -0700, Rares Vernica wrote:
> Michael R. Head wrote:
> > This is fixed in cups 1.2.8-0ubuntu6. See bug
> > https://bugs.launchpad.net/ubuntu/+source/cupsys/+bug/92205
> > 
> > On Wed, 2007-03-14 at 14:27 -0700, Rares Vernica wrote:
> >> Hi,
> >>
> >> After I did "atp-get upgrade" I get some error when starting cups.
> >>
> >> I think apt logged the actions and it is trying to start cups every time 
> >> I run it:
> >>
> >> avocado:~> sudo apt-get autoremove
> >> Reading package lists... Done
> >> Building dependency tree
> >> Reading state information... Done
> >> 0 upgraded, 0 newly installed, 0 to remove and 21 not upgraded.
> >> 1 not fully installed or removed.
> >> Need to get 0B of archives.
> >> After unpacking 0B of additional disk space will be used.
> >> Setting up cupsys (1.2.8-0ubuntu5) ...
> >>   * Starting Common Unix Printing System: cupsd 
> >>        cupsd: Child exited with status 2!
> >> invoke-rc.d: initscript cupsys, action "start" failed.
> >> dpkg: error processing cupsys (--configure):
> >>   subprocess post-installation script returned error exit status 2
> >> Errors were encountered while processing:
> >>   cupsys
> >> E: Sub-process /usr/bin/dpkg returned an error code (1)
> >> avocado:~>
> >>
> >> If I try to start it manually it also fails:
> >>
> >> avocado:~> sudo /etc/init.d/cupsys start
> >>   * Starting Common Unix Printing System: cupsd 
> >>        cupsd: Child exited with status 2!
> >> avocado:~>
> >>
> >> I checked the logs for cups and here is what it says:
> >>
> >> avocado:~> tail -2 /var/log/cups/error_log
> >> X [14/Mar/2007:14:24:37 -0700] Unable to load MIME database from 
> >> '/usr/share/cups/mime:/etc/cups'!
> >> X [14/Mar/2007:14:25:13 -0700] Unable to load MIME database from 
> >> '/usr/share/cups/mime:/etc/cups'!
> >> avocado:~>
> >>
> >> Thanks a lot,
> >> Ray
> >>
> >>
> >>
> >>
> 
> Thanks a lot,
> Ray
> 
I had the same problem after yesterday's update run.  

At about 10:00PM yesterday I did:

sudo aptitude update
sudo aptitude upgrade

After the upgrade, all is back to normal.

John