openSUSE Bugs October 2013

bugs@lists.opensuse.org

1 participants
4307 discussions

[Bug 842979] VUL-0: mozilla-nss: CVE-2013-1739: 3.15.2 security fix (CVE-2013-1739)
by bugzilla_noreply＠novell.com 01 Oct '13

01 Oct '13

https://bugzilla.novell.com/show_bug.cgi?id=842979 https://bugzilla.novell.com/show_bug.cgi?id=842979#c Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |obs:running:2046:moderate -- 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 831790] New: RF kill switch and LCD backlight don't work on HP EliteBook 8470p
by bugzilla_noreply＠novell.com 01 Oct '13

01 Oct '13

https://bugzilla.novell.com/show_bug.cgi?id=831790 https://bugzilla.novell.com/show_bug.cgi?id=831790#c0 Summary: RF kill switch and LCD backlight don't work on HP EliteBook 8470p Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: adrien.clerc(a)gls-france.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 With an out of the box installation of openSuse 12.3, the kill switch for WiFi and LCD backlight don't work. According to http://comments.gmane.org/gmane.linux.kernel/1421265 The ACPI table is wrong (once again). Adding acpi_osi="!Windows 2012" on kernel command line solved the issue. Incidentally, the Bootloader YaST configuration fails to update with this parameter, I had to add it manually. 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 13

[Bug 813306] New: glibc 2.17 fprintf(stderr, ...) triggers write of undefined values if stderr is closed
by bugzilla_noreply＠novell.com 01 Oct '13

01 Oct '13

https://bugzilla.novell.com/show_bug.cgi?id=813306 https://bugzilla.novell.com/show_bug.cgi?id=813306#c0 Summary: glibc 2.17 fprintf(stderr, ...) triggers write of undefined values if stderr is closed Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: tr(a)thomasrast.ch QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=533396) --> (http://bugzilla.novell.com/attachment.cgi?id=533396) Test case; run with stderr closed under valgrind or strace User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130307 Firefox/17.0 conkeror/1.0pre Running the attached small program under valgrind causes a bunch of errors about undefined values: $ gcc -o die_test die_test.c $ valgrind -q --log-fd=3 ./die_test 3>&2 2>&- ==27895== Conditional jump or move depends on uninitialised value(s) ==27895== at 0x4EA864B: _IO_file_overflow@@GLIBC_2.2.5 (in /lib64/libc-2.17.so) ==27895== by 0x4EA93D8: _IO_default_xsputn (in /lib64/libc-2.17.so) ==27895== by 0x4EA7AA2: _IO_file_xsputn@@GLIBC_2.2.5 (in /lib64/libc-2.17.so) ==27895== by 0x4E7D133: buffered_vfprintf (in /lib64/libc-2.17.so) ==27895== by 0x4E77E9D: vfprintf (in /lib64/libc-2.17.so) ==27895== by 0x4E82096: fprintf (in /lib64/libc-2.17.so) ==27895== by 0x4005C2: main (in /home/thomas/BIG/tmp/die_test) ==27895== ==27895== Syscall param write(buf) points to uninitialised byte(s) ==27895== at 0x4F0C9C0: __write_nocancel (in /lib64/libc-2.17.so) ==27895== by 0x4EA71D2: _IO_file_write@@GLIBC_2.2.5 (in /lib64/libc-2.17.so) ==27895== by 0x4EA70B1: new_do_write (in /lib64/libc-2.17.so) ==27895== by 0x4EA83B4: _IO_do_write@@GLIBC_2.2.5 (in /lib64/libc-2.17.so) ==27895== by 0x4EA86FE: _IO_file_overflow@@GLIBC_2.2.5 (in /lib64/libc-2.17.so) ==27895== by 0x4EA93D8: _IO_default_xsputn (in /lib64/libc-2.17.so) ==27895== by 0x4EA7AA2: _IO_file_xsputn@@GLIBC_2.2.5 (in /lib64/libc-2.17.so) ==27895== by 0x4E7D133: buffered_vfprintf (in /lib64/libc-2.17.so) ==27895== by 0x4E77E9D: vfprintf (in /lib64/libc-2.17.so) ==27895== by 0x4E82096: fprintf (in /lib64/libc-2.17.so) ==27895== by 0x4005C2: main (in /home/thomas/BIG/tmp/die_test) ==27895== Address 0x51d9103 is 131 bytes inside data symbol "_IO_2_1_stderr_" Also, running the program with strace shows this immediately before exiting (make sure stderr is again closed): write(2, "fatal: needed a single revision\n", 32) = -1 EBADF (Bad file descriptor) write(2, "\0", 1) = -1 EBADF (Bad file descriptor) exit_group(0) = ? +++ exited with 0 +++ The fprintf() call is actually of the sort that 'git rev-parse --verify foo' runs immediately before exiting, which is how I noticed. I can't see how that could (attempt to) write a "\0". Thus it seems to be an issue with the handling of that EBADF in the implementation details of fprintf(). (I know that closing stderr isn't exactly the most brilliant idea, and I'm working on fixing that.) Reproducible: Always $ rpm -q gcc glibc gcc-4.7-7.1.1.x86_64 glibc-2.17-4.4.1.x86_64 -- 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 819524] New: nscd segfault
by bugzilla_noreply＠novell.com 01 Oct '13

01 Oct '13

https://bugzilla.novell.com/show_bug.cgi?id=819524 https://bugzilla.novell.com/show_bug.cgi?id=819524#c0 Summary: nscd segfault Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: openSUSE 12.3 Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: twild(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: System Test Blocker: No nscd[2320]: segfault at 0 ip 00007f911bd87741 sp 00007f910e202188 error 4 in libc-2.17.so[7f911bc38000+1a3000] I get frequently the error in syslog files: nscd[2320]: segfault at 0 ip 00007f911bd87741 sp 00007f910e202188 error 4 in libc-2.17.so fortunately the systemd re-spawns the nscd immediately. After my quick core dump analysis I'm quite sure that the problem comes from: glibc-2.17-4.4.1, nscd netgroupcache.c in line 205: size_t userlen = strlen (nuser) + 1; <------ core dump because nuser in the triple code is 0 in case of (host,,) entries in NIS! This may causes the core dump. I found two work arounds to avoid a nscd crash: 1.) switch off netgroup in nscd.conf enable-cache netgroup yes -> no or 2.) in NIS change entries in netgroup (host,,) -> (host,-,<youdomain> regards Thomas -- 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 824046] New: glibc: blacklist code in bindresvport doesn't release lock, results in double-lock
by bugzilla_noreply＠novell.com 01 Oct '13

01 Oct '13

https://bugzilla.novell.com/show_bug.cgi?id=824046 https://bugzilla.novell.com/show_bug.cgi?id=824046#c0 Summary: glibc: blacklist code in bindresvport doesn't release lock, results in double-lock Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: aj(a)suse.com ReportedBy: jeffm(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Development Blocker: --- Created an attachment (id=543388) --> (http://bugzilla.novell.com/attachment.cgi?id=543388) [PATCH] Updated glibc-2.3.90-bindresvport.blacklist.diff This issue was originally reported in bnc#799496, but I incorrectly diagnosed it as a bug in the linuxrc open-coded NFS routines. It turns out that the bindresvport() futex hang was the issue all along. The issue is that in glibc 2.17 (http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=f6da27e53695ad1cc0e2a…) introduced a lock to make bindresvport() threadsafe. The blacklist code was altered to handle it, but the locking was only added at the beginning and end of the function and it returns from two other places. As a result, the lock wasn't released and when bindresvport takes the lock itself, it hangs due to the double locking condition. I have a fix already worked up. It also handles a race condition in the original patch where the blacklist_read variable could be set to 1 between the test and the lock acquisition, producing undesired results. I would have just issued a submit request with the fix but OBS seems to be unresponsive tonight. -- 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 819383] New: pldd a process multiple times can freeze the process
by bugzilla_noreply＠novell.com 01 Oct '13

01 Oct '13

https://bugzilla.novell.com/show_bug.cgi?id=819383 https://bugzilla.novell.com/show_bug.cgi?id=819383#c0 Summary: pldd a process multiple times can freeze the process Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: yjcoshc(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.32 (KHTML, like Gecko) Chrome/27.0.1425.0 Safari/537.32 SUSE/27.0.1425.0 When I used pldd to show loading shared objects of a running process for multiple times, the process stopped (or freezed), and sent SIGCONT can make it continue to run. Reproducible: Sometimes Steps to Reproduce: 1.Open a terminal emulator, for example konsole. 2.ps aux|grep konsole, and remember the pid of it. 3.pldd <pid> |grep lib. 4.repeat step 3 multiple times(maybe more than twenty). Actual Results: The konsole window is freezed. You can send SIGCONT to make it continue to run. Expected Results: No matter how many times we execute pldd, the process shouldn't be freezed. -- 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 23

[Bug 805054] New: man 1 locale mentions nonexistant file
by bugzilla_noreply＠novell.com 01 Oct '13

01 Oct '13

https://bugzilla.novell.com/show_bug.cgi?id=805054 https://bugzilla.novell.com/show_bug.cgi?id=805054#c0 Summary: man 1 locale mentions nonexistant file Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jw(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- man 1 locale has this: Files: /usr/share/i18n/SUPPORTED List of supported values (and their associated encoding) for the locale name. This representation is recommended over --all-locales one, due being the system wide supported values. This file appears to be missing. -- 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

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs October 2013