openSUSE Bugs April 2011

bugs@lists.opensuse.org

1 participants
5537 discussions

[Bug 679584] New: I have a AUTO noticifation after configuring kerberos as new LDAP server
by bugzilla_noreply＠novell.com 01 Apr '11

01 Apr '11

https://bugzilla.novell.com/show_bug.cgi?id=679584 https://bugzilla.novell.com/show_bug.cgi?id=679584#c0 Summary: I have a AUTO noticifation after configuring kerberos as new LDAP server Classification: openSUSE Product: openSUSE 11.3 Version: RC 2 Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: AutoYaST AssignedTo: ug(a)novell.com ReportedBy: qwatli(a)yahoo.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.6) Gecko/20100626 SUSE/3.6.6-1.2 Firefox/3.6.6 Dear friend I have an Error appear when I finished kerberos SERVER told me: (Use of uninitialized value $value in numeric eq (==) at /usr/share/YaST2/modules/LdapServer.pm line 1335 (#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 and 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. Use of uninitialized value $hashAlgo in string eq at /usr/share/YaST2/modules/LdapServer.pm line 2606 (#1) Use of uninitialized value in subroutine entry at /usr/lib/perl5/vendor_perl/5.12.1/x86_64-linux-thread-multi/YaST/YCP.pm line 423 (#1) YaST got signal 6 at YCP file kerberos-server/complex.ycp:2 /sbin/yast2: line 399: 8307 Aborted $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS ) it's my first time I found this Error and as you see it's a technical issue and I can't run kerberos as usually thanks in advance BR Reproducible: Always Steps to Reproduce: 1.kerberos never run and 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 4

[Bug 683582] New: rpmdb PANIC
by bugzilla_noreply＠novell.com 01 Apr '11

01 Apr '11

https://bugzilla.novell.com/show_bug.cgi?id=683582 https://bugzilla.novell.com/show_bug.cgi?id=683582#c0 Summary: rpmdb PANIC Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86 OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ludvigbakos(a)gmail.com QAContact: jsrain(a)novell.com Found By: Other Blocker: --- Yast was not able to install it the fresh packages! --------------------------------------------------- Subprocess failed. Error: RPM sikertelen: rpmdb: PANIC: Invalid argument rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from dbcursor->c_put: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) storing record libc.so.6(GLIBC_2.2) into Requirename rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libc.so.6(GLIBC_2.3.4)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libc.so.6(GLIBC_2.4)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libgdk-x11-2.0.so.0" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libgdk_pixbuf-2.0.so.0" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libglib-2.0.so.0" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libgobject-2.0.so.0" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libgtk-x11-2.0.so.0" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "liblcms.so.1" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libm.so.6" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libm.so.6(GLIBC_2.0)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libm.so.6(GLIBC_2.1)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libpango-1.0.so.0" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libpthread.so.0" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libpthread.so.0(GLIBC_2.0)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Providename index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Dirnames index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Requireversion index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Provideversion index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Installtid index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Sigmd5 index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Sha1header index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Filedigests index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error, run database recovery -- 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 683082] New: Education/SLE-11-SP1 GnuPG key is expired
by bugzilla_noreply＠novell.com 01 Apr '11

01 Apr '11

https://bugzilla.novell.com/show_bug.cgi?id=683082 https://bugzilla.novell.com/show_bug.cgi?id=683082#c0 Summary: Education/SLE-11-SP1 GnuPG key is expired Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: is(a)lft.uni-erlangen.de QAContact: adrian(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.16) Gecko/20110319 Firefox/3.6.16 Hello, I would add the following repository for a linux system: http://download.opensuse.org/repositories/Education/SLE-11-SP1 The system notify me that the GnuPG key for this repository is expired: --- ID: C6D1B74AC0951497 Fingerprint: 703D 37BF 0782 3426 FF9F 7960 C6D1 B74A C095 1497 Name: Education OBS Project <Education(a)build.opensuse.org> Created: 01/22/08 Expires: 04/01/10 --- Could you update the GnuPG Key for this repository? Kind regards, is 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 684334] New: flash-player malfunctions after update to 10.2.153.1-0.4.1
by bugzilla_noreply＠novell.com 01 Apr '11

01 Apr '11

https://bugzilla.novell.com/show_bug.cgi?id=684334 https://bugzilla.novell.com/show_bug.cgi?id=684334#c0 Summary: flash-player malfunctions after update to 10.2.153.1-0.4.1 Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: d.dewey(a)caprus.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13 I recall that yesterday's updates to my 11.4 KDE included an update of Flash Player to 10.2.135.1-0.4.1 Until that update I'd had no problems using Chrome and Flash, but now I've just gone to a page that contains a small Flash element. When the page closes the element remains on screen and shows on top of any portion of any window that does not contain either a graphic or a background color. Problem is very similar with Firefox. Only way I can recover is init 3 then init 5 I just rolled back my flash-player to 10.2.152.26-2.1 and my browsers are behaving fine again. Reproducible: Always Steps to Reproduce: 1.update flash-update to 10.2.153.1-0.4.1 2.browse to www.broadvoice.com 3.browse to other sites, ex. forums.opensuse.org Actual Results: When the first page closes the element remains on screen and shows on top of any portion of any window that does not contain either a graphic or a background color. Expected Results: No artifacts should remain when new page loads I just rolled back my flash-player to 10.2.152.26-2.1 and my browsers are behaving fine again. OpenSUSE 11.4, KDE 4.6, Chrome 9.0.597.107, Firefox 4.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 4

[Bug 683751] New: Desktop API is not supported on the current platform
by bugzilla_noreply＠novell.com 01 Apr '11

01 Apr '11

https://bugzilla.novell.com/show_bug.cgi?id=683751 https://bugzilla.novell.com/show_bug.cgi?id=683751#c0 Summary: Desktop API is not supported on the current platform Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: i686 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Java AssignedTo: bnc-team-java(a)forge.provo.novell.com ReportedBy: johannes.mueller(a)troeber.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0.0) Gecko/20100101 Firefox/4.0 We are trying to run a java applet in Firefox (4.0) or Konqueror, which should open a new window with desired information. The new window doesn't open and we get this error on the java console: --------- UNCAUGHT EXCEPTION --------- 21.2.2011 13:49:18 java.lang.UnsupportedOperationException: Desktop API is not supported on the current platform at java.awt.Desktop.getDesktop(Desktop.java:126) at start.start.showTrackingPage(start.java:2895) at start.start.setSearchResults(start.java:3145) at tools.AS400_Connection.transmittData(AS400_Connection.java:283) at tools.AS400_Connection.run(AS400_Connection.java:241) at java.lang.Thread.run(Thread.java:662) -------------------------------------- Reproducible: Always Steps to Reproduce: 1. Load java applet 2. Click on a detail position to run the tracking information Expected Results: Should open a new window with redirect to the tracking provider. Works so far on OpenSuSE 11.2 and OpenSuSE 11.3. Also works on any Windows Systems (XP or 7). I guess its related to KDE 4.6. -- 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 683109] New: home:repabuild: Bug blender 2.56.34784-109.2
by bugzilla_noreply＠novell.com 01 Apr '11

01 Apr '11

https://bugzilla.novell.com/show_bug.cgi?id=683109 https://bugzilla.novell.com/show_bug.cgi?id=683109#c0 Summary: home:repabuild: Bug blender 2.56.34784-109.2 Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: SLED 11 Status: NEW Severity: Critical Priority: P5 - None Component: 3rd party software AssignedTo: Rene.vanPaassen(a)gmail.com ReportedBy: is(a)lft.uni-erlangen.de QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: Customer Blocker: --- Hello, I've installed the blender package (2.56.34784-109.2) from the repository http://download.opensuse.org/repositories/home:/repabuild/SLE_11_SP1 After I try the start blender from konsole I get the following message --- Info: Config directory with "startup.blend" file not found. Xlib: extension "NV-GLX" missing on display "notebook:0.0". ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:3532:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:3532:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name ALSA lib conf.c:3532:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:4004:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2205:(snd_pcm_open_noupdate) Unknown PCM default AL lib: alsa.c:512: Could not open playback device 'default': No such file or directory AL lib: oss.c:169: Could not open /dev/dsp: No such file or directory Could not find platform independent libraries <prefix> Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>] Fatal Python error: Py_Initialize: can't initialize sys standard streams ImportError: No module named encodings.utf_8 Aborted --- The older blender version 2.49b9.7 has worked very well, but is not longer available from the repository: http://download.opensuse.org/repositories/home:/repabuild/SLE_11_SP1 Kind regards, 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 578843] New: intel [G33]: openarena too dark with KMS
by bugzilla_noreply＠novell.com 01 Apr '11

01 Apr '11

http://bugzilla.novell.com/show_bug.cgi?id=578843 http://bugzilla.novell.com/show_bug.cgi?id=578843#c0 Summary: intel [G33]: openarena too dark with KMS Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: jslaby(a)novell.com QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- When I switch to KMS when migrating from 11.2 to 11.3 factory, openarena is dark. I need to use /r_overbrightBits 0 and still the output is ugly and darker than in 11.2. -- 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 33

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs April 2011