March 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 392305] New: System does not notice plugging/unplugging power adapter
by bugzilla_noreply＠novell.com 03 Mar '09

03 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=392305 Summary: System does not notice plugging/unplugging power adapter Product: openSUSE 11.0 Version: Beta 3 Platform: i586 OS/Version: openSUSE 11.0 Status: NEW Severity: Critical Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: registration(a)grek.tuffmail.com QAContact: qa(a)suse.de Found By: --- I installed Beta3 of openSUSE 11.0 release on my laptop HP dv6530ew. Previously, along to this installation I kept 10.3 installation. I noticed several regressions (will report all of them in separate issues). One of them is that openSUSE does not notice plugging and unplugging of power adapter. There is no icon change of KPowersave, no change of power scheme etc. If you need any other information I'm all willing to provide it. -- 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 37

[Bug 476426] New: plasma suddenly crashed
by bugzilla_noreply＠novell.com 03 Mar '09

03 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=476426 Summary: plasma suddenly crashed Classification: openSUSE Product: openSUSE 11.2 Version: Alpha 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: mmrazik(a)novell.com QAContact: qa(a)suse.de Found By: --- Created an attachment (id=273240) --> (https://bugzilla.novell.com/attachment.cgi?id=273240) plasma.kcrash I don't know how to reproduce.It just suddenly happened. All I've got is the backtrace (attached). I'm using KDE 4.2 (http://download.opensuse.org/repositories/KDE:/KDE4:/Factory:/Desktop/openS…) on top of openSUSE 11.1. -- 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 440127] New: libgdiplus0-2.0-11.18: broken code
by bugzilla_noreply＠novell.com 03 Mar '09

03 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=440127 Summary: libgdiplus0-2.0-11.18: broken code Product: openSUSE 11.1 Version: Factory Platform: All OS/Version: openSUSE 11.0 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 tried to build the Suse Linux package libgdiplus0-2.0-11.18 and the compiler said region-bitmap.c:359: warning: operation on 'pos' may be undefined region-bitmap.c:359: warning: operation on 'pos' may be undefined region-bitmap.c:359: warning: operation on 'pos' may be undefined The source code is BYTE combine = source [pos++] | source [pos++] | source [pos++] | source [pos]; I agree with the compiler. The order of evaluation isn't left to right. Suggest code rework. Maybe BYTE combine = source [ pos] | source [ pos + 1] | source [ pos + 2] | source [pos + 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 6

[Bug 471291] New: lam-7.1.4-75.39: attempt to free a non-heap object 'ifaddr'
by bugzilla_noreply＠novell.com 03 Mar '09

03 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=471291 Summary: lam-7.1.4-75.39: attempt to free a non-heap object 'ifaddr' Classification: openSUSE Product: openSUSE 11.2 Version: unspecified 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 tried to compile the Suse Factory package lam-7.1.4-75.39 and the compiler said lamnet.c:314: warning: attempt to free a non-heap object 'ifaddr' The source code is free(ifaddr); But free( *ifaddr); might be close to what the original programmer intended. -- 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 480992] New: python gnome extra fail to load (and find) libmozjs.so
by bugzilla_noreply＠novell.com 03 Mar '09

03 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=480992 Summary: python gnome extra fail to load (and find) libmozjs.so Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: andrea(a)opensuse.org QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; it; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1.2 Firefox/3.0.6 here all you need to know: anubis@suse-netbook:~/Desktop> python Python 2.6 (r26:66714, Feb 3 2009, 20:52:03) [GCC 4.3.2 [gcc-4_3-branch revision 141291]] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import gtkmozembed Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: libmozjs.so: cannot open shared object file: No such file or directory >>> anubis@suse-netbook:~/Desktop> locate libmozjs.so /usr/lib/thunderbird/libmozjs.so /usr/lib/xulrunner-1.8.1.19/libmozjs.so /usr/lib/xulrunner-1.9.0.6/libmozjs.so anubis@suse-netbook:~/Desktop> sudo ln -s /usr/lib/xulrunner-1.9.0.6/libmozjs.so /usr/lib/ root's password: anubis@suse-netbook:~/Desktop> pythonPython 2.6 (r26:66714, Feb 3 2009, 20:52:03) [GCC 4.3.2 [gcc-4_3-branch revision 141291]] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import gtkmozembed >>> sorry if i do not add more info but battery is low.. Reproducible: Always -- 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 1

[Bug 437889] New: yast2 crashes by saving queue data
by bugzilla_noreply＠novell.com 03 Mar '09

03 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=437889 Summary: yast2 crashes by saving queue data Product: openSUSE 11.0 Version: Final Platform: i386 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ulrike.pieper(a)t-online.de QAContact: jsrain(a)novell.com Found By: Other after configuring a printer and trying to save the queue, yast crashes with "an error occured while saving queue xxx. Try selekting the printer modell again" -- 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 5

[Bug 464473] New: Printer Driver Options Disabled in YaST
by bugzilla_noreply＠novell.com 03 Mar '09

03 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=464473 Summary: Printer Driver Options Disabled in YaST Product: openSUSE 11.0 Version: Final Platform: 32bit OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: alanprescott(a)yahoo.co.uk QAContact: jsrain(a)novell.com Found By: Customer Created an attachment (id=263864) --> (https://bugzilla.novell.com/attachment.cgi?id=263864) screenshot showing disabled options When attempting to configure a printer using YaST select printer -> Configure -> Printer Options tab Even though Driver Options is checked the contents of that frame are greyed out and disabled. Unchecking and re-checking the Driver options will enable them but this is not an obvious thing to do. It took me quite a while to find this so that I could configure the duplex option for my laser printer. -- 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 481369] New: testing autoyast schema is hard
by bugzilla_noreply＠novell.com 03 Mar '09

03 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=481369 Summary: testing autoyast schema is hard Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: ASSIGNED Severity: Minor Priority: P5 - None Component: AutoYaST AssignedTo: mvidner(a)novell.com ReportedBy: mvidner(a)novell.com QAContact: qa(a)suse.de CC: ug(a)novell.com Found By: --- As seen in bug 480466, it is easy to have outdated schema for AutoYaST. That is probably because testing it is hard, as I have witnessed while helping Miso fix his part of that bug. In particular it is currently not possible to validate from a source tree. The developer must mimic building yast2-schema.rpm by doing $ trang networking.rnc networking.rng $ sudo cp networking.rng /usr/share/YaST2/schema/autoyast/rng (Using /usr/share/YaST2/schema/autoyast/rnc/profile.rnc does not work because it references *.rnc from packages that my not be installed) How it should work instead: $ vi networking.rnc $ cat test1.xml <?xml ...> <profile> <networking> ... </networking> </profile> $ ay-test-validate ./networking.rnc ./test1.xml Once this works, the next step is to include the validation test in the testsuite. -- 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 1

[Bug 480746] New: software management: packages from imaginary repositories
by bugzilla_noreply＠novell.com 03 Mar '09

03 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=480746 Summary: software management: packages from imaginary repositories Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: jsrain(a)novell.com Found By: --- Created an attachment (id=276202) --> (https://bugzilla.novell.com/attachment.cgi?id=276202) y2logs.tgz software management: packages from imaginary repositories I just try to install nspluginwrapper, no big deal, right. One of the repos where this package is available is openSUSE_11.1_7. The only problem is I don't have such repository defined in "software repositories". -- 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 7

[Bug 477833] New: Feature Proposal/Request: Add Ability to explicitly choose driver-extension for wpa_supplicant
by bugzilla_noreply＠novell.com 03 Mar '09

03 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=477833 Summary: Feature Proposal/Request: Add Ability to explicitly choose driver-extension for wpa_supplicant Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: All OS/Version: SuSE Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: AxelKoellhofer(a)web.de QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.10 (like Gecko) SUSE Background: Since Version 0.6.7, wpa_supplicant offers the new (generic) extension "nl80211" for "new" wireless drivers based on mac80211. The ifup-wireless script chooses the appropriate driver-extension for wpa_supplicant by looking at the kernel module used for the device. case $ACTION in up) case "${DRIVER}" in ath_pci) WPA_DRIVER=wext ;; at76c5*) WPA_DRIVER=atmel PREFER_WPA_SUPPLICANT=no ;; prism54) WPA_DRIVER=prism54 PREFER_WPA_SUPPLICANT=no ;; ipw2200|ipw3945|hostap_*) WPA_DRIVER=wext ;; ipw2100) WPA_DRIVER=wext ;; ndiswrapper|*.sys) WPA_DRIVER=wext ;; rt2500*) WPA_DRIVER=wext ;; *) WPA_DRIVER=unsupported PREFER_WPA_SUPPLICANT=no ;; esac However, this would not work here, as there are now two different extensions available for the same kernel module, so the basic idea is to give the user the possibility to explicitly choose the driver used by wpa_supplicant. I am not a "scripting guru", but this little hack in /etc/sysconfig/network/scripts/wireless makes this at least possible. mkdir -p /var/run/wpa_supplicant message "`printf " %-9s starting wpa_supplicant" $INTERFACE`" ########### lines added start ########### if [ -n "$WIRELESS_WPA_DRIVER" ]; then WPA_DRIVER="$WIRELESS_WPA_DRIVER" else WPA_DRIVER=$WPA_DRIVER fi ########### lines added end ############## eval wpa_supplicant -i$INTERFACE -c$WPA_SUPP_CONF -D$WPA_DRIVER $SUPPARGS Now, by setting the variable "WIRELESS_WPA_DRIVER='name_of_wpa_driver' in the respective /etc/sysconfig/network/ifcfg-*wireless-devie'-file, one can define which extension wpa_supplicant will use when connecting via ifup. I think this is quite useful and hopefully also easy to implement (at least into ifup) without breaking already existing functionality, as ifup will use the existing method for determination of the wpa-extension, when this variable is not set. In addition, users who have to use "exotic" drivers for their wireless hardware (old "otus"-driver for Atheros draft-n USB-dongles or "legacy" drivers for Ralink-devices rt61/rt73, which both need their own wpa-extensions "otus" or "ralink") would have an easy method of accomplishing this task (of course, they will still need to build a wpa_supplicant capable of using those "non-standard" wpa-extensions, but thats a different story). 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 10