Le lundi, 5 mai 2014, 15.19:30 BogDan Vatra a écrit : > > I expect the cups maintainers are going to need more information > > here. Please look in the journal (or syslog) to see what went > > wrong, and quote it on the bug.
Yay, thanks for the initial response. > > Useful commands might include "journalctl", "less /var/log/syslog", > > "journalctl -xn", "systemctl -a status cups.service", "systemctl > > list-units". > > Here we go: > > journalctl: > .... > mai 05 15:07:25 zmeu sudo[2830]: bogdan : TTY=pts/3 ; PWD=/home/bogdan > ; USER=root ; COMMAND=/bin/bash > mai 05 15:07:25 zmeu sudo[2830]: pam_unix(sudo:session): session > opened for user root by bogdan(uid=0) > mai 05 15:07:37 zmeu systemd[1]: Reloading. > mai 05 15:07:37 zmeu systemd[1]: Starting CUPS Printing Service > Sockets. mai 05 15:07:37 zmeu systemd[1]: cups.socket failed to > listen on sockets: Cannot assign requested address Hmm. 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` ? Do you happen to have a specific IPv6 setup on this machine? Kernel module unloaded or not built? > Well, cups worked perfectly for me before I SID replaced sysvinit with > systemd. Because I was sure that some people will say "it works for > me", I removed them, and I tried to install them again. The result is > the same, so for me is just a simple "doesn't work on systemd". :) Did you upgrade all your system to sid? What is the install status of cups-browsed? Thanks in advance, cheers, OdyX -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
