Bug 611046 - [abrt] crash in yum-utils-1.1.26-1.fc12: sqlitesack.py:55:newFunc:RepoError: database disk image is malformed
[abrt] crash in yum-utils-1.1.26-1.fc12: sqlitesack.py:55:newFunc:RepoError: ...
Product: Fedora
Classification: Fedora
Component: yum-utils (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Seth Vidal
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-07-03 06:10 EDT by colinmw
Modified: 2014-01-21 18:15 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-07-09 13:45:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (2.10 KB, text/plain)
2010-07-03 06:10 EDT, colinmw
no flags Details

  None (edit)
Description colinmw 2010-07-03 06:10:14 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/debuginfo-install abrt --skip-broken
component: yum-utils
executable: /usr/bin/debuginfo-install
package: yum-utils-1.1.26-1.fc12
reason: sqlitesack.py:55:newFunc:RepoError: database disk image is malformed
release: Fedora release 12 (Constantine)
Comment 1 colinmw 2010-07-03 06:10:17 EDT
Created attachment 429238 [details]
File: backtrace
Comment 2 seth vidal 2010-07-06 12:44:45 EDT
The error causing the traceback has something to do with some pretty broken sqlite dbs you have - this is causing the other issues you've posted by abrt, too.

however, yum[utils] should not be tracing back in this way and I've committed code upstream to properly catch and report this error.

is there any chance your /var/cache path is mounted on an odd filesystem and/or network-mounted filesystem?
Comment 3 colinmw 2010-07-07 06:02:16 EDT
All filesystems are ext4 format on localhost, configured through lvm.
Comment 4 seth vidal 2010-07-09 13:45:19 EDT
okay - well we'll exit more gracefully if this error occurs. Given all the rest of the problems you seem to be having on your system I'm not inclined to pursue this further than catching the traceback.


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