April 2007 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 249672] New: emacs-21-3.1 : Invalid free() / delete / delete[]
by bugzilla_noreply＠novell.com 04 Apr '07

04 Apr '07

https://bugzilla.novell.com/show_bug.cgi?id=249672 Summary: emacs-21-3.1 : Invalid free() / delete / delete[] Product: openSUSE 10.3 Version: Alpha 1 Platform: x86-64 OS/Version: SuSE Other 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 I just tried to build package apel-10.6-100 with valgrind on Suse Linux 10.3 Alpha 1. I used command line valgrind -q --trace-children=yes rpmbuild -bc apel.spec The output contains + make 'CFLAGS=-O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2' LDFLAGS=-s EMACS=emacs PREFIX=/usr emacs -batch -q -no-site-file -l APEL-MK -f what-where-apel \ /usr NONE NONE ==8538== Invalid free() / delete / delete[] ==8538== at 0x4C22D57: realloc (in /usr/lib64/valgrind/amd64-linux/vgpreload_memcheck.so) ==8538== by 0x4F2EED: (within /usr/bin/emacs) ==8538== by 0x4E63A0: re_compile_pattern (in /usr/bin/emacs) ==8538== by 0x4E1CA0: (within /usr/bin/emacs) ==8538== by 0x4E1EDB: (within /usr/bin/emacs) ==8538== by 0x4E2145: (within /usr/bin/emacs) ==8538== by 0x5075A6: (within /usr/bin/emacs) ==8538== by 0x535855: (within /usr/bin/emacs) ==8538== by 0x507010: (within /usr/bin/emacs) ==8538== by 0x507230: (within /usr/bin/emacs) ==8538== by 0x50604A: (within /usr/bin/emacs) ==8538== by 0x509ADE: (within /usr/bin/emacs) ==8538== Address 0x9CFCB0 is not stack'd, malloc'd or (recently) free'd ==8538== So it seems that there is a problem with memory allocation in emacs-21-3.1. Suggest code rework. -- 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, or are watching someone who is.

1 4

[Bug 169059] KDE Parts Plugin (libdragonegg) feels not responsible for pdf
by bugzilla_noreply＠novell.com 04 Apr '07

04 Apr '07

https://bugzilla.novell.com/show_bug.cgi?id=169059 dmueller(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|dsieben(a)novell.com | Resolution| |WORKSFORME ------- Comment #7 from dmueller(a)novell.com 2007-04-04 04:32 MST ------- considered 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, or are watching someone who is.

1 0

[Bug 253665] New: kmail - attachments not forwarded
by bugzilla_noreply＠novell.com 04 Apr '07

04 Apr '07

https://bugzilla.novell.com/show_bug.cgi?id=253665 Summary: kmail - attachments not forwarded Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gassauer(a)kde.org QAContact: qa(a)suse.de the distributed version (KDE 3.5.6 latest OpenSuSE builds) does not forward attachments. (3.5.x SVN does) pls backport this functionality asap. -- 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, or are watching someone who is.

1 7

[Bug 251679] New: open-iscsi - Ports for SuSEfirewall added via packages
by bugzilla_noreply＠novell.com 04 Apr '07

04 Apr '07

https://bugzilla.novell.com/show_bug.cgi?id=251679 Summary: open-iscsi - Ports for SuSEfirewall added via packages Product: openSUSE 10.3 Version: Alpha 1plus Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem AssignedTo: hare(a)novell.com ReportedBy: locilka(a)novell.com QAContact: qa(a)suse.de CC: mzugec(a)novell.com There is a new feature: FATE #300687: Ports for SuSEfirewall2 added via packages implemented in SuSEfirewall2 and YaST2-Firewall. This functionality offers to define needed ports for particular package. The definition is then transparently used in Firewall. Please, add such definition into the package mentioned in $subject by following steps in this article: http://en.opensuse.org/SuSEfirewall2/Service_Definitions_Added_via_Packages 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, or are watching someone who is.

1 5

[Bug 254456] New: iSNS - Ports for SuSEfirewall added via packages
by bugzilla_noreply＠novell.com 04 Apr '07

04 Apr '07

https://bugzilla.novell.com/show_bug.cgi?id=254456 Summary: iSNS - Ports for SuSEfirewall added via packages Product: openSUSE 10.3 Version: Alpha 2 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: locilka(a)novell.com QAContact: qa(a)suse.de CC: wrwhitehead(a)novell.com There is a new feature: FATE #300687: Ports for SuSEfirewall2 added via packages implemented in SuSEfirewall2 and YaST2-Firewall. This functionality offers to define needed ports for particular package. The definition is then transparently used in Firewall. Please, add such definition into the package mentioned in $subject by following steps in this article: http://en.opensuse.org/SuSEfirewall2/Service_Definitions_Added_via_Packages Thanks PS: see also bug #253826 -- 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, or are watching someone who is.

1 4

[Bug 260261] New: Remove ipv6 proposal (part of network proposal) from control file.
by bugzilla_noreply＠novell.com 04 Apr '07

04 Apr '07

https://bugzilla.novell.com/show_bug.cgi?id=260261 Summary: Remove ipv6 proposal (part of network proposal) from control file. Product: openSUSE 10.3 Version: Alpha 2plus Platform: All OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: locilka(a)novell.com ReportedBy: kmachalkova(a)novell.com QAContact: jsrain(a)novell.com Due to fix of bug #255609 + further usability changes of y2-network module, ipv6 set-up is no longer a separate proposal. This change is applicable for y2-network 2.15.21 or newer. Please remove it from appropriate control file. -- 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, or are watching someone who is.

1 1

[Bug 239101] New: Fans do not (re)start on hp compaq nx6325 laptop
by bugzilla_noreply＠novell.com 04 Apr '07

04 Apr '07

https://bugzilla.novell.com/show_bug.cgi?id=239101 Summary: Fans do not (re)start on hp compaq nx6325 laptop Product: openSUSE 10.2 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: trenn(a)novell.com ReportedBy: bernhard.bender(a)web.de QAContact: qa(a)suse.de Hi Thomas, as you requested in comment 119 bug 179702, I am opening this new bug: I am using your 2.6.18.5-34-default kernel to solve some ACPI problems with my hp nx 6325 Turion X2 laptop. A problem with the fans still remains: The ACPI subsystem is unable to start any fan (it does succeed to stop them during boot). I can see messages like this in dmesg: >>> ACPI: Transitioning device [C352] to D0 ACPI: Transitioning device [C352] to D0 ACPI: Unable to turn cooling device [dffde9b4] 'on' ACPI: Transitioning device [C351] to D0 ACPI: Transitioning device [C351] to D0 ACPI: Unable to turn cooling device [dffdea04] 'on' ACPI: Transitioning device [C350] to D0 ACPI: Transitioning device [C350] to D0 ACPI: Unable to turn cooling device [dffdea54] 'on' ACPI: Transitioning device [C34F] to D0 ACPI: Transitioning device [C34F] to D0 ACPI: Unable to turn cooling device [dffdeab8] 'on' <<< The BIOS on this machine seems to be the latest version (F.04) Bernhard -- 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, or are watching someone who is.

1 47

[Bug 259304] yast doesn't start firewall when set for manual start
by bugzilla_noreply＠novell.com 04 Apr '07

04 Apr '07

https://bugzilla.novell.com/show_bug.cgi?id=259304 locilka(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #5 from locilka(a)novell.com 2007-04-04 02:27 MST ------- I have here a table of possible states in which a firewall can operate. Some of them could be merged into one by using variables. Anyway, just to present the pieces of information with which the YaST firewall needs to work: - There is the initial state of a firewall: enabled/disabled* - And another initial state: running/not running - User can enable/disable the firewall in UI* - User can start/stop the firewall in UI - Firewall can be enabled/disabled at the end* - Firewall can be running/stopped at the end * enabled/disabled means that it starts automatically at the boot process, disabled means "Manually" in UI. Without user's help (question), we sometimes just can't know what to do. User might want to disable the firewall (or leave it disabled) while he/she wants to leave it running. To be honest, this has been discussed many times before and despite the fact that firewall isn't the only one service that has exactly the current behavior, it is the only reported case in bugzilla. Never mind, ... so how to solve that? Radio buttons: (*) When booting ( ) Manually don't fit to a situation when a common user wants to simply disable the firewall. However, if I only change them to: (*) Enable firewall ( ) Disable firewall it wouldn't work for experts with their manual setup. Let's forget now, that manual setup (manual start) doesn't make much sense in a desktop or even server environment. Maybe if experts call `rcSuSEfirewall2 start` from some (another) starting script but what's the point? That's why I've decided to rename these radio buttons to: (*) Enable firewall automatic starting ( ) Disable firewall automatic starting (or something similar using a proper English ;)) Additionally, a new functionality has been added: 1.) Unless the enable/disable is changed by user in that dialog, no status change is proposed for the currently running/stopped service. 2.) If user selects to "Enable firewall...", it's also proposed to be started after the configuration is written. 3.) If user selects to "Disable firewall...", user is asked whether he/she wants to stop the firewall after the configuration is written (default "yes, stop it"). 4.) Text about stopping or starting the firewall service uses a bold text in a summary. This new solution cannot be added into SLES10 SP1. The right product is openSUSE 10.3 where it should prove its correctness or escalate into discussion about another, better, solution that would appear in SLES11 (after oS 10.3). This is a part of the yast2-firewall changes file: --- cut --- - A brand new and better revolutionary solution has been worked out for a firewall service starting/stopping and enabling/disabling in order to maximize user understanding and minimize errors (#259304). - yast2-firewall-2.15.5 --- cut --- Closing as 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, or are watching someone who is.

1 0

[Bug 259686] New: Missing iLBC and ZRTP support in Twinkle
by bugzilla_noreply＠novell.com 04 Apr '07

04 Apr '07

https://bugzilla.novell.com/show_bug.cgi?id=259686 Summary: Missing iLBC and ZRTP support in Twinkle Product: openSUSE 10.2 Version: Final Platform: i586 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: cmorve69(a)yahoo.es QAContact: qa(a)suse.de CC: mskibbe(a)novell.com Twinkle, a VoIP SIP program, has support fot both the iLBC CODEC and the ZRTP protocol, but they aren't compiled in the package twinkle-0.9-21.i586.rpm. Both libraries are in the Build Service with X11/MIT, and (L)GPL licenses, so there isn't any legal problem with them. The package twinkle-1.0-7.1.i586.rpm from the Build Service has the same problem. And must be noted that the package changelog says: * jue mar 22 2007 mskibbe(a)suse.de - add ilbc support by requirering the ilbc package * jue feb 22 2007 mskibbe(a)suse.de - add zrtp support And no, the spec file isn't requirering the ilbc package: BuildRequires: boost-devel ccrtp-devel kdelibs3-devel libsndfile-devel qt-devel speex-devel xorg-x11-devel commoncpp2-devel Requires: ccrtp commoncpp2 xorg-x11 libsndfile Between, qt-devel openSUSE name is qt3-devel. pd. OK, I must admit I am only concerned about the Build Service package. But since I don't see any progress with bug 229213 I put here the "official" package too ;-) -- 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, or are watching someone who is.

1 8

[Bug 260617] New: Error on Install of Guile Package
by bugzilla_noreply＠novell.com 04 Apr '07

04 Apr '07

https://bugzilla.novell.com/show_bug.cgi?id=260617 Summary: Error on Install of Guile Package Product: openSUSE 10.3 Version: Alpha 2plus Platform: x86 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: arthur(a)bluecollarcomp.com QAContact: jsrain(a)novell.com During the install the following error pops up: Installation of package /suse/i586/guile-1.8.1-35.i586.rpm failed. The details list shows: Subprocess failed. Error: RPM failed: ERROR: Could not find slib/require.scm in ("/usr/share/guile/site" "/usr/share/guile/1.8" "/usr/share/guile") error: %trigger(slib-3a1-89.noarch) scriplet failed, exit status 1 This is using the DVD install media doing the typical Gnome install. -- 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, or are watching someone who is.

1 2