Ubuntu
gwibber package

gwibber-service crashed with DatabaseError in handle_max_id(): database disk image is malformed

Bug #825440 reported by Evertjan Garretsen
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

after distribution upgrade to 11.10

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gwibber-service 3.1.4.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-8.10-generic-pae 3.0.1
Uname: Linux 3.0.0-8-generic-pae i686
NonfreeKernelModules: fglrx
Architecture: i386
CheckboxSubmission: 22b3432f25ce9cc1abec6b97b5b7c5b8
CheckboxSystem: b8f3ec504801f13fc208edb5c785b099
Date: Fri Aug 12 21:31:24 2011
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 PATH=(custom, no user)
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/gwibber-service']
SourcePackage: gwibber
Title: gwibber-service crashed with DatabaseError in handle_max_id(): database disk image is malformed
UpgradeStatus: Upgraded to oneiric on 2011-08-12 (0 days ago)
UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare www-data

Revision history for this message
Evertjan Garretsen (egarretsen) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #820921, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-duplicate-check
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gwibber (Ubuntu):
status: New → Confirmed
Revision history for this message
Guillaume Duval (guillaume-duval) wrote :

I have the same problem but i can't access to the bug #820921 ...

Revision history for this message
Alan Pope 🍺🐧🐱 🦄 (popey) wrote :

Have you tried following this guide for clearing out the gwibber database?

http://askubuntu.com/questions/90506/how-to-delete-gwibber-history

Revision history for this message
Steve Mayne (steve-mayne) wrote :

Unfortunately the database becomes so corrupt that editing the records within the sqlite database (~/.config/gwibber/gwibber.sqlite) using either sqlitebrowser or sqliteman does not work. Sqliteman returns "database disk image is malformed" when attempting to delete records from the messages table.

Removing the database file and restarting the qwibber-service does not work either (as it won't recreate an absent database - the crash report just changes to 'file not found').

The solution I've used is to remove the gwibber database file, then reinstall gwibber-service using apt. The installation of the package creates a new (empty) gwibber database. You will lose your message history and account setup by doing this, however.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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