February 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 639379] confusing kernel-binary.nosrc.rpm content
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=639379 https://bugzilla.novell.com/show_bug.cgi?id=639379#c4 Michal Marek <mmarek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |mmarek(a)suse.com Component|Kernel |Kernel Version|Factory |13.2 Milestone 0 Resolution|FIXED | AssignedTo|mmarek(a)suse.com |mq(a)suse.com Product|openSUSE 11.4 |openSUSE Factory --- Comment #4 from Michal Marek <mmarek(a)suse.com> 2014-02-10 10:30:01 UTC --- Jan, can you have a look at this one? The Nosource: lines are generated by the 'mkspec' script. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 821612] New: bad release number in update candidate openSUSE:Maintenance:1686:176387
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=821612 https://bugzilla.novell.com/show_bug.cgi?id=821612#c0 Summary: bad release number in update candidate openSUSE:Maintenance:1686:176387 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: i586 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: rommel(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 The kernel-release of the update candidate kernel is reported as boxer:~ # uname -a Linux boxer.suse.de 3.7.10-1.9.gadf31bb-desktop #1 SMP PREEMPT Thu May 16 20:27:27 UTC 2013 (adf31bb) i686 i686 i386 GNU/Linux resp. boxer:~ # rpm -q kernel-desktop kernel-desktop-3.7.10-1.9.1.gadf31bb.i686 The "gadf31bb" part of the release number breaks the dependency chains: boxer:~ # zypper install kernel-syms Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides kernel-xen-devel = 3.7.10-1.9 needed by kernel-syms-3.7.10-1.9.1.i586 Solution 1: do not install kernel-syms-3.7.10-1.9.1.i586 Solution 2: break kernel-syms-3.7.10-1.9.1.i586 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c] (c): c boxer:~ # rpm -q --provides kernel-xen-devel kernel-xen-devel = 3.7.10-1.4 kernel-xen-devel = 3.7.10-1.4.1 kernel-xen-devel(x86-32) = 3.7.10-1.4.1 multiversion(kernel) kernel-xen-devel = 3.7.10-1.9.1.gadf31bb kernel-xen-devel = 3.7.10-1.9.gadf31bb kernel-xen-devel(x86-32) = 3.7.10-1.9.1.gadf31bb multiversion(kernel) Reproducible: Always Steps to Reproduce: 1. zypper ar -f http://download.opensuse.org/repositories/openSUSE:/Maintenance:/1686/openS… openSUSE:/Maintenance:/1686-TESTING 2. zypper update -t patch openSUSE_Maintenance_1686 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 12

[Bug 759635] New: os-prober fails to mount UFS2 partitions
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=759635 https://bugzilla.novell.com/show_bug.cgi?id=759635#c0 Summary: os-prober fails to mount UFS2 partitions Classification: openSUSE Product: openSUSE 12.2 Version: Milestone 3 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: hippolyte(a)shaw.ca QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 os-prober detects BSD UFS partitions but fails to mount ufs2 without the proper ufs type (ufs2). I seems to default to 44bsd (mount -u ufs is equivalent to mount -u ufs -o ufstype=44bsd). Reproducible: Always Steps to Reproduce: 1. add the --verbose option (-v) to the mount command and do not redirect standard error in file /usr/lib/os-probes/50mounted-tests --- /usr/lib/os-probes/50mounted-tests.orig 2012-04-27 03:05:50.883133225 -0700 +++ /usr/lib/os-probes/50mounted-tests 2012-04-27 03:48:58.885248552 -0700 @@ -60,7 +60,7 @@ else ro_partition "$partition" for type in $types $delaytypes; do - if mount -o ro -t "$type" "$partition" "$tmpmnt" 2>/dev/null; then + if mount -v -o ro -t "$type" "$partition" "$tmpmnt" ; then debug "mounted as $type filesystem" mounted=1 break 2. run os-prober on a system with ufs2 partitions Actual Results: ... /dev/sda22 on /var/lib/os-prober/mount type ufs (ro) /dev/sda23 on /var/lib/os-prober/mount type ufs (ro) /dev/sda24 on /var/lib/os-prober/mount type ufs (ro) mount: wrong fs type, bad option, bad superblock on /dev/sda25, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so mount: wrong fs type, bad option, bad superblock on /dev/sda26, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so mount: wrong fs type, bad option, bad superblock on /dev/sda27, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so /dev/sda28 on /var/lib/os-prober/mount type ufs (ro) ... Expected Results: /dev/sda24 on /var/lib/os-prober/mount type ufs (ro,ufstype=44bsd) /dev/sda25 on /var/lib/os-prober/mount type ufs (ro,ufstype=ufs2) /dev/sda25:unknown Linux distribution:Linux1:linux /dev/sda26 on /var/lib/os-prober/mount type ufs (ro,ufstype=ufs2) /dev/sda27 on /var/lib/os-prober/mount type ufs (ro,ufstype=ufs2) /dev/sda27:unknown Linux distribution:Linux2:linux /dev/sda28 on /var/lib/os-prober/mount type ufs (ro,ufstype=44bsd) The outputs of actual and expected results will be different when you remove the option -v from the mount command. I just used this option here for debugging. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 15

[Bug 784988] New: Update to kernel 3.4.6-2.10 leaves system unbootable
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=784988 https://bugzilla.novell.com/show_bug.cgi?id=784988#c0 Summary: Update to kernel 3.4.6-2.10 leaves system unbootable Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: suse(a)stanmiller.info QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0.1 Ran the Apper updater this morning and it fetched a new kernel, upon restart my system is unbootable with a hard to read message from grub that looks something like this: ----------------- Loading Linux 3.4.6-2.10-desktop error: file /boot/vmlinuz-3.4.6-2.10-desktop not found Loading initial ramdisk error: you need to load the kernel first press any key to continue... ---------------- Reproducible: Always Steps to Reproduce: 1. run apper update 2. update to new kernel 3. reboot 4. get stuck at grub error message above Actual Results: System will not boot Expected Results: System should boot -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 7

[Bug 753889] New: grub2: Sorts "previous" kernel versions in wrong order
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=753889 https://bugzilla.novell.com/show_bug.cgi?id=753889#c0 Summary: grub2: Sorts "previous" kernel versions in wrong order Classification: openSUSE Product: openSUSE 12.2 Version: Milestone 2 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jeffm(a)suse.com QAContact: qa-bugs(a)suse.de CC: coolo(a)suse.com Found By: Development Blocker: --- Created an attachment (id=483053) --> (http://bugzilla.novell.com/attachment.cgi?id=483053) grub.cfg I installed 12.2M2 and immediately installed Kernel:HEAD to get 3.3-final plus a few fixes. I'm using grub2 and 3.3-rc6 still appeared as the latest installed kernel with the 3.3-final kernel appearing under "previous linux versions." I haven't installed any updates from Factory or updated grub2 at all. The grub2 config was generated, as expected, my /boot/grub2/grub.cfg was generated by grub-mkconfig. I'm not sure who, if any, is the grub2 maintainer. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 7

[Bug 821763] New: After kernel update /boot/grub2/grub.cfg not updated. Impossible to boot the system
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=821763 https://bugzilla.novell.com/show_bug.cgi?id=821763#c0 Summary: After kernel update /boot/grub2/grub.cfg not updated. Impossible to boot the system Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: linuxk(a)linuxmail.org QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 After today's update, kernel 3.4.33-2.24-desktop to kernel 3.4.42-2.28-desktop asked for a restart but /boot/grub2/grub.cfg was not updated to the new version so booting was not possible. Message error was similar to "you must load kernel first". After opening /grub.cfg, as root, in other computer, and replacing the old entries by the new ones (3.4.42-2.28-desktop instead of 3.4.33-2.24-desktop), I could boot the system again. Suse Linux Rel 12.2 (Mantis) 64-bit Reproducible: Always Steps to Reproduce: 1.accept proposed update kernel 3.4.33-2.24-desktop to 3.4.33-2.24-desktop 2.Rreboot 3.Get error message similar to "you must load kernel first" Actual Results: After opening /grub.cfg, as root, in other computer, and replacing the old entries by the new ones (3.4.42-2.28-desktop instead of 3.4.33-2.24-desktop), I could boot the system again. Expected Results: The software should update /grub.cfg to allow booting the newly installed kernel -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 9

[Bug 800123] New: restrictive kernel command line parameters in default entry of grub.cfg
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=800123 https://bugzilla.novell.com/show_bug.cgi?id=800123#c0 Summary: restrictive kernel command line parameters in default entry of grub.cfg Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: christopher.lang(a)acurana.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=521595) --> (http://bugzilla.novell.com/attachment.cgi?id=521595) grub.cfg installed on dell notebook User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 After installing 12.2 on a Dell M6700 Laptop the default kernel command line used in grub.cfg disables power management via acpi=off. Some more things are being disabled too. linux /boot/vmlinuz-3.4.11-2.16-desktop root=UUID=5b87eae9-3584-4a0f-8716-449c315bc98a apm=off acpi=off mce=off barrier=off ide=nodma idewait=50 i8042.nomux psmouse.proto=bare irqpoll pci=nommconf video=1920x1080 resume=/dev/disk/by-id/md-uuid-0d9cbb31:1c18abe9:4c9445c9:04aac321-part5 splash=silent quiet showopts Shouldn't the default kernel command line used in grub.cfg be less restrictive? How does the installer determine which kernel command line parameters to use? acpi=off more or less disables all power mgmt on notebooks. Full grub.cfg attached. Reproducible: Always Steps to Reproduce: 1. Download 12.2 dvd 2. install on notebook without network connection 3. check /boot/grub2/grub.cfg Actual Results: restrictive kernel ccommand line parameters in default entry of grub.cfg, especially acpi=off -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4

[Bug 788921] New: Grub2 only shows one Windows boot entry, but I have installed two Windows versions.
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=788921 https://bugzilla.novell.com/show_bug.cgi?id=788921#c0 Summary: Grub2 only shows one Windows boot entry, but I have installed two Windows versions. Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: poolbarde(a)web.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20100101 Firefox/16.0 I have installed two Windows versions (XP and 7) on my PC. Then I have installed openSUSE 12.2. After installation grub2 only provides a boot entry for my Windows 7, but noot for my XP. In case I install XP, then 7, then opensuse without using hidden partitions (for windows), the Windows 7 boot entry will boot the windows boot loader which offers to boot XP and 7. But when install XP, hide the partition, then windows 7 and then Linux, I can't boot XP anymore. When installing openSUSE 12.2 using grub (not grub2), then everything works as expected. Reproducible: Always Steps to Reproduce: 1.Install Windows XP (into 1st PArtition) 2.Install Windows 7 (into 2nd Partition) 3.Install openSUSE 12.2 using grub2 bootloader. Actual Results: Can't boot XP from grub2 boot menu Expected Results: It should be possible to boot openSUE 12.4, Windows XP and Windows 7 from the grub2 boot menu. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 1

[Bug 788871] New: Themed GRUB 2 is painfully slow
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=788871 https://bugzilla.novell.com/show_bug.cgi?id=788871#c0 Summary: Themed GRUB 2 is painfully slow Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: szotsaki(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux x86_64; Edition Next) Presto/2.12.388 Version/12.10 I installed openSUSE 12.2 and chose that GRUB 2 has a graphical interface (parameters: VGA mode: unspecified, use graphical console, resolution: 1680x1050). After it slowly loads it takes a second until it realizes that I pressed an arrow button. It requires 3 seconds „navigation time” until I move the selection from the Linux to the Windows entry... Setting 1 second waiting time is not possible because it doesn't detect any keyboard activity within that time. Reproducible: Always -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 2

[Bug 784140] New: UEFI boot partition no longer recognized after online update on 8th October, 2012
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=784140 https://bugzilla.novell.com/show_bug.cgi?id=784140#c0 Summary: UEFI boot partition no longer recognized after online update on 8th October, 2012 Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: sbo(a)mis.mpg.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0.1 One of the online updates provided today seems to have broken the UEFI boot process. After the updates had been installed, the system asked me to reboot. When I did, Windows was started instead of OpenSUSE. I rebooted again and brought up the boot device menu: No "opensuse" entry anymore, only two Windows entries. Using the rescue system, I took a look at the /boot/efi directory: one of the files had been changed roughly at the time of the online update. I tried grub2-efi-install to re-install the bootloader (a little tricky, since the rescue system does not include the grub2 executables and I had to mount the installed version's root directory to find them) and it changed the timestamp on the file again, but still the "opensuse" entry is not recognized by the BIOS. Details: I have two EFI system partitions on /dev/sda, but only the one created by Windows 7 is identified as "EFI System Partition" in parted, the one created by OpenSUSE appears to be just a standard fat32 partition with an "EFI" directory. Before the update, it seemed to work. I am using an Asus P9X79 Pro motherboard, the BIOS version is 2104, apparently the current one. Reproducible: Always Steps to Reproduce: 1. Install OpenSUSE 12.2, create new GPT 2. Install Windows 7 3. Include Windows stanza (by hand) in 41_custom script to enable multi-booting 4. Install updates release on 8th of October, 2012 Actual Results: grub2 EFI partition no longer recognized, OpenSUSE cannot boot. Expected Results: Obviously, I would have expected OpenSUSE to boot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 6