September 2007 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 293726] New: [AI] Creation of Babel wiki
by bugzilla_noreply＠novell.com 28 Jan '09

28 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=293726 Summary: [AI] Creation of Babel wiki Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: ASSIGNED Severity: Enhancement Priority: P5 - None Component: wiki AssignedTo: mrueckert(a)novell.com ReportedBy: stbinner(a)novell.com QAContact: adrian(a)novell.com CC: mlasars(a)suse.de Found By: --- Action item assigned 4th April: "creation of a new wiki called Babel, for languages which haven't yet its own wiki, the Babylon wiki is to build up the language content here and when ready move it to its own wiki, advantage clean up the current wiki and remove the funny "language boxes"" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 5

[Bug 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 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 326957] New: annoying warnings on agent startup
by bugzilla_noreply＠novell.com 23 Jan '09

23 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=326957 Summary: annoying warnings on agent startup Product: openSUSE 10.3 Version: RC 1 Platform: All OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: mrueckert(a)novell.com ReportedBy: thomas.anders(a)blue-cable.de QAContact: qa(a)suse.de Found By: Customer When starting the net-snmp agent (snmpd) in openSUSE 10.3 RC1, it *always* logs the following three annoying warnings: netsnmp_assert !"registration != duplicate" failed agent_registry.c:535 netsnmp_subtree_load() netsnmp_assert !"registration != duplicate" failed agent_registry.c:535 netsnmp_subtree_load() netsnmp_assert !"registration != duplicate" failed agent_registry.c:535 netsnmp_subtree_load() This is fully reproducible and will probably happen for any customer. This has been fixed upstream in SVN Revision 16669. I request to apply a similar patch to the 10.3 net-snmp package. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 2

[Bug 329648] New: KDE hyphenation looks strange
by bugzilla_noreply＠novell.com 23 Jan '09

23 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=329648 Summary: KDE hyphenation looks strange Product: openSUSE 10.3 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: kkemenczy(a)novell.com QAContact: qa(a)suse.de Found By: --- The automatic hyphenation or wordbreak looks strange. Please check the picture. The full message is "Windows-tartománytagság beállítása" and it appears as "Windows-tartománytagsá <break> g beállítása". We have a same issue with KDE desktop trash which is "Szemétkosár" and apperars as "Szemétkos <break> ár". That's why I think this is KDE or Qt and YaST 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 3

[Bug 327104] New: kbluetooth sometimes crashes when auto-starting on device activation
by bugzilla_noreply＠novell.com 23 Jan '09

23 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=327104#c6 Summary: kbluetooth sometimes crashes when auto-starting on device activation Product: openSUSE 10.3 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Mobile Devices AssignedTo: tpatzig(a)novell.com ReportedBy: robin.knapp(a)fujitsu-siemens.com QAContact: qa(a)suse.de Found By: --- This issue has already beend discussed in another bugreport but it was somehow offtopic there, so I'm opening a fresh report after seeing this in RC1. Description: When activating the bluetooth switch of my notebook, kbluetooth starts automatically, but from time to time it directly crashes while starting up. It's possible to run it manually without any crashes afterwards. I have absolutely no idea how to reproduce it for 100%, sometimes it just works several times (switch on, starts, switch off, exit kbluetooth, switch on, starts,...), but sometimes it crashes just on each activation of the switch. With RC1 I was finally able to create a backtrace including linenumbers (with kbluetooth-debuginfo installed), so this may help fixing it. [KCrash handler] #6 0xb749462d in QString::latin1 () from /usr/lib/qt3/lib/libqt-mt.so.3 #7 0xb7495f35 in QString::ascii () from /usr/lib/qt3/lib/libqt-mt.so.3 #8 0xb7f03ce6 in KBluetooth::DBusSignal::newMessage (this=0x0, method=@0xbf8c3588) at /usr/src/debug/kdebluetooth-1.0_beta8/kdebluetooth/libkbluetooth/dbussignal.cpp:83 #9 0xb7f04aec in KBluetooth::DBusSignal::getString (this=0x0, method=@0xbf8c3588, first_type=0) at /usr/src/debug/kdebluetooth-1.0_beta8/kdebluetooth/libkbluetooth/dbussignal.cpp:181 #10 0xb7f04ce8 in KBluetooth::DBusSignal::getString (this=0x0, method=@0xbf8c3588) at /usr/src/debug/kdebluetooth-1.0_beta8/kdebluetooth/libkbluetooth/dbussignal.cpp:167 #11 0xb7effc05 in KBluetooth::Adapter::getMode (this=0x0) at /usr/src/debug/kdebluetooth-1.0_beta8/kdebluetooth/libkbluetooth/adapter.cpp:98 #12 0x0805bb57 in TrayIcon::updateIcon (this=0x80d2c18) at /usr/src/debug/kdebluetooth-1.0_beta8/kdebluetooth/kbluetooth/trayicon.cpp:259 #13 0x0805e6a7 in TrayIcon (this=0x80d2c18, app=0xbf8c3908) at /usr/src/debug/kdebluetooth-1.0_beta8/kdebluetooth/kbluetooth/trayicon.cpp:124 #14 0x0805fbe0 in KBluetoothApp (this=0xbf8c3908) at /usr/src/debug/kdebluetooth-1.0_beta8/kdebluetooth/kbluetooth/application.cpp:84 #15 0x0805ea64 in main (argc=) at /usr/src/debug/kdebluetooth-1.0_beta8/kdebluetooth/kbluetooth/main.cpp:48 #16 0xb6d0bfe0 in __libc_start_main () from /lib/libc.so.6 #17 0x08054791 in _start () -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3

[Bug 329630] New: GNOME menu structure
by bugzilla_noreply＠novell.com 22 Jan '09

22 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=329630 Summary: GNOME menu structure Product: openSUSE 10.3 Version: RC 1 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: infernux(a)web.de QAContact: qa(a)suse.de Found By: Beta-Customer First off, I was amazed by the polishment that went into openSUSE 10.3 so far. But yet, I have a thing that keeps me from using openSUSE as my main distribution: I don't like using the new start menu "slab", while I can see that it is of use for some people, it is not that great for me (I use a wide range of software, more that would fit into "favorites" and the applications window feels "slow" for my needs). Anyway, there is the old menu applet, which I would love to use. However, the menu displayed here is not the default GNOME layout, but a custom layout with a lot of submenus. The same layout is also used when I add custom application launchers to the panel. The problem with the submenus is that I rearely see more than one entry in one submenu. So, for example, in the Graphics menu, I have a submenu "Image Editing" which only holds Gimp. In all, I would have 6 launchers in Graphics, now I have 5 submenus, with each holding one (one holding two) launchers. To make things worse, the submenus use KDE icons, mostly, thus feeling really out of place. It would be great if the default GNOME layout (no submenus) would be used. This would also be more consistant with the SLAB menu, as it would show the same categories as the application window. Perhaps keep the submenus around, but the default should be off. -- 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 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 327454] New: Acer 4320: brightness special keys are not recognized
by bugzilla_noreply＠novell.com 20 Jan '09

20 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=327454 Summary: Acer 4320: brightness special keys are not recognized Product: openSUSE 10.3 Version: RC 1 Platform: i586 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: qa(a)suse.de Found By: --- ( Is this a wish or a bug? -- I am not sure. ) It is typical for laptops that fn+arrow increase or decrease the brightness of the screen. In opensuse 10.3 it does not work, those keys are simply ignored (in console, while booting, they produces sequences like [[^M ) but when KDE starts, no reaction. For comparison I tested also Gparted-live and Slax Popcorn -- those keys work as expected. And what is odd here (in opensuse 10.3), that other special keys like volume up, standby, monitor switch work! And while I am talking about hardware -- many thanks for improved hardware detection, 10.3 is much better than 10.2. Thank you very much! -- 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 11