Bug 498138
Summary: | bzr viz always fails first attempt, succeeds second | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Warren Togami <wtogami> |
Component: | bzr-gtk | Assignee: | Toshio Ernie Kuratomi <a.badger> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 11 | CC: | a.badger, shahms |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-11-11 16:43:35 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Warren Togami
2009-04-29 03:17:28 UTC
I'm not able to reproduce this. It works for me with seahorse installed and uninstalled. When seahorse-daemon is running or not running. To see if seahorse is a red herring could you try: $ ps aux |grep warren > before-fail.log $ bzr viz [traceback] $ ps aux |grep warren > after-fail.log $ bzr viz [success] $ ps aux | grep warren > after-success.log If I'm right we'll see that seahorse-daemon is not running in the before-fail case and then it will be in one of the after cases. I'm curious to know whether it's started by the time we get to after-fail or not until after-success. Also if there's anything other process that gets started in the meantime... Maybe dbus itself is having to start? Versions of dbus and seahorse here are: dbus-1.2.4-2.fc10.i386 dbus-python-0.83.0-3.fc10.i386 seahorse-2.24.1-1.fc10.i386 This looks like the upstream bug. Trying the patch proposed here: http://bundlebuggy.aaronbentley.com/project/bzr/request/%3Cbb631e240905260124h7fefe79btb0fdf911c96e7b64%40mail.gmail.com%3E Built for RawHide. Leaving this open until we see if upstream comes up with what the problem is: http://koji.fedoraproject.org/koji/taskinfo?taskID=1380071 This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Looks like when upstream figured out that it's a bug in seahorse, they reverted the workaround in bzr-gtk. Warren will try the patch in the seahorse bug http://bugzilla.gnome.org/show_bug.cgi?id=583356 If that works, we can see if the seahorse maintainer would be willing to inlude it in a bugfix release. Fixed in F-12 |