Description of problem: Using fedora 12 i386 since update of beginning of March, Yum is broken #yum update There was a problem importing one of the Python modules required to run yum. The error leading to this problem was: /lib/libcom_err.so.2: invalid ELF header Please install a package which provides this module, or verify that the module is installed correctly. It's possible that the above module doesn't match the current version of Python, which is: 2.6.2 (r262:71600, Aug 21 2009, 12:22:21) [GCC 4.4.1 20090818 (Red Hat 4.4.1-6)] If you cannot solve this problem yourself, please go to the yum faq at: http://wiki.linux.duke.edu/YumFaq [root@pluto ~]# rpm -qf /lib/libcom_err.so.2 libcom_err-1.41.9-7.fc12.i686 ls -l /lib/libcom_err.so.2 lrwxrwxrwx. 1 root root 17 2010-03-07 00:47 /lib/libcom_err.so.2 -> libcom_err.so.2.1 [root@pluto ~]# ls -l /lib/libcom_err.so.2.1 -rwxr-xr-x. 1 root root 11648 2010-02-07 23:20 /lib/libcom_err.so.2.1 rpm -qi yum Name : yum Relocations: (not relocatable) Version : 3.2.25 Vendor: Fedora Project Release : 1.fc12 Build Date: Fri 16 Oct 2009 10:44:46 PM CEST Install Date: Sat 21 Nov 2009 09:21:16 PM CET Build Host: x86-5.fedora.phx.redhat.com Group : System Environment/Base Source RPM: yum-3.2.25-1.fc12.src.rpm Size : 3529047 License: GPLv2+ Signature : RSA/8, Sat 17 Oct 2009 05:41:23 AM CEST, Key ID 9d1cc34857bbccba Packager : Fedora Project URL : http://yum.baseurl.org/ Summary : RPM installer/updater Description : Yum is a utility that can check for and automatically download and install updated RPM packages. Dependencies are obtained and downloaded automatically prompting the user as necessary. How reproducible: Always Expected results: functional yum Any idea why yum is broken ??? Do I have good versions ?
(In reply to comment #0) > /lib/libcom_err.so.2: invalid ELF header [...] > [root@pluto ~]# rpm -qf /lib/libcom_err.so.2 > libcom_err-1.41.9-7.fc12.i686 > > > ls -l /lib/libcom_err.so.2 > lrwxrwxrwx. 1 root root 17 2010-03-07 00:47 /lib/libcom_err.so.2 -> > libcom_err.so.2.1 > [root@pluto ~]# ls -l /lib/libcom_err.so.2.1 > -rwxr-xr-x. 1 root root 11648 2010-02-07 23:20 /lib/libcom_err.so.2.1 The libcomm_err version is as expected and the file length is correct too. Its contents may be damaged though. Have you tried "rpm -Vf /lib/libcom_err.so.2.1" ? Does "file /lib/libcom_err.so.2.1" recognize it as an ELF shared object? Does "ldd /lib/libcom_err.so.2.1" produce reasonable-looking output? Or even better, "rpm -Va" to check the contents of all packages. Did you have any unusual events during the unlucky update? A power failure or a system crash? Do you have logs from that time (there should be files /var/log/yum.log*)?
same error with Fedora 13 : /lib/libcom_err.so.2: invalid ELF header symptom : all kind of problems (sshd not working, ... firefox crashing at stop, ....) rebooting "solve" the problem. I had this problem after a hibernate event (ie suspend to disk) (hardware is acer aspire one) it's not reproductible as hibernate usually work well.
All-around system breakage after resuming from hibernation must be a kernel problem. Did any logs after the failed resume make it to /var/log/messages ?
transferring over to the kernel
Created attachment 423046 [details] messages file messages file on Jun 10 17:35:53, I unplunged network then power to move the netbook (without suspend but unplunging power seems to activate suspend to ram) then I plugged a usb key and did some copy. Then I did nothing and as power was unplunged (battery was still ok, can last 2H), the system suspended on Jun 10 18:45:44 , I had a completely unsuable system (I had to power down, X was respawning, console were non functional) I restarted on Jun 10 18:45:44 and the system didn't finished to boot On the second boot it reworked
reported abrt crash as : same time as crash above bug 602839 bug 602843 bug 602845 a little older probably related bug 602877
same suspend pb: 2 more abrt : 603550 and 603552
If a kernel bug causes memory corruption after hibernation, it's not useful to file bugs against all userspace components that break afterwards. I'm going to close them as duplicates of this one. Could you attach the output of "lspci -vvvnn"? Bug 551570 might be related.
*** Bug 602839 has been marked as a duplicate of this bug. ***
*** Bug 602843 has been marked as a duplicate of this bug. ***
*** Bug 602845 has been marked as a duplicate of this bug. ***
*** Bug 602877 has been marked as a duplicate of this bug. ***
*** Bug 603550 has been marked as a duplicate of this bug. ***
*** Bug 603552 has been marked as a duplicate of this bug. ***
http://www.smolts.org/client/show/pub_7441b11b-0284-4d52-8467-3f98e3083ac5
Created attachment 423976 [details] result of lspci -vvvnn Acer Aspire One
Recently a memory corruption bug in hibernation was fixed in the upstream kernel. It might explain bugs like this one. commit 966cca029f739716fbcc8068b8c6dfe381f86fc3 Author: KAMEZAWA Hiroyuki <kamezawa.hiroyu.com> Date: Mon Aug 9 17:20:09 2010 -0700 mm: fix corruption of hibernation caused by reusing swap during image saving The patch is in 2.6.32.19, 2.6.34.4, 2.6.35.2 too.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.