February 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 802529] New: bootloader does not set video=
by bugzilla_noreply＠novell.com 07 Feb '13

07 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=802529 https://bugzilla.novell.com/show_bug.cgi?id=802529#c0 Summary: bootloader does not set video= Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: All OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: bwiedemann(a)suse.com QAContact: jsrain(a)suse.com CC: snwint(a)suse.com, mchang(a)suse.com, arvidjaar(a)gmail.com Found By: Development Blocker: --- in kvm, text console uses a too high resolution of 1280x1024 which does not fit on my netbook's display of 1024x600, but yast2 bootloader will only set resolution for grub2 itself and even adds a vga=0x314 which does not do anything in this case but does not add a video=800x600-16 line which would do something -- 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 802600] New: cron segfault in libc
by bugzilla_noreply＠novell.com 07 Feb '13

07 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=802600 https://bugzilla.novell.com/show_bug.cgi?id=802600#c0 Summary: cron segfault in libc Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rmilasan(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- I've just installed openSUSE 12.3 RC1 KDE Live and I'm seeing in dmesg a lot of segfaults from cron: [ 275.853963] cron[1247]: segfault at 0 ip 00007f12d2fe06e1 sp 00007ffffd1e7d70 error 4 in libc-2.17.so[7f12d2f6d000+1a3000] [ 1175.878594] cron[1316]: segfault at 0 ip 00007f12d2fe06e1 sp 00007ffffd1e7d70 error 4 in libc-2.17.so[7f12d2f6d000+1a3000] I've enabled debugging in cron and set it to cron -x ext (but not sure which option is the best). -- 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 727348] New: when using pulseaudio unmuting the master volume is not possible via kmix
by bugzilla_noreply＠novell.com 07 Feb '13

07 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=727348 https://bugzilla.novell.com/show_bug.cgi?id=727348#c0 Summary: when using pulseaudio unmuting the master volume is not possible via kmix Classification: openSUSE Product: openSUSE 12.1 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound AssignedTo: tiwai(a)suse.com ReportedBy: jdsn(a)suse.com QAContact: qa(a)suse.de Found By: Product Management Blocker: --- In openSUSE 12.1 RC1 using pulseaudio and KDE it is no possible to "unmute" the master volume after it was muted with Kmix. Once the master channel is muted it is not possible to enable sound via Kmix. I don't know wheter the bug is in Kmix or pulseaudio. The workaround is to unmute it using alsamixer on the commandline. --------------- This is the sound device that was used: $ hwinfo --sound 15: PCI 1b.0: 0403 Audio device [Created at pci.319] Unique ID: u1Nb.F9GrCco9uN5 SysFS ID: /devices/pci0000:00/0000:00:1b.0 SysFS BusID: 0000:00:1b.0 Hardware Class: sound Model: "Intel 5 Series/3400 Series Chipset High Definition Audio" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x3b56 "5 Series/3400 Series Chipset High Definition Audio" SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x3b56 Revision: 0x06 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xc0520000-0xc0523fff (rw,non-prefetchable) IRQ: 48 (1878 events) Module Alias: "pci:v00008086d00003B56sv00008086sd00003B56bc04sc03i00" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=yes, avail=yes, need=no, active=unknown -- 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 802625] New: Crash kernel size limitations cause dumps on large systems to fail
by bugzilla_noreply＠novell.com 07 Feb '13

07 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=802625 https://bugzilla.novell.com/show_bug.cgi?id=802625#c0 Summary: Crash kernel size limitations cause dumps on large systems to fail Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: lisa.mitchell(a)hp.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; GTB7.4; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.0.30729; .NET CLR 1.0.3705; .NET CLR 1.1.4322; .NET CLR 3.5.30729; InfoPath.2) I have filed a bugzilla about this to SLES11SP3, and this bugzilla is to get this user space code solution we want, makedumpfile v1.5.1 into Open SUSE release for the exposure it needs before it can be taken into a SLES release. The current SLES11SP2 shipping version of makedumpfile makes a bitmap of all the memory in the system, which requires 64 MB per each terabyte of system memory. As memory size increases, this means the crashkernel size must increase to contain this bit map. For a 12 TB system, this means the bitmap must be 768 MB in size to dump this memory. With at least 128 MB needed for the kernel (and with various IO, driver configurations, we've seen the kernel take up more space), this would require crashkernel sizes greater than 896 MB to get a successful dump of this memory size. On upstream kernel versions 3.3 later, crashkernel sizes are now limited to less than 512 MB, due to a page table allocation now required at 512MB which bisects the space the crashkernel can occupy. See https://lkml.org/lkml/2012/3/13/372 https://lkml.org/lkml/2012/3/13/36 This clearly will not be enough to allow a dump to succeed for a 12 TB system. We have also seen indications that greater than 1 GB crashkernel sizes are needed for certain configurations of our largest DL980 systems with 4 TB memory, and certain IO cards or file system types that use a lot of kernel memory. We have been testing a new upstream version of makedumpfile, makedumpfile v1.5.1, which uses a fixed amount of memory. The new version employs a cyclic buffer size to cycle through all the memory to do its job, and this will allow the crashkernel to remain at a fixed size below the 512 MB maximum, and still be able to successfully dump arbitrarily large memory sizes. We have done tests with this new version of makedumpfile on a DL980 on with 4 TBytes of memory, and and were able to successfully dump systems with crashkernel sizes of 256 to 386 MB, on kernel versions of 3.3 and 2.6.32. Therefore, we request that the new makedumpfile, v1.5.1, be incorporated in SLES11SP3 the best solution for scaling dumps to 12 TB and beyond, and for preventing dumps in our largets configurations of the DL980 from failing due to lack of memory. The following link gives the source of the upstream posted makedumpfile v1.5.1 command: http://lists.infradead.org/pipermail/kexec/2012-December/007460.html As part of the request, there is also a kernel patch that is submitted upstream that we would request as part of this SLES11SP3 solution, as it improves performance with this new makedumpfile, so that there is no regression in dump times. https://lkml.org/lkml/2012/11/21/90 Reproducible: Didn't try Steps to Reproduce: 1.Install a DL980 with 4 TB, SLES11SP2 and maximum IO cards, with Fusion cards or VXVM/VXFS root file system from Symantec, installed later 2.If version 3.3 kernel is applied crashkernel max is less than 512 MB, if SLES11SP2 is applied 896 MB is the max. 3.Configure max crashkernel size, and trigger a dump Actual Results: The dump will fail due to out of memory while makedumpfile attempts to create the bitmap. Expected Results: The dump should complete successfully. -- 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 802060] New: autoyast installation shows empty screen with iscsi-initiator
by bugzilla_noreply＠novell.com 07 Feb '13

07 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=802060 https://bugzilla.novell.com/show_bug.cgi?id=802060#c0 Summary: autoyast installation shows empty screen with iscsi-initiator Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: 64bit OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST AssignedTo: fehr(a)suse.com ReportedBy: thorsten.staerk(a)sap.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 The following lines cause an autoyast installation to fail and show an empty screen: <iscsi-client> <initiatorname></initiatorname> <targets config:type="list"/> <version>1.0</version> </iscsi-client> I have created two autoinst.xml, one does not work: https://raw.github.com/tstaerk/autoinst/fa93c9da57d6fd9f98d65b0cd077549d959… and one works: https://raw.github.com/tstaerk/autoinst/c7086f2129e92f2cd00f35c1fb6883c3497… Reproducible: Always Steps to Reproduce: 1.use a VirtualBox virtual machine 2.get autoinst.xml from https://raw.github.com/tstaerk/autoinst/fa93c9da57d6fd9f98d65b0cd077549d959… 3.start the installation Actual Results: you see an empty screen Expected Results: system is installed automatically -- 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 802371] New: YaST2 users cmdline error
by bugzilla_noreply＠novell.com 07 Feb '13

07 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=802371 https://bugzilla.novell.com/show_bug.cgi?id=802371#c0 Summary: YaST2 users cmdline error Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: jsuchome(a)suse.com ReportedBy: msvec(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- bash# yast2 users add username=somebody uid=12345 Use of uninitialized value $initial_skip in concatenation (.) or string at /usr/lib/perl5/vendor_perl/5.16.0/Parse/RecDescent.pm line 3054 (#1) (W uninitialized) An undefined value was used as if it were already defined. It was interpreted as a "" or a 0, but maybe it was a mistake. To suppress this warning assign a defined value to your variables. To help you figure out what was undefined, perl will try to tell you the name of the variable (if any) that was undefined. In some cases it cannot do this, so it also tells you what operation you used the undefined value in. Note, however, that perl optimizes your program anid the operation displayed in the warning may not necessarily appear literally in your program. For example, "that $foo" is usually optimized into "that " . $foo, and the warning will refer to the concatenation (.) operator, even though there is no . in your program. -- 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 802549] New: On UEFI system, upon booting from installation media, grub has issues with interface
by bugzilla_noreply＠novell.com 07 Feb '13

07 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=802549 https://bugzilla.novell.com/show_bug.cgi?id=802549#c0 Summary: On UEFI system, upon booting from installation media, grub has issues with interface Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: mpluskal(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=523716) --> (http://bugzilla.novell.com/attachment.cgi?id=523716) screenshot When booting from installation media on UEFI machine (or virtualbox with UEFI enabled), grub apparently has issues with interface (console detection not working properly?). See attached screenshot. -- 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 764524] getbinaries: missing packages: pkgname
by bugzilla_noreply＠novell.com 07 Feb '13

07 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=764524 https://bugzilla.novell.com/show_bug.cgi?id=764524#c7 --- Comment #7 from Michael Schröder <mls(a)suse.com> 2013-02-07 10:41:01 UTC --- Because it was assigned to you before you reassigned it to me with your question in comment #4. You should use NEEDINFO if you ask questions. Anyway, it can appear if the project is misconfigured, i.e. bogus packages in preinstall or something like that. Unfortunately it seems like it can also happen when there's a network error, though I'm not sure if that has been fixed. -- 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 764524] getbinaries: missing packages: pkgname
by bugzilla_noreply＠novell.com 07 Feb '13

07 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=764524 https://bugzilla.novell.com/show_bug.cgi?id=764524#c6 Adrian Schröter <adrian(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|adrian(a)suse.com |mls(a)suse.com --- Comment #6 from Adrian Schröter <adrian(a)suse.com> 2013-02-07 10:33:45 UTC --- So, what can the api do here at all or why do you assign this bug back to me? It is either a backend or a network/setup problem from my POV. Can you please explain the reasons under which circumstances this error can 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 0

[Bug 596732] New: Eject Live-CD from the drive during shutdown
by bugzilla_noreply＠novell.com 07 Feb '13

07 Feb '13

http://bugzilla.novell.com/show_bug.cgi?id=596732 http://bugzilla.novell.com/show_bug.cgi?id=596732#c0 Summary: Eject Live-CD from the drive during shutdown Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Enhancement Priority: P5 - None Component: Live Medium AssignedTo: coolo(a)novell.com ReportedBy: wizard160888(a)mail.ru QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (Windows NT 6.1; U; ru) Presto/2.5.22 Version/10.51 Eject Live-CD from the drive during shutdown. Or unlock the drive, that would-Live-CD can be obtained after restart. In Ubuntu (for example) during shutdown with the Live-CD ejects and is expected to pressing "Enter". Reproducible: Always Steps to Reproduce: 1. Restart your computer with your openSUSE Live-CD -- 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 7