cupsys 1.2.1-0ubuntu1 doesn't support 11.22.33.* network masks
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cupsys (Ubuntu) |
Fix Released
|
High
|
Martin Pitt | ||
Dapper |
Fix Released
|
High
|
Martin Pitt |
Bug Description
Binary package hint: cupsys
Dapper 6.06 LTS - upgrade from cupsys 1.2.0* breaks with a previously successful /etc/cups/
Printer: HP LaserJet6L printer.
Fully updated 6.06 system.
After today's upgrades, including the upgrade to cupsys:
1. System - Admin - Printing reports "unable to contact cups server".
2. sudo /etc/init.d/cupsys restart ( or stop --> start ) fails
3. "sudo dpkg-reconfigure cupsys" reports the package as broken
4. Output of
$ tail /var/log/
E [09/Jul/
I [09/Jul/
I [09/Jul/
E [09/Jul/
E [09/Jul/
E [09/Jul/
I [09/Jul/
I [09/Jul/
E [09/Jul/
E [09/Jul/
and changing line 800 from "Allow From 10.1.1.* " to "Allow From 10.1.1.0/24" , followed by
sudo /etc/init.d/cupsys restart
rectifies the problem, and the printer successfully prints a test page both from the local machine at 10.1.1.4 and from the network ( 10.1.1.2 )
Changed in cupsys: | |
status: | Confirmed → In Progress |
description: | updated |
Changed in cupsys: | |
assignee: | nobody → pitti |
importance: | Untriaged → High |
status: | Unconfirmed → Fix Committed |
status: | Fix Committed → In Progress |
You have configuration from Breezy. On upgrade to Dapper you were asked if you want to keep old config or get a new one. Since you choosed old one, new cups package didn't overwrite it. And since new minor CUPS release didn't have any changes in config, it didn't ask you same question again.
CUPS 1.2 doesn't support RunAsUser, but you have a valid bug here:
Address masks with * are broken in CUPS.