March 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 716107] New: Insufficient (too little) options for change the resolution via bootmenu
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=716107 https://bugzilla.novell.com/show_bug.cgi?id=716107#c0 Summary: Insufficient (too little) options for change the resolution via bootmenu Classification: openSUSE Product: openSUSE 12.1 Version: Milestone 5 Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: is(a)lft.uni-erlangen.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.20) Gecko/20110803 Firefox/3.6.20 Hello, I've tested this iso image burned on a CD-RW 10x: http://download.opensuse.org/distribution/12.1-Milestone5/iso/openSUSE-KDE-… The native resolution of my monitor is 1600x1200, but the highest available resultion in the bootmenu is only 1280x1024. Operation the monitor with the maximum resolution of 1280x1024 leads to an unreadably blured image. Reproducible: Always Steps to Reproduce: 1. Boot Live-CD 2. [F3]... change resolution -> 1280x1024 3. After KDE is fully loaded, -> "Actual Results" Actual Results: Monitor: unreadably blured image. Expected Results: Monitor: If lower resolution is chosen, then the screen should always been readable -- 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 716905] New: After installing OS 12.1-M5 (build0250) the only item in menu.lst is windows
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=716905 https://bugzilla.novell.com/show_bug.cgi?id=716905#c0 Summary: After installing OS 12.1-M5 (build0250) the only item in menu.lst is windows Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: linxt(a)comcast.net QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0 During repeated installations of openSUSE 12.1-M5 into re-formatted partition, /boot/grub/menu.lst has only windows. Consequently system would not finish installing after initial restart. However, /boot/grub/menu.lst.old has the OS 12.1-M5 listing. The solution was to rename menu.lst to menu.lst.saved and rename menu.lst.old to menu.lst. This allowed correct reboot and finishing installation. This is to be a dual boot with windows-7 already installed. Reproducible: Always Steps to Reproduce: 1.Install OS 12.1-M5(0250) from DVD after re-formatting root (/) partition. 2.Initial reboot during install goes directly to windows. 3.Rename menu.lst to menu.lst.saved and menu.lst.old to menu.lst 4.System then reboots into OS 12.1 correctly and finishes instalation. Actual Results: During repeated attempts to install OS 12.1-M5 to freshly re-formatted partition it went into windows after first reboot. Expected Results: Boot into OS 12.1 and finish installation. M/B: ASUS M4N98TD EVO CPU: Athlon Phenom II x4 RAM: 4 GB HD1: WD 1.5 TB sata3 HD2: WD 1.5 TB sata3 VID: ASUS 210 (GeForce 210) -- 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 728566] New: Net install cd not restart at the end of the installation
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=728566 https://bugzilla.novell.com/show_bug.cgi?id=728566#c0 Summary: Net install cd not restart at the end of the installation Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gy3544(a)yahoo.fr QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 I download the netinstall cd of 12.1rc2. I burned it. I run installation for update. Update of 11.4. The installation has been ok. At the end it has blocked during the restart. I shutdown my computer and start it. I can use 12.1 opensuse. 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 2

[Bug 730152] New: update-bootloader does not update menu.lst
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=730152 https://bugzilla.novell.com/show_bug.cgi?id=730152#c0 Summary: update-bootloader does not update menu.lst Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: All OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Bootloader AssignedTo: snwint(a)suse.com ReportedBy: bwiedemann(a)suse.com QAContact: jsrain(a)suse.com CC: cfarrell(a)suse.com Found By: Development Blocker: --- When installing from a DVD-image on USB-stick, an additional boot entry for the USB device is created as "Linux other". When updating kernels later, without USB-stick, update-bootloader fails to update /boot/grub/menu.lst Reproducible: Always # update-bootloader --refresh Perl-Bootloader: 2011-11-11 20:26:44 WARNING: GRUB::GrubDev2UnixDev: No partition found for /dev/disk/by-id/usb-SMI_USB_DISK_2010060400001304-0:0 with 1. # cat /boot/grub/device.map (hd1) /dev/disk/by-id/usb-SMI_USB_DISK_2010060400001304-0:0 (hd0) /dev/disk/by-id/ata-SAMSUNG_HM040HI_S07WJ10Y710009 I needed to drop the hd1 entry in device.map and menu.lst for update-bootloader to work again yast2 bootloader => Propose New Configuration could have helped, too. -- 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 737705] New: dosemu dies with segmentation fault when starting
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=737705 https://bugzilla.novell.com/show_bug.cgi?id=737705#c0 Summary: dosemu dies with segmentation fault when starting Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: roland(a)logikalsolutions.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 roland@linux-853v:~> dosemu -t LOWRAM mmap: Invalid argument Creating symbolic link for /home/roland/.dosemu/drive_c as /home/roland/.dosemu/drives/c Creating symbolic link for /usr/share/dosemu/drive_z as /home/roland/.dosemu/drives/c Segmentation fault roland@linux-853v:~> Reproducible: Always Steps to Reproduce: 1.Install dosemu from YAST 2.Open a terminal and attempt to start dosemu 3. Actual Results: segmentation fault Expected Results: should have DOS window appear -- 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 742512] New: instsys does not boot
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=742512 https://bugzilla.novell.com/show_bug.cgi?id=742512#c0 Summary: instsys does not boot Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: All OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bwiedemann(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 instsys did not boot for several weeks - seen on openQA as early as Build0011 2011-11-23 Reproducible: Always Steps to Reproduce: 1. boot Factory NET iso Actual Results: currently complains "SHA1 sum wrong" or when run with insecure=1 it writes "Could not find the openSUSE Repository" Expected Results: should boot the installation system -- 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 769236] New: Installation kernel hangs (12% loaded) on Intel XEON system (E7520)
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=769236 https://bugzilla.novell.com/show_bug.cgi?id=769236#c0 Summary: Installation kernel hangs (12% loaded) on Intel XEON system (E7520) Classification: openSUSE Product: openSUSE 12.2 Version: Beta 2 Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Winfrid.Tschiedel(a)t-online.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20100101 Firefox/14.0 Installation of openSUSE 12.2 Beta 2 on Intel Jarrell system (E7520 controller) fails. Kernel hangs after loading 12%. Reproducible: Always Steps to Reproduce: 1. Install openSUSE 12.2 Beta 2 on Intel Jarrell server (E7520) 2. 3. Actual Results: Kernel hangs after loading 12%. This is independent of the used installation method (save, no acpi, default) Expected Results: Successful installtion No problems installing openSUSE 12.1 Previous openSUSE 12.2 installation failed with other reasons - as far as I remember only installation of M1 was successful, but after reboot the kernel crashed -- 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

[Bug 798966] New: y2start.log reveals VNC password
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=798966 https://bugzilla.novell.com/show_bug.cgi?id=798966#c0 Summary: y2start.log reveals VNC password Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 2 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: yast2-maintainers(a)suse.de ReportedBy: locilka(a)suse.com QAContact: jsrain(a)suse.com Found By: Development Blocker: --- Created an attachment (id=520577) --> (http://bugzilla.novell.com/attachment.cgi?id=520577) y2start.log After entering a VNC password, I can find it in y2start.log: grep -i password y2start.log |-- export VNCPassword="<your-password>" |-- export vncpassword="asdfghjkl" * Once hidden * Then logged as it is -- 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 801676] New: Removing "grub2" package should not be allowed if boot loader type is grub2
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=801676 https://bugzilla.novell.com/show_bug.cgi?id=801676#c0 Summary: Removing "grub2" package should not be allowed if boot loader type is grub2 Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: joschibrauchle(a)gmx.de QAContact: jsrain(a)suse.com Found By: Beta-Customer Blocker: --- Installing openSUSE12.3 Beta1 with all default setting **except removing the grub2** package in the software selection leads to an unbootable system (with multiple errors during bootloader installation), because obviously the default settings use Grub2 as bootloader. Hence, 1) YaST should detect which boot loader is configured for booting and should either force the corresponding package to be installed or 2) adapt the boot loader config if the required boot loader is not in the software selection or 3) at least display a warning message, informing about the invalid configuration. Also note that during the installation of the boot loader in stage2, a reconfiguration is offered by YaST. Switching the config to GRUB and clicking OK does not prevent failure of initrd creation -> unbootable system. See screenshots of the installation procedure with missing grub2 package... -- 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 8

[Bug 675793] New: KMS broke traditional framebuffer modes
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=675793 https://bugzilla.novell.com/show_bug.cgi?id=675793#c0 Summary: KMS broke traditional framebuffer modes Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)novell.com ReportedBy: mrmazda(a)earthlink.net QAContact: jsrain(a)novell.com Found By: --- Blocker: --- I think this has been going on since KMS went into 11.3M3 or so a year ago, but since I've been using mostly displays with missing/invalid EDID, I hadn't noticed. Pre-KMS one would normally one set e.g. vga=791 or vga=0x31a in order to get appropriate sizes of font, rows and columns on the virtual consoles, and use xorg.conf to configure the most appropriate mode for X. Now that I've added a display with valid EDID to my repertoire, I cannot achieve desired console configuration with these legacy framebuffer modes. That is, I want 0x305/791/0x317 on my consoles, which happen to be 1024x768 modes, but I want X to run in the display's best native mode, which is unlikely to be 1024x768 on currently available desktop displays, and also unlikely on any but the tiniest of laptops (aka netbooks). In the instant case of a UXGA (1600x1200) display, vga=791 (with splash=verbose and no quiet) on cmdline only produces 1024x768 on tty1 briefly, then KMS switches to a 1600x1200 mode. IOW, the switch that happens constitutes brokenness, as opposed to making this bug a new feature request. What does produce expected results, that is, 1024x768 on the ttys and 1600x1200 in X (via autoconfig aka no xorg.conf file), is to put video=1024x768 on cmdline instead of any of the vga modes in YaST's "Vga Mode" select list. YaST Bootloader needs to augment or supplant the available legacy framebuffer modes with selections using the KMS syntax. Probably the title "Vga Mode" should be changed somehow, possibly to "Virtual Console Video Mode", since what vga or video parameter on cmdline appears doesn't affect X at all, at least not when EDID is valid. -- 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 13