Bug 744387

Summary:	after installation yum database disk image is malformed
Product:	[Fedora] Fedora	Reporter:	Alexander van Loon <a.vanloon>
Component:	yum	Assignee:	Seth Vidal <skvidal>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	16	CC:	ffesti, james.antill, maxamillion, pmatilai, tla, zpavlas
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-11-27 12:42:27 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 Alexander van Loon 2011-10-08 08:29:59 UTC

I just installed the Fedora 16 beta on my laptop. I used the GNOME iso file. Everything went fine during the installation. When I logged in after the installation I decided the first thing I would do is install a certain package and check for updates as well. Finding a package in add/remove software didn't work, it just kept searching forever. Then I opened software update and figured out the problem: when I hit 'check now' I got an error message reporting there was a problem connecting to a software source, giving the detailed error message: 'database disk image is malformed'.

This forum post [1] provided a workaround in the second post which did not work for me. May be related to bug #642913, but that bug was apparently triggered in Anaconda while mine occured when I was logged in to GNOME. Because the other bug also affected F14 I thought it was better to file a new bug.

[1] http://forums.fedoraforum.org/showthread.php?t=260195

Comment 1 Alexander van Loon 2011-10-08 08:37:57 UTC

Just a while ago I deleted all the content of /var/lib/yum and gave the command 'yum clean all' which fixed it for me.

Comment 2 Alexander van Loon 2011-11-27 12:42:27 UTC

After doing a fresh installation of Fedora 16 this no longer happened. Closing this.