Description of problem: After installing bzr-gtk and launching it, there is a python error: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.seahorse was not provided by any .service files Version-Release number of selected component (if applicable): 0.94.0-1.fc9 Steps to Reproduce: 1. Install a clean F9 installation 2. Install bzr-gtk-0.94.0-1.fc9 3. See if it start :) Actual results: Don't start Expected results: It start Additional info: It is resolvable if you install seahorse :)
Created attachment 306582 [details] Patch from upstream I've been waiting on upstream to refine this patch. Could you test it to make sure there are no side effects?
I don't have enought experience to test this patch. I will try the same to build from source and I will tell to you.
bzr-gtk-0.94.0-2.fc9 has been submitted as an update for Fedora 9
Hi Michele, Could you test this update? Until it gets moved to the testing repository, you can get it from: http://koji.fedoraproject.org/koji/buildinfo?buildID=51030
bzr-gtk-0.94.0-2.fc8 has been submitted as an update for Fedora 8
bzr-gtk-0.94.0-2.fc7 has been submitted as an update for Fedora 7
Hi, I tested it and it is perfect. It was successfully tested on Fedora core 9. It solve the seahorse problem. Thank you for the great work :)
bzr-gtk-0.94.0-2.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update bzr-gtk'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F7/FEDORA-2008-4838
bzr-gtk-0.94.0-2.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
bzr-gtk-0.94.0-2.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.
bzr-gtk-0.94.0-2.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.