Bug 594430
| Summary: | Gwibber does not start | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Aioanei Rares <schaiba> |
| Component: | gwibber | Assignee: | Tom "spot" Callaway <tcallawa> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 14 | CC: | tcallawa |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | gwibber-2.31.4-1.fc12 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-08-20 01:55:43 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: | |||
gwibber-2.31.2-7.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/gwibber-2.31.2-7.fc12 gwibber-2.31.2-7.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/gwibber-2.31.2-7.fc13 gwibber-2.31.2-7.fc13 has been pushed to the Fedora 13 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 gwibber'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gwibber-2.31.2-7.fc13 gwibber-2.31.2-7.fc12 has been pushed to the Fedora 12 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 gwibber'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gwibber-2.31.2-7.fc12 This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle. Changing version to '14'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping gwibber-2.31.4-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/gwibber-2.31.4-1.fc12 gwibber-2.31.4-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/gwibber-2.31.4-1.fc13 gwibber-2.31.4-1.fc12 has been pushed to the Fedora 12 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 gwibber'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gwibber-2.31.4-1.fc12 gwibber-2.31.4-1.fc13 has been pushed to the Fedora 13 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 gwibber'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gwibber-2.31.4-1.fc13 gwibber-2.31.4-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. gwibber-2.31.4-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: After installing it, I start gwibber and it asks me top set up a keyring password (this is KDE); after that, and subsequent starts, nothing happens. Version-Release number of selected component (if applicable): gwibber-2.30.0.1-6.fc14.noarch How reproducible: Everytime Steps to Reproduce: 1.start gwibber 2. 3. Actual results: None but a traceback (below) Expected results: gwibber Additional info: $ gwibber Removing stale, deceptive pid file. Apache CouchDB has started, time to relax. Browse your desktop CouchDB at file:///home/arares/.local/share/desktop-couch/couchdb.html Traceback (most recent call last): File "/usr/bin/gwibber", line 67, in <module> client.Client() File "/usr/lib/python2.6/site-packages/gwibber/client.py", line 459, in __init__ self.w = GwibberClient() File "/usr/lib/python2.6/site-packages/gwibber/client.py", line 28, in __init__ self.model = gwui.Model() File "/usr/lib/python2.6/site-packages/gwibber/gwui.py", line 42, in __init__ self.settings = util.SettingsMonitor() File "/usr/lib/python2.6/site-packages/gwibber/util.py", line 91, in __init__ DEFAULT_SETTINGS) File "/usr/lib/python2.6/site-packages/gwibber/microblog/util/couch.py", line 65, in __init__ self.database = CouchDatabase(dbname, create=True) File "/usr/lib/python2.6/site-packages/desktopcouch/records/server.py", line 57, in __init__ server_class=server_class, oauth_tokens=oauth_tokens, ctx=ctx) File "/usr/lib/python2.6/site-packages/desktopcouch/records/server_base.py", line 147, in __init__ if database not in self._server: File "/usr/lib/python2.6/site-packages/couchdb/client.py", line 120, in __contains__ self.resource.head(validate_dbname(name)) File "/usr/lib/python2.6/site-packages/couchdb/client.py", line 1019, in head return self._request('HEAD', path, headers=headers, **params) File "/usr/lib/python2.6/site-packages/couchdb/client.py", line 1073, in _request raise ServerError((status_code, error)) couchdb.client.ServerError: (500, '') Since I never got to setup any accounts, why would any server respond with 500?