October 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 533243] New: After starting YaST LDAP server, during initialization get error
by bugzilla_noreply＠novell.com 29 Jul '13

29 Jul '13

http://bugzilla.novell.com/show_bug.cgi?id=533243 Summary: After starting YaST LDAP server, during initialization get error Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: aliks-os(a)yandex.ru QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/530.5 (KHTML, like Gecko) Chrome/2.0.172.31 Safari/530.5 After starting YaST LDAP server, during initialization get error Error while enabling LDAPI listener Enabling thi LDAPI Protocol listener failed And after that YaST LDAP-SERVER closing. Meantime, ldap server working fine, accessable from local and remote machne. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 16

[Bug 498345] New: ld.so segfaults on /lib/modules/.../vdso.so
by bugzilla_noreply＠novell.com 09 Jul '13

09 Jul '13

http://bugzilla.novell.com/show_bug.cgi?id=498345 Summary: ld.so segfaults on /lib/modules/.../vdso.so Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: pbaudis(a)novell.com ReportedBy: mmarek(a)novell.com QAContact: qa(a)suse.de Found By: --- During kernel build, something runs ldd on the vdso.so binary, which results in a segfault in ld.so. Can be reproduced in the live system too: $ ldd /lib/modules/2.6.27.21-0.1-default/vdso/vdso.so ldd: exited with unknown exit code (139) $ /lib64/ld-linux-x86-64.so.2 --verify /lib/modules/2.6.27.21-0.1-default/vdso/vdso.so Segmentation fault -- 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 6

[Bug 549447] New: Able to ping, no DNS
by bugzilla_noreply＠novell.com 09 Jul '13

09 Jul '13

http://bugzilla.novell.com/show_bug.cgi?id=549447 Summary: Able to ping, no DNS Classification: openSUSE Product: openSUSE 11.2 Version: RC 1 Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: chusty(a)attglobal.net QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-3.1 Firefox/3.5.3 1. able to ping 2. firefox does not work 3. no repositories available. 4. resolve.conf is blank 5. if in firefox <about:config> and set network.dns.disableIPv6 to true then firefox work. Then I set it back to false as default. 6. Now yast/network devices/network setting/Hostname-DNS and I add the DNS from the router then all is back to normal. 7. resolve.conf ### /etc/resolv.conf file autogenerated by netconfig! # # Before you change this file manually, consider to define the # static DNS configuration using the following variables in the 8. Remove the DNS from the Hostname-DNS field and firefox does not work and the resolve.conf files is blanc again. There is a similar problem under Bug 546213 but I think there are difference. I reported what looks like the same problem under opensuse 11.1 The solution there was perfect. Here are bug reported under 11.1 which I believe is the same. Bug 463015 - Able to ping unable to connect Bug 441947 - getaddrinfo() breaks when resolv.conf points at buggy nameservers Reproducible: Always Steps to Reproduce: 1.able to ping. firefox unable to connect 2.if I change to true <network.dns.disableIPv6> in firefox, it works. 3.If I add DNS servers to the network device everything work Under opensuse 11.1 the problem was resolved replacing glibc. -- 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 20

[Bug 533274] New: Make filters work on expanded packages
by bugzilla_noreply＠novell.com 08 Jul '13

08 Jul '13

http://bugzilla.novell.com/show_bug.cgi?id=533274 Summary: Make filters work on expanded packages Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Hermes AssignedTo: freitag(a)novell.com ReportedBy: vuntz(a)novell.com QAContact: adrian(a)novell.com Found By: --- I'm sure I'm right, but I think a filter like "files regexp *.spec" won't work if the package that has changed is a link package. Is this something that we could fix? (My rationale is that the hermes message will contain "added file: project.diff" and so hermes doesn't see that project.diff changes the .spec file) -- 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 6

[Bug 533273] New: Missing documentation for many things (hard to use the expert interface)
by bugzilla_noreply＠novell.com 08 Jul '13

08 Jul '13

http://bugzilla.novell.com/show_bug.cgi?id=533273 Summary: Missing documentation for many things (hard to use the expert interface) Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Hermes AssignedTo: freitag(a)novell.com ReportedBy: vuntz(a)novell.com QAContact: adrian(a)novell.com Found By: --- It's really hard to use the expert interface in hermes because a lot of settings are unclear and not documented. Here's a first list of things: + some message types are unclear. For example, what's the difference between "File upload", "Source commit", and "Package data updated"? + it's not clear what kind of regexp should be used. Apparently, it's perl regexp (since hermes is in perl), so mentioning it somewhere would be nice (with a link to some perl doc, I guess) + I have no clue what some filters are: rm? _type? There might be more. + when oneof or containsitem is used, what is the syntax that should be used? + does the digest mode mean "include everything since the previous minute/hour/day"? -- 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 4

[Bug 522660] New: more information in package change / project change / package updated requests
by bugzilla_noreply＠novell.com 08 Jul '13

08 Jul '13

http://bugzilla.novell.com/show_bug.cgi?id=522660 Summary: more information in package change / project change / package updated requests Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Hermes AssignedTo: freitag(a)novell.com ReportedBy: meissner(a)novell.com QAContact: adrian(a)novell.com CC: coolo(a)novell.com, mls(a)novell.com Found By: Development We need more information in the package / project changed and updated request. This is two parts: - bs_srcserver needs to send more information to Hermes - Hermes template needs to include this data. Its probably possible to diff the XML before/after. (not text diff, but some other diff method). -- 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 23

[Bug 542539] New: xsane-0.997-1.5: memory leak
by bugzilla_noreply＠novell.com 05 Jul '13

05 Jul '13

http://bugzilla.novell.com/show_bug.cgi?id=542539 Summary: xsane-0.997-1.5: memory leak Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dcb314(a)hotmail.com QAContact: qa(a)suse.de Found By: --- I just had a look at factory package xsane-0.997-1.5 For source code file xsane-0.997/src/xsane-batch-scan.c around line 691, function xsane_batch_scan_create_list_entry, is the source code data = calloc(size, size); but I fail to find any matching call to free. Further, I find that the local variable "data" is essentially unused in the routine. Suggest delete local variable "data" to remove useless memory leak. -- 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 5

[Bug 515041] New: lirc-0.8.5-1.3:array index out of range
by bugzilla_noreply＠novell.com 05 Jul '13

05 Jul '13

http://bugzilla.novell.com/show_bug.cgi?id=515041 Summary: lirc-0.8.5-1.3:array index out of range Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dcb314(a)hotmail.com QAContact: qa(a)suse.de Found By: --- I just had a look at factory package lirc-0.8.5-1.3 In file lirc-0.8.5/daemons/hw_commandir.c around line 834, is the source code for(i=0;i<MAX_CHANNELS;i++) { next_signalq_per_channel[i] = -1; channels_en[i] = 0xff; but static char channels_en[MAX_DEVICES]; and lirc-0.8.5/daemons/hw_commandir.h:#define MAX_DEVICES 4 lirc-0.8.5/daemons/hw_commandir.h:#define MAX_CHANNELS 16 This looks like broken code because the array channels_en only has four entries, but 16 are written into it. Suggest code rework. -- 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 3

[Bug 527213] New: Updates don't Update
by bugzilla_noreply＠novell.com 30 May '13

30 May '13

http://bugzilla.novell.com/show_bug.cgi?id=527213 Summary: Updates don't Update Classification: openSUSE Product: openSUSE 11.0 Version: Final Platform: i686 OS/Version: openSUSE 11.0 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rfengineer(a)juno.com QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/4.0; Linux) KHTML/4.0.4 (like Gecko) SUSE Both a specific, and a general issue: Occasionally, an update/patch doesn't work. This is not computer specific, as I have 3 boxes all with the same problem right now with the exact same patch/update. The particular box I am on at this instant is configured as follows: ++++++++++++++ CPU: Genuine Intel(R) CPU T2300 @ 1.66GHz Speed: 1,000.00 MHz Cores: 2 Linux 2.6.25.20-0.4-default i686 openSUSE 11.0 (i586) KDE: 4.0.4 (KDE 4.0.4 >= 20080505) "release 15.2" Mozilla Thunderbird version 2.0.0.19 (20081227) Mozilla Firefox 3.0.12 ++++++++++++ The specific issue is an update Mozilla Thunderbird Update 2.0.0.22, which will not complete. It also causes other updates to not complete, unless I uncheck the update for Thunderbird. When checked to complete, the patch will not apply, and will not allow any other patches/updates to apply either. Reproducible: Always Steps to Reproduce: 1.Check for Updates 2."New Software Available" 3.Click "Install" 4.Give Password 5.Returns back to step 2 without installing or applying the new software. Actual Results: Does not install new software, or allow other patches/updates to install. No "don't ever apply this one" option for the operator. Expected Results: Specifically, this patch should be looked into to find the cause of the problem. Perhaps it is a problem with the repository? More generally, though, there should be an OPTION ADDED to allow a specific patch to be deleted from an/or ignored by the patch list (on a permanent basis) by the user at his option if it does not appear to work normally. Of course such an option should come with a warning statement so the user knows that not applying the patch may leave his computer vulnerable to attack, etc. But when there is a problem/issue with a specific patch not working on a specific system there needs to be an "out" for the user, which at present - there really isn't, except for allowing the user to uncheck a specific "bad patch", assuming the user knows which patch is bad. If the user is unaware of which patch is causing his computer to not proceed with other updates, he may wind up with several patches undone, because he is unaware of which patch (or patches ) to uncheck. Additionally, it might be a good idea to allow the operator ( at this time ) to notify the vendor of the problem, by sending a "hey, your patch didn't work on my machine" notice in real time. If this notice grabbed data from the sysinfo:/ file, it would then tell the vendor not only that there may be a problem with the patch, but on what particular system types, os's, microchips, etc. -- 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 9

[Bug 547233] New: Cold fusion still not invented!
by bugzilla_noreply＠novell.com 28 May '13

28 May '13

http://bugzilla.novell.com/show_bug.cgi?id=547233 Summary: Cold fusion still not invented! Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: All OS/Version: All Status: NEW Severity: Critical Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mantel(a)novell.com QAContact: qa(a)suse.de Found By: System Test The summary pretty much says it all: Cold fusion still is not invented. This means we are still forced to combust material containing carbon in order to generate electric power. But the biggest problem is that we still need to pay large sums in order to be able to run our computers. So somebody please fix this. You will probably be awarded the nobel price for physics then. -- 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 23