Description of problem: I used yumex to update my F12 today. In the list it showed an update for kernel-2.6.31.6-145.fc12.x86_64 It all seemed to go OK, but when I restated my computer it spit up an error and wouldn't boot" "Could not load /lib/modules/2.6.31.6-145.f12.x86_64/modules.dep: No such file or directory" Luckily the old kernel still works. Along with the new Kernel, there was an update to ABRT, after booting back to the old Kernel ABRT isn't working. A panel applet kindly advises abrt is not running. Version-Release number of selected component (if applicable): kernel 2.6.31.6-145.f12.x86_64 How reproducible: Every boot with this kernel Steps to Reproduce: 1.Boot to the new kernel 2. 3. Actual results: Can not boot to the new kernel. Expected results: New kernel booted. Additional info: I do have the disk encryption set, could this be related to that? From the abrt install using yumex: 17:01:50 : YUM: Running rpm_check_debug 17:01:51 : YUM: --> Populating transaction set with selected packages. Please wait. 17:01:51 : YUM: ---> Package abrt.x86_64 0:1.0.0-1.fc12 set to be updated 17:01:53 : YUM: /var/tmp/rpm-tmp.OD7Ywo: line 1: /usr/sbin/groupadd: Permission denied 17:01:53 : YUM: Error in PREIN scriptlet in rpm package abrt-1.0.0-1.fc12.x86_64 17:01:53 : YUM: RPM Scriptlet: error: %pre(abrt-1.0.0-1.fc12.x86_64) scriptlet failed, exit status 126 17:01:53 : YUM: error: install: %pre scriptlet failed (2), skipping abrt-1.0.0-1.fc12 17:01:53 : YUM: abrt-0.0.11-2.fc12.x86_64 was supposed to be removed but is not! 17:01:54 : Transaction completed successfully
I have the same problem with kernel-2.6.31.6-145.fc12.i686.PAE. It was broken on reboot with the same missing modules.dep error. I am NOT using disk encryption. I initially had the same problem with abrt, but was able to run 'yum update' to install the new abrt (yumex failed for me too on the abrt update).
I have the same problem, kernel 2.6.31.6-145.f12.x86_64, nvidia gforce 9400. Updated abrt but still crashes.
I was able to get the new kernel running by removing and reinstalling it: # yum erase kernel-PAE-2.6.31.6-145.fc12.i686 # yum update However, there were still a couple of warnings in the output from the update: ---- Running Transaction Installing : kernel-PAE-2.6.31.6-145.fc12.i686 1/1 W: Possible missing firmware aic94xx-seq.fw for module aic94xx.ko W: Possible missing firmware ql8100_fw.bin for module qla2xxx.ko Running DKMS auto installation service for kernel 2.6.31.6-145.fc12.i686.PAE . Installed: kernel-PAE.i686 0:2.6.31.6-145.fc12 Complete! ----
The same as #3, it seems to be something related to yumex. http://forums.fedoraforum.org/showthread.php?t=235453
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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
I was unable to use either yum or yumex to install any subsequent updates. So I successfully performed a backup and performed a clean re-install of Fedora 12. I suspect that as part of that installation's updates the problem with yumex was fixed. I had no further problems. I subsequently installed a clean version of Fedora 13 a few days after its release, so I have no further experience with Fedora 12. As far as I am concerned, this bug can be CLOSED. I have not experienced the problem on Fedora 13.
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.