Bug 707854 - anaconda failed to upgrade kdm, kernel and maybe other packages
Summary: anaconda failed to upgrade kdm, kernel and maybe other packages
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-26 07:36 UTC by Sebastian Krämer
Modified: 2013-01-10 06:37 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-19 22:06:59 UTC
Type: ---


Attachments (Terms of Use)
/var/log/anaconda/anaconda.log (10.26 KB, text/plain)
2011-05-28 04:50 UTC, Sebastian Krämer
no flags Details
/root/upgrade.log (62.74 KB, text/plain)
2011-05-28 04:52 UTC, Sebastian Krämer
no flags Details

Description Sebastian Krämer 2011-05-26 07:36:17 UTC
Description of problem:
I did a F15 install from the official DVD. In F14, I used slim as login manager. For whatever reason in F15 the startup sequence fell back to using kdm which was also installed. The screen stayed black. Further examination showed that kdm was unable to load some libraries (kdm_greet, I think). Turned out that it was still the f14 version. After an upgrade from kdm-4.6.3-5.fc14.x64_64 to the same kdm version (but f15) the startup went through.
I only later noticed that some of the first-boot-F15-after-installation issues came from an old kernel. It was after the upgrade that I installed a proper f15 kernel with 'yum upgrade'. So kdm wasn't the only package that was left out!

Version-Release number of selected component (if applicable):
kdm-4.6.3-5.fc14.x64_64

How reproducible:
Now idea how to produce this now after installation..

I still hope that this information can be useful in some way. Missing upgrades caused quite some trouble and took me some time to analyze and fix. For a less experienced user, the upgrade could have been a complete failure resulting in a fresh install (something I considered at some point..). Talking about user experience, this is really something that should taken into focus.

Comment 1 Sebastian Krämer 2011-05-26 07:38:39 UTC
I imagine there are other people that might have the same problem (since I upgraded from F14 with latest updates, and a DVD upgrade based on that should be a standard case). Adding CommonBugs so this might be found easier and in case people suffer from it, makes it to the "common bugs" wiki page..

Comment 2 Chris Lumens 2011-05-27 21:05:15 UTC
Can you grab /root/upgrade.log, /root/install.log, and /var/log/anaconda.log from the installed system to this bug report?  Thanks.

Also, do you have multilib (i686) packages installed as well?

Comment 3 Sebastian Krämer 2011-05-28 04:50:56 UTC
Created attachment 501435 [details]
/var/log/anaconda/anaconda.log

(it's newer than /var/log/anaconda.log, which is from the preupgrade install before)

Comment 4 Sebastian Krämer 2011-05-28 04:52:45 UTC
Created attachment 501436 [details]
/root/upgrade.log

Here is upgrade.log.
Unfurtunately, it appears, I don't have /root/install.log any more..

Comment 5 Sebastian Krämer 2011-05-28 04:55:54 UTC
(In reply to comment #2)
> Can you grab /root/upgrade.log, /root/install.log, and /var/log/anaconda.log
> from the installed system to this bug report?  Thanks.

Sure. Thanks for picking this report up so quickly.

> Also, do you have multilib (i686) packages installed as well?

No, I'm pretty sure there aren't any i686 packages.

Comment 6 Adam Williamson 2011-11-08 06:32:06 UTC

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 7 Jesse Keating 2012-07-19 22:06:59 UTC
Was it possible that your F14 was updated after F15 was released, so that you had packages that were rpm newer in your F14 install than what was on the f15 media?  That's what looks like is happening here, and not much we can do about that when upgrading to DVD.

Upgrade is going to be re-written post F17 so closing this bug.

Comment 8 Sebastian Krämer 2012-07-20 06:31:18 UTC
Hm, I guess this is possible.
Thanks for a late explanation :)


Note You need to log in before you can comment on or make changes to this bug.