> I don't think catching this particular exception and ignoring it is the > right way to go, as this is a genuine error indicating a problem > communicating with DBus. I'd rather see the error underneath being > fixed.
I don't think it's that bad to ignore this exception, since it only happens for the first time you run "bzr viz". From a user experience point of view it's way better to not have seahorse integration for the first run, than getting an ugly traceback not knowing that it's just a one-time issue. Szilveszter -- bzr-gtk mailing list [email protected] Modify settings or unsubscribe at: https://lists.canonical.com/mailman/listinfo/bzr-gtk
