July 2007 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 269747] New: NetworkManager slow to start Wifi
by bugzilla_noreply＠novell.com 24 Jan '09

24 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=269747 Summary: NetworkManager slow to start Wifi Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: o.wise.1(a)bigpond.com QAContact: qa(a)suse.de I am running SUSE10.2 on a Dell laptop (Inspirion 8200) with a Belkin wireless card. Networking works fine .... once it gets going (bit like me in the morning). If I use ifup the card starts OK during boot. If I use the Networkmanager tool the card takes a long time to start up and get an IP address. Networkmanager also tries stating the built in wired eth0 connection even though there is no cable connected (does not appear to support sensing cable connection). Setting the wired connection to manual does not change behaviour. Looking at networkmanager log there is a message about request_and_convert_scan_results(): card took too much time scanning. Get a better one." It appears that networkmanager may not be waiting long enough for this card to pickup a signal? log output from var/log/networkmanager follows: Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.034292] nm_system_device_get_system_config(): found config '/etc/sysconfig/network/ifcfg-wlan-id-00:30:bd:d2:6a:61' for interface 'eth1' Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.186370] nm_system_device_get_system_config(): BOOTPROTO=dhcp Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.186677] nm_system_device_get_system_config(): Adding 'WLAN' to the list of trusted networks Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.186747] nm_system_device_get_system_config(): ------ Config (eth1) Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.186782] nm_system_device_get_system_config(): dhcp=1 Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.186854] nm_system_device_get_system_config(): addr=0.0.0.0 Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.186886] nm_system_device_get_system_config(): gw=0.0.0.0 Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.186915] nm_system_device_get_system_config(): mask=0.0.0.0 Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.186950] nm_system_device_get_system_config(): --------------------- Apr 27 19:07:53 laptop NetworkManager: <info> eth1: Device is fully-supported using driver 'atmel_cs'. Apr 27 19:07:53 laptop NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start Apr 27 19:07:53 laptop NetworkManager: <info> nm_device_init(): device's worker thread started, continuing. Apr 27 19:07:53 laptop NetworkManager: <info> Now managing wireless (802.11) device 'eth1'. Apr 27 19:07:53 laptop NetworkManager: <info> Deactivating device eth1. Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.466229] nm_system_device_get_system_config(): found config '/etc/sysconfig/network/ifcfg-eth-id-00:0b:db:16:6a:1b' for interface 'eth0' Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.466543] nm_system_device_get_system_config(): BOOTPROTO=dhcp Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.466664] nm_system_device_get_system_config(): ------ Config (eth0) Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.466762] nm_system_device_get_system_config(): dhcp=1 Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.466856] nm_system_device_get_system_config(): addr=0.0.0.0 Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.466948] nm_system_device_get_system_config(): gw=0.0.0.0 Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.467039] nm_system_device_get_system_config(): mask=0.0.0.0 Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.467127] nm_system_device_get_system_config(): --------------------- Apr 27 19:07:53 laptop NetworkManager: <info> eth0: Device is fully-supported using driver '3c59x'. Apr 27 19:07:53 laptop NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start Apr 27 19:07:53 laptop NetworkManager: <info> nm_device_init(): device's worker thread started, continuing. Apr 27 19:07:53 laptop NetworkManager: <info> Now managing wired Ethernet (802.3) device 'eth0'. Apr 27 19:07:53 laptop NetworkManager: <info> Deactivating device eth0. Apr 27 19:07:53 laptop NetworkManager: <info> Will activate wired connection 'eth0' because it now has a link. Apr 27 19:07:53 laptop NetworkManager: <info> SWITCH: no current connection, found better connection 'eth0'. Apr 27 19:07:53 laptop NetworkManager: <info> Will activate connection 'eth0'. Apr 27 19:07:53 laptop NetworkManager: <info> Device eth0 activation scheduled... Apr 27 19:07:53 laptop NetworkManager: <info> Activation (eth0) started... Apr 27 19:07:53 laptop NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... Apr 27 19:07:53 laptop NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started... Apr 27 19:07:53 laptop NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... Apr 27 19:07:53 laptop NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete. Apr 27 19:07:53 laptop NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting... Apr 27 19:07:53 laptop NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful. Apr 27 19:07:53 laptop NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. Apr 27 19:07:53 laptop NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete. Apr 27 19:07:53 laptop NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started... Apr 27 19:07:54 laptop NetworkManager: <info> Activation (eth0) Beginning DHCP transaction. Apr 27 19:07:55 laptop NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Apr 27 19:07:55 laptop NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface eth0 Apr 27 19:07:55 laptop NetworkManager: <info> Old device 'eth0' activating, won't change. Apr 27 19:07:57 laptop NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface eth0 Apr 27 19:08:03 laptop NetworkManager: <info> Old device 'eth0' activating, won't change. Apr 27 19:08:33 laptop NetworkManager: <info> Old device 'eth0' activating, won't change. Apr 27 19:08:40 laptop NetworkManager: <info> Deactivating device eth1. Apr 27 19:08:40 laptop NetworkManager: <info> Updating allowed wireless network lists. Apr 27 19:08:40 laptop NetworkManager: <info> Old device 'eth0' activating, won't change. Apr 27 19:08:40 laptop NetworkManager: <info> Device 'eth0' DHCP transaction took too long (>45s), stopping it. Apr 27 19:08:41 laptop NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Timeout) scheduled... Apr 27 19:08:41 laptop NetworkManager: <info> DHCP daemon state is now 14 (normal exit) for interface eth0 Apr 27 19:08:41 laptop NetworkManager: <info> DHCP daemon state is now 11 (unknown) for interface eth0 Apr 27 19:08:41 laptop NetworkManager: <info> DHCP daemon state is now 14 (normal exit) for interface eth0 Apr 27 19:08:41 laptop NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Timeout) started... Apr 27 19:08:41 laptop NetworkManager: <info> No DHCP reply received. Automatically obtaining IP via Zeroconf. Apr 27 19:08:41 laptop NetworkManager: <info> autoip: Sending probe #0 for IP address 169.254.74.81. Apr 27 19:08:41 laptop NetworkManager: <info> autoip: Waiting for reply... Apr 27 19:08:41 laptop NetworkManager: <info> Old device 'eth0' activating, won't change. Apr 27 19:08:43 laptop NetworkManager: <info> autoip: Sending probe #1 for IP address 169.254.74.81. Apr 27 19:08:43 laptop NetworkManager: <info> autoip: Waiting for reply... Apr 27 19:08:45 laptop NetworkManager: <info> autoip: Sending probe #2 for IP address 169.254.74.81. Apr 27 19:08:45 laptop NetworkManager: <info> autoip: Waiting for reply... Apr 27 19:08:47 laptop NetworkManager: <info> autoip: Sending announce #0 for IP address 169.254.74.81. Apr 27 19:08:47 laptop NetworkManager: <info> autoip: Waiting for reply... Apr 27 19:08:50 laptop NetworkManager: <info> autoip: Sending announce #1 for IP address 169.254.74.81. Apr 27 19:08:50 laptop NetworkManager: <info> autoip: Waiting for reply... Apr 27 19:08:52 laptop NetworkManager: <info> Old device 'eth0' activating, won't change. Apr 27 19:08:53 laptop NetworkManager: <info> autoip: Sending announce #2 for IP address 169.254.74.81. Apr 27 19:08:53 laptop NetworkManager: <info> autoip: Waiting for reply... Apr 27 19:08:56 laptop NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... Apr 27 19:08:56 laptop NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Timeout) complete. Apr 27 19:08:56 laptop NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started... Apr 27 19:08:57 laptop NetworkManager: <info> Clearing nscd hosts cache. Apr 27 19:08:57 laptop NetworkManager: <info> Activation (eth0) successful, device activated. Apr 27 19:08:57 laptop NetworkManager: <info> Activation (eth0) Finish handler scheduled. Apr 27 19:08:57 laptop NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete. Apr 27 19:09:03 laptop NetworkManager: <debug> [1177664943.028429] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'WLAN' Apr 27 19:09:03 laptop NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/eth1 / WLAN Apr 27 19:09:03 laptop NetworkManager: <info> Deactivating device eth1. Apr 27 19:09:03 laptop NetworkManager: <info> Device eth1 activation scheduled... Apr 27 19:09:03 laptop NetworkManager: <info> Deactivating device eth0. Apr 27 19:09:03 laptop NetworkManager: <info> Activation (eth1) started... Apr 27 19:09:03 laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... Apr 27 19:09:03 laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started... Apr 27 19:09:03 laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled... Apr 27 19:09:03 laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete. Apr 27 19:09:03 laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting... Apr 27 19:09:03 laptop NetworkManager: <info> Activation (eth1/wireless): access point 'WLAN' is unencrypted, no key needed. Apr 27 19:09:03 laptop NetworkManager: <info> SUP: sending command 'INTERFACE_ADD eth1 wext /var/run/wpa_supplicant ' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: response was 'OK' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: sending command 'AP_SCAN 1' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: response was 'OK' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: sending command 'ADD_NETWORK' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: response was '0' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 574c414e' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: response was 'OK' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 scan_ssid 1' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: response was 'OK' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: response was 'OK' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: response was 'OK' Apr 27 19:09:03 laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete. Apr 27 19:09:04 laptop NetworkManager: <info> Old device 'eth1' activating, won't change. Apr 27 19:09:20 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:09:27 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:09:32 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:09:37 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:09:41 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:09:45 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:09:50 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:09:50 laptop NetworkManager: <info> Activation (eth1/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point 'WLAN'. Apr 27 19:09:50 laptop NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled. Apr 27 19:09:54 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:09:58 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:02 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:07 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:11 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:15 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:20 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:24 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:28 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:33 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:37 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:41 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:46 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:50 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:50 laptop NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) started... Apr 27 19:10:51 laptop NetworkManager: <info> Activation (eth1) Beginning DHCP transaction. Apr 27 19:10:52 laptop NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) complete. Apr 27 19:10:52 laptop NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface eth1 Apr 27 19:10:52 laptop NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface eth1 Apr 27 19:10:57 laptop NetworkManager: <info> DHCP daemon state is now 2 (bound) for interface eth1 Apr 27 19:10:57 laptop NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) scheduled... Apr 27 19:10:57 laptop NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) started... Apr 27 19:10:57 laptop NetworkManager: <info> Retrieved the following IP4 configuration from the DHCP daemon: Apr 27 19:10:57 laptop NetworkManager: <info> address 192.168.2.58 Apr 27 19:10:57 laptop NetworkManager: <info> netmask 255.255.255.0 Apr 27 19:10:57 laptop NetworkManager: <info> broadcast 255.255.255.255 Apr 27 19:10:57 laptop NetworkManager: <info> gateway 192.168.2.1 Apr 27 19:10:57 laptop NetworkManager: <info> nameserver 192.168.2.1 Apr 27 19:10:57 laptop NetworkManager: <info> domain name 'Belkin' Apr 27 19:10:57 laptop NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) scheduled... Apr 27 19:10:57 laptop NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) complete. Apr 27 19:10:57 laptop NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) started... Apr 27 19:10:58 laptop NetworkManager: <info> Clearing nscd hosts cache. Apr 27 19:10:58 laptop NetworkManager: <info> Activation (eth1) successful, device activated. Apr 27 19:10:58 laptop NetworkManager: <info> Activation (eth1) Finish handler scheduled. Apr 27 19:10:58 laptop NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete. -- 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 17

[Bug 214311] New: Package "sapinit" sets shared memory too low
by bugzilla_noreply＠novell.com 22 Jan '09

22 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=214311 Summary: Package "sapinit" sets shared memory too low Product: SUSE Linux 10.1 Version: Final Platform: x86-64 OS/Version: SLES 10 Status: NEW Severity: Normal Priority: P5 - None Component: Commercial AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Ulrich.Windl(a)rz.uni-regensburg.de QAContact: qa(a)suse.de The /etc/sysctl.conf.sap file (of package "sapinit") includes a shared memory setting kernel.shmall of about 5GB. As about 90% of SAP R/3's memory is located within shared memory segments, this setting prevents to use 8 GB or larger shared memory configurations. dev_disp of SAP says: Warning: tmpfs at /dev/shm is configured quite small with 3584 MB! Minimum value is 8192 MB. Recommended size is 75 % of RAM + swap -- 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 9

[Bug 284339] New: Can't digitally sign OpenOffice documents on x86_64
by bugzilla_noreply＠novell.com 21 Jan '09

21 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=284339 Summary: Can't digitally sign OpenOffice documents on x86_64 Product: openSUSE 10.3 Version: Alpha 5 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: OpenOffice.org AssignedTo: eward(a)novell.com ReportedBy: sbrys(a)novell.com QAContact: qa(a)suse.de Environment: - openSUSE Alpha5 on x86_64 platform Steps to duplicate: - open Firefox and go to Edit > Preferences > View Certificates - click Import and import the pfx file attached -- the password is "novell". You'll also need to enter an NSS password of your choice. - click Ok and Close - open a terminal window - type the following command: export MOZILLA_CERTIFICATE_FOLDER="/home/sbrys/.mozilla/firefox/1chxc07l.default" (replace with the path to your firefox profile) - still in the terminal window, run oowriter - in oowriter, create a document and save it - click File > Digital Signatures > Add - enter the NSS password you entered previously when you imported the pfx file - view the certificate -- everything should be valid - select the certificate and click Ok - result: nothing is added to the signatures list Notes: - I tested the procedure above on an openSUSE 10.3 Alpha4 on i386 and there it works fine. - The same problem exists when using the Belgian electronic identity card (eID) - I tested mail signing (Evolution and Thunderbird) and web site authentication (Firefox) using eID and that works fine. So it looks like the NSS part is working properly. -- 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 11

[Bug 281147] New: We should increase fs.inotify.max_user_watches to 65536 in /etc/sysctl.conf
by bugzilla_noreply＠novell.com 19 Jan '09

19 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=281147 Summary: We should increase fs.inotify.max_user_watches to 65536 in /etc/sysctl.conf Product: openSUSE 10.3 Version: Alpha 4plus Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: joeshaw(a)novell.com QAContact: qa(a)suse.de A common problem for users with large home directories is that Beagle tends to use up all of the inotify watches as it monitors file changes for indexing. We should set fs.inotify.max_user_watches in /etc/sysctl.conf to a pretty high value like 65536 -- the default is 8192 -- to help alleviate this problem for many users. Kernel memory is allocated as the watches are taken, so for those who would not use additional watches, there is no adverse effect. -- 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 275767] New: Konqueror doesn't always cleanup status bar
by bugzilla_noreply＠novell.com 19 Jan '09

19 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=275767 Summary: Konqueror doesn't always cleanup status bar Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: suse-beta(a)cboltz.de QAContact: qa(a)suse.de (using KDE from the buildservice, kdebase3-3.5.6-64.4, builddate 2007-04-23) I noticed that Konqueror doesn't always clean up the status bar. This happens when you move from a "normal" <a href=...> link to a JavaScript onClick link or a form label. To reproduce, - go to http://www.suse.de/~fs/opensuse/download/index_cols.html - scroll down to section "3. Choose a download method" - hover the word "BitTorrent" (near the option button, left of the "Help" link) -> status bar empty, OK - hover the "Help" link next to "BitTorrent" -> status bar shows the link target, OK - hover the word "BitTorrent" (near the option button, left of the "Help" link) -> status bar still shows the "Help" link target - _not_ OK Expected result: - the status bar should be empty after leaving the "Help" link This is just an optical problem in the status bar, clicking does the right thing. -- 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 3

[Bug 207608] New: Options for NIC are ignored
by bugzilla_noreply＠novell.com 19 Jan '09

19 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=207608 Summary: Options for NIC are ignored Product: SUSE Linux 10.1 Version: Final Platform: x86-64 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST AssignedTo: ug(a)novell.com ReportedBy: pgunreben(a)lucent.com QAContact: qa(a)suse.de Although, I have configured options for the NIC, these options seem to be ignored by AutoYaST. The XML file has been generated using yast2 autoyast on a SuSE 10.1 OS. Here's the section for the NIC kernel module: <modules config:type="list"> <module_entry> <device>static-0</device> <module>tg3</module> <options>line_speed=100 auto_speed=0 full_duplex=1</options> </module_entry> </modules> In the installed computer, I found the file /etc/sysconfig/hardware/hwcfg-bus-pci-0000:02:00.0 with the following content: MODULE='tg3' MODULE_OPTIONS='' STARTMODE='auto' I suspect that the NIC options should be written to this file, shouldn't they? -- 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 266936] New: Update via network from (unfinished inst of) 10.2 to 10.3 creates strange Network Test dialog content
by bugzilla_noreply＠novell.com 19 Jan '09

19 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=266936 Summary: Update via network from (unfinished inst of) 10.2 to 10.3 creates strange Network Test dialog content Product: openSUSE 10.3 Version: Alpha 3 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: kmachalkova(a)novell.com ReportedBy: locilka(a)novell.com QAContact: jsrain(a)novell.com How did I get there? * Installed fist stage of 10.2 (minimal installation) * Unfinished second stage installation (reboot before network setup) * Network installation / Upgrade to 10.3 * First stage, reboot and second stage... Test Internet Connection dialog contains: (x) Yes, Test Connection to the Internet via Unknown device - unknown (127.0.0.1) Pressing the [Change Device] button opens up a table with this content: Device Type | Device Name | IP Address | Device -------------+----------------+------------------------+------- network card | Unknown device | No IP address assigned | eth0 network card | Unknown device | No IP address assigned | eth1 This is a network installation so at least, some connection could have been established. rcnetwork status returns: No configuration found for eth0 .... unused No configuration found for eth1 .... unused IP address: 127.0.0.1/8 .... running Honestly, upgrade from unfinished installation of 10.2 to 10.3 doesn't seem to be a 100% valid case, nevertheless test via 127.0.0.1 should not appear there. -- 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

[Bug 222967] New: Disk Usage should return mounted disks starting with the slash
by bugzilla_noreply＠novell.com 16 Jan '09

16 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=222967 Summary: Disk Usage should return mounted disks starting with the slash Product: openSUSE 10.3 Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: libzypp AssignedTo: lslezak(a)novell.com ReportedBy: locilka(a)novell.com QAContact: kkaempf(a)novell.com Currently the pattern selector shows this: / [==| ] 3% usr [====| ] 9% var [=| ] 0% but it should look like: / [==| ] 3% /usr [====| ] 9% /var [=| ] 0% Screenshot will be attached also with y2logs. -- 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 10

[Bug 256642] New: STL redefines try and catch keywords
by bugzilla_noreply＠novell.com 15 Jan '09

15 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=256642 Summary: STL redefines try and catch keywords Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: llunak(a)novell.com QAContact: qa(a)suse.de CC: dmueller(a)novell.com == testcase == #include <memory> void bar(); struct Foo; bool test() { try { bar(); } catch (Foo&) { return false; } return true; } == testcase == This testcase compiles without an error when compiled with -fno-exceptions, even though clearly it should not. The reason is /usr/include/c++/4.1.2/exception_defines.h which globally changes the keywords. Since compiling with exceptions has some costs associated, it makes sense to compile with -fno-exceptions and explicitly enable exceptions only for source that actually needs it. However, including any STL header effectively breaks this approach, as such places won't be found due to the missing compiler error. -- 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 14

[Bug 269856] New: Network Manager shows "No Network Connection" yet internet access available through WLAN
by bugzilla_noreply＠novell.com 15 Jan '09

15 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=269856 Summary: Network Manager shows "No Network Connection" yet internet access available through WLAN Product: openSUSE 10.3 Version: Alpha 3 Platform: x86 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: casualprogrammer(a)yahoo.com QAContact: qa(a)suse.de This is on an FSC Amilo Si1520 running openSuSE 10.3 alpha3plus ( GNOME ) with Network Manager enabled. While no wired network is connected and Network Manager claims not to be able to connect to any available WLAN, a connection is made to an access point and internet access is possible. dmesg shows: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready eth0: no IPv6 routers present martian source 255.255.255.255 from 192.168.0.1, on dev eth0 ll header: ff:ff:ff:ff:ff:ff:00:04:0e:a4:4f:a5:08:00 martian source 255.255.255.255 from 192.168.0.1, on dev eth0 ll header: ff:ff:ff:ff:ff:ff:00:04:0e:a4:4f:a5:08:00 eth1: no IPv6 routers present eth0: no IPv6 routers present SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.0.30 DST=195.135.221.130 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=16678 DF PROTO=TCP SPT=13131 DPT=80 WINDOW=3353 RES=0x00 ACK FIN URGP=0 OPT (0101080A000DF9AE10D546A9) SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.0.30 DST=88.191.250.2 LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=49603 DF PROTO=TCP SPT=22404 DPT=80 WINDOW=66 RES=0x00 ACK FIN URGP=0 e100: eth0: e100_watchdog: link down eth1: no IPv6 routers present ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready eth1: no IPv6 routers present martian source 255.255.255.255 from 192.168.182.1, on dev eth1 ll header: 00:13:02:18:12:ac:00:18:84:11:bb:51:08:00 martian source 255.255.255.255 from 192.168.182.1, on dev eth1 ll header: 00:13:02:18:12:ac:00:18:84:11:bb:51:08:00 eth1: no IPv6 routers present -- 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 15