Bug 699139 - [abrt] gwibber-2.91.92-2.fc15: storage.py:62:maintenance:OperationalError: database is locked
Summary: [abrt] gwibber-2.91.92-2.fc15: storage.py:62:maintenance:OperationalError: da...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gwibber
Version: 15
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2b8a5317bc1de7c691965e0e4b9...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-23 13:39 UTC by Juanjo Marin
Modified: 2011-05-25 03:27 UTC (History)
1 user (show)

Fixed In Version: gwibber-3.0.0.1-2.fc13
Clone Of:
Environment:
Last Closed: 2011-05-19 04:57:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (697 bytes, text/plain)
2011-04-23 13:39 UTC, Juanjo Marin
no flags Details

Description Juanjo Marin 2011-04-23 13:39:07 UTC
abrt version: 2.0.1
uid: 500
cmdline: /usr/bin/python /usr/bin/gwibber-service
executable: /usr/bin/gwibber-service
component: gwibber
architecture: i686
kernel: 2.6.38.2-9.fc15.i686.PAE
reason: storage.py:62:maintenance:OperationalError: database is locked
package: gwibber-2.91.92-2.fc15
username: jjmarin
os_release: Fedora release 15 (Lovelock)
time: 1303565513

backtrace
-----
storage.py:62:maintenance:OperationalError: database is locked

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/gwibber/microblog/dispatcher.py", line 309, in do_maintenance
    self.messages.maintenance()
  File "/usr/lib/python2.7/site-packages/gwibber/microblog/storage.py", line 62, in maintenance
    self.db.execute("VACUUM")
OperationalError: database is locked

Local variables in innermost frame:
acct: (u'b6551ef6d17711df8a3c0013e8bfe705',)
self: <gwibber.microblog.storage.MessageManager at /com/gwibber/Messages at 0x93b0dec>
accounts: [(u'2551f90ad17811dfae2c0013e8bfe705',), (u'9c43b1eed17711df866c0013e8bfe705',), (u'b6551ef6d17711df8a3c0013e8bfe705',)]

Comment 1 Juanjo Marin 2011-04-23 13:39:10 UTC
Created attachment 494430 [details]
File: backtrace

Comment 2 Fedora Update System 2011-05-12 19:16:58 UTC
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

Comment 3 Fedora Update System 2011-05-12 19:17:44 UTC
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

Comment 4 Fedora Update System 2011-05-12 19:18:28 UTC
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

Comment 5 Fedora Update System 2011-05-13 22:56:06 UTC
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).

Comment 6 Fedora Update System 2011-05-19 04:56:17 UTC
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.

Comment 7 Fedora Update System 2011-05-25 02:26:16 UTC
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.

Comment 8 Fedora Update System 2011-05-25 03:26:35 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.