Application: python2 (1.5) KDE Platform Version: 4.5.1 (KDE 4.5.1) Qt Version: 4.7.0 Operating System: Linux 2.6.35-28-generic x86_64 Distribution: Ubuntu 10.10 -- Information about the crash: - What I was doing when the application crashed: /etc/init.d/dbus restart - Unusual behavior I noticed(before the crash): somethimes dbus seem to hang(ant hints to diag this): - applications dont show dialogs or have unresponsive behavior - dbus-daemon prossess uses 100% cpu - /etc/init.d/dbus restart seems to fix it for most apps(ex.: save dialog in tsclient 0.150 pops up emidiently when dbus is restarted, while i clicked the button before) -- Backtrace: Application: Printer Applet (python2.6), signal: Segmentation fault [KCrash Handler] #6 QSocketNotifier::setEnabled (this=0x34306e0, enable=true) at kernel/qsocketnotifier.cpp:293 #7 0x00007f8f1b4b94ff in ?? () from /usr/lib/pymodules/python2.6/dbus/mainloop/qt.so #8 0x00007f8f1b4b9bb4 in ?? () from /usr/lib/pymodules/python2.6/dbus/mainloop/qt.so #9 0x00007f8f26a4fb27 in QMetaObject::activate (sender=0x34306e0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7f8f1bb219d1) at kernel/qobject.cpp:3280 #10 0x00007f8f26a9bb1e in QSocketNotifier::activated (this=0x34306e0, _t1=11) at .moc/release-shared/moc_qsocketnotifier.cpp:89 #11 0x00007f8f26a54653 in QSocketNotifier::event (this=0x34306e0, e=0x7fff9fd29f90) at kernel/qsocketnotifier.cpp:317 #12 0x00007f8f24495fdc in QApplicationPrivate::notify_helper (this=0x302c100, receiver=0x34306e0, e=0x7fff9fd29f90) at kernel/qapplication.cpp:4396 #13 0x00007f8f2449baed in QApplication::notify (this=0x302c010, receiver=0x34306e0, e=0x7fff9fd29f90) at kernel/qapplication.cpp:4277 #14 0x00007f8f1ef49156 in KApplication::notify (this=0x302c010, receiver=0x34306e0, event=0x7fff9fd29f90) at ../../kdeui/kernel/kapplication.cpp:310 #15 0x00007f8f1f92af36 in sipKApplication::notify(QObject*, QEvent*) () from /usr/lib/pymodules/python2.6/PyKDE4/kdeui.so #16 0x00007f8f26a37cdc in QCoreApplication::notifyInternal (this=0x302c010, receiver=0x34306e0, event=0x7fff9fd29f90) at kernel/qcoreapplication.cpp:732 #17 0x00007f8f26a6454a in sendEvent (source=0x301ed30) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #18 socketNotifierSourceDispatch (source=0x301ed30) at kernel/qeventdispatcher_glib.cpp:110 #19 0x00007f8f25d04342 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #20 0x00007f8f25d082a8 in ?? () from /lib/libglib-2.0.so.0 #21 0x00007f8f25d0845c in g_main_context_iteration () from /lib/libglib-2.0.so.0 #22 0x00007f8f26a64193 in QEventDispatcherGlib::processEvents (this=0x2d859b0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:415 #23 0x00007f8f24548a4e in QGuiEventDispatcherGlib::processEvents (this=0x34306e0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #24 0x00007f8f26a36a02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149 #25 0x00007f8f26a36dec in QEventLoop::exec (this=0x7fff9fd2a1f0, flags=) at kernel/qeventloop.cpp:201 #26 0x00007f8f26a3aebb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009 #27 0x00007f8f25456a15 in ?? () from /usr/lib/pymodules/python2.6/PyQt4/QtGui.so #28 0x00000000004a51ae in PyEval_EvalFrameEx () #29 0x00000000004a6bd1 in PyEval_EvalCodeEx () #30 0x00000000004a6ca2 in PyEval_EvalCode () #31 0x00000000004c702e in PyRun_FileExFlags () #32 0x00000000004c7244 in PyRun_SimpleFileExFlags () #33 0x00000000004180c1 in Py_Main () #34 0x00007f8f27513d8e in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff9fd2a798) at libc-start.c:226 #35 0x00000000004172c9 in _start () Possible duplicates by query: bug 187667. Reported using DrKonqi
[Comment from a bug triager] This issue is being tracked at bug 171572, merging. Thanks *** This bug has been marked as a duplicate of bug 171572 ***