Description of problem: The package updater threw an exception and couldn't be restarted without reboot, claiming another application was accessing the software database. The exception summary was: TBccefa5c9 yumRepo.py:426:__get:RepoError: failure: repodata/updateinfo.xml.gz from updates: [Errno 256] No more mirrors to try. Version-Release number of selected component (if applicable): Name : pirut Relocations: (not relocatable) Version : 1.2.8 Vendor: Red Hat, Inc. Release : 1.fc6 Build Date: Fri 10 Nov 2006 05:16:51 How reproducible: software update Steps to Reproduce: 1. Select "View Updates..." from the notification area. 2. Select "Apply Updates" from the software updater. Actual results: Exception Expected results: Software update Additional info: The exception indicates a problem with mirror servers. I couldn't find any configuration for pirut that selects a preferred mirror server but just in case it does - I used ftp://ftp.uni-koeln.de/redhat/linux/6.0/en/os/i386/ or ftp://ftp.stw-bonn.de/pub/fedora/linux/core/6/i386/ to install the system.
Created attachment 148659 [details] Exception dump
Created attachment 148671 [details] Crash Dump from Exception I had the same exception occur and have attached the crash dump I received. When the Updates Available message pops up it indicates there are 4 updates available. _Steps_to_Reproduce_ 1) Click on View Updates 2) Enter Root Password 3) App sits for about 4-5 minutes at Retrieving update information and then produces the exception. I also tried running the Software Updater separately from the menu with the same results. If I run yum update at the command line it shows 6 updates available (see below). It looks like I could run this through to completion, but wanted to wait and report the exception. Updating: libswt3-gtk2 i386 1:3.2.2-1.fc6 updates 3.4 M pam i386 0.99.6.2-3.16.fc6 updates 924 k pam-devel i386 0.99.6.2-3.16.fc6 updates 187 k slang i386 2.0.7-1.fc6 updates 328 k slang-devel i386 2.0.7-1.fc6 updates 539 k slrn i386 0.9.8.1pl1-2.fc6 updates 806 k
*** This bug has been marked as a duplicate of 229663 ***