September 2011 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 606951] New: amarok 1.4.10 cover download broken
by bugzilla_noreply＠novell.com 03 Sep '11

03 Sep '11

http://bugzilla.novell.com/show_bug.cgi?id=606951 http://bugzilla.novell.com/show_bug.cgi?id=606951#c0 Summary: amarok 1.4.10 cover download broken Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE3 AssignedTo: kde-maintainers(a)suse.de ReportedBy: juergen.helmers(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=363060) --> (http://bugzilla.novell.com/attachment.cgi?id=363060) patch to fix the cover download problem. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.3) Gecko/20100401 SUSE/3.6.3-1.2 Firefox/3.6.3 The cover dowlnoad in the amarok 1.4.10 version (kde3-amarok-1.4.10-39.28.i586) is broken. Neither the cover manager nor the right click in the context side bar does work. The attached patch fixes the problem. the SRPM can be rebuild nicely after including the patch as patch1. patch from: wget http://mail.kde.org/pipermail/amarok/attachments/20090822/52116f4a/attachme… -O covermanager-fix.patch Reproducible: Always Steps to Reproduce: 1. running the cover manager using amazon germany 2. running the cover manager using amazon international 3. right click in the context sidebar and choosing to download the cover. -- 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 13

[Bug 672973] New: wpa_supplicant crashes once per minute
by bugzilla_noreply＠novell.com 03 Sep '11

03 Sep '11

https://bugzilla.novell.com/show_bug.cgi?id=672973 https://bugzilla.novell.com/show_bug.cgi?id=672973#c0 Summary: wpa_supplicant crashes once per minute Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: uli.2001(a)gmx.de QAContact: qa(a)suse.de Found By: --- Blocker: --- I am using wireless network with iwlagn on my Thinkpad T410s. I am connecting to a WPA/WPA2 Enterprise encrypted network using TTLS and PAP with KNetworkManager. Roughly once per minute, the connection is lost, and it is reconnected. cat /var/log/messages |grep wpa_supplicant gives: Feb 17 11:39:18 linux-tku4 kernel: [ 2193.542496] wpa_supplicant[30829]: segfault at 1c0 ip 0000000000414e16 sp 00007ffffb01a440 error 4 in wpa_supplicant[400000+a9000] Feb 17 11:40:33 linux-tku4 kernel: [ 2268.502163] wpa_supplicant[31279]: segfault at 10 ip 0000000000414e16 sp 00007fffa8a17cb0 error 4 in wpa_supplicant[400000+a9000] Feb 17 11:41:48 linux-tku4 kernel: [ 2343.472854] wpa_supplicant[31733]: segfault at 50 ip 0000000000414e16 sp 00007fff320cbef0 error 4 in wpa_supplicant[400000+a9000] Feb 17 11:44:03 linux-tku4 kernel: [ 2478.416053] wpa_supplicant[32230] general protection ip:414e16 sp:7fffbc58a020 error:0 in wpa_supplicant[400000+a9000] Feb 17 11:45:18 linux-tku4 kernel: [ 2553.384951] wpa_supplicant[32700]: segfault at 10 ip 0000000000414e16 sp 00007fff9c473260 error 4 in wpa_supplicant[400000+a9000] Feb 17 11:46:33 linux-tku4 kernel: [ 2628.348920] wpa_supplicant[708] general protection ip:414e16 sp:7fff176821f0 error:0 in wpa_supplicant[400000+a9000] Feb 17 11:47:48 linux-tku4 kernel: [ 2703.322338] wpa_supplicant[1172]: segfault at 1e ip 0000000000414e16 sp 00007fff15874da0 error 4 in wpa_supplicant[400000+a9000] Feb 17 11:49:03 linux-tku4 kernel: [ 2778.285122] wpa_supplicant[1747] general protection ip:414e16 sp:7fffacdab0c0 error:0 in wpa_supplicant[400000+a9000] Feb 17 11:50:15 linux-tku4 kernel: [ 2850.498242] wpa_supplicant[2227] general protection ip:414e16 sp:7fffbdf0fbb0 error:0 in wpa_supplicant[400000+a9000] Feb 17 11:51:30 linux-tku4 kernel: [ 2925.130136] wpa_supplicant[2700]: segfault at 35001d70 ip 0000000000414e16 sp 00007fffdc938ab0 error 4 in wpa_supplicant[400000+a9000] Feb 17 11:52:44 linux-tku4 kernel: [ 2999.185657] wpa_supplicant[3158] general protection ip:414e16 sp:7fffb4d5aa80 error:0 in wpa_supplicant[400000+a9000] Feb 17 11:53:59 linux-tku4 kernel: [ 3074.154115] wpa_supplicant[3652]: segfault at 10 ip 0000000000414e16 sp 00007fff4652e1c0 error 4 in wpa_supplicant[400000+a9000] Feb 17 11:55:14 linux-tku4 kernel: [ 3149.126033] wpa_supplicant[4247]: segfault at 10 ip 0000000000414e16 sp 00007fffc667e970 error 4 in wpa_supplicant[400000+a9000] Feb 17 11:56:29 linux-tku4 kernel: [ 3224.088666] wpa_supplicant[4836]: segfault at 10 ip 0000000000414e16 sp 00007ffff8b55110 error 4 in wpa_supplicant[400000+a9000] A typical list of entries between two wpa_supplicant lines in /var/log/messages is: Feb 17 11:56:29 linux-tku4 kernel: [ 3224.088666] wpa_supplicant[4836]: segfault at 10 ip 0000000000414e16 sp 00007ffff8b55110 error 4 in wpa_supplicant[400000+a9000] Feb 17 11:56:29 linux-tku4 avahi-daemon[2218]: Withdrawing address record for 194.94.154.109 on wlan0. Feb 17 11:56:29 linux-tku4 avahi-daemon[2218]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 194.94.154.109. Feb 17 11:56:29 linux-tku4 avahi-daemon[2218]: Interface wlan0.IPv4 no longer relevant for mDNS. Feb 17 11:56:29 linux-tku4 kernel: [ 3224.342108] mac80211-phy0: failed to remove key (0, 0a:0b:6b:2a:f3:3a) from hardware (-22) Feb 17 11:56:29 linux-tku4 kernel: [ 3224.342189] wlan0: deauthenticating from 0a:0b:6b:2a:f3:3a by local choice (reason=3) Feb 17 11:56:29 linux-tku4 kernel: [ 3224.357115] cfg80211: Calling CRDA to update world regulatory domain Feb 17 11:56:29 linux-tku4 kernel: [ 3224.380738] cfg80211: World regulatory domain updated: Feb 17 11:56:29 linux-tku4 kernel: [ 3224.380741] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Feb 17 11:56:29 linux-tku4 kernel: [ 3224.380744] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Feb 17 11:56:29 linux-tku4 kernel: [ 3224.380747] (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Feb 17 11:56:29 linux-tku4 kernel: [ 3224.380749] (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Feb 17 11:56:29 linux-tku4 kernel: [ 3224.380752] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Feb 17 11:56:29 linux-tku4 kernel: [ 3224.380755] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Feb 17 11:56:32 linux-tku4 kernel: [ 3227.618086] wlan0: authenticate with 0a:0b:6b:2a:f3:3a (try 1) Feb 17 11:56:32 linux-tku4 kernel: [ 3227.621090] wlan0: authenticated Feb 17 11:56:32 linux-tku4 kernel: [ 3227.621942] wlan0: associate with 0a:0b:6b:2a:f3:3a (try 1) Feb 17 11:56:32 linux-tku4 kernel: [ 3227.629225] wlan0: RX AssocResp from 0a:0b:6b:2a:f3:3a (capab=0x31 status=0 aid=5) Feb 17 11:56:32 linux-tku4 kernel: [ 3227.629232] wlan0: associated Feb 17 11:56:32 linux-tku4 kernel: [ 3227.634123] cfg80211: Calling CRDA for country: DE Feb 17 11:56:32 linux-tku4 kernel: [ 3227.637896] cfg80211: Current regulatory domain updated by AP to: DE Feb 17 11:56:32 linux-tku4 kernel: [ 3227.637899] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Feb 17 11:56:32 linux-tku4 kernel: [ 3227.637902] (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 1800 mBm) Feb 17 11:56:33 linux-tku4 dhclient: Internet Systems Consortium DHCP Client 4.1-ESV-R1 Feb 17 11:56:33 linux-tku4 dhclient: Copyright 2004-2011 Internet Systems Consortium. Feb 17 11:56:33 linux-tku4 dhclient: All rights reserved. Feb 17 11:56:33 linux-tku4 dhclient: For info, please visit https://www.isc.org/software/dhcp/ Feb 17 11:56:33 linux-tku4 dhclient: Feb 17 11:56:33 linux-tku4 dhclient: Listening on LPF/wlan0/58:94:6b:07:e6:48 Feb 17 11:56:33 linux-tku4 dhclient: Sending on LPF/wlan0/58:94:6b:07:e6:48 Feb 17 11:56:33 linux-tku4 dhclient: Sending on Socket/fallback Feb 17 11:56:36 linux-tku4 dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67 Feb 17 11:56:36 linux-tku4 dhclient: DHCPACK from 194.94.154.254 Feb 17 11:56:36 linux-tku4 dhclient: bound to 194.94.154.109 -- renewal in 506 seconds. Feb 17 11:56:36 linux-tku4 avahi-daemon[2218]: Joining mDNS multicast group on interface wlan0.IPv4 with address 194.94.154.109. Feb 17 11:56:36 linux-tku4 avahi-daemon[2218]: New relevant interface wlan0.IPv4 for mDNS. Feb 17 11:56:36 linux-tku4 avahi-daemon[2218]: Registering new address record for 194.94.154.109 on wlan0.IPv4. Feb 17 11:56:37 linux-tku4 SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ... Feb 17 11:56:37 linux-tku4 SuSEfirewall2: using default zone 'ext' for interface pan0 Feb 17 11:56:37 linux-tku4 SuSEfirewall2: batch committing... Feb 17 11:56:37 linux-tku4 SuSEfirewall2: Firewall rules successfully set Feb 17 11:57:44 linux-tku4 kernel: [ 3299.060425] wpa_supplicant[5290] general protection ip:414e16 sp:7fff0f9106f0 error:0 in wpa_supplicant[400000+a9000] -- 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 615681] New: wpa_supplicant is not installed into target system, although network depends on it
by bugzilla_noreply＠novell.com 03 Sep '11

03 Sep '11

http://bugzilla.novell.com/show_bug.cgi?id=615681 http://bugzilla.novell.com/show_bug.cgi?id=615681#c0 Summary: wpa_supplicant is not installed into target system, although network depends on it Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: andreasfrische(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Opera/9.80 (Windows NT 6.1; U; de) Presto/2.6.30 Version/10.50 The network install nowadays can establish a secure wireless connection. However, after the first boot into the target system, wpa_supplicant and iw have not been installed. Reproducible: Didn't try Steps to Reproduce: 1. start netinstall 2. use wpa connection 3. start 1st time configuration, click through to network config Actual Results: 4. fails with network error when trying to install wpa_supplicant and iw packages Expected Results: these packages should just be part of a standard install. In a home environment encrypted wireless networks are very common -- 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 12

[Bug 612010] New: eth0 provisioned and routes set to interface even when unplugged and overrides wlan0
by bugzilla_noreply＠novell.com 03 Sep '11

03 Sep '11

http://bugzilla.novell.com/show_bug.cgi?id=612010 http://bugzilla.novell.com/show_bug.cgi?id=612010#c0 Summary: eth0 provisioned and routes set to interface even when unplugged and overrides wlan0 Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: 64bit OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: michaelcook_mjc(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.4) Gecko/20100513 SUSE/3.6.4-1.11 Firefox/3.6.4 When the laptop comes up and it has eth0 NIC and wlan0 both are provisioned. Somehow, the eth0 NIC gets an address assigned (looks like the last one it was assigned when plugged in) and the default route goes to that interface. The wlan0 which is attached to the network also gets an address but all traffic is routed to eth0. I would only expect this behaviour if eth0 was in fact up (connected) and received valid DHCP address. I dont see a network-applet on the task-bar (like I might under Ubuntu) and when I check with Yast Networking I see it is as configured as DHCP. I'm new to Yast networking but I've asked it to use ifup method as I'm trying to get XEN networking too... although this behaviour was been seen pre-XEN installation. (see dmesg/messages from this posting https://bugzilla.novell.com/show_bug.cgi?id=612006) I presently have it connected via wlan0 by ifdown eth0 and adding default route to the wlan0 interface. Wlan0 is successfully connecting and assigned a valid IP address. Reproducible: Always Steps to Reproduce: 1. start W510 laptop using suse 11.3 m7 with Intel 6000 firmware for wireless device support. 2. eth0 and wlan0 both come up, eth0 seems to be assigned an address even though not connected. 3. wait for wlan0 to be assigned an address 4. check route -n and see that default route goes to eth0 Actual Results: Routing table is pointing to eth0 interface Expected Results: whichever interface is up and using DHCP should provision the default gateway to it... in this case, eth0 is not connected, so would expect default to point to wlan0. Expect not to have to hardwire this under Network Settings in YaST because it would be more useful to automatically configure the default route based on which ever interface was in use (wired taken precedence as seen in Ubuntu). I dont think this is XEN related and would expect dom0 to still behaviour as I described. -- 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 604055] New: Couldn't turnoff wireless or bluetooth separately
by bugzilla_noreply＠novell.com 03 Sep '11

03 Sep '11

http://bugzilla.novell.com/show_bug.cgi?id=604055 http://bugzilla.novell.com/show_bug.cgi?id=604055#c0 Summary: Couldn't turnoff wireless or bluetooth separately Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 6 Platform: 64bit OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: michalng(a)gmail.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.4) Gecko/20100417 SUSE/3.6.4-1.1 Firefox/3.6.4 On a Thinkpad T410, using the (Fn+F5) key combination, unable to - turn off wireless only - turn off bluetooth only. Either both is on or both is off. Reproducible: Always Steps to Reproduce: 1. Startup 2. Press Fn+F5 button 3. Wireless AND Bluetooth (On or Off together, supposed to be able to turn on/off separately). Actual Results: Wireless AND Bluetooth on or Off together. Expected Results: Wireless AND Bluetooth supposed to be able to turn on/off separately. -- 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 13

[Bug 591316] New: wifi not working in opensuse 11.2 for dell wireless 1397
by bugzilla_noreply＠novell.com 03 Sep '11

03 Sep '11

http://bugzilla.novell.com/show_bug.cgi?id=591316 http://bugzilla.novell.com/show_bug.cgi?id=591316#c0 Summary: wifi not working in opensuse 11.2 for dell wireless 1397 Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ruchir.brahmbhatt(a)ecosmob.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/532.5 (KHTML, like Gecko) Chrome/4.1.249.1036 Safari/532.5 I have dell inspiron 1464 with dell wireless 1397. I setup broadcom-wl package from packman but wifi is not working. I get following error when wireless starts. Mar 26 08:38:27 Ruchir-Linux dhcpcd[17417]: wlan0: ioctl SIOCSIFFLAGS: Unknown error 132 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 23

[Bug 617790] New: Cannot connect to hidden wireless network with ThinkPad T60p
by bugzilla_noreply＠novell.com 03 Sep '11

03 Sep '11

http://bugzilla.novell.com/show_bug.cgi?id=617790 http://bugzilla.novell.com/show_bug.cgi?id=617790#c0 Summary: Cannot connect to hidden wireless network with ThinkPad T60p Classification: openSUSE Product: openSUSE 11.3 Version: RC 1 Platform: Other OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: fstrba(a)novell.com QAContact: qa(a)suse.de Found By: Community User Blocker: Yes Although it was possible at certain stage of factory between 11.2 and 11.3, It is again impossible with ThinkPad T60p using iwl driver to connect to hidden wireless network with WEP security (did not try other security). The network status can be seen, but authentication fails over and over again. It works though with many other laptops using the same operating system but different wireless hardware. -- 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 8

[Bug 713727] changing password for local user not possible
by bugzilla_noreply＠novell.com 02 Sep '11

02 Sep '11

https://bugzilla.novell.com/show_bug.cgi?id=713727 https://bugzilla.novell.com/show_bug.cgi?id=713727#c16 --- Comment #16 from Bernhard Wiedemann <bwiedemann(a)suse.com> 2011-09-02 23:00:22 CEST --- This is an autogenerated message for OBS integration: This bug (713727) was mentioned in https://build.opensuse.org/request/show/80726 Evergreen:11.2 / libxcrypt -- 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 696963] New: systemd does not start syslog
by bugzilla_noreply＠novell.com 02 Sep '11

02 Sep '11

https://bugzilla.novell.com/show_bug.cgi?id=696963 https://bugzilla.novell.com/show_bug.cgi?id=696963#c0 Summary: systemd does not start syslog Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: mt(a)novell.com ReportedBy: aj(a)novell.com QAContact: qa(a)suse.de CC: kasievers(a)novell.com Blocks: 696902 Found By: --- Blocker: --- Currently systemd does not start syslog at all. This might be a fallout from removing the syslog.service file from the syslog package. I have to start syslog manually and then it runs fine... -- 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 16

[Bug 66013] pthread_rwlock_rdlock: blocking error
by bugzilla_noreply＠novell.com 02 Sep '11

02 Sep '11

https://bugzilla.novell.com/show_bug.cgi?id=66013 https://bugzilla.novell.com/show_bug.cgi?id=66013#c14 Greg Kroah-Hartman <gregkh(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |chrubis(a)suse.com --- Comment #14 from Greg Kroah-Hartman <gregkh(a)suse.com> 2011-09-02 16:15:38 UTC --- Proving LTP wrong, or fixing it, or the kernel, is on the _very_ low list of things we need to work on at the moment. Have you brought this issue up on the upstream LTP mailing list? What do the developers there say about this? Have they asked the kernel community about this issue? -- 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