[Bug 224081] New: knetwork crashes sigabrt, up to and including latest svn
https://bugzilla.novell.com/show_bug.cgi?id=224081 Summary: knetwork crashes sigabrt, up to and including latest svn Product: openSUSE 10.2 Version: RC 2 Platform: x86-64 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers@suse.de ReportedBy: avuton@gmail.com QAContact: qa@suse.de I posted this here at the request of http://bugs.kde.org/show_bug.cgi?id=137271 This is actually a gentoo system, but it gives me no choice but say it's opensuse :). I'm not sure it's the same bug but it looks like it and I've got debugging symbols :) Here's what dumps to the console: sbh@rocket ~ % knetworkmanager Session management error: Could not open network socket process 18978: 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. /usr/lib64/libdbus-1.so.3 [0x2b2390087c8c] /usr/lib64/libdbus-1.so.3 [0x2b2390087319] /usr/lib64/libdbus-1.so.3 [0x2b239007d305] /usr/lib64/libdbus-1.so.3(dbus_connection_dispatch+0x1c8) [0x2b239005d6d8] /usr/lib64/libdbus-qt-1.so.1(_ZN6DBusQt10Connection12dispatchReadEv+0x10) [0x2b238fc113a0] /usr/lib64/libdbus-qt-1.so.1(_ZN6DBusQt10Connection9qt_invokeEiP8QUObject+0x6c) [0x2b238fc11abc] /usr/qt/3/lib64/libqt-mt.so.3(_ZN7QObject15activate_signalEP15QConnectionListP8QUObject+0x12a) [0x2b23920539b0] /usr/qt/3/lib64/libqt-mt.so.3(_ZN7QObject15activate_signalEi+0x1e1) [0x2b23920548e7] /usr/lib64/libdbus-qt-1.so.1(_ZN6DBusQt8Internal10Integrator8slotReadEi+0x46) [0x2b238fc120f6] /usr/lib64/libdbus-qt-1.so.1(_ZN6DBusQt8Internal10Integrator9qt_invokeEiP8QUObject+0x3e) [0x2b238fc1215e] /usr/qt/3/lib64/libqt-mt.so.3(_ZN7QObject15activate_signalEP15QConnectionListP8QUObject+0x12a) [0x2b23920539b0] /usr/qt/3/lib64/libqt-mt.so.3(_ZN7QObject15activate_signalEii+0x242) [0x2b239205466e] /usr/qt/3/lib64/libqt-mt.so.3(_ZN15QSocketNotifier9activatedEi+0x2a) [0x2b23924450fc] /usr/qt/3/lib64/libqt-mt.so.3(_ZN15QSocketNotifier5eventEP6QEvent+0x40) [0x2b239207a8c0] /usr/qt/3/lib64/libqt-mt.so.3(_ZN12QApplication14internalNotifyEP7QObjectP6QEvent+0x27e) [0x2b2391fe0b4e] /usr/qt/3/lib64/libqt-mt.so.3(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x28d) [0x2b2391fe2a9d] /usr/kde/3.5/lib/libkdecore.so.4(_ZN12KApplication6notifyEP7QObjectP6QEvent+0x1ea) [0x2b23912ca63a] /usr/qt/3/lib64/libqt-mt.so.3(_ZN12QApplication9sendEventEP7QObjectP6QEvent+0x5e) [0x2b2391f69136] /usr/qt/3/lib64/libqt-mt.so.3(_ZN10QEventLoop23activateSocketNotifiersEv+0x108) [0x2b2391fd1986] /usr/qt/3/lib64/libqt-mt.so.3(_ZN10QEventLoop13processEventsEj+0xdbe) [0x2b2391f7f4c8] /usr/qt/3/lib64/libqt-mt.so.3(_ZN10QEventLoop9enterLoopEv+0x72) [0x2b2391ffe69e] /usr/qt/3/lib64/libqt-mt.so.3(_ZN10QEventLoop4execEv+0x2f) [0x2b2391ffe4a7] /usr/qt/3/lib64/libqt-mt.so.3(_ZN12QApplication4execEv+0x22) [0x2b2391fe27a2] /usr/kde/3.5/lib/libkdeinit_knetworkmanager.so(kdemain+0x140) [0x2b238fab08b0] /lib/libc.so.6(__libc_start_main+0xf4) [0x2b239471b394] knetworkmanager [0x400829] ERROR: Communication problem with knetworkmanager, it probably crashed. sbh@rocket ~ % KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = knetworkmanager path = <unknown> pid = 18978 Here's the dump: Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 47431816559584 (LWP 18978)] [KCrash handler] #5 0x00002b239472d7b5 in *__GI_raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #6 0x00002b239472ea4e in *__GI_abort () at abort.c:88 #7 0x00002b2390087335 in _dbus_abort () at dbus-sysdeps.c:84 #8 0x00002b239007d305 in _dbus_warn_check_failed ( format=0x2b2390098860 "arguments to %s() were incorrect, assertion \"%s\" failed in file %s line %d.\nThis is normally a bug in some application using the D-Bus library.\n") at dbus-internals.c:283 #9 0x00002b239005d6d8 in dbus_connection_dispatch (connection=0x56b0a0) at dbus-connection.c:4213 #10 0x00002b238fc113a0 in DBusQt::Connection::dispatchRead (this=0x56c4b0) at ./connection.cpp:119 #11 0x00002b238fc11abc in DBusQt::Connection::qt_invoke (this=0x56c4b0, _id=8, _o=0x7fff1b14ff00) at ./connection.moc:112 #12 0x00002b23920539b0 in QObject::activate_signal (this=0x56c5e0, clist=0x5836e0, o=0x7fff1b14ff00) at kernel/qobject.cpp:2356 #13 0x00002b23920548e7 in QObject::activate_signal (this=0x56c5e0, signal=2) at kernel/qobject.cpp:2325 #14 0x00002b238fc120f6 in DBusQt::Internal::Integrator::slotRead ( this=0x56c5e0, fd=<value optimized out>) at ./integrator.cpp:169 #15 0x00002b238fc1215e in DBusQt::Internal::Integrator::qt_invoke ( this=0x56c5e0, _id=2, _o=0x7fff1b1500b0) at ./integrator.moc:233 #16 0x00002b23920539b0 in QObject::activate_signal (this=0x582ec0, clist=0x583340, o=0x7fff1b1500b0) at kernel/qobject.cpp:2356 #17 0x00002b239205466e in QObject::activate_signal (this=0x582ec0, signal=2, param=10) at kernel/qobject.cpp:2449 #18 0x00002b23924450fc in QSocketNotifier::activated (this=0x582ec0, t0=10) at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85 #19 0x00002b239207a8c0 in QSocketNotifier::event (this=0x582ec0, e=0x7fff1b1505b0) at kernel/qsocketnotifier.cpp:258 #20 0x00002b2391fe0b4e in QApplication::internalNotify (this=0x7fff1b150980, receiver=0x582ec0, e=0x7fff1b1505b0) at kernel/qapplication.cpp:2635 #21 0x00002b2391fe2a9d in QApplication::notify (this=0x7fff1b150980, receiver=0x582ec0, e=0x7fff1b1505b0) at kernel/qapplication.cpp:2358 #22 0x00002b23912ca63a in KApplication::notify (this=0x7fff1b150980, receiver=0x582ec0, event=0x7fff1b1505b0) at kapplication.cpp:550 #23 0x00002b2391f69136 in QApplication::sendEvent (receiver=0x582ec0, event=0x7fff1b1505b0) at ../include/qapplication.h:496 #24 0x00002b2391fd1986 in QEventLoop::activateSocketNotifiers (this=0x54c590) at kernel/qeventloop_unix.cpp:578 #25 0x00002b2391f7f4c8 in QEventLoop::processEvents (this=0x54c590, flags=4) at kernel/qeventloop_x11.cpp:383 #26 0x00002b2391ffe69e in QEventLoop::enterLoop (this=0x54c590) at kernel/qeventloop.cpp:198 #27 0x00002b2391ffe4a7 in QEventLoop::exec (this=0x54c590) at kernel/qeventloop.cpp:145 #28 0x00002b2391fe27a2 in QApplication::exec (this=0x7fff1b150980) at kernel/qapplication.cpp:2758 #29 0x00002b238fab08b0 in kdemain () from /usr/kde/3.5/lib/libkdeinit_knetworkmanager.so #30 0x00002b238faeb880 in typeinfo name for QGList () from /usr/kde/3.5/lib/libkdeinit_knetworkmanager.so #31 0x0000000000000000 in ?? () -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=224081 coolo@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kde-maintainers@suse.de |thoenig@novell.com ------- Comment #1 from coolo@novell.com 2006-11-30 04:07 MST ------- that assert was removed afaik -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=224081 thoenig@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Comment #2 from thoenig@novell.com 2006-11-30 04:15 MST ------- Avuton, I debugged this issue before and it looks like a 64 bit bug in libdbus. If you break it down to a small test case you may raise this issue on the D-Bus list. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=224081 ------- Comment #3 from avuton@gmail.com 2006-12-01 22:05 MST ------- If anyone else comes to you with this issue please let them know they need to recompile their libdbus with -O1 or less. That was the issue with me. -- 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.
participants (1)
-
bugzilla_noreply@novell.com