Ok, that's understandable. In that case, I would posit that the bug is that seahorse was installed by the Gutsy upgrade without notification of the user, and/or that the dialog gives no clues on how to disable seahorse. The Gutsy upgrade broke system-critical processes without notifying the user, and without providing documentation on how to restore functionality. At its very least, that's a usability bug.
-- vim editing gpg encrypted files broken by Gnome encryption system https://bugs.launchpad.net/bugs/247345 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
