Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Author Message
bobibobi0Offline
Post subject: cups stopped working after d-u  PostPosted: 04.08.2014, 20:06



Joined: 2014-06-20
Posts: 2

Status: Offline
Hello all

I did a dist-upgrade today and I got an error upgrading cups packages. I tried purging all cups related packages and then reinstalling, this is the error message I got:

root@cassini:~# apt-get install cups
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
cups-core-drivers cups-daemon
Suggested packages:
cups-bsd printer-driver-hpcups hplip cups-pdf
Recommended packages:
avahi-daemon colord printer-driver-gutenprint
The following NEW packages will be installed:
cups cups-core-drivers cups-daemon
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/788 kB of archives.
After this operation, 1,681 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Preconfiguring packages ...
Selecting previously unselected package cups-daemon.
(Reading database ... 241037 files and directories currently installed.)
Preparing to unpack .../cups-daemon_1.7.4-4_amd64.deb ...
Unpacking cups-daemon (1.7.4-4) ...
Selecting previously unselected package cups-core-drivers.
Preparing to unpack .../cups-core-drivers_1.7.4-4_amd64.deb ...
Unpacking cups-core-drivers (1.7.4-4) ...
Selecting previously unselected package cups.
Preparing to unpack .../cups_1.7.4-4_amd64.deb ...
Unpacking cups (1.7.4-4) ...
Processing triggers for man-db (2.6.7.1-1) ...
Setting up cups-daemon (1.7.4-4) ...
A dependency job for cups.service failed. See 'journalctl -xn' for details.
invoke-rc.d: initscript cups, action "start" failed.
dpkg: error processing package cups-daemon (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of cups-core-drivers:
cups-core-drivers depends on cups-daemon (>= 1.7.4-4); however:
Package cups-daemon is not configured yet.

dpkg: error processing package cups-core-drivers (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of cups:
cups depends on cups-core-drivers (>= 1.7.4-4); however:
Package cups-core-drivers is not configured yet.
cups depends on cups-daemon (>= 1.7.4-4); however:
Package cups-daemon is not configured yet.

dpkg: error processing package cups (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
cups-daemon
cups-core-drivers
cups
E: Sub-process /usr/bin/dpkg returned an error code (1)

Any suggestions?
 
 View user's profile Send private message  
Reply with quote Back to top
slhOffline
Post subject: RE: cups stopped working after d-u  PostPosted: 05.08.2014, 00:58



Joined: 2010-08-25
Posts: 758

Status: Offline
dpkg's suggestion, as shocking as it may sound, could be spot on - "journalctl -xn" or "systemctl status cups.service" can be of some use.

CUPS is working for me, both on a regularly dist-upgraded system just as well as a bulk-upgrade from a fresh install of our last release. Did you eventually actively disable IPv6 on your system?
 
 View user's profile Send private message  
Reply with quote Back to top
bobibobi0Offline
Post subject: RE: cups stopped working after d-u  PostPosted: 05.08.2014, 09:31



Joined: 2014-06-20
Posts: 2

Status: Offline
I had eventually disabled IPv6.

I reconfigured cups to listen to IPv4 only, now all is well.

Best regards
 
 View user's profile Send private message  
Reply with quote Back to top
slhOffline
Post subject: RE: cups stopped working after d-u  PostPosted: 06.08.2014, 04:43



Joined: 2010-08-25
Posts: 758

Status: Offline
Just for posterity, your response confirmed my suspicion. CUPS is configured to listen on 127.0.0.1 and ::1 (the IPv6 equivalent of localhost). If you forcefully disable IPv6, CUPS can't bind to all configured addresses (::1) and the systemd unit fails because of this.

The recommended action is not to force-disable IPv6 support (you can expect similar behaviour from other services as well; full IPv6 support has been a release goal for Debian for quite a while), if -for whatever 'wrong' reason- you can't do that, you'll have to reconfigure all involved services not to bind to ::1.
 
 View user's profile Send private message  
Reply with quote Back to top
Display posts from previous:     
Jump to:  
All times are GMT - 12 Hours
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Powered by Zafenio