Comment 5 for bug 14187

I just installed Ubuntu today (Ubuntu 5.04 _Hoary Hedgehog_ - Preview i386), so
this may not be the cause of the problem for previously installed systems,
however, on my system the problem was caused by the lack of an ipv4 loopback
(the lo interface had an ipv6 address but not the ipv4 address of 127.0.0.1).
Thus, running "ifconfig lo inet 127.0.0.1" as root solved the problem.

(In reply to comment #0)
> I'm getting the following error when trying to upgrade cupsys-driver-gimpprint
> usinf apt-get dist-upgrade
>
> dbasinge@pheonix:~$ sudo apt-get dist-upgrade
> Reading Package Lists... Done
> Building Dependency Tree... Done
> Calculating Upgrade... Done
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> 1 not fully installed or removed.
> Need to get 0B of archives.
> After unpacking 0B of additional disk space will be used.
> Do you want to continue? [Y/n] y
> Setting up cupsys-driver-gimpprint (4.2.7-4ubuntu2) ...
> No Gimp-Print PPD files to update.
> * Restarting Common Unix Printing System: cupsd
> cupsd: Child exited with status 98!
> dpkg: error processing cupsys-driver-gimpprint (--configure):
> subprocess post-installation script returned error exit status 2
> Errors were encountered while processing:
> cupsys-driver-gimpprint
> E: Sub-process /usr/bin/dpkg returned an error code (1)

(In reply to comment #3)
> A little wild guess here: maybe a "sleep 5" after the "kill -9" as it was
> originally proposed in latest patch for cupsys.postinst (Comment #6 of Bug 11037)
> would do the trick; or maybe an additional sleep somewhere else in that script?
> Maybe cupsys doesn't have the time to properly stop before its restart in some
> configurations? (I know that I haven't experienced this problem on my computer
> during the last cupsys upgrade)
>
>