Bug 702992

Summary: [abrt] gwibber-3.0.0.1-1.fc15: storage.py:65:maintenance:OperationalError: database is locked
Product: [Fedora] Fedora Reporter: Kiril Aleksandrov <kiril.aleksandrov.89>
Component: gwibberAssignee: Tom "spot" Callaway <tcallawa>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: tcallawa
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:5ce19bdc44d574e229f00d2bf155ff529d9037cd
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:56:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Kiril Aleksandrov 2011-05-08 22:10:19 UTC
abrt version: 2.0.1
architecture:   x86_64
cmdline:        /usr/bin/python /usr/bin/gwibber-service
component:      gwibber
executable:     /usr/bin/gwibber-service
kernel:         2.6.38.5-24.fc15.x86_64
os_release:     Fedora release 15 (Lovelock)
package:        gwibber-3.0.0.1-1.fc15
reason:         storage.py:65:maintenance:OperationalError: database is locked
time:           Mon May  9 00:50:11 2011
uid:            500
username:       flyingbear

backtrace:
:storage.py:65:maintenance:OperationalError: database is locked
:
:Traceback (most recent call last):
:  File "/usr/lib/python2.7/site-packages/gwibber/microblog/dispatcher.py", line 356, in do_maintenance
:    self.messages.maintenance()
:  File "/usr/lib/python2.7/site-packages/gwibber/microblog/storage.py", line 65, in maintenance
:    self.db.execute("VACUUM")
:OperationalError: database is locked
:
:Local variables in innermost frame:
:count: 1482
:acct: (u'deeb735268d411e082b2001846014d02',)
:self: <gwibber.microblog.storage.MessageManager at /com/gwibber/Messages at 0x2e8a450>
:accounts: [(u'deeb735268d411e082b2001846014d02',)]

Comment 1 Fedora Update System 2011-05-12 19:16:48 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 2 Fedora Update System 2011-05-12 19:17:35 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 3 Fedora Update System 2011-05-12 19:18:19 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 4 Fedora Update System 2011-05-13 22:55:56 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 5 Fedora Update System 2011-05-19 04:56:08 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 6 Fedora Update System 2011-05-25 02:26:04 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 7 Fedora Update System 2011-05-25 03:26:25 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.