Bug 535985 - Kernel update errased old entry, but made no new one.
Summary: Kernel update errased old entry, but made no new one.
Status: RESOLVED DUPLICATE of bug 533766
Alias: None
Product: openSUSE 11.2
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Milestone 6
Hardware: 64bit SUSE Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Josef Reidinger
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-01 16:08 UTC by Robby Verberne
Modified: 2009-09-03 06:28 UTC (History)
1 user (show)

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
y2logs (6.09 MB, application/x-gzip)
2009-09-02 07:37 UTC, Kyrill Detinov 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Robby Verberne 2009-09-01 16:08:48 UTC 
I do not know if i have selected the right component.

Again there is no new entry, while the old one is gone.
Other entries were untouched.
Comment 1 Robby Verberne 2009-09-01 16:09:38 UTC 
Sorry, forgot to say entries in the bootloader.
Comment 2 Kyrill Detinov 2009-09-02 07:37:09 UTC 
Created attachment 316330 [details]
y2logs

y2logs after kernel upgrade
Comment 3 Kyrill Detinov 2009-09-02 07:39:23 UTC 
Upgrading kernel to 2.6.31-rc7-4-desktop.

After reboot I got openSUSE 11.2 missing from menu.lst
Comment 4 Kyrill Detinov 2009-09-02 19:44:11 UTC 
Well, the bug is similar to bug https://bugzilla.novell.com/show_bug.cgi?id=524759. I have got the same configuratin.

I've reported dualboot problem. It's critical or not? I can't boot into openSUSE 11.2 -- manually fixing menu.lst
Comment 5 Josef Reidinger 2009-09-03 06:28:25 UTC 
hi, you reach same bug 533766, problem is that for some reason is changed behavior of kernel base package and it cause bad install order, so kernel is added and immediatelly after it is removed.

*** This bug has been marked as a duplicate of bug 533766 ***