Bug#343539: the daemon doesn't start after upgrade

2005-12-15 Thread Mark Robinson
Found it. After the upgrade both /etc/cups/cupsd.conf and /etc/cups/cups.d/ports.conf contain the line Port 631 It is assumed that each appearance of this line causes the daemon to attempt to grab the port, the second resulting in failure. Removing either one restores operation. a

Bug#343539: the daemon doesn't start after upgrade

2005-12-15 Thread Mark Robinson
I'm seeing this behaviour too. Here's the error log for a startup attempt. Note that the first line appears twice. I [16/Dec/2005:11:38:44 +1300] Listening to 0:631 I [16/Dec/2005:11:38:44 +1300] Listening to 0:631 I [16/Dec/2005:11:38:44 +1300] Loaded configuration file "/etc/cups/cupsd.conf"

Bug#343539: the daemon doesn't start after upgrade

2005-12-15 Thread Josselin Mouette
Package: cupsys Version: 1.1.23-13 Severity: important During the cupsys upgrade, I noticed that the daemon failed to restart. I tried to launch it by hand, without a positive result: $ sudo /etc/init.d/cupsys start Starting Common Unix Printing System: cupsdcupsd: Child exited with status 98! I