August 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 591700] New: System fails to boot after "zypper up" from 11.3 M2 to M4
by bugzilla_noreply＠novell.com 15 Aug '14

15 Aug '14

http://bugzilla.novell.com/show_bug.cgi?id=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c0 Summary: System fails to boot after "zypper up" from 11.3 M2 to M4 Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 4 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)novell.com ReportedBy: kkaempf(a)novell.com QAContact: jsrain(a)novell.com Found By: Development Blocker: --- /boot/grub/menu.lst is wrong after "zypper up" (see attachment) - It contains multiple entries (2.6.33-5-default, which is not installed) - The first entries have the wrong disk ( hd(1,0) vs hd(0,0) ) - The second entries have the wrong kernel ( 2.6.33-5 vs 2.6.3-6 ) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 77

[Bug 618286] New: RAID1 installation makes multiboot system completely unbootable (active flag removed with standard MBR code)
by bugzilla_noreply＠novell.com 15 Aug '14

15 Aug '14

http://bugzilla.novell.com/show_bug.cgi?id=618286 http://bugzilla.novell.com/show_bug.cgi?id=618286#c0 Summary: RAID1 installation makes multiboot system completely unbootable (active flag removed with standard MBR code) Classification: openSUSE Product: openSUSE 11.3 Version: RC 1 Platform: x86 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)novell.com ReportedBy: mrmazda(a)earthlink.net QAContact: jsrain(a)novell.com Found By: --- Blocker: --- Created an attachment (id=372494) --> (http://bugzilla.novell.com/attachment.cgi?id=372494) y2logs to reproduce: 1-partition multiboot and suitably format partitions 2-install standard MBR code 3-install DOS and/or Windows and/or OS/2 to standard primary partition(s) 4-install other distros to md devices comprised exclusively of logical partitions 5-configure a bootloader on some primary partition 6-set a primary partition active 7-test that every installed OS will boot 8-install RC1 to an md device comprised exclusively of logical partitions, specifying via the checkbox custom partition in (grub) bootloader configuration and leaving active flag checkbox checked actual behavior: 1-system will not boot anything from any HD 2-active flags are missing from all primary partitions expected behavior: 1-active flags remain as they were prior to installation 2-all previously bootable operating systems remain bootable as before 3-RC1 can be booted via chainload and/or configfile from pre-existing Grub on custom boot partition Notes: On installations to non-primary partitions there should never be any reason to touch active flags on existing primary partitions, particularly when YaST is not called upon to alter any partition tables (make no changes to _any_ partitions). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 11

[Bug 671085] New: bootloader error from opensuse 11.3 (bug 638232) continues into 11.4 mile 6
by bugzilla_noreply＠novell.com 15 Aug '14

15 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=671085 https://bugzilla.novell.com/show_bug.cgi?id=671085#c0 Summary: bootloader error from opensuse 11.3 (bug 638232) continues into 11.4 mile 6 Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)novell.com ReportedBy: fenriswoolf(a)gmx.net QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_6; en-us) AppleWebKit/533.19.4 (KHTML, like Gecko) Version/5.0.3 Safari/533.19.4 in the installation settings: under bootloader: The bootloader is installed on a partition that does not lie entirely below 128GB. The system might not boot, if BIOS support only lba24 (result is error18 during install grub MBR). in the installation settings: under software: nothing provides libc.so.6 needed by grub-0.97-173.6.x86_64 this is a systemic error that arrived with opensuse 11.3 (see bug 638232) installation works fine until i get to the installation settings. i did not continue with installation, because the out come is known from bug 638232. Reproducible: Always Steps to Reproduce: 1.insert install disk opensuse 11.3 and begin install 2.go through installation steps 3.install runs smooth until one reaches installation overview, when under bootloader the following message is displayed: “ Bootloader is installed on a partition that does not lie entirely below 128 GB. The system might not boot, if BIOS support only lba24 (result is error18 during install grub MBR)." Actual Results: continue with the installation, but initial boot takes you straight to win7 Expected Results: grub menu should appear and opensuse 11.3 should be launchable this error does not exist in opensuse 11.2 ... i worked around the problem as described in bug 638232, but this is by no means an elegant solution ... the bootloader from 11.3/11.4M6 on needs to be fixed, or the older version from 11.2 should be implemented. -- 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

[Bug 704916] New: Specifying iscsi-client section in autoyast file results in error (pgrep: command not found)
by bugzilla_noreply＠novell.com 15 Aug '14

15 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=704916 https://bugzilla.novell.com/show_bug.cgi?id=704916#c0 Summary: Specifying iscsi-client section in autoyast file results in error (pgrep: command not found) Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: Other OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: max(a)noc-ps.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.41 Safari/535.1 I'm trying to automate an installation to an ISCSI target using an AutoYast script along the lines of: == <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> [......] <iscsi-client> <targets config:type="list"> <listentry> <authmethod>None</authmethod> <portal>1.2.3.4:3260</portal> <startup>onboot</startup> <target>iqn.1986-03.com.sun:02:my-iqn</target> </listentry> </targets> <version>1.0</version> </iscsi-client> </profile> == However I receive a red "an error occured during installation" error message. y2log seems to suggest "pgrep" is called, but that command is not present in the installation environement. == 2011-07-11 08:25:12 <1> iscsitest(2970) [YCP] Service.ycp:287 Running service initscript open-iscsi reload 2011-07-11 08:25:14 <3> iscsitest(2970) [bash] ShellCommand.cc(shellcommand):78 .unused 2011-07-11 08:25:14 <3> iscsitest(2970) [bash] ShellCommand.cc(shellcommand):78 sh: pgrep: command not found == Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 3

[Bug 846751] New: "Failed to mount RW root filesystem" during boot from openSUSE 13.1 Live-USB
by bugzilla_noreply＠novell.com 15 Aug '14

15 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=846751 https://bugzilla.novell.com/show_bug.cgi?id=846751#c0 Summary: "Failed to mount RW root filesystem" during boot from openSUSE 13.1 Live-USB Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: 32bit OS/Version: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Live Medium AssignedTo: coolo(a)suse.com ReportedBy: sebastiankuhne1(a)googlemail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=564136) --> (http://bugzilla.novell.com/attachment.cgi?id=564136) Error Message Screen Shot User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Firefox/24.0 I have generated a USB live system by using Suse StudioImagewriter. This pocedure is well known to me, there was no issue do far with previous openSUSE versions. The system starts to boot normally, the start screen appears and I am selecting the language to German, and start the boot process. The system hangs during boot from openSUSE 13.1 Live USB with the message "failed to mount RW root filesystem", "reboot Exception: reboot in 120 sec...": After reboot the content of the USB stick obviously has been destroyed. It appears the message to insert a boot media. It is not possible to repeat that procedure - the USB stick needs to be rewritten by Suse StudioImagewriter first. Then, the failure is completely reproducible. The same procedure runs fine with openSUSE 12.3. It is neither an issue of the USB stick nor of my computer system. Thanks a lot for your help! Best regards Sebastian Reproducible: Always Steps to Reproduce: 1. Rewrite USB stick with Suse StudioImagewriter 2. Boot from USB device with openSUSE Live Image 3. -- 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 725903] New: menu.lst got additional and broken line
by bugzilla_noreply＠novell.com 15 Aug '14

15 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=725903 https://bugzilla.novell.com/show_bug.cgi?id=725903#c0 Summary: menu.lst got additional and broken line Classification: openSUSE Product: openSUSE 12.1 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: lmuelle(a)suse.com QAContact: jsrain(a)suse.com Found By: Development Blocker: --- In /etc/sysconfig/bootloader I got: DEFAULT_APPEND=" repair=1 resume=/dev/disk/by-id/ata-WDC_WD20EARS-22MVWB0_WD-WCAZA0230853-part3 splash=silent quiet showopts" And in /boot/grub/menu.lst I had after an upgrade from 11.4 ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 12.1 root (hd0,0) kernel /boot/vmlinuz-3.1.0-rc9-1-default root=/dev/disk/by-label/giles_root_1 repair=1 resume=/dev/disk/by-id/ata-WDC_WD20EARS-22MVWB0_WD-WCAZA0230853-part3 splash=silent quiet showopts vga=0x348 initrd /boot/initrd-3.1.0-rc9-1-default ###Don't change this comment - YaST2 identifier: Original name: openSUSE 12.1 RC1 1 - 3.1.0-rc9-1 (default) (/dev/sda2)### title openSUSE 12.1 RC1 1 - 3.1.0-rc9-1 (default) (/dev/sda2) root (hd0,1) configfile /boot/grub/menu.lst ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy rootnoverify (fd0) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 12.1 root (hd0,0) kernel /boot/vmlinuz-3.1.0-rc9-1-default root=/dev/disk/by-label/giles_root_1 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x348 initrd /boot/initrd-3.1.0-rc9-1-default Before the upgrade the Floppy item had been the second last and Memory test the last. I'm going to attach both full files next. -- 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 5

[Bug 871814] New: Perl-Bootloader: ... pbl-6062.2 Core::GRUB2::GrubDev2UnixDev.215: Error: did not find a match for hd0 in the device map
by bugzilla_noreply＠novell.com 15 Aug '14

15 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=871814 https://bugzilla.novell.com/show_bug.cgi?id=871814#c0 Summary: Perl-Bootloader: ... pbl-6062.2 Core::GRUB2::GrubDev2UnixDev.215: Error: did not find a match for hd0 in the device map Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mpluskal(a)suse.com QAContact: qa-bugs(a)suse.de CC: snwint(a)suse.com Found By: --- Blocker: --- Created an attachment (id=584889) --> (http://bugzilla.novell.com/attachment.cgi?id=584889) y2logs During update of factory, when kernel update is being installed I noticed following error: *** Creating image file done *** Perl-Bootloader: 2014-04-03 13:07:50 <3> pbl-6062.2 Core::GRUB2::GrubDev2UnixDev.215: Error: did not find a match for hd0 in the device map It however seems that issue is not critical -- 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 890223] New: openSUSE-Factory-KDE-Live-i686-Current.iso -- Media Check Failure
by bugzilla_noreply＠novell.com 15 Aug '14

15 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=890223 https://bugzilla.novell.com/show_bug.cgi?id=890223#c0 Summary: openSUSE-Factory-KDE-Live-i686-Current.iso -- Media Check Failure Classification: openSUSE Product: openSUSE Factory Version: 201408* Platform: i686 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: yast2-maintainers(a)suse.de ReportedBy: michalng(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=600906) --> (http://bugzilla.novell.com/attachment.cgi?id=600906) No base product found User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20140723 Firefox/24.0 Iceweasel/24.7.0 Affected ISO ============ 1. Downloaded the Factory iso for the previous 3 (03-Aug-2014, 01-Aug-2014 and Jul 14) openSUSE-Factory-KDE-Live-i686-Current from http://download.opensuse.org/factory/iso/ Steps taken =========== 1. Each time downloaded 2 copies using , Firefox and kget separately. 2. Check md5sum to ensure that both are identical (since no md5sum is listed on the site) 3. Using dd and imagewriter (separately), copied the iso onto a usb thumbdrive. Error ===== 1. Boot up the live iso and select Check Installation Media. 2. Received the "ISO check failed, you have been warned" message. 3. Proceed to install and received the following error Details: No base product found Caller" /usr/share/YaST2/modules/Product.rb.118:in 'FindBaseProducts' Item 3 may have been report earlier (Bug 889157 - yast2-live-installer fails at summary screen, no base product found) Reproducible: Always Steps to Reproduce: 1.Download and burn into thumbdrive 2.Boot live iso. Actual Results: 1. Check Installation Media -> error message "ISO check failed, you have been warned". 2. Proceed to install and received the following error Details: No base product found Caller" /usr/share/YaST2/modules/Product.rb.118:in 'FindBaseProducts' Expected Results: Able to install without problem. -- 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 22

[Bug 889426] New: deptestomatic.noui missing from libzypp-testsuite-tools
by bugzilla_noreply＠novell.com 15 Aug '14

15 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=889426 https://bugzilla.novell.com/show_bug.cgi?id=889426#c0 Summary: deptestomatic.noui missing from libzypp-testsuite-tools Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: kashmancy(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 After installing libzypp-testsuite-tools in openSUSE 13.1, the command deptestomatic.noui is missing. Instead, deptestomatic.multi is located at "/usr/lib/zypp/testsuite/bin/". I expected deptestomatic.noui to be installed, after reading "http://wiki.novell.com/index.php/SUSE_Manager/SolverTestcase". Reproducible: Always Steps to Reproduce: - Install libzypp-testsuite-tools Actual Results: - Notice that deptestomatic.noui is not installed at "/usr/lib/zypp/testsuite/bin/" Expected Results: - deptestomatic.noui should be installed, after reading "http://wiki.novell.com/index.php/SUSE_Manager/SolverTestcase" I would expect deptestomatic.noui to be installed with the testsuite, especially since I am running this on a headless server; deptestomatic.multi appears to require GUI tools. -- 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 888919] New: When removing (not disabling) repositories, YaST should also remove their cache etc.
by bugzilla_noreply＠novell.com 15 Aug '14

15 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=888919 https://bugzilla.novell.com/show_bug.cgi?id=888919#c0 Summary: When removing (not disabling) repositories, YaST should also remove their cache etc. Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: antoine.mechelynck(a)belgacom.net QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0 SeaMonkey/2.27a1 After removing repositories (already disabled) for earlier releases from the list of repositories known to YaST, I brought my HD from "0 bytes available" to "16 GiB available" by manually removing whatever concerned these obsolete versions in /var/cache/zypp/packages/. See details below. Reproducible: Always Steps to Reproduce: 0. You must have obsolete still-defined repositories which you will never use again. 1. Start up YaST 2. Select "Software → Software Repositories" 3. Select any obsolete repositories one by one, and "Delete" them. -- Note: There is no multi-select feature (no Ctrl-click) but this is only a minor annoyance and not the object of this bug. 4. OK, then close YaST. (We'll do the rest at a bash prompt.) 5. pushd /var/cache/zypp/packages 6. ls -lt 7. Identify the repositories which you just removed, and any ones removed previously and use them as operands to the "rm -Rv" command (without quotes of quotes). You may want to log the output. (by > or |tee, or by >> or |tee -a). 8. Have a look at all the files and directories deleted at step 8. Actual Results: Directory caches are not removed at steps 3-4 (by YaST) but only at step 7 (manually) Expected Results: YaST should already have removed them. Additional info: Of the directories removed at step 7, I noticed that some (the oldest ones) were empty, others weren't, and several (removed at step 3-4 immediately before) were extremely far from empty. As mentioned at top, my total win was 16 GiB of disk space, reducing /var/cache/zypp/packages/ from the biggest thing on my HD to almost nothing in comparison to e.g /root/. "Dataloss" can happen in any other application if, as was my case, failure to remove obsolete data causes the disk to become full. -- 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 11