> That's not something Diodon has under control. IMO it's sufficient to detect that the external resource is in an illegal or malfunctional state and forward that information to the user. The check needs to be included anyway in order to avoid a non-responsive state of `diodon` regardless of the issue and its fix - after fixing the issue/requesting the fix in `zeitgeist` or the usage of `zeitgeist` within `diodon` it can still occur that it misbehaves at a later point for other reasons.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1405525 Title: database is locked error prevents Diodon from adding items to or clearing history To manage notifications about this bug go to: https://bugs.launchpad.net/diodon/+bug/1405525/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
