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

Bug #1054016 reported by Javier Rivera on 2012-09-21
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
Medium
Unassigned

Bug Description

I was just opening the session, did nothing related to gwibber.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gwibber-service 3.5.90-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
Date: Fri Sep 21 14:26:52 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=gl_ES.UTF-8
PythonArgs: ['/usr/bin/gwibber-service']
SourcePackage: gwibber
Title: gwibber-service crashed with OperationalError in __init__(): database is locked
UpgradeStatus: Upgraded to quantal on 2012-08-30 (22 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

Javier Rivera (javier-isotecsl) wrote :
visibility: private → public
tags: removed: need-duplicate-check
Changed in gwibber (Ubuntu):
importance: Undecided → Medium
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gwibber (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers