May 2007 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 232984] New: ifolder on 10.3
by bugzilla_noreply＠novell.com 05 Feb '09

05 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=232984 Summary: ifolder on 10.3 Product: openSUSE 10.3 Version: unspecified Platform: All URL: http://lists.opensuse.org/opensuse-factory/2006- 12/msg00403.html OS/Version: SuSE Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: tbullock(a)canada.com QAContact: qa(a)suse.de This is a request for inclusion of the ifolder server in the 10.3 distribution. Thread discussing this on the opensuse-factory mailing list: http://lists.opensuse.org/opensuse-factory/2006-12/msg00403.html -- 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 22

[Bug 223868] New: kcontrol logitech mouse settings want to access /proc/bus/usb
by bugzilla_noreply＠novell.com 04 Feb '09

04 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=223868 Summary: kcontrol logitech mouse settings want to access /proc/bus/usb Product: openSUSE 10.2 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: robin.knapp(a)fujitsu-siemens.com QAContact: qa(a)suse.de Trying to set the advanced settings of logitech mice in KDE Control Center, the applet complains about wrong rights. In documentation "help:/kcontrol/mouse/index.html" there is some information that the applet needs access to /proc/bus/usb which does not exist in udev. Instead /dev/bus/usb should be used. -- 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 26

[Bug 238282] New: while changing the first or last name of ldap users, the cn is not updated
by bugzilla_noreply＠novell.com 04 Feb '09

04 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=238282 Summary: while changing the first or last name of ldap users, the cn is not updated Product: SUSE Linux 10.1 Version: Final Platform: x86-64 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: reitenbach(a)rapideye.de QAContact: jsrain(a)novell.com As the cn entry in ldap consists of a first name and last name, it should get updated when the first name or last name of the user is changed. Many services use the cn, and not the first and last name fields from the ldap server, and therefore present the "not updated", plain wrong, values. as far as I can see, the uid is the field to distinguish users, it shouldn't be a problem to change the cn. -- 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 13

[Bug 227392] New: dialog translated badly to german ("Cancel" should be "Abbrechen", not "Verwerfen")
by bugzilla_noreply＠novell.com 02 Feb '09

02 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=227392 Summary: dialog translated badly to german ("Cancel" should be "Abbrechen", not "Verwerfen") Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Translations AssignedTo: ke(a)novell.com ReportedBy: timmi(a)gmx-topmail.de QAContact: ke(a)novell.com CC: timmi(a)gmx-topmail.de It's about the following dialog: YaST -> Partitioning. Try to delete a partition which is currently mounted. You get displayed in dialog (english: snapshot1.png, german: Bildschirmphoto3.png). In the german translation, you see "Wenn Sie unsicher sind, drücken Sie auf 'Verwerfen'." Should be 'Abbrechen' instead, because the button is also 'Abbrechen'. (In the english version, both is 'Cancel'.) -- 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 38

[Bug 259698] New: [DSL] patch /etc/ppp/if-up to support ip of access gateway not in local lan
by bugzilla_noreply＠novell.com 28 Jan '09

28 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=259698 Summary: [DSL] patch /etc/ppp/if-up to support ip of access gateway not in local lan Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: fl(a)fl.priv.at QAContact: qa(a)suse.de When one sets up a PPTP DSL connection to an access gateway which does not reside in the local LAN but behind some gateway in the local LAN then one needs to patch /etc/ppp/if-up to add a route via that gateway to the access gateway. Otherwise pppd sets the route to the access gateway through the tunnel which breaks horribly. Already submitted after SuSE 9.2 cam out but has never been locked at as it seems. Attachment with patch follows later. -- 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 18

[Bug 223290] New: [AI] better wishlist handling using FATE
by bugzilla_noreply＠novell.com 28 Jan '09

28 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=223290 Summary: [AI] better wishlist handling using FATE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Action Items AssignedTo: adrian(a)novell.com ReportedBy: suse-beta(a)cboltz.de QAContact: adrian(a)novell.com http://en.opensuse.org/Meetings/Status_Meeting_2006-11-22 Action Item AdrianS / klaas: - implement better wishlist handling with FATE (Handling it in the wiki is painful.) -- 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 40

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

25 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 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