Better yet, how about we develop a patch to move the STATE information out of the CONFIG file, and into /var/lib/cups or so where it properly belongs, and then file a new bug upstream with the patch, since upstream decided that they won't fix this bug, since they see no difference between configuration and state info.
(Yes, it means writing and reading two files instead of one, and actually knowing what is config and what is state... 'Status: disconnected' isn't part of the configuration, it's STATE.) Meanwhile, maybe I'll just cron a "sed -i /Time/d /etc/cups/printers.conf" so that it will stop being a modified file in /etc every time cups is restarted... lamont -- FHS violation? https://bugs.launchpad.net/bugs/301594 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
