Bug 386171
Summary: | Miro 0.9.9.9 will not start | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Steve Fox <steve> |
Component: | Miro | Assignee: | Thorsten Scherf <tscherf> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 8 | CC: | alex |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-11-21 04:57:27 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
Steve Fox
2007-11-16 02:59:11 UTC
I can't reproduce this on my F-8 machine, it starts just fine for me. I'm running i386, perhaps that might account for the difference. I'm planning to upgrade to 1.0 soon (bug #380811), I'll check to see if any python/d-bus related bugs have been fixed since 0.9.9.9 Unfortunately, I get the same error with Miro-1.0-1.fc8. Okay, I dug around in the source a bit, trying to figure out what's going on. It turns out that I had a stale miro process running and Miro's "OneTime" class apparently has a bug in it. Killing the stale process fixed it. |