Thanks for following up. I'm closing this report due to your last comment regarding that you've fixed if with an upgrade.
To answer your question about triggers the definition from the blueprint is "A dpkg trigger is a facility that allows events caused by one package but of interest to another package to be recorded and aggregated, and processed later by the interested package. This feature simplifies various registration and system-update tasks and reduces duplication of processing. " You can read more at https://wiki.ubuntu.com/DpkgTriggers and http://www.dpkg.org/dpkg/Triggers In our case, what happened is that cups has been installed and configured but triggers were not executed because the upgrade has been interrupted. Then during the next run, the system found that cups was already installed and configured and was waiting for triggers which would never execute because of the previous failure. This is a known problem and the devs are working on it (it's probably already fixed in Jaunty) ** Changed in: cups (Ubuntu) Status: Incomplete => Invalid -- package cups 1.3.9-2ubuntu1 failed to install/upgrade: package cups is already installed and configured https://bugs.launchpad.net/bugs/295552 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
