Description of problem: https://admin.fedoraproject.org/updates/FEDORA-2014-9383/zeitgeist-0.9.14-3.fc20 broke Empathy and GNOME Contacts, please fix or revert ASAP!
Version-Release number of selected component (if applicable): zeitgeist-libs-0.9.14-3.fc20.x86_64
How reproducible: Always
Steps to Reproduce:
1. Start Empathy or Contacts
Actual results: Crash
Expected results: No crash
Additional info: Downgrade to zeitgeist-libs-0.9.14-2.fc20.x86_64 and they work again.
Upstream bugs (with stacktraces):
Probably I need to update zeitgeist to a newer version. As I didn't modify the sources. Something wrong in the gnome side.
On Fedora rawhide, with zeitgeist latest git snapshot I updated days ago, gnome-contacts starts without issues.(under KDE, empathy not tested)
I will push an update of 0.9.15 and please test again.
I believe vala has some changes that affect zeitgeist.
I think pushing 0.9.15 may be too harsh, I decide to push a fix committed in upstream VCS.
Richard, next time when you push update of vala, could you test and verify if the new version won't cause troubles to other packages?
zeitgeist-0.9.14-4.fc20 has been submitted as an update for Fedora 20.
> Richard, next time when you push update of vala, could you test and
> verify if the new version won't cause troubles to other packages?
As pointed out in bodhi, rushing out updates is irresponsible, regardless of whether it is an upgrade of the tool-chain or a simple rebuild of a package. It undermines our testing process. All those updates need sufficient testing. The broken zeitgeist update would have been caught, if it had been kept in updates-testing for a longer time.
If an upgrade of Vala breaks the rebuild results of other packages, that would be very difficult to notice, unless all depending packages would be rebuilt and tested painstakingly. A karma threshold of +1 is just not a clever idea. Eventually, the Fedora Project will need to enforce strict rules to avoid such incidents.
0.9.14-4 does not appear to fix the problem with Empathy starting up. I still need to downgrade to 0.9.14-2:
g_dbus_connection_real_closed: Remote peer vanished with error: Error receiving message: Connection reset by peer (g-io-error-quark, 0). Exiting.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing zeitgeist-0.9.14-4.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Unfortunately, zeitgeist-libs-0.9.14-4.fc20 doesn't solve all issues. If you do need Empathy, downgrade with:
# su -c 'yum downgrade package zeitgeist-libs-0.9.14-2.fc20'
(In reply to Václav Mocek from comment #9)
> Unfortunately, zeitgeist-libs-0.9.14-4.fc20 doesn't solve all issues. If you
> do need Empathy, downgrade with:
> # su -c 'yum downgrade package zeitgeist-libs-0.9.14-2.fc20'
bijiben also crashes with 0.9.14-3. I just downgraded and this fixed the issue.
For me too, updating to 0.9.14-4 (or 0.9.14-3) results in Empathy crashing. Downgrading to 0.9.14-2 fixed the problem.
zeitgeist-0.9.16-0.2.20140808.git.ce9affa.fc20 has been submitted as an update for Fedora 20.
The latest zeitgeist-0.9.16 seems to work for me:
Empathy startup seems fixed with 0.9.16-0.2.20140808.git.ce9affa.
zeitgeist-0.9.16-0.2.20140808.git.ce9affa.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
Well, gnome-activity-journal still crashes and zeitgeist just seems broken (it doesn't seem to be indexing anymore).
(In reply to Christian Klomp from comment #16)
> Well, gnome-activity-journal still crashes and zeitgeist just seems broken
> (it doesn't seem to be indexing anymore).
Have you reported a bug against activity-control?
(In reply to Christopher Meng from comment #17)
> (In reply to Christian Klomp from comment #16)
> > Well, gnome-activity-journal still crashes and zeitgeist just seems broken
> > (it doesn't seem to be indexing anymore).
> Have you reported a bug against activity-control?
I don't know what you mean with activity-control, but after some fiddling I managed to fix the issues by removing all the ~/.local/share/zeitgeist/activity.sqlite files, forcefully killing zeitgeist and then starting it again.