March 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 483135] New: GW/SOAP: Any actions taking place (syncing messages etc) hangs if internet connectivity is lost
by bugzilla_noreply＠novell.com 07 Mar '09

07 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=483135 Summary: GW/SOAP: Any actions taking place (syncing messages etc) hangs if internet connectivity is lost Classification: openSUSE Product: openSUSE 11.2 Version: Alpha 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Evolution AssignedTo: bnc-team-evolution(a)forge.provo.novell.com ReportedBy: captain.magnus(a)opensuse.org QAContact: lakhil(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-1.3 Firefox/3.0.5 If Evo is doing anything with SOAP and internet connectivity is lost, evo will never recover (everything GW/SOAP are hung). Evo will also never be able to exist so one must kill it. It must be able to recover from these failures. Reproduce is as simple as hitting Get Mail and once it starts pull the network cable 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 0

[Bug 483067] New: error when trying to start the Gcompris administration module in openSUSE 11.1
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=483067 Summary: error when trying to start the Gcompris administration module in openSUSE 11.1 Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i386 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lucifer.yellow(a)gmail.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1.2 Firefox/3.0.6 GTB5 When I run gcompris -a at the command line, I get: ^ SyntaxError: invalid syntax Reproducible: Always Steps to Reproduce: 1.at CLI, enter gcompris -a 2. 3. Actual Results: When I run gcompris -a at the command line, I get: XF86VidMode: Compiled with XF86VidMode. If you have problems starting GCompris in fullscreen, try the -x option to disable XF86VidMode. ** (process:12221): WARNING **: Binary relocation disabled ** (process:12221): WARNING **: exec_prefix NONE package_data_dir = /usr/share/gcompris/boards package_locale_dir = /usr/share/locale package_plugin_dir = /usr/lib/gcompris package_python_plugin_dir= /usr/share/gcompris/python Infos: Config dir '/home/decastro/.config/gcompris' Users dir '/home/decastro/My GCompris' Database '/home/decastro/.config/gcompris/gcompris_sqlite.db' Traceback (most recent call last): File "/usr/share/gcompris/python/administration.py", line 89, in start exec('from admin import module_' + module + ' as ' + module) File "<string>", line 1, in <module> File "/usr/share/gcompris/python/admin/module_profiles.py", line 28, in <module> import profile_list File "/usr/share/gcompris/python/admin/profile_list.py", line 32, in <module> import profile_edit File "/usr/share/gcompris/python/admin/profile_edit.py", line 226 def __create_model(self, with, profile_id): ^ SyntaxError: invalid syntax Expected Results: The Gcompris administrative module GUI should appear. Apparently, thius has to do with Python 2.6 using "with" as a keyword. The Gcompris developer reports the following status: "the commit in trunk that fixes this is r3749" -- 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 463273] New: /var/log/messages becomes really huge
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=463273 Summary: /var/log/messages becomes really huge Product: openSUSE 11.0 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: richard.bos(a)xs4all.nl QAContact: qa(a)suse.de Found By: --- Since upgrading to openSUSE_11.1 /var/log/messages becomes really huge: med111:/var/log # ls -l messages -rw-r----- 1 root root 112104181 Jan 2 15:25 messages That's more than 112MB. The collection of messages in this file started only 20 hours ago: med111:/var/log # head messages Jan 1 17:46:15 med111 kernel: sd 2:0:0:3: [sde] Add. Sense: Logical unit not supported Jan 1 17:46:15 med111 kernel: sd 2:0:0:1: [sdc] Unit Not Ready Jan 1 17:46:15 med111 kernel: sd 2:0:0:1: [sdc] Sense Key : Illegal Request [current] The messages accountable for this huge amount of data is: med111:/var/log # cut -c17- messages | sort | uniq -c | sort -nr | head -30 67350 med111 kernel: sd 2:0:0:3: [sde] Add. Sense: Logical unit not supported 67350 med111 kernel: sd 2:0:0:1: [sdc] Sense Key : Illegal Request [current] 67350 med111 kernel: sd 2:0:0:1: [sdc] Add. Sense: Logical unit not supported 67349 med111 kernel: sd 2:0:0:3: [sde] Sense Key : Illegal Request [current] 67345 med111 kernel: sd 2:0:0:2: [sdd] Sense Key : Illegal Request [current] 67345 med111 kernel: sd 2:0:0:2: [sdd] Add. Sense: Logical unit not supported 67342 med111 kernel: sd 2:0:0:0: [sdb] Sense Key : Illegal Request [current] 67342 med111 kernel: sd 2:0:0:0: [sdb] Add. Sense: Logical unit not supported 33675 med111 kernel: sd 2:0:0:3: [sde] Test WP failed, assume Write Enabled 33675 med111 kernel: sd 2:0:0:3: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK 33675 med111 kernel: sd 2:0:0:3: [sde] READ CAPACITY failed 33675 med111 kernel: sd 2:0:0:1: [sdc] Unit Not Ready 33675 med111 kernel: sd 2:0:0:1: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK 33675 med111 kernel: sd 2:0:0:1: [sdc] READ CAPACITY failed 33674 med111 kernel: sd 2:0:0:3: [sde] Unit Not Ready 33674 med111 kernel: sd 2:0:0:3: [sde] Assuming drive cache: write through 33674 med111 kernel: sd 2:0:0:1: [sdc] Test WP failed, assume Write Enabled 33674 med111 kernel: sd 2:0:0:1: [sdc] Assuming drive cache: write through 33673 med111 kernel: sd 2:0:0:2: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK 33673 med111 kernel: sd 2:0:0:2: [sdd] READ CAPACITY failed 33672 med111 kernel: sd 2:0:0:2: [sdd] Unit Not Ready 33672 med111 kernel: sd 2:0:0:2: [sdd] Test WP failed, assume Write Enabled 33672 med111 kernel: sd 2:0:0:2: [sdd] Assuming drive cache: write through 33671 med111 kernel: sd 2:0:0:0: [sdb] Unit Not Ready 33671 med111 kernel: sd 2:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK 33671 med111 kernel: sd 2:0:0:0: [sdb] READ CAPACITY failed 33670 med111 kernel: sd 2:0:0:0: [sdb] Test WP failed, assume Write Enabled 33670 med111 kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through 41 med111 kernel: ata2: clearing spurious IRQ 8 med111 kernel: usb 1-3: reset high speed USB device using ehci_hcd and address 2 In a second the following messages are seen (just a random second): Jan 2 15:28:40 med111 kernel: sd 2:0:0:1: [sdc] Unit Not Ready Jan 2 15:28:40 med111 kernel: sd 2:0:0:1: [sdc] Sense Key : Illegal Request [current] Jan 2 15:28:40 med111 kernel: sd 2:0:0:1: [sdc] Add. Sense: Logical unit not supported Jan 2 15:28:40 med111 kernel: sd 2:0:0:2: [sdd] Unit Not Ready Jan 2 15:28:40 med111 kernel: sd 2:0:0:2: [sdd] Sense Key : Illegal Request [current] Jan 2 15:28:40 med111 kernel: sd 2:0:0:2: [sdd] Add. Sense: Logical unit not supported Jan 2 15:28:40 med111 kernel: sd 2:0:0:0: [sdb] Unit Not Ready Jan 2 15:28:40 med111 kernel: sd 2:0:0:0: [sdb] Sense Key : Illegal Request [current] Jan 2 15:28:40 med111 kernel: sd 2:0:0:0: [sdb] Add. Sense: Logical unit not supported Jan 2 15:28:40 med111 kernel: sd 2:0:0:3: [sde] Unit Not Ready Jan 2 15:28:40 med111 kernel: sd 2:0:0:3: [sde] Sense Key : Illegal Request [current] Jan 2 15:28:40 med111 kernel: sd 2:0:0:3: [sde] Add. Sense: Logical unit not supported Jan 2 15:28:40 med111 kernel: sd 2:0:0:1: [sdc] READ CAPACITY failed Jan 2 15:28:40 med111 kernel: sd 2:0:0:1: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK Jan 2 15:28:40 med111 kernel: sd 2:0:0:1: [sdc] Sense Key : Illegal Request [current] Jan 2 15:28:40 med111 kernel: sd 2:0:0:1: [sdc] Add. Sense: Logical unit not supported Jan 2 15:28:40 med111 kernel: sd 2:0:0:2: [sdd] READ CAPACITY failed Jan 2 15:28:40 med111 kernel: sd 2:0:0:2: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK Jan 2 15:28:40 med111 kernel: sd 2:0:0:2: [sdd] Sense Key : Illegal Request [current] Jan 2 15:28:40 med111 kernel: sd 2:0:0:2: [sdd] Add. Sense: Logical unit not supported Jan 2 15:28:40 med111 kernel: sd 2:0:0:3: [sde] READ CAPACITY failed Jan 2 15:28:40 med111 kernel: sd 2:0:0:3: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK Jan 2 15:28:40 med111 kernel: sd 2:0:0:3: [sde] Sense Key : Illegal Request [current] Jan 2 15:28:40 med111 kernel: sd 2:0:0:3: [sde] Add. Sense: Logical unit not supported Jan 2 15:28:40 med111 kernel: sd 2:0:0:1: [sdc] Test WP failed, assume Write Enabled Jan 2 15:28:40 med111 kernel: sd 2:0:0:1: [sdc] Assuming drive cache: write through Jan 2 15:28:40 med111 kernel: sd 2:0:0:0: [sdb] READ CAPACITY failed Jan 2 15:28:40 med111 kernel: sd 2:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK Jan 2 15:28:40 med111 kernel: sd 2:0:0:0: [sdb] Sense Key : Illegal Request [current] Jan 2 15:28:40 med111 kernel: sd 2:0:0:0: [sdb] Add. Sense: Logical unit not supported Jan 2 15:28:40 med111 kernel: sd 2:0:0:2: [sdd] Test WP failed, assume Write Enabled Jan 2 15:28:40 med111 kernel: sd 2:0:0:2: [sdd] Assuming drive cache: write through Jan 2 15:28:40 med111 kernel: sd 2:0:0:3: [sde] Test WP failed, assume Write Enabled Jan 2 15:28:40 med111 kernel: sd 2:0:0:3: [sde] Assuming drive cache: write through Jan 2 15:28:40 med111 kernel: sd 2:0:0:0: [sdb] Test WP failed, assume Write Enabled Jan 2 15:28:40 med111 kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through Jan 2 15:28:40 med111 kernel: sd 2:0:0:1: [sdc] Unit Not Ready Jan 2 15:28:40 med111 kernel: sd 2:0:0:1: [sdc] Sense Key : Illegal Request [current] Jan 2 15:28:40 med111 kernel: sd 2:0:0:1: [sdc] Add. Sense: Logical unit not supported Jan 2 15:28:40 med111 kernel: sd 2:0:0:2: [sdd] Unit Not Ready Jan 2 15:28:40 med111 kernel: sd 2:0:0:2: [sdd] Sense Key : Illegal Request [current] Jan 2 15:28:40 med111 kernel: sd 2:0:0:2: [sdd] Add. Sense: Logical unit not supported Jan 2 15:28:40 med111 kernel: sd 2:0:0:0: [sdb] Unit Not Ready Jan 2 15:28:40 med111 kernel: sd 2:0:0:0: [sdb] Sense Key : Illegal Request [current] Jan 2 15:28:40 med111 kernel: sd 2:0:0:0: [sdb] Add. Sense: Logical unit not supported Jan 2 15:28:40 med111 kernel: sd 2:0:0:3: [sde] Unit Not Ready Jan 2 15:28:40 med111 kernel: sd 2:0:0:3: [sde] Sense Key : Illegal Request [current] Jan 2 15:28:40 med111 kernel: sd 2:0:0:3: [sde] Add. Sense: Logical unit not supported Jan 2 15:28:40 med111 kernel: sd 2:0:0:1: [sdc] READ CAPACITY failed Jan 2 15:28:40 med111 kernel: sd 2:0:0:1: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK Jan 2 15:28:40 med111 kernel: sd 2:0:0:1: [sdc] Sense Key : Illegal Request [current] Jan 2 15:28:40 med111 kernel: sd 2:0:0:1: [sdc] Add. Sense: Logical unit not supported Jan 2 15:28:40 med111 kernel: sd 2:0:0:3: [sde] READ CAPACITY failed Jan 2 15:28:40 med111 kernel: sd 2:0:0:3: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK Jan 2 15:28:40 med111 kernel: sd 2:0:0:3: [sde] Sense Key : Illegal Request [current] Jan 2 15:28:40 med111 kernel: sd 2:0:0:3: [sde] Add. Sense: Logical unit not supported Jan 2 15:28:40 med111 kernel: sd 2:0:0:2: [sdd] READ CAPACITY failed Jan 2 15:28:40 med111 kernel: sd 2:0:0:2: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK Jan 2 15:28:40 med111 kernel: sd 2:0:0:2: [sdd] Sense Key : Illegal Request [current] Jan 2 15:28:40 med111 kernel: sd 2:0:0:2: [sdd] Add. Sense: Logical unit not supported Jan 2 15:28:40 med111 kernel: sd 2:0:0:0: [sdb] READ CAPACITY failed Jan 2 15:28:40 med111 kernel: sd 2:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK Jan 2 15:28:40 med111 kernel: sd 2:0:0:0: [sdb] Sense Key : Illegal Request [current] Jan 2 15:28:40 med111 kernel: sd 2:0:0:0: [sdb] Add. Sense: Logical unit not supported Jan 2 15:28:40 med111 kernel: sd 2:0:0:1: [sdc] Test WP failed, assume Write Enabled Jan 2 15:28:40 med111 kernel: sd 2:0:0:1: [sdc] Assuming drive cache: write through Jan 2 15:28:40 med111 kernel: sd 2:0:0:0: [sdb] Test WP failed, assume Write Enabled Jan 2 15:28:40 med111 kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through Jan 2 15:28:40 med111 kernel: sd 2:0:0:3: [sde] Test WP failed, assume Write Enabled Jan 2 15:28:40 med111 kernel: sd 2:0:0:3: [sde] Assuming drive cache: write through Jan 2 15:28:40 med111 kernel: sd 2:0:0:2: [sdd] Test WP failed, assume Write Enabled Jan 2 15:28:40 med111 kernel: sd 2:0:0:2: [sdd] Assuming drive cache: write through Is there something that can be disable to rid of those messages (to prevent waste of diskspace and resource)? -- 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 458979] New: nfs v3 and v4 performance is /really/ bad
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=458979 Summary: nfs v3 and v4 performance is /really/ bad Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: --- Long around September of 2008 (this year, for the next 16 or so days) I did some quick benchmarking of NFS(v3). I was able to see, pretty reliably, 45 MB/s or so. This is with a benchmark like this: dd if=/dev/zero of=some_file bs=1024k count=10000 conv=fdatasync Where $CWD is on an NFS share. I recently re-tested and got really, *really* awful numbers. dd reports a high of 19MB/s (iptraf reports more like half of that). The NFS server's filesystem is not to blame: A test on the actual NFS server's *local* filesystem (the filesystem that has been exported shows not less than 50MB/s, as high as 80MB/s, depending on whether I use ext2, ext3, jfs, or xfs. TCP performance between the two machines averages 50-60MB/s (client->server) and 110-112MB/s (server->client), so it's not network. If it's not network, and it's not the local filesystem performance, it has to be NFS. Where did the performance go? I even tried NFSv4 and the performance was *worse*, not better, than NFSv3. NFSv3 mounted like this: mount -t nfs 192.168.2.1:/exports/huge /mnt -o async,rsize=32768,wsize=32768 and NFSv4 mounted like this: mount -t nfs4 192.168.2.1:/huge /mnt -o async,rsize=32768,wsize=32768 Both over TCP. This is using 2.6.25.18-0.2-default (the stock kernel for openSUSE 11.0, x86_64) which is a more recent kernel than my original tests in September. -- 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 463372] New: Kernel 2.6.27.7 SuSE file monitoring serious bug (inotify )
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=463372 Summary: Kernel 2.6.27.7 SuSE file monitoring serious bug (inotify) Product: openSUSE 11.1 Version: Final Platform: i686 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: johanp(a)aditus.nu QAContact: qa(a)suse.de Found By: Other There's a bug in linux kernel 2.6.27.7 that is used in SuSE 11.1 that creates unkillable, runaway processes when file monitoring is enabled. This is especially critical when trying to run an IMAP service (which needs file monitoring for efficiency reasons) on SuSE 11.1 since it will force the entire server to be hard reset several times a week and makes SuSE 11.1 unsuitable as an IMAP server Hence it is important that the latest stable 2.6.27.10+ kernel can be packaged and distributed as an update. When this update is done notification also needs to go to affected graphic drivers (e.g. NVidia) so they can release appropriate update drivers that match the new kernel and modules. There's a kernel patch [1], and it's supposedly fixed in 2.6.27.10. 1: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h… -- 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 15

[Bug 435594] New: iwl3945 fails to associate with AP
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=435594 Summary: iwl3945 fails to associate with AP Product: openSUSE 11.1 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: david(a)lovesunix.net QAContact: qa(a)suse.de Found By: --- My iwl3945 fails to associate with my AP, the configuration has been tried both with WPA2-PSK as well as entirely unsecured. Same result no network connection. eth0: link down eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.2.204 DST=224.0.0.251 LEN=260 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=240 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.2.204 DST=224.0.0.251 LEN=490 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=470 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.2.204 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.2.204 DST=224.0.0.251 LEN=490 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=470 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.2.204 DST=224.0.0.251 LEN=454 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=434 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.2.204 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.2.204 DST=224.0.0.251 LEN=414 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=394 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.2.204 DST=224.0.0.251 LEN=454 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=434 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.2.204 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44 wlan0: authenticate with AP 00:0e:2e:d5:9e:89 wlan0: authenticated wlan0: associate with AP 00:0e:2e:d5:9e:89 wlan0: RX ReassocResp from 00:0e:2e:d5:9e:89 (capab=0x421 status=0 aid=2) wlan0: associated SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.2.204 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44 wlan0: disassociating by local choice (reason=3) wlan0: authenticate with AP 00:0e:2e:d5:9e:89 wlan0: deauthenticated wlan0: authenticated wlan0: associate with AP 00:0e:2e:d5:9e:89 wlan0: RX AssocResp from 00:0e:2e:d5:9e:89 (capab=0x421 status=0 aid=2) wlan0: associated wlan0: disassociating by local choice (reason=3) SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.2.204 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44 -- 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 45

[Bug 468436] New: sound card disappears periodically under 11.1 - no problems w/11.0 or 10.3
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=468436 Summary: sound card disappears periodically under 11.1 - no problems w/11.0 or 10.3 Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound AssignedTo: tiwai(a)novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-1.1 Firefox/3.0.5 I have a T61p Thinkpad which ran great under 10.3 and 11.0, but under 11.1 I've had no end of sound issues. The first thing after trying and failing several times to get pulseaudio to work, I gave up and removed everything pulseaudio that I could and made sure it was disabled in /etc/sysconfig and went back to using alsa. More or less things work OK except the sound system is very unstable - applications will either hang trying to access the sound device or, what happened today, in the middle of playback the sound device "disappeared". aplay now reports there are 0 sound cards installed The first symptom is that playback stops and the device is reported as busy, then subsequent attempts fail with permission denied, and then nothing works at all: The only messages I've found are in ~/.xsession-errors - there is NOTHING in /var/log/messages or dmesg output. ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:3513:(_snd_config_evaluate) function snd_func_card_driver returned error: Permission denied ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:3513:(_snd_config_evaluate) function snd_func_concat returned error: Permission denied ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name ALSA lib conf.c:3513:(_snd_config_evaluate) function snd_func_refer returned error: Permission denied ALSA lib conf.c:3985:(snd_config_expand) Evaluate error: Permission denied ALSA lib pcm.c:2202:(snd_pcm_open_noupdate) Unknown PCM default crw-rw----+ 1 root audio 116, 7 2009-01-19 16:11 controlC0 crw-rw----+ 1 root audio 116, 6 2009-01-19 16:11 hwC0D0 crw-rw----+ 1 root audio 116, 5 2009-01-20 17:37 pcmC0D0c crw-rw----+ 1 root audio 116, 4 2009-01-22 08:26 pcmC0D0p crw-rw----+ 1 root audio 116, 3 2009-01-19 16:11 pcmC0D1p crw-rw----+ 1 root audio 116, 8 2009-01-19 16:12 seq crw-rw----+ 1 root audio 116, 2 2009-01-19 16:11 timer If I restart alsasound, then things work again for a while. Sometimes it takes more than a day and sometimes it's immediate. I know that twinkle (VOIP phone) was pretty stable under 11.0 and is so far very unstable under 11.1, and using strace it appears to be sound issues. After restarting, /var/log/messages has: usbcore: deregistering interface driver snd-usb-audio HDA Intel 0000:00:1b.0: PCI INT B disabled HDA Intel 0000:00:1b.0: PCI INT B -> GSI 17 (level, low) -> IRQ 17 hda_intel: probe_mask set to 0x1 for device 17aa:20ac HDA Intel 0000:00:1b.0: setting latency timer to 64 And aplay -l: **** List of PLAYBACK Hardware Devices **** card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 1: AD198x Digital [AD198x Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 Reproducible: Sometimes -- 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 408897] New: git-svn 'fetch' broke in opensuse 11.0
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=408897 Summary: git-svn 'fetch' broke in opensuse 11.0 Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: --- The only message I get is this (between ===): === Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi/SVN/Core.pm line 584. Error from SVN, (220001): Item is not readable: === -- 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 447903] New: KDE3 Desktop Settings does not list screensavers.
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=447903 Summary: KDE3 Desktop Settings does not list screensavers. Product: openSUSE 11.1 Version: Beta 5 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE3 AssignedTo: kde-maintainers(a)suse.de ReportedBy: michael_denker(a)gmx.de QAContact: qa(a)suse.de Found By: Beta-Customer The list box of available screen savers in the corresponding KDE3 Control Center applet is empty (fresh install). However, screen savers seem properly installed and are working by the default setting (random screen saver starts after inactivity). -- 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 18

[Bug 470456] New: hald started to suck up all available memory
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=470456 Summary: hald started to suck up all available memory Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Hotplug AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: --- Created an attachment (id=268501) --> (https://bugzilla.novell.com/attachment.cgi?id=268501) screenshot1 User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-1.1 Firefox/3.0.5 I came back from a short absence to find my reasonable machine very sluggish. A quick trip to 'top' showed the cause and culprit - memory pressure induced by hald, which was at that point consuming some 1.4G of memory. Further investigation by our friends 'ps' and 'grep' showed many many many hal-related processes littering the process table. A call to 'killall -9' seemed to resolve the latter, while an 'rchal restart' served the former quite well. However, this should not have happened. Attached please find 2 (two) screenshots. Additionally, I shall paste below some lines from /var/log/messages: Jan 28 18:39:45 worklaptop hald[2692]: forcibly attempting to lazy unmount /dev/sdb as enclosing drive was disconnected Jan 28 18:39:45 worklaptop hald[2692]: forcibly attempting to lazy unmount /dev/sdb as enclosing drive was disconnected Jan 28 18:39:45 worklaptop hald[2692]: forcibly attempting to lazy unmount /dev/sdb as enclosing drive was disconnected Jan 28 18:39:46 worklaptop hald[2692]: forcibly attempting to lazy unmount /dev/sdb as enclosing drive was disconnected Jan 28 18:39:46 worklaptop hald[2692]: forcibly attempting to lazy unmount /dev/sdb as enclosing drive was disconnected Jan 28 18:39:46 worklaptop hald[2692]: forcibly attempting to lazy unmount /dev/sdb as enclosing drive was disconnected Jan 28 18:39:46 worklaptop hald[2692]: forcibly attempting to lazy unmount /dev/sdb as enclosing drive was disconnected Jan 28 18:39:46 worklaptop hald[2692]: forcibly attempting to lazy unmount /dev/sdb as enclosing drive was disconnected Jan 28 18:39:46 worklaptop hald[2692]: forcibly attempting to lazy unmount /dev/sdb as enclosing drive was disconnected Jan 28 18:39:46 worklaptop hald[2692]: forcibly attempting to lazy unmount /dev/sdb as enclosing drive was disconnected Jan 28 18:39:46 worklaptop hald[2692]: forcibly attempting to lazy unmount /dev/sdb as enclosing drive was disconnected Jan 28 18:39:46 worklaptop hald[2692]: forcibly attempting to lazy unmount /dev/sdb as enclosing drive was disconnected Jan 28 18:39:46 worklaptop hald[2692]: forcibly attempting to lazy unmount /dev/sdb as enclosing drive was disconnected Jan 28 18:39:46 worklaptop hald[2692]: forcibly attempting to lazy unmount /dev/sdb as enclosing drive was disconnected Reproducible: Didn't try 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 25