Bug 220234

Summary: Knetworkmanager crash imediately after startup.
Product: [openSUSE] openSUSE 10.2 Reporter: Robby Verberne <monkey9>
Component: KDEAssignee: Timo Hoenig <thoenig>
Status: VERIFIED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Blocker    
Priority: P5 - None CC: hugo.costelha, wittemar, wns
Version: Beta 2   
Target Milestone: Beta 2 plus   
Hardware: 64bit   
OS: SUSE Other   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: KNetworkManager crash log
My actual backtrace
knetwrkmngrtrcbk
kdekicker
kmserver
NetworkManager log

Description Robby Verberne 2006-11-11 22:15:37 UTC 
This happens every startup.
During upgrading to Beta2, i saw the systemtray icon change to not connected, but the connection was allright, and the mouseover told: wired conection ok.
TRhe connection is allright, networkmanager is down.

System configuration startup check disabled.

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47453506218032 (LWP 3696)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#4  0x00002b289d25b535 in raise () from /lib64/libc.so.6
#5  0x00002b289d25c990 in abort () from /lib64/libc.so.6
#6  0x00002b28a2713c65 in dbus_malloc () from /usr/lib64/libdbus-1.so.3
#7  0x00002b28a271023a in dbus_watch_handle () from /usr/lib64/libdbus-1.so.3
#8  0x00002b28a26fb7c1 in dbus_connection_dispatch ()
   from /usr/lib64/libdbus-1.so.3
#9  0x00002b28a20d2290 in DBusQt::Connection::dispatchRead ()
   from /usr/lib64/libdbus-qt-1.so.1
#10 0x00002b28a20d28cf in DBusQt::Connection::qt_invoke ()
   from /usr/lib64/libdbus-qt-1.so.1
#11 0x00002b289c2deadc in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#12 0x00002b289c2df7b3 in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#13 0x00002b28a20d3021 in DBusQt::Internal::Integrator::slotRead ()
   from /usr/lib64/libdbus-qt-1.so.1
#14 0x00002b28a20d328e in DBusQt::Internal::Integrator::qt_invoke ()
   from /usr/lib64/libdbus-qt-1.so.1
#15 0x00002b289c2deadc in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#16 0x00002b289c2df6df in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#17 0x00002b289c2f92cb in QSocketNotifier::event ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#18 0x00002b289c287eb5 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#19 0x00002b289c288c40 in QApplication::notify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#20 0x00002b289bccde28 in KApplication::notify ()
   from /opt/kde3/lib64/libkdecore.so.4
#21 0x00002b289c27d61b in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#22 0x00002b289c23e5f0 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#23 0x00002b289c29c963 in QEventLoop::enterLoop ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#24 0x00002b289c29c812 in QEventLoop::exec ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#25 0x00002b28a1ca1480 in kdemain ()
   from /opt/kde3/lib64/libkdeinit_knetworkmanager.so
#26 0x0000000000407491 in QGList::~QGList ()
#27 0x0000000000407dc4 in QGList::~QGList ()
#28 0x0000000000408185 in QGList::~QGList ()
#29 0x00000000004091da in QGList::~QGList ()
#30 0x00002b289d248ae4 in __libc_start_main () from /lib64/libc.so.6
#31 0x0000000000404a89 in QGList::~QGList ()
#32 0x00007fff0fa278d8 in ?? ()
#33 0x0000000000000000 in ?? ()
Comment 1 Dirk Mueller 2006-11-11 22:39:32 UTC 
can you try reproducing this with knetworkmanager started from a terminal? there should have been some output which might be helpful finding the bug.
Comment 3 Timo Hoenig 2006-11-11 22:47:54 UTC 
Robby, the behavior as described in the initial bug report sounds like the IPC between KNetworkManager and NetworkManager got interrupted as D-Bus was updated and restarted.

Are you saying that now KNetworkManager keeps crashing on each start?
Comment 4 Robby Verberne 2006-11-12 09:46:59 UTC 
Indeed, it happens all the time.
(Most disturbing, however, is that i have to log in tty1, before i can startx, to enter the graphic environment,each time, after upgrading to B2...i will file a bug about that also.)
I will use the terminal, and post output here...
Comment 5 Timo Hoenig 2006-11-12 10:01:04 UTC 
It will most likely help if you could install the package 'NetworkManager-kde-debuginfo'.  To accomplish that, please add

ftp://mirrors.kernel.org/opensuse/distribution/SL-OSS-factory-debug/inst-source-debug/

as an additional installation source.

Then run 'knetworkmanager' from a terminal and post the debug output to this bug.

Thanks!
Comment 6 Robby Verberne 2006-11-12 10:53:04 UTC 
(First this:
#### YaST2 conflicts list - generated 2006-11-12 11:42:04 ####

NetworkManager-kde-debuginfo-0.1r602671-2.x86_64[20061112-112007] kan niet worden ge�stalleerd vanwege ontbrekende afhankelijkheden
    Er zijn geen installeerbare aanbieders van NetworkManager-kde == 0.1r602671-2 voor NetworkManager-kde-debuginfo-0.1r602671-2.x86_64[20061112-112007]
    Conflictoplossing:
        ( ) NetworkManager-kde-debuginfo niet installeren
        ( ) Deze vereiste alleen hier negeren

#### YaST2 conflicts list END ###

I ignored to install)
____________

monkey9@tribal-sfn2:~> knetworkmanager
process 5495: arguments to dbus_pending_call_unref() were incorrect, assertion "pending != NULL" failed in file dbus-pending-call.c line 563.
This is normally a bug in some application using the D-Bus library.
  D-Bus not built with -rdynamic so unable to print a backtrace
KCrash: Application 'knetworkmanager' crashing...
ERROR: Communication problem with knetworkmanager, it probably crashed.
monkey9@tribal-sfn2:~>

System configuration startup check disabled.

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47846551634560 (LWP 5495)]
[KCrash handler]
#4  0x00002b841d0a3535 in raise () from /lib64/libc.so.6
#5  0x00002b841d0a4990 in abort () from /lib64/libc.so.6
#6  0x00002b841dc06c65 in dbus_malloc () from /usr/lib64/libdbus-1.so.3
#7  0x00002b841dc0323a in dbus_watch_handle () from /usr/lib64/libdbus-1.so.3
#8  0x00002b841dbee7c1 in dbus_connection_dispatch ()
   from /usr/lib64/libdbus-1.so.3
#9  0x00002b841d5c4290 in DBusQt::Connection::dispatchRead ()
   from /usr/lib64/libdbus-qt-1.so.1
#10 0x00002b841d5c48cf in DBusQt::Connection::qt_invoke ()
   from /usr/lib64/libdbus-qt-1.so.1
#11 0x00002b841f60cadc in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#12 0x00002b841f60d7b3 in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#13 0x00002b841d5c5021 in DBusQt::Internal::Integrator::slotRead ()
   from /usr/lib64/libdbus-qt-1.so.1
#14 0x00002b841d5c528e in DBusQt::Internal::Integrator::qt_invoke ()
   from /usr/lib64/libdbus-qt-1.so.1
#15 0x00002b841f60cadc in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#16 0x00002b841f60d6df in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#17 0x00002b841f6272cb in QSocketNotifier::event ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#18 0x00002b841f5b5eb5 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#19 0x00002b841f5b6c40 in QApplication::notify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#20 0x00002b841edbee28 in KApplication::notify ()
   from /opt/kde3/lib64/libkdecore.so.4
#21 0x00002b841f5ab61b in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#22 0x00002b841f56c5f0 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#23 0x00002b841f5ca963 in QEventLoop::enterLoop ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#24 0x00002b841f5ca812 in QEventLoop::exec ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#25 0x00002b841ce50480 in kdemain (argc=<value optimized out>, 
    argv=<value optimized out>) at ./knetworkmanager/src/main.cpp:55
#26 0x00002b841d090ae4 in __libc_start_main () from /lib64/libc.so.6
#27 0x0000000000400599 in _start ()
Comment 7 Hugo Costelha 2006-11-12 11:37:21 UTC 
*** Bug 220235 has been marked as a duplicate of this bug. ***
Comment 8 Hugo Costelha 2006-11-12 11:57:44 UTC 
Created attachment 104832 [details]
KNetworkManager crash log

The same hapends to me. I attached my log (with *-debuginfo installed, althout the lates versions do not seem to be available in the FACTORY-DEGUG tree).

Using AMD64.
Comment 9 Timo Hoenig 2006-11-12 13:45:47 UTC 
I'm still not able to reproduce the problem but found some suspicious code paths.  Please install the updated packages available at

* http://beta.suse.com/private/thoenig/10.2/

and let me know if it fixes the problem.

Thanks!
Comment 10 Robby Verberne 2006-11-12 15:09:26 UTC 
Did what you asked:

Systeemconfiguratie opstartcontrole uitgeschakeld.

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47394891827248 (LWP 3729)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#4  0x00002b1af7751535 in raise () from /lib64/libc.so.6
#5  0x00002b1af7752990 in abort () from /lib64/libc.so.6
#6  0x00002b1afcc09c65 in dbus_malloc () from /usr/lib64/libdbus-1.so.3
#7  0x00002b1afcc0623a in dbus_watch_handle () from /usr/lib64/libdbus-1.so.3
#8  0x00002b1afcbf17c1 in dbus_connection_dispatch ()
   from /usr/lib64/libdbus-1.so.3
#9  0x00002b1afc5c8290 in DBusQt::Connection::dispatchRead ()
   from /usr/lib64/libdbus-qt-1.so.1
#10 0x00002b1afc5c88cf in DBusQt::Connection::qt_invoke ()
   from /usr/lib64/libdbus-qt-1.so.1
#11 0x00002b1af67d4adc in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#12 0x00002b1af67d57b3 in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#13 0x00002b1afc5c9021 in DBusQt::Internal::Integrator::slotRead ()
   from /usr/lib64/libdbus-qt-1.so.1
#14 0x00002b1afc5c928e in DBusQt::Internal::Integrator::qt_invoke ()
   from /usr/lib64/libdbus-qt-1.so.1
#15 0x00002b1af67d4adc in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#16 0x00002b1af67d56df in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#17 0x00002b1af67ef2cb in QSocketNotifier::event ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#18 0x00002b1af677deb5 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#19 0x00002b1af677ec40 in QApplication::notify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#20 0x00002b1af61c3e28 in KApplication::notify ()
   from /opt/kde3/lib64/libkdecore.so.4
#21 0x00002b1af677361b in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#22 0x00002b1af67345f0 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#23 0x00002b1af6792963 in QEventLoop::enterLoop ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#24 0x00002b1af6792812 in QEventLoop::exec ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#25 0x00002b1afc197490 in kdemain (argc=<value optimized out>, 
    argv=<value optimized out>) at ./knetworkmanager/src/main.cpp:55
#26 0x0000000000407491 in QGList::~QGList ()
#27 0x0000000000407dc4 in QGList::~QGList ()
#28 0x0000000000408185 in QGList::~QGList ()
#29 0x00000000004091da in QGList::~QGList ()
#30 0x00002b1af773eae4 in __libc_start_main () from /lib64/libc.so.6
#31 0x0000000000404a89 in QGList::~QGList ()
#32 0x00007fffb55313c8 in ?? ()
#33 0x0000000000000000 in ?? ()
Comment 11 Timo Hoenig 2006-11-12 15:14:08 UTC 
Hugo, as your backtrace looks different:  Do the updated packages work for you?
Comment 12 Warren Stockton 2006-11-12 15:31:04 UTC 
I also see this problem on AMD64 with ndiswrapper...
The symptom did not change with the newer packages.
Using NetworkManager-kde-0.1r602671-5.x86_64.rpm and NetworkManager-kde-debuginfo-0.1r602671-5.x86_64.rpm, I get the following:
$ knetworkmanager 
process 29103: arguments to dbus_pending_call_unref() were incorrect, assertion "pending != NULL" failed in file dbus-pending-call.c line 563.
This is normally a bug in some application using the D-Bus library.
  D-Bus not built with -rdynamic so unable to print a backtrace
KCrash: Application 'knetworkmanager' crashing...
ERROR: Communication problem with knetworkmanager, it probably crashed.


System configuration startup check disabled.

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47898596102784 (LWP 29103)]
[KCrash handler]
#4  0x00002b903b21c535 in raise () from /lib64/libc.so.6
#5  0x00002b903b21d990 in abort () from /lib64/libc.so.6
#6  0x00002b903bd7fc65 in dbus_malloc () from /usr/lib64/libdbus-1.so.3
#7  0x00002b903bd7c23a in dbus_watch_handle () from /usr/lib64/libdbus-1.so.3
#8  0x00002b903bd677c1 in dbus_connection_dispatch ()
   from /usr/lib64/libdbus-1.so.3
#9  0x00002b903b73d290 in DBusQt::Connection::dispatchRead ()
   from /usr/lib64/libdbus-qt-1.so.1
#10 0x00002b903b73d8cf in DBusQt::Connection::qt_invoke ()
   from /usr/lib64/libdbus-qt-1.so.1
#11 0x00002b903d785adc in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#12 0x00002b903d7867b3 in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#13 0x00002b903b73e021 in DBusQt::Internal::Integrator::slotRead ()
   from /usr/lib64/libdbus-qt-1.so.1
#14 0x00002b903b73e28e in DBusQt::Internal::Integrator::qt_invoke ()
   from /usr/lib64/libdbus-qt-1.so.1
#15 0x00002b903d785adc in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#16 0x00002b903d7866df in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#17 0x00002b903d7a02cb in QSocketNotifier::event ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#18 0x00002b903d72eeb5 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#19 0x00002b903d72fc40 in QApplication::notify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#20 0x00002b903cf37e28 in KApplication::notify ()
   from /opt/kde3/lib64/libkdecore.so.4
#21 0x00002b903d72461b in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#22 0x00002b903d6e55f0 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#23 0x00002b903d743963 in QEventLoop::enterLoop ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#24 0x00002b903d743812 in QEventLoop::exec ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#25 0x00002b903afc9490 in kdemain (argc=<value optimized out>, 
    argv=<value optimized out>) at ./knetworkmanager/src/main.cpp:55
#26 0x00002b903b209ae4 in __libc_start_main () from /lib64/libc.so.6
#27 0x0000000000400599 in _start ()
Comment 13 Hugo Costelha 2006-11-12 15:41:45 UTC 
First of all, if NetworkManager is not running, KNetworkManager does not crash (it simply complains that NetworkManager is no running), but you probably already knew that.

Using the updated packages still makes it crash. On the konsole I get the following when it crashes:

process 7705: arguments to dbus_pending_call_unref() were incorrect, assertion "pending != NULL" failed in file dbus-pending-call.c line 563.
This is normally a bug in some application using the D-Bus library.
  D-Bus not built with -rdynamic so unable to print a backtrace
ERROR: Communication problem with knetworkmanager, it probably crashed.

On /var/log/messages I get the following:

Nov 12 15:36:27 pinguim NetworkManager: <info>  Updating allowed wireless network lists.
Nov 12 15:36:27 pinguim NetworkManager: <WARN>  nm_dbus_get_networks_cb(): error received: org.freedesktop.DBus.Error.NoReply - Message did not receive a reply (timeout by message bus).

Do you want the backtrace to?
Comment 14 Robby Verberne 2006-11-12 16:48:50 UTC 
monkey9@tribal-sfn2:~> gdb -exec /opt/kde3/bin/knetworkmanager
GNU gdb 6.5
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
(gdb) run
Starting program: /opt/kde3/bin/knetworkmanager
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47796112253568 (LWP 5961)]
process 5964: arguments to dbus_pending_call_unref() were incorrect, assertion "pending != NULL" failed in file dbus-pending-call.c line 563.
This is normally a bug in some application using the D-Bus library.
  D-Bus not built with -rdynamic so unable to print a backtrace
KCrash: Application 'knetworkmanager' crashing...
ERROR: Communication problem with knetworkmanager, it probably crashed.

Program exited with code 0377.
(gdb)

Systeemconfiguratie opstartcontrole uitgeschakeld.

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47796112253568 (LWP 5964)]
[KCrash handler]
#4  0x00002b785e9e5535 in raise () from /lib64/libc.so.6
#5  0x00002b785e9e6990 in abort () from /lib64/libc.so.6
#6  0x00002b785f548c65 in dbus_malloc () from /usr/lib64/libdbus-1.so.3
#7  0x00002b785f54523a in dbus_watch_handle () from /usr/lib64/libdbus-1.so.3
#8  0x00002b785f5307c1 in dbus_connection_dispatch ()
   from /usr/lib64/libdbus-1.so.3
#9  0x00002b785ef06290 in DBusQt::Connection::dispatchRead ()
   from /usr/lib64/libdbus-qt-1.so.1
#10 0x00002b785ef068cf in DBusQt::Connection::qt_invoke ()
   from /usr/lib64/libdbus-qt-1.so.1
#11 0x00002b7860f4eadc in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#12 0x00002b7860f4f7b3 in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#13 0x00002b785ef07021 in DBusQt::Internal::Integrator::slotRead ()
   from /usr/lib64/libdbus-qt-1.so.1
#14 0x00002b785ef0728e in DBusQt::Internal::Integrator::qt_invoke ()
   from /usr/lib64/libdbus-qt-1.so.1
#15 0x00002b7860f4eadc in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#16 0x00002b7860f4f6df in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#17 0x00002b7860f692cb in QSocketNotifier::event ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#18 0x00002b7860ef7eb5 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#19 0x00002b7860ef8c40 in QApplication::notify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#20 0x00002b7860700e28 in KApplication::notify ()
   from /opt/kde3/lib64/libkdecore.so.4
#21 0x00002b7860eed61b in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#22 0x00002b7860eae5f0 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#23 0x00002b7860f0c963 in QEventLoop::enterLoop ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#24 0x00002b7860f0c812 in QEventLoop::exec ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#25 0x00002b785e792490 in kdemain (argc=<value optimized out>, 
    argv=<value optimized out>) at ./knetworkmanager/src/main.cpp:55
#26 0x00002b785e9d2ae4 in __libc_start_main () from /lib64/libc.so.6
#27 0x0000000000400599 in _start ()
Comment 15 Timo Hoenig 2006-11-12 17:03:30 UTC 
New packages available at

* http://beta.suse.com/private/thoenig/10.2/

Please install, test and report whether things look better now.
Comment 16 Warren Stockton 2006-11-12 17:33:49 UTC 
No change.  The backtrace is exactly the same.  
Tested with:
$ rpm -qa --qf "%{n}-%{v}-%{r}    %{buildtime}\n" NetworkManager-kde*
NetworkManager-kde-debuginfo-0.1r602671-5    1163349431
NetworkManager-kde-0.1r602671-5    1163349431

Please bump the %{release} on the next cut of the rpm (if possible).
Comment 17 Timo Hoenig 2006-11-12 17:41:10 UTC 
Thanks for the feedback, I will need a system on which I can reproduce the bug in order to fix it.
Comment 18 Hugo Costelha 2006-11-12 17:48:06 UTC 
Created attachment 104848 [details]
My actual backtrace

I tested here, and still crashes, although it seems that there are some differences in the backtrace.
Comment 19 Robby Verberne 2006-11-12 17:59:12 UTC 
Program exited with code 0377.
(gdb) KCrash: Application 'knetworkmanager' crashing...

(gdb) tb
No default breakpoint address now.
(gdb)
Comment 20 Robby Verberne 2006-11-12 18:04:00 UTC 
Created attachment 104850 [details]
knetwrkmngrtrcbk
Comment 21 Markus Kriewald 2006-11-12 19:14:13 UTC 
Same bug here on AMD 64 notebook with x86_64beta2 onboard: Knetworkmanger crashes immidetely after startup.

Almost always there are some other problems occured, if Knetworkmanger crashes: Automount isn´t working, after pressing the hardware power on button computer doesn´t shut down, Power status fails (No information about battery and AC status available). If the mouse thouches the new green chamälion on the left side of the taskleiste KsessionManger crashes. The Only way to reboot is to press Strg+Alt+F1 and reboot in text modus. After updating to knetworkmanger-5 the knetworkmanger and the other problems occured further on. KsessionManger (kmserver) is now alive but KDEPanel (kicker) crashes after moving the  mouse to the green chamälion. In the Text-Modus (Strg+Alt+F1) there is now nothing recognizable (Ati X300 chipset).

The problems hang directly togehter with the Knetworkmanger. If i take the Traditionelle Methode mit ifup all thinks are working fine.
Comment 22 Hugo Costelha 2006-11-12 19:18:18 UTC 
I would say that Comment#21 seems to be a problem with DBUS. That happened to me once, but I though it was a problem with all the dbus-*-debuginfo I had installed (the debuginfo supplied versions online do not match the packages available on Beta2), since when I uninstalled the problem didn't appear again since.
Comment 23 Markus Kriewald 2006-11-12 19:18:32 UTC 
Created attachment 104851 [details]
kdekicker
Comment 24 Markus Kriewald 2006-11-12 19:20:06 UTC 
Created attachment 104852 [details]
kmserver
Comment 25 Markus Kriewald 2006-11-12 19:22:19 UTC 
Created attachment 104853 [details]
NetworkManager log
Comment 26 Marcel Witte 2006-11-12 21:50:22 UTC 
I had similiar problems like Comment #21 here, but I think it's because hal is crashing. See Bug 217563. I would say you should the new hal-package and then it should work (besides knetworkmanager, which isn't a hal-problem...).
Comment 27 Timo Hoenig 2006-11-13 13:52:10 UTC 
There was a underlying problem that D-Bus asserted on a regular check which made KNetworkManager (and the other KDE applications) crash.

Fixed D-Bus packages are shortly available at

* http://beta.suse.com/private/thoenig/10.2/

For the time being a warning "pending != NULL" will remain when started from a terminal.

Fixed D-Bus packages submitted to STABLE.

Closing as FIXED.
Comment 28 Hugo Costelha 2006-11-14 21:58:51 UTC 
Confirmed here, it is up and running.