Gwibber

gwibber-service crashed with OperationalError in maintenance(): database is locked

Bug #741035 reported by Chen Liang on 2011-03-23

402

This bug affects 55 people

Affects		Status	Importance	Assigned to	Milestone
	Gwibber	Confirmed	Undecided	Unassigned
	gwibber (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

Binary package hint: gwibber

Gwibber crashed on start up.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gwibber-service 2.91.92-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.38-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Wed Mar 23 14:40:57 2011
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
SHELL=/bin/bash
LANGUAGE=en_IE:en
LANG=en_IE.UTF-8
PythonArgs: ['/usr/bin/gwibber-service']
SourcePackage: gwibber
Title: gwibber-service crashed with OperationalError in maintenance(): database is locked
UpgradeStatus: Upgraded to natty on 2011-03-20 (3 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Chen Liang (chenliang) wrote on 2011-03-23:

Dependencies.txt Edit (3.4 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (35.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (781 bytes, text/plain; charset="utf-8")
Traceback.txt Edit (386 bytes, text/plain; charset="utf-8")
gwibber.log.txt Edit (150.3 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2011-03-23

tags:

removed: need-duplicate-check

Victor Vargas (kamus) on 2011-03-25

visibility:

private → public

Victor Vargas (kamus) on 2011-03-25

Changed in gwibber (Ubuntu):
importance:	Undecided → Medium

Revision history for this message

Victor Vargas (kamus) wrote on 2011-03-25:

Please can you stop to using gwibber and then run this command in a terminal: "echo -e "delete from messages;\nvacuum;" | sqlite3 ~/.config/gwibber/gwibber.sqlite".. after that try to open gwibber again.

Changed in gwibber (Ubuntu):
status:	New → Incomplete

Revision history for this message

Chen Liang (chenliang) wrote on 2011-04-01:

I tried the instruction, however, echo -e "delete from messages;\nvacuum;" | sqlite3 ~/.config/gwibber/gwibber.sqlite" seems to be incomplete.

The terminal returns ">", and I have to kill it with "ctrl+c"

Revision history for this message

Victor Vargas (kamus) wrote on 2011-04-08:

cliang, you must run that command without comas (""), at least for me did the trick

Revision history for this message

Chen Liang (chenliang) wrote on 2011-04-08: Re: [Bug 741035] Re: gwibber-service crashed with OperationalError in maintenance(): database is locked

I must say, I haven't had the same problem since filling the bug report.
It's possible that the bug was fixed.

Regards

On 8 April 2011 19:19, Kamus <email address hidden> wrote:

> cliang, you must run that command without comas (""), at least for me
> did the trick
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/741035
>
> Title:
> gwibber-service crashed with OperationalError in maintenance():
> database is locked
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/741035/+subscribe
>

--
Chen Liang
Mr
*Dublin Institute of Technology*
34 New Bride Street
Dublin 8
Dublin
Ireland
Email: <email address hidden>
http://postgrad.comp.dit.ie/~chen.liang/

Sent from Ubuntu

Revision history for this message

Launchpad Janitor (janitor) wrote on 2011-06-08:

[Expired for gwibber (Ubuntu) because there has been no activity for 60 days.]

Changed in gwibber (Ubuntu):
status:	Incomplete → Expired

Apport retracing service (apport) on 2011-09-27

tags:

added: bugpattern-needed

Revision history for this message

Vladimir Scherbaev (zemik) wrote on 2012-01-21:

affect me on 12.04

Changed in gwibber (Ubuntu):
status:	Expired → Confirmed

Brian Murray (brian-murray) on 2012-02-01

tags:	removed: bugpattern-needed
tags:	added: bugpattern-written

Ken VanDine (ken-vandine) on 2012-02-10

tags:

added: sqlite

Revision history for this message

Tim (swearingen-tim) wrote on 2012-03-19:

crashed on update.

Revision history for this message

JG (jdogzz-g5) wrote on 2012-04-04:

Happens at pretty much every boot, and it's often linked to the problem with multiple instances being opened.

Revision history for this message

Ted Gould (ted) wrote on 2012-04-17:

#10

For me this was because Gwibber had a SQLLite file with a journal. By deleting ~/.config/gwibber/gwibber.sqlite-journal I was able to stop getting this bug. Gwibber needs to learn how to apply that and recover though :-)

Brian Murray (brian-murray) on 2012-05-17

tags:

added: precise

Revision history for this message

David Gomes (davidgomes) wrote on 2012-10-28:

#11

Just booted Ubuntu 12.10 for the first time on a USB Disk, I was just starting my system, opening the Wireless indicator and everything crashed with this bug.

Ursula Junque (ursinha) on 2013-01-28

tags:

added: raring

Revision history for this message

Sasa Paporovic (melchiaros) wrote on 2013-02-01:

#12

This crasher affects 52 people starting from gwibber version gwibber-service 2.91.92-0ubuntu1

up to gwibber 3.6.0 which is actual and in Ubuntu 13.04 developer branch(called raring).

In respect to this I set the status of the upstream report to confirmed.

Changed in gwibber:
status:	New → Confirmed

Revision history for this message

psamuel (persaudsamuel) wrote on 2013-03-09:

#13

Alguien tiene alguna idea de este error?

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.