[Bug 990701] New: Leap with KOTD repo doesnt upgrade booted kernel to 4.7 rtm from rc2 (did so for previous KOTD rc1, rc2,....) - openSUSE Bugs - openSUSE Mailing Lists

newer
[Bug 1002865] New: Cannot login as...

[Bug 990701] New: Leap with KOTD repo doesnt upgrade booted kernel to 4.7 rtm from rc2 (did so for previous KOTD rc1, rc2,....)

older
[Bug 749888] Unable to install on...

bugzilla_noreply＠novell.com

26 Jul 2016 26 Jul '16

16:21

http://bugzilla.opensuse.org/show_bug.cgi?id=990701 Bug ID: 990701 Summary: Leap with KOTD repo doesnt upgrade booted kernel to 4.7 rtm from rc2 (did so for previous KOTD rc1, rc2,....) Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers@forge.provo.novell.com Reporter: abittner@opensuse.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I have the KOTD repo added to a pretty simple plain Leap 42.1 x64 machine. I did add this KOTD for a few months now. It always upgraded the kernels in the past within the KOTD branch. Recently it went from 4.7 rc1 to rc2, then another rc2 release and today zypper ref and zypper lu displayed that there would be a non rc2 (rtm i suppose) for 4.7 kernel. Zypper up installed this kernel but didnt activate this rtm one in the grub2 bootloader and thus didnt switch over after I just rebooted this machine. ---------- kernel-default-4.7.0-1.1.g24f30d5.x86_64 kernel-default-4.7.rc7-2.1.g152f160.x86_64 kernel-firmware-20160503-3.1.noarch ------ 1 | KOTD | KOTD | Yes | (r ) Yes | No | 100 | rpm-md | http://download.opensuse.org/repositories/Kernel:/HEAD/standard --------------- Linux linux 4.7.0-rc7-2.g152f160-default #1 SMP PREEMPT Thu Jul 21 12:38:47 UTC 2016 (152f160) x86_64 x86_64 x86_64 GNU/Linux ---------- There was a zypper and libzypp update just some days ago. I briefly read about some new zypper problems and discussion on the bugs list or somewhere. Maybe this is a bug within current zypper? ----- zypper-aptitude-1.12.44-12.1.noarch snapper-zypp-plugin-0.2.9.1-3.1.noarch libzypp-15.22.2-12.1.x86_64 zypper-1.12.44-12.1.x86_64 PackageKit-backend-zypp-1.0.7-3.5.x86_64 zypper-log-1.12.44-12.1.noarch zypp-plugin-python-0.5-4.2.x86_64 ----- How exactly does zypper replace the currently selected and in use kernel for grub2 config? How can I manually select which kernel package to use for grub2 when there are multiple installed as in this case? what config setting and where and how influences what stuff becomes added or replaced in the grub2 config? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

Attachments:

attachment.htm (text/html — 4.1 KB)

Reply

Sign in to reply online Use email software

Show replies by date

bugzilla_noreply＠novell.com

26 Jul 26 Jul

17:05

New subject: [Bug 990701] Leap with KOTD repo doesnt upgrade booted kernel to 4.7 rtm from rc2 (did so for previous KOTD rc1, rc2,....)

http://bugzilla.opensuse.org/show_bug.cgi?id=990701 http://bugzilla.opensuse.org/show_bug.cgi?id=990701#c1 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |abittner@opensuse.org Component|libzypp |Bootloader Assignee|zypp-maintainers@forge.prov |jsrain@suse.com |o.novell.com | QA Contact|qa-bugs@suse.de |jsrain@suse.com Flags| |needinfo?(abittner@opensuse | |.org) --- Comment #1 from Michael Andres --- (In reply to andreas bittner from comment #0)

How exactly does zypper replace the currently selected and in use kernel for grub2 config?

How can I manually select which kernel package to use for grub2 when there are multiple installed as in this case? what config setting and where and how influences what stuff becomes added or replaced in the grub2 config?

Zypper does not treat the kernel packages special. The kernel packages pre/post install scripts must take care about all this. The kernel scripts usually use perl-Bootloader to adjust the boot menu. I'll assign the bug to the perl-Bootloader maintainer to figure out why the newly installed kernel was not added to the boot menu. @Andreas: Please attach your /var/log/zypp/history file, so we can see exactly which kernel was installed and whether the install scripts wrote out some messages. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

17:06

New subject: [Bug 990701] Leap with KOTD repo doesnt upgrade booted kernel to 4.7 rtm from rc2 (did so for previous KOTD rc1, rc2,....)

http://bugzilla.opensuse.org/show_bug.cgi?id=990701 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jsrain@suse.com |snwint@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

17:10

New subject: [Bug 990701] Leap with KOTD repo doesnt upgrade booted kernel to 4.7 rtm from rc2 (did so for previous KOTD rc1, rc2,....)

http://bugzilla.opensuse.org/show_bug.cgi?id=990701 http://bugzilla.opensuse.org/show_bug.cgi?id=990701#c2 andreas bittner changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(abittner@opensuse | |.org) | --- Comment #2 from andreas bittner --- I have the last few lines of that history file from today: --------------- 2016-07-26 18:08:11|command|root@linux-ang0|'zypper' 'up'| # 2016-07-26 18:08:42 kernel-default-4.7.0-1.1.g24f30d5.x86_64.rpm installed ok # Additional rpm output: # warning: /var/cache/zypp/packages/KOTD/x86_64/kernel-default-4.7.0-1.1.g24f30d5.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 03579c1d: NOKEY # Creating initrd: /boot/initrd-4.7.0-1.g24f30d5-default # Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force --force-drivers "pata_atiixp ahci ata_generic xennet xenblk" /boot/initrd-4.7.0-1.g24f30d5-default 4.7.0-1.g24f30d5-default # *** Including module: bash *** # *** Including module: warpclock *** # *** Including module: i18n *** # *** Including module: ifcfg *** # *** Including module: drm *** # *** Including module: plymouth *** # *** Including module: kernel-modules *** # *** Including module: resume *** # *** Including module: rootfs-block *** # *** Including module: terminfo *** # *** Including module: udev-rules *** # Skipping udev rule: 91-permissions.rules # Skipping udev rule: 80-drivers-modprobe.rules # *** Including module: haveged *** # *** Including module: systemd *** # *** Including module: usrmount *** # *** Including module: base *** # *** Including module: fs-lib *** # *** Including module: shutdown *** # *** Including module: suse *** # *** Including modules done *** # *** Installing kernel module dependencies and firmware *** # *** Installing kernel module dependencies and firmware done *** # *** Resolving executable dependencies *** # *** Resolving executable dependencies done*** # *** Hardlinking files *** # *** Hardlinking files done *** # *** Stripping files *** # *** Stripping files done *** # *** Generating early-microcode cpio image *** # *** Constructing AuthenticAMD.bin **** # *** Store current command line parameters *** # Stored kernel commandline: # rd.driver.pre=pata_atiixp # rd.driver.pre=ahci # rd.driver.pre=ata_generic # rd.driver.pre=xennet # rd.driver.pre=xenblk # resume=UUID=3b29e730-3b40-4eb1-a5ae-b68e4f3edd63 # root=UUID=4a103dea-0699-4fce-a2f5-d456b8da39e0 rootflags=rw,relatime,data=ordered rootfstype=ext4 # *** Creating image file *** # *** Creating image file done *** # Some kernel modules could not be included # This is not necessarily an error: # scsi_dh # swap # Update bootloader... # 2016-07-26 18:08:42|install|kernel-default|4.7.0-1.1.g24f30d5|x86_64||KOTD|3436c6a601882ea753048f067cf43fdab5fb5e6c2a04f451aeabbba0e7eeba09| 2016-07-26 18:08:43|install|chromium-ffmpegsumo|52.0.2743.82-61.1|x86_64||repo-update|5156a704173baf1bca51630a4deb46ddee13a9a43b0942db073f0848a7d29317| 2016-07-26 18:08:44|install|libfbembed2_5|2.5.6.27020-7.1|x86_64||repo-update|1bb419f4f825f7a69e112a2072115c36ee59d0177773f9e6dd499128b2939d46| 2016-07-26 18:09:02|install|chromium|52.0.2743.82-61.1|x86_64||repo-update|fbe4d71109b16bf9f73f9cf7709fa8d2cfb68145721dc3baba1de18a9025049e| 2016-07-26 18:09:02|install|chromium-desktop-kde|52.0.2743.82-61.1|x86_64||repo-update|4d3ed71a6f3596501d1023a953c2cd0ab7f8c998cf14c83023e5854025c8538a| -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

17:14

New subject: [Bug 990701] Leap with KOTD repo doesnt upgrade booted kernel to 4.7 rtm from rc2 (did so for previous KOTD rc1, rc2,....)

http://bugzilla.opensuse.org/show_bug.cgi?id=990701 http://bugzilla.opensuse.org/show_bug.cgi?id=990701#c3 --- Comment #3 from andreas bittner --- I have grepped for "4.7.0" in grub2/grub.cfg and it seems that there are some entries in there even for the rtm kernel version, but this is not what the grub2 graphical screen boots when then first graphical entry there that is selected for default is chosen, or if one waits for the timeout and autocontinuing to boot. ------------ /boot/grub2 # grep "4.7.0" grub.cfg echo 'Loading Linux 4.7.0-rc7-2.g152f160-default ...' linux /boot/vmlinuz-4.7.0-rc7-2.g152f160-default root=UUID=4a103dea-0699-4fce-a2f5-d456b8da39e0 video=1680x1050 resume=/dev/disk/by-id/ata-SAMSUNG_HD321KJ_S0MQJ1KP116340-part1 splash=silent quiet showopts initrd /boot/initrd-4.7.0-rc7-2.g152f160-default menuentry 'openSUSE Leap 42.1, with Linux 4.7.0-rc7-2.g152f160-default' --hotkey=2 --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.7.0-rc7-2.g152f160-default-advanced-4a103dea-0699-4fce-a2f5-d456b8da39e0' { echo 'Loading Linux 4.7.0-rc7-2.g152f160-default ...' linux /boot/vmlinuz-4.7.0-rc7-2.g152f160-default root=UUID=4a103dea-0699-4fce-a2f5-d456b8da39e0 video=1680x1050 resume=/dev/disk/by-id/ata-SAMSUNG_HD321KJ_S0MQJ1KP116340-part1 splash=silent quiet showopts initrd /boot/initrd-4.7.0-rc7-2.g152f160-default menuentry 'openSUSE Leap 42.1, with Linux 4.7.0-1.g24f30d5-default' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.7.0-1.g24f30d5-default-advanced-4a103dea-0699-4fce-a2f5-d456b8da39e0' { echo 'Loading Linux 4.7.0-1.g24f30d5-default ...' linux /boot/vmlinuz-4.7.0-1.g24f30d5-default root=UUID=4a103dea-0699-4fce-a2f5-d456b8da39e0 video=1680x1050 resume=/dev/disk/by-id/ata-SAMSUNG_HD321KJ_S0MQJ1KP116340-part1 splash=silent quiet showopts initrd /boot/initrd-4.7.0-1.g24f30d5-default -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

17:21

New subject: [Bug 990701] Leap with KOTD repo doesnt upgrade booted kernel to 4.7 rtm from rc2 (did so for previous KOTD rc1, rc2,....)

http://bugzilla.opensuse.org/show_bug.cgi?id=990701 http://bugzilla.opensuse.org/show_bug.cgi?id=990701#c4 --- Comment #4 from andreas bittner --- I have found some more, my /etc/default/ -rw-r--r-- 1 root root 1757 Oct 28 2015 grub is from october 2015 and it has GRUB_DEFAULT=saved -------------- # Modified by YaST2. Last modification on Thu Oct 15 20:06:34 CEST 2015 # THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader # For the new kernel it try to figure out old parameters. In case we are not able to recognize it (e.g. change of flavor or strange install order ) it it use as fallback installation parameters from /etc/sysconfig/bootloader # If you change this file, run 'grub2-mkconfig -o /boot/grub2/grub.cfg' afterwards to update # /boot/grub2/grub.cfg. GRUB_DISTRIBUTOR= GRUB_DEFAULT=saved .... .... ---------------- -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

17:22

New subject: [Bug 990701] Leap with KOTD repo doesnt upgrade booted kernel to 4.7 rtm from rc2 (did so for previous KOTD rc1, rc2,....)

http://bugzilla.opensuse.org/show_bug.cgi?id=990701 http://bugzilla.opensuse.org/show_bug.cgi?id=990701#c5 --- Comment #5 from andreas bittner --- and /boot/grub2/ has -rw------- 1 root root 7724 Jul 26 18:08 grub.cfg so that file has been regenerated when the rtm 4.7.0 kernel package came in via zypper -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

28 Jul 28 Jul

12:45

New subject: [Bug 990701] Leap with KOTD repo doesnt upgrade booted kernel to 4.7 rtm from rc2 (did so for previous KOTD rc1, rc2,....)

http://bugzilla.opensuse.org/show_bug.cgi?id=990701 Andreas Stieger changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Bootloader |3rd party software Version|Leap 42.1 |unspecified Product|openSUSE Distribution |openSUSE.org -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

6 Aug 6 Aug

15:58

New subject: [Bug 990701] Leap with KOTD repo doesnt upgrade booted kernel to 4.7 rtm from rc2 (did so for previous KOTD rc1, rc2,....)

http://bugzilla.opensuse.org/show_bug.cgi?id=990701 http://bugzilla.opensuse.org/show_bug.cgi?id=990701#c7 --- Comment #7 from andreas bittner --- meanwhile kotd repo gave me another 4.7 rtm update but still not installed as default: rpm -aq | grep kernel kernel-default-4.7.0-3.1.ga8847da.x86_64 kernel-default-4.7.0-1.1.g24f30d5.x86_64 kernel-default-4.7.rc7-2.1.g152f160.x86_64 kernel-firmware-20160503-3.1.noarch Apparently inside the grub2 menu, i can select the newer 4.7.0 kernels via the advanced options and they become listed there only the latest kernel is apparently never put as the default to be booted this is new as of the post-rc kernels for 4.7 as I report in this bugreport can i delete the older kernels now and move over to the latest 4.7 keeping only one kernel or are you guys needing my system to stay at this downgraded state? i really like to move on if this bugreport can be worked with even if my system advances to newer kernels. thanks for a short reply on this matter. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

16 Aug 16 Aug

07:49

New subject: [Bug 990701] Leap with KOTD repo doesnt upgrade booted kernel to 4.7 rtm from rc2 (did so for previous KOTD rc1, rc2,....)

http://bugzilla.opensuse.org/show_bug.cgi?id=990701 http://bugzilla.opensuse.org/show_bug.cgi?id=990701#c8 --- Comment #8 from andreas bittner --- Today came a newer 4.8 rc1 kernel, and apparently this one has become the default in the grub2 menu. so is it possible that there are or were some misconfigurations in the KOTD kernel packages from before, that some sort order or naming or parsing of package names or parts have caused the bad order of entries in grub2? right now i have uname -a Linux linux 4.8.0-rc1-1.gf3b2ad2-default #1 SMP PREEMPT Mon Aug 15 00:08:33 UTC 2016 (f3b2ad2) x86_64 x86_64 x86_64 GNU/Linux rpm -aq | grep kernel kernel-default-4.7.0-3.1.ga8847da.x86_64 kernel-default-4.8.rc1-1.1.gf3b2ad2.x86_64 kernel-default-4.7.0-1.1.g24f30d5.x86_64 kernel-default-4.7.rc7-2.1.g152f160.x86_64 kernel-firmware-20160503-3.1.noarch and it boots the 4.8.rc1 as default so the newest that just gotton installed a few moments ago -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

18 Aug 18 Aug

10:54

New subject: [Bug 990701] Leap with KOTD repo doesnt upgrade booted kernel to 4.7 rtm from rc2 (did so for previous KOTD rc1, rc2,....)

http://bugzilla.opensuse.org/show_bug.cgi?id=990701 http://bugzilla.opensuse.org/show_bug.cgi?id=990701#c9 --- Comment #9 from andreas bittner --- upgrade to 4.8.0 rc2 from 4.8.0 rc1 went fine as well, also gets set as default booted kernel in grub2 uname -a Linux linux 4.8.0-rc2-2.g0fce644-default #1 SMP PREEMPT Tue Aug 16 17:00:15 UTC 2016 (0fce644) x86_64 x86_64 x86_64 GNU/Linux linux:~ # rpm -aq | grep kernel kernel-default-4.7.0-3.1.ga8847da.x86_64 kernel-default-4.8.rc1-1.1.gf3b2ad2.x86_64 kernel-default-4.8.rc2-2.1.g0fce644.x86_64 kernel-firmware-20160503-3.1.noarch -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

22 Aug 22 Aug

14:06

New subject: [Bug 990701] Leap with KOTD repo doesnt upgrade booted kernel to 4.7 rtm from rc2 (did so for previous KOTD rc1, rc2,....)

http://bugzilla.opensuse.org/show_bug.cgi?id=990701 http://bugzilla.opensuse.org/show_bug.cgi?id=990701#c10 --- Comment #10 from andreas bittner --- some newer 4.8 rc2.x kernel came in today and it became default boot entry as well uname -a Linux linux 4.8.0-rc2-3.gda13dfd-default #1 SMP PREEMPT Sun Aug 21 14:36:31 UTC 2016 (da13dfd) x86_64 x86_64 x86_64 GNU/Linux @linux:~> rpm -aq | grep kernel kernel-default-4.8.rc2-3.1.gda13dfd.x86_64 kernel-default-4.8.rc1-1.1.gf3b2ad2.x86_64 kernel-default-4.8.rc2-2.1.g0fce644.x86_64 kernel-firmware-20160503-3.1.noarch -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

25 Aug 25 Aug

17:10

New subject: [Bug 990701] Leap with KOTD repo doesnt upgrade booted kernel to 4.7 rtm from rc2 (did so for previous KOTD rc1, rc2,....)

http://bugzilla.opensuse.org/show_bug.cgi?id=990701 http://bugzilla.opensuse.org/show_bug.cgi?id=990701#c11 --- Comment #11 from andreas bittner --- 4.8 rc3 became default as well uname -a Linux linux 4.8.0-rc3-1.gc0d2ef5-default #1 SMP PREEMPT Mon Aug 22 14:52:18 UTC 2016 (c0d2ef5) x86_64 x86_64 x86_64 GNU/Linux rpm -aq | grep kernel kernel-default-4.8.rc2-3.1.gda13dfd.x86_64 kernel-default-4.8.rc2-2.1.g0fce644.x86_64 kernel-default-4.8.rc3-1.1.gc0d2ef5.x86_64 kernel-firmware-20160503-3.1.noarch -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

3 Sep 3 Sep

19:45

New subject: [Bug 990701] Leap with KOTD repo doesnt upgrade booted kernel to 4.7 rtm from rc2 (did so for previous KOTD rc1, rc2,....)

http://bugzilla.opensuse.org/show_bug.cgi?id=990701 http://bugzilla.opensuse.org/show_bug.cgi?id=990701#c12 --- Comment #12 from andreas bittner --- 4.8.0 rc3 to 4.8.0 rc4 went fine and became default as well. Linux linux 4.8.0-rc4-2.gb12c2a7-default #1 SMP PREEMPT Thu Sep 1 13:08:35 UTC 2016 (b12c2a7) x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

6 Oct 6 Oct

10:41

New subject: [Bug 990701] Leap with KOTD repo doesnt upgrade booted kernel to 4.7 rtm from rc2 (did so for previous KOTD rc1, rc2,....)

http://bugzilla.opensuse.org/show_bug.cgi?id=990701 http://bugzilla.opensuse.org/show_bug.cgi?id=990701#c13 --- Comment #13 from andreas bittner --- I am again having this issue, if its to be considered an issue at all, or maybe its by design or I am at a loss of understanding why this is happening every now and then. Are final kernel packages considered or to be taken and regarded differently from all the rcX and betaN whatever kernel packages? right now on leap 42.2 beta3 I switched over to the KOTD repo there, and yesterday I was (and am still booting as default) on: Linux linux 4.8.0-rc8-2.g991ee60-default #1 SMP PREEMPT Tue Sep 27 11:01:09 UTC 2016 (991ee60) x86_64 x86_64 x86_64 GNU/Linux although it has just "upgraded" or added the final 4.8.0 (non-rc) kernel package just minutes ago. I rebooted and grub default entry, but still brings up the rc8 kernel and booting it. Why doesnt it switch over to the "higher" non-rc final release 4.8 kernel? rpm -aq | grep kerne kernel-default-4.8.rc8-2.1.g991ee60.x86_64 kernel-default-4.8.0-1.1.gbbbf852.x86_64 kernel-firmware-20160516git-3.1.noarch ----- /var/log/zypp/history: 016-10-05 12:07:36|install|kernel-default|4.8.rc8-2.1.g991ee60|x86_64|root@linux-ang0|kernel-head-standard-KOTD|bf077c659284ffd7904a0130fd7f90450c52c46fa3aa7b475ced301dd4d9dd38| 2016-10-06 12:27:23|command|root@linux-ang0|'zypper' 'up' 'ucode-amd' 'kernel-firmware' 'kernel-default'| # 2016-10-06 12:28:24 kernel-default-4.8.0-1.1.gbbbf852.x86_64.rpm installed ok # Additional rpm output: # Creating initrd: /boot/initrd-4.8.0-1.gbbbf852-default # dracut: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force --force-drivers "pata_atiixp ahci ata_generic xennet xenblk" /boot/initrd-4.8.0-1.gbbbf852-default 4.8.0-1.gbbbf852-default ..... # dracut: resume=UUID=...... # dracut: root=UUID=...... rootfstype=ext4 rootflags=rw,relatime,data=ordered # dracut: *** Creating image file '/boot/initrd-4.8.0-1.gbbbf852-default' *** # dracut: *** Creating initramfs image file '/boot/initrd-4.8.0-1.gbbbf852-default' done *** # 2016-10-06 12:28:24|install|kernel-default|4.8.0-1.1.gbbbf852|x86_64|root@linux-ang0|kernel-head-standard-KOTD|943f9d5df7eba11f3b2156166dc763b98ac12d757efcfa81289fc129bb354be2| but it never becomes the default entry for grub2 why not? :( -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

2783

Age (days ago)

2855

Last active (days ago)

Download

14 comments

1 participants

tags

participants (1)

bugzilla_noreply＠novell.com