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.