March 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 731601] New: Swap files which are not full partitions are not mounted at boot time
by bugzilla_noreply＠novell.com 13 Mar '13

13 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=731601 https://bugzilla.novell.com/show_bug.cgi?id=731601#c0 Summary: Swap files which are not full partitions are not mounted at boot time Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: antoine.mechelynck(a)belgacom.net QAContact: qa(a)suse.de Found By: Community User Blocker: --- My /etc/fstab includes the following two lines: /dev/disk/by-id/ata-WDC_WD800JD-60LSA0_WD-WMAM9E273734-part2 swap swap defaults 0 0 /swapfile swap swap nofail 0 0 Under openSUSE 11.4, "swapon -s" showed that (with no explicit action by me) both were in use, with priorities -1 and -2 respectively. Under openSUSE 12.1, only /dev/sda2 is mentioned, and with priority 0. -- 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 25

[Bug 809135] New: Typo in Release notes: availale -> available
by bugzilla_noreply＠novell.com 13 Mar '13

13 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=809135 https://bugzilla.novell.com/show_bug.cgi?id=809135#c0 Summary: Typo in Release notes: availale -> available Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Release Notes AssignedTo: ke(a)suse.com ReportedBy: trans(a)michael-skiba.de QAContact: coolo(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 >From this block: Prior to installing openSUSE on a system that boots using UEFI (Unified Extensible Firmware Interface) you are urgently advised to check for any firmware updates the hardware vendor recommends and, if availale, to install such an update. A pre-installed Windows 8 is a strong indication that your system boots using UEFI. availale should be available 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 1

[Bug 804882] New: Text install does not set grub2 to be text mode
by bugzilla_noreply＠novell.com 13 Mar '13

13 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=804882 https://bugzilla.novell.com/show_bug.cgi?id=804882#c0 Summary: Text install does not set grub2 to be text mode Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 2 Platform: x86 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: roger(a)opq.se QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20100101 Firefox/12.0 When installing 12.3 RC1, I had to use text mode because there seem to be issues with my intel graphics chip and grub2 (X works fine). The only problem is that text mode install does not set grub2 to also be in text mode. So, the initial reboot to complete installation did not happen correctly. Also, every boot just went, eventually, to the default OS start. So, I was not able to do things like enter kernel option when booting. Eventually, when I could log in over the network and run yast in text mode, I could configure grub2 to be character based. Reproducible: Always Steps to Reproduce: 1. Install 12.3 RC1 in text mode 2. reboot 3. Actual Results: There is no visible grub2 menu. Presumably it is there. Eventually the default OS boots. Expected Results: Grub in the same mode as the OS install: text In the text mode install, I guess an option to set if grub should be in text mode as well would work. -- 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 780636] New: notebook directly resumes after performing s2ram via lid-close
by bugzilla_noreply＠novell.com 13 Mar '13

13 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=780636 https://bugzilla.novell.com/show_bug.cgi?id=780636#c0 Summary: notebook directly resumes after performing s2ram via lid-close Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: ctrippe(a)opensuse.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.34 (KHTML, like Gecko) konqueror/4.9.1 Safari/534.34 I am using KDE and have it configured to suspend to ram when I close the lid, which works fine. However often after performing this the laptop wakes up again (and resumes fine) without opening the lid. As I did not have the problem with KDE 4.8 on openSUSE 12.1 (e.g. the version used with 12.2) my guess is that this is a bug somewhere deeper in the stack. Performing manually s2ram from konsole as root does not show this problem. Please tell me which additional information could be useful. This is with an Fujituse Lifebook A Series. Reproducible: Sometimes -- 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 808876] New: openSUSE 12.3. ACPI Error on ASUS Sabertooth Z77.
by bugzilla_noreply＠novell.com 13 Mar '13

13 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=808876 https://bugzilla.novell.com/show_bug.cgi?id=808876#c0 Summary: openSUSE 12.3. ACPI Error on ASUS Sabertooth Z77. Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: ylalym(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=529275) --> (http://bugzilla.novell.com/attachment.cgi?id=529275) dmesg User-Agent: Opera/9.80 (X11; Linux x86_64) Presto/2.12.388 Version/12.14 Hello. openSUSE 12.3 x86_64 + ASUS Sabertooth Z77 - more I can add nothing. ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359) ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff88040a0b5a38), AE_NOT_FOUND (20120913/psparse-536) ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359) ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node ffff88040a0b5858), AE_NOT_FOUND (20120913/psparse-536) ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359) ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff88040a0b5a38), AE_NOT_FOUND (20120913/psparse-536) ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359) ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT3._GTF] (Node ffff88040a0b58d0), AE_NOT_FOUND (20120913/psparse-536) ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359) ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node ffff88040a0b5858), AE_NOT_FOUND (20120913/psparse-536) ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359) ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT3._GTF] (Node ffff88040a0b58d0), AE_NOT_FOUND (20120913/psparse-536) I apply logs 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 5

[Bug 801417] New: glance requires python-requests < 1.0 but we have 1.1.0
by bugzilla_noreply＠novell.com 13 Mar '13

13 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=801417 https://bugzilla.novell.com/show_bug.cgi?id=801417#c0 Summary: glance requires python-requests < 1.0 but we have 1.1.0 Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: speilicke(a)suse.com ReportedBy: aj(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Product Management Blocker: --- aj@byrd:~> glance image-create --name="Studio built VM" --is-public=True \ > --disk-format=qcow2 --container-format=bare \ > --copy-from http://bit.ly/UHn5C7 Traceback (most recent call last): File "/usr/bin/glance", line 5, in <module> from pkg_resources import load_entry_point File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 2833, in <module> parse_requirements(__requires__), Environment() File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 604, in resolve raise DistributionNotFound(req) pkg_resources.DistributionNotFound: requests<1.0 -- 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 807589] New: Failed to instal vmware workstation 9.0.1
by bugzilla_noreply＠novell.com 13 Mar '13

13 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=807589 https://bugzilla.novell.com/show_bug.cgi?id=807589#c0 Summary: Failed to instal vmware workstation 9.0.1 Classification: openSUSE Product: openSUSE 12.3 Version: RC 2 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: peter(a)plord.co.uk QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 I've tried to install vmware workstation 9.0.1 on OpenSuse 12.3 RC2. I see the build fails to find the kernel source "C header files matching your running kernel were not found. Refer to your distributor's documentation for installation instructions" The install log file complains about :- 2013-03-05T18:59:45.910Z| vthread-3| I120: Setting header path for 3.7.10-1.1-desktop to "/lib/modules/3.7.10-1.1-desktop/build/include". 2013-03-05T18:59:45.910Z| vthread-3| I120: Validating path "/lib/modules/3.7.10-1.1-desktop/build/include" for kernel release "3.7.10-1.1-desktop". 2013-03-05T18:59:45.910Z| vthread-3| I120: Failed to find /lib/modules/3.7.10-1.1-desktop/build/include/linux/version.h 2013-03-05T18:59:45.910Z| vthread-3| I120: Failed version test: /lib/modules/3.7.10-1.1-desktop/build/include/linux/version.h not found. I have installed :- linux-glibc-devel-3.7.1-2.1.3.noarch kernel-devel-3.7.10-1.1.1.noarch kernel-desktop-3.7.9-1.1.2.x86_64 kernel-desktop-devel-3.7.10-1.1.1.x86_64 kernel-source-3.7.10-1.1.1.noarch Reproducible: Always Steps to Reproduce: 1. Install vmware workstation 9.0.1 2. run vmware 3. Actual Results: "C header files matching your running kernel were not found. Refer to your distributor's documentation for installation instructions" Expected Results: Kernel modules to build -- 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 776221] New: grub legacy: DEFAULT_APPEND and FAILSAFE_APPEND are not preferred to "it try to figure out old parameters"
by bugzilla_noreply＠novell.com 13 Mar '13

13 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=776221 https://bugzilla.novell.com/show_bug.cgi?id=776221#c0 Summary: grub legacy: DEFAULT_APPEND and FAILSAFE_APPEND are not preferred to "it try to figure out old parameters" Classification: openSUSE Product: openSUSE 12.2 Version: RC 1 Platform: PC OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: mrmazda(a)earthlink.net QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Each YaST2/perl-Bootloader-generated menu.lst includes this text: "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" It should be the other way around when stanzas for new kernels are created at their installation time. Whatever is specified by DEFAULT_APPEND and FAILSAFE_APPEND (probably *_APPEND, but I've never needed the others) should be on the new kernel lines exactly as to both included parameters and parameter order, including whitespace. I want to see in the GFXmenu edit field exactly what I put in bootloader, so that my keystrokes and potential for mistakes for common boot time edits are minimized. The runlevel integer and one space need to be last so that my most commonly used edit initializes with only two backspaces, so that I can add a new parameter without starting with a space, and so that my second most common edits, changing vga= and/or video= can be initialized with only 3 keystrokes. I was able to get that by setting DEFAULT_VGA and FAILSAFE_VGA to null after initial activities to bug 643984, but this stopped working early in 12.2 development (not just recently in RC1, the earliest option Bugzilla's "found in version" allows me). To reproduce: 1-set in /etc/sysconfig/bootloader: ... DEFAULT_APPEND="ipv4only=1 CPUFREQ=off noresume splash=verbose vga=794 video=1152x864@60 3 " FAILSAFE_APPEND="ipv4only=1 CPUFREQ=off apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=794 3 " ... 2-install new kernel Actual results: 1-new default kernel stanza: kernel /boot/vmlinuz-3.4.6-1.1-desktop root=/dev/disk/by-label/11suse122 showopts ipv4only=1 CPUFREQ=off noresume splash=verbose video=1152x864@60 3 vga=794(EOL) 2-new failsafe kernel stanza: kernel /boot/vmlinuz-3.4.6-1.1-desktop root=/dev/disk/by-label/11suse122 showopts ipv4only=1 CPUFREQ=off apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe 3 vga=794(EOL) Expected results: 1-new default kernel stanza: kernel /boot/vmlinuz-3.4.6-1.1-desktop root=/dev/disk/by-label/11suse122 ipv4only=1 CPUFREQ=off noresume splash=verbose vga=794 video=1152x864@60 3 (EOL) 2-new failsafe kernel stanza: kernel /boot/vmlinuz-3.4.6-1.1-desktop root=/dev/disk/by-label/11suse122 ipv4only=1 CPUFREQ=off apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=794 3 (EOL) Comments: 1-showopts is missing from my DEFAULT_APPEND and FAILSAFE_APPEND because YaST2/perl-Bootloader insist it fall after root=, so I put it where I want it in front of root= for both after new kernel installation is complete. 2-bug 754332 noted, but I won't be using Grub2 before it matures well beyond genuine v1.0 aka 2.0. -- 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 663749] New: Boot Loader Settings Section Management - allow multiple concurrent selections via shift-LMB/ctrl-LMB
by bugzilla_noreply＠novell.com 13 Mar '13

13 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=663749 https://bugzilla.novell.com/show_bug.cgi?id=663749#c0 Summary: Boot Loader Settings Section Management - allow multiple concurrent selections via shift-LMB/ctrl-LMB Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: All OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mrmazda(a)earthlink.net QAContact: jsrain(a)novell.com Found By: --- Blocker: --- example: On Boot Loader Settings Section Management tab, 25 proposed Grub stanzas are displayed. All except openSUSE 11.4M5 and Failsafe 11.4M5 need to be deleted. Current behavior: 1-Each unwanted stanza must be selected, deleted, confirmed, 69 LMBs in all, spread over widely varying areas, taking much time and arthritic wrist/finger aggravation. 2-On deletion, neither selection adjacent to the deleted section remains selected. Wanted behavior (same as typical X DTEs and web browsers in select lists): A: 1-LMB on 2nd stanza 2-shift-LMB on next to last stanza 3-LMB on delete 4-LMB on confirm summary: 4 clicks total to eliminate 23 unwanted stanzas B: After any deletion, a selection adjacent to the just deleted section is selected, preferably the one below/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 10

[Bug 643984] New: want option to have no vga= on default kernel line in menu.lst at initial installation
by bugzilla_noreply＠novell.com 13 Mar '13

13 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=643984 https://bugzilla.novell.com/show_bug.cgi?id=643984#c0 Summary: want option to have no vga= on default kernel line in menu.lst at initial installation Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: All OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Bootloader AssignedTo: jreidinger(a)novell.com ReportedBy: mrmazda(a)earthlink.net QAContact: jsrain(a)novell.com Found By: --- Blocker: --- from: https://bugzilla.novell.com/show_bug.cgi?id=620434#c19 > > > Also I want runlevel number as last item on Grub kernel lines. I would expect > > > separate vga= configuration line must be null in my /etc/sysconfig/bootloader > > > for that to happen. On fresh install this cannot happen because there is no way > > > in installation to specify no vga config. > > > Also still problem is that it is hardcoded, so it is not easy way to do. > > Again, hardcoded where? It seems to me during installation select list could > also have additional option to make vga=normal not result on default kernel > cmdline made by perl-Bootloader. Yes, it sounds reasonable. Could you please open separate bug report to easier track as it is out of context of this bug report? Thanks -- 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 20