Hi Giuseppe, and thanks for your followup,
Le mardi, 6 mai 2014, 14.23:41 Giuseppe Bilotta a écrit :
> I've just come across this issue during a dist-upgrade. The situation
> is the same as that of the original message: nothing is using port
> 631 or the cups socket, but:
Are you sure of that? Can you paste the output of the following command
(run as root):
netstat -lnptu | grep 631
> May 06 14:12:51 labrador systemd[1]: Starting CUPS Printing Service
> Sockets. May 06 14:12:51 labrador systemd[1]: cups.socket failed to
> listen on sockets: Address already in use May 06 14:12:51 labrador
> systemd[1]: Failed to listen on CUPS Printing Service Sockets. May 06
> 14:12:56 labrador systemd[1]: Closed CUPS Printing Service Sockets.
>
> so cups-daemon, cups and cups-core-drivers fail to complete the
> upgrade/configure.
Do you have a specific ipv6 configuration (module unloaded or
blacklisted?
Can you attach the content of all files and symlinks in
/etc/systemd/system/cups.socket.d ?
Could you also attach the output of `systemctl show cups.socket` ?
Thanks in advance, cheers,
OdyX
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
