This bug was fixed in the package zeitgeist - 0.8.1.1-1
---
zeitgeist (0.8.1.1-1) unstable; urgency=low
* New upstream release:
- Fix problem when replacing an existing Zeitgeist instance (LP: #809569).
- Fix possible crash when zeitgeist-datahub isn't available (LP: #7913
** Branch linked: lp:debian/zeitgeist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791392
Title:
zeitgeist-daemon crashed with GError in start_datahub(): Failed to
execute child process "zeitgeis
** Changed in: zeitgeist
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791392
Title:
zeitgeist-daemon crashed with GError in start_datahub(): Failed to
** Branch linked: lp:zeitgeist
** Branch linked: lp:~zeitgeist-packagers/zeitgeist/debian
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791392
Title:
zeitgeist-daemon crashed with GError in start_d
** Also affects: zeitgeist
Importance: Undecided
Status: New
** Changed in: zeitgeist
Importance: Undecided => Medium
** Changed in: zeitgeist
Status: New => Fix Committed
** Changed in: zeitgeist
Milestone: None => 0.8.1.1
** Changed in: zeitgeist
Assignee: (unassi
** Changed in: zeitgeist (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791392
Title:
zeitgeist-daemon crashed with GError in start_datahub(): Failed to
exe
Note to myself:
This should have been ignored by Zeitgeist since zeitgeist-datahub is optional.
It looks like glib.spawn_async changed from raising a OSError to raising this
GError, so we need to update the try/catch to consider both.
** Visibility changed to: Public
--
You received this bug n
