This bug is attacked and fixed from two directions at once (as it really
looks like two bugs to me).
In version 1.1.23-1ubuntu12 of cupsys, the init script is a bit smarter
about how it tries to stop/start/restart the daemon, and should succeed
more often now.
Furthermore, in version 4.2.7-4ubuntu3 of cupsys-driver-gimpprint, even in
the even that cupsys's init script does exit with an error, which it just
plain WILL sometimes, cupsys-driver-gimpprint no longer fails to configure,
and dpkg carries on its merry way.
This bug is attacked and fixed from two directions at once (as it really
looks like two bugs to me).
In version 1.1.23-1ubuntu12 of cupsys, the init script is a bit smarter
about how it tries to stop/start/restart the daemon, and should succeed
more often now.
Furthermore, in version 4.2.7-4ubuntu3 of cupsys- driver- gimpprint, even in driver- gimpprint no longer fails to configure,
the even that cupsys's init script does exit with an error, which it just
plain WILL sometimes, cupsys-
and dpkg carries on its merry way.