| Summary: | [abrt] gwibber-1:2.91.92-2.fc15: storage.py:44:setup_table:OperationalError: table messages already exists | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | bibo | ||||
| Component: | gwibber | Assignee: | Tom "spot" Callaway <tcallawa> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 15 | CC: | tcallawa | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:7e05404d | ||||||
| Fixed In Version: | gwibber-3.0.0.1-2.fc13 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-05-19 04:57:06 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
Created attachment 493360 [details]
File: backtrace
gwibber-3.0.0.1-2.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/gwibber-3.0.0.1-2.fc14 gwibber-3.0.0.1-2.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/gwibber-3.0.0.1-2.fc15 gwibber-3.0.0.1-2.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/gwibber-3.0.0.1-2.fc13 Package gwibber-3.0.0.1-2.fc13: * should fix your issue, * was pushed to the Fedora 13 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gwibber-3.0.0.1-2.fc13' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/gwibber-3.0.0.1-2.fc13 then log in and leave karma (feedback). gwibber-3.0.0.1-2.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. gwibber-3.0.0.1-2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. gwibber-3.0.0.1-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. |
abrt version: 1.1.17 architecture: i686 cmdline: /usr/bin/python /usr/bin/gwibber-service comment: I don't know when the gwibber-service stopped his service. component: gwibber executable: /usr/bin/gwibber-service kernel: 2.6.38.2-9.fc15.i686 package: gwibber-1:2.91.92-2.fc15 reason: storage.py:44:setup_table:OperationalError: table messages already exists release: Fedora release 15 (Lovelock) time: 1303252130 uid: 500 backtrace ----- storage.py:44:setup_table:OperationalError: table messages already exists Traceback (most recent call last): File "/usr/bin/gwibber-service", line 80, in <module> dispatcher = dispatcher.Dispatcher(loop) File "/usr/lib/python2.7/site-packages/gwibber/microblog/dispatcher.py", line 254, in __init__ self.messages = storage.MessageManager(self.db) File "/usr/lib/python2.7/site-packages/gwibber/microblog/storage.py", line 39, in __init__ self.setup_table() File "/usr/lib/python2.7/site-packages/gwibber/microblog/storage.py", line 44, in setup_table self.db.execute("CREATE TABLE messages (%s)" % schema) OperationalError: table messages already exists Local variables in innermost frame: self: <gwibber.microblog.storage.MessageManager at /com/gwibber/Messages at 0x87582ac> schema: 'rowid integer primary key autoincrement,\n id text,\n mid text,\n account text,\n service text,\n operation text,\n transient text,\n stream text,\n time integer,\n text text,\n from_me integer,\n to_me integer,\n sender text,\n recipient text,\n data text\n ' How to reproduce ----- 1. Started Gwibber after fresh install. 2. Quitted the App after leaving everything untouched. 3.