Description of problem: After the upgrade no Fedora 18 kernels were installed in the system. Version-Release number of selected component (if applicable): fedup-0.7.2-1.fc17.noarch How reproducible: Perform upgrade from mounted DVD media Steps to Reproduce: 1. Run: fedup --device /media/Fedora\ 18\ i386 2. 3. Actual results: No Fedora 18 kernel is installed Expected results: Fedora 18 kernel should have been installed Additional info: The kernels installed on the system: kernel-PAE-3.3.5-2.fc16.i686 kernel-PAE-3.3.6-3.fc16.i686 kernel-PAE-3.6.11-5.fc17.i686 KDE logon errors: startkde: Starting up... klauncher: error while loading shared libraries: libudev.so.0: cannot open shared object file: No such file or directory kdeinit4: Communication error with launcher. Exiting! kdeinit4_wrapper: Warning: connect(/home/panos/.kde/socket-virtual/kdeinit4__0) failed: : Connection refused ksmserver: error while loading shared libraries: libudev.so.0: cannot open shared object file: No such file or directory startkde: Shutting down... kdeinit4_wrapper: Warning: connect(/home/panos/.kde/socket-virtual/kdeinit4__0) failed: : Connection refused Error: Can not contact kdeinit4! startkde: Running shutdown scripts... startkde: Done. Possibly all of them are solved with "yum distro-sync". I haven't issued that yet. I will wait for your investigation.
The kernel issue might be related to Bug 820351
The KDE issue is explained in Bug 888085 and Bug 892061. Only the kernel issue remains a mystery, as there is no way that F18 had a lower version number than F17 kernel. There must be some kind of exception.
Created attachment 687289 [details] Log file /root/upgrade.log
Created attachment 687290 [details] Log file /root/upgrade.log.syslog
Oops sorry! Ignore the attached logs. They are old and from previous upgrade. It seems that fedup leaves no logs after the job is done.
(In reply to comment #5) > Oops sorry! Ignore the attached logs. They are old and from previous > upgrade. It seems that fedup leaves no logs after the job is done. It does, actually. Try /var/log/upgrade.log. (In reply to comment #2) > Only the kernel issue remains a mystery, as there is no way that F18 had a > lower version number than F17 kernel. There must be some kind of exception. Actually, that's also incorrect. The F17 kernel has been newer than the F18 kernel at certain points. That's bug 904112. *** This bug has been marked as a duplicate of bug 904112 ***
I also checked /var/log and there was nothing with newer date there. I'll check again :) My system had 3.6 F17 kernel before the upgrade and it was out in the updates 3.7 for F18. That's very newer in the minor number than previous release kernel and I'm not sure it is related to bug 904112. It simply doesn't make any sense. I have just upgraded my desktop and after logging in, no F18 kernel and when checking updates there is one there: # yum check-update kernel.x86_64 3.7.4-204.fc18 updates kernel-devel.x86_64 3.7.4-204.fc18 updates kernel-headers.x86_64 3.7.4-204.fc18 updates # rpm -q kernel kernel-3.6.10-2.fc17.x86_64 kernel-3.6.11-5.fc17.x86_64 kernel-3.7.3-101.fc17.x86_64 why it asks for this update and it was not performed few minutes before that I have issued the fedup command? It is 3.7.4-204 > 3.7.3-101, isn't it? My check for updates should have been empty after the upgrade.
From the /var/log/upgrade.log the proof that fedup didn't get the upgraded F18 kernel at all and made nvidia module to complain: Jan 26 18:45:51 charon upgrade[947]: checking RPM transaction... Jan 26 18:45:53 charon upgrade[947]: non-fatal problems with RPM transaction: Jan 26 18:45:53 charon upgrade[947]: kernel-uname-r = 3.7.4-204.fc18.x86_64 is needed by kmod-nvidia-3.7.4-204.fc18.x86_64-1:304.64-2.fc18.4.x86_64
Created attachment 688759 [details] Log file /var/log/upgrade.log Indeed, the log file found in /var/log.