Bug 200135 - Printer applet crashed when DBus daemon restarted
Summary: Printer applet crashed when DBus daemon restarted
Status: RESOLVED DUPLICATE of bug 171572
Alias: None
Product: printer-applet
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Jonathan Riddell
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-14 07:22 UTC by Dima Ryazanov
Modified: 2009-07-14 15:11 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dima Ryazanov 2009-07-14 07:22:19 UTC
Version:            (using KDE 4.2.96)
OS:                Linux
Installed from:    Ubuntu Packages

When I restarted the DBus daemon and other services, the printer applet crashed:

Application: Printer Applet (printer-applet), signal: Segmentation fault
[KCrash Handler]
#5  QSocketNotifier::setEnabled (this=0x2790240, enable=true) at kernel/qsocketnotifier.cpp:292
#6  0x00007febe91d4857 in ?? () from /var/lib/python-support/python2.6/dbus/mainloop/qt.so
#7  0x00007febe91d4c8f in ?? () from /var/lib/python-support/python2.6/dbus/mainloop/qt.so
#8  0x00007febf3dba8d2 in QMetaObject::activate (sender=0x2790240, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x7febe9404cc1) at kernel/qobject.cpp:3120
#9  0x00007febf3df1b0e in QSocketNotifier::activated (this=0x2790240, _t1=10) at .moc/release-shared/moc_qsocketnotifier.cpp:83
#10 0x00007febf3dbf533 in QSocketNotifier::event (this=0x2790240, e=0x7ffffd5ae510) at kernel/qsocketnotifier.cpp:316
#11 0x00007febf1891b9d in QApplicationPrivate::notify_helper (this=0x2471100, receiver=0x2790240, e=0x7ffffd5ae510) at kernel/qapplication.cpp:4057
#12 0x00007febf1899dea in QApplication::notify (this=0x2470ec0, receiver=0x2790240, e=0x7ffffd5ae510) at kernel/qapplication.cpp:4022
#13 0x00007febec3aa63b in KApplication::notify (this=0x2470ec0, receiver=0x2790240, event=0x7ffffd5ae510) at /build/buildd/kde4libs-4.2.96/kdeui/kernel/kapplication.cpp:302
#14 0x00007febecc1af36 in sipKApplication::notify () from /usr/lib/python2.6/dist-packages/PyKDE4/kdeui.so
#15 0x00007febf3da4dfc in QCoreApplication::notifyInternal (this=0x2470ec0, receiver=0x2790240, event=0x7ffffd5ae510) at kernel/qcoreapplication.cpp:610
#16 0x00007febf3dce7a9 in socketNotifierSourceDispatch (source=0x2478f90) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#17 0x00007febf30a020a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#18 0x00007febf30a38e0 in ?? () from /usr/lib/libglib-2.0.so.0
#19 0x00007febf30a3a7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#20 0x00007febf3dce52f in QEventDispatcherGlib::processEvents (this=0x2241520, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:324
#21 0x00007febf192a70f in QGuiEventDispatcherGlib::processEvents (this=0x2790240, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#22 0x00007febf3da36a2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -44374224}) at kernel/qeventloop.cpp:149
#23 0x00007febf3da3a6d in QEventLoop::exec (this=0x7ffffd5ae770, flags={i = -44374144}) at kernel/qeventloop.cpp:200
#24 0x00007febf3da5d34 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#25 0x00007febf27d78d9 in ?? () from /usr/lib/python2.6/dist-packages/PyQt4/QtGui.so
#26 0x00000000004a2b03 in PyEval_EvalFrameEx ()
#27 0x00000000004a4649 in PyEval_EvalCodeEx ()
#28 0x00000000004a4762 in PyEval_EvalCode ()
#29 0x00000000004c4c3c in PyRun_FileExFlags ()
#30 0x00000000004c4f6b in PyRun_SimpleFileExFlags ()
#31 0x00000000004189ce in Py_Main ()
#32 0x00007febf457b5a6 in __libc_start_main (main=0x417bb0 <main>, argc=2, ubp_av=0x7ffffd5aeef8, init=0x54a180 <__libc_csu_init>, fini=<value optimized out>, rtld_fini=<value optimized out>, 
    stack_end=0x7ffffd5aeee8) at libc-start.c:220
#33 0x0000000000417ae9 in _start ()
Comment 1 Dario Andres 2009-07-14 15:11:09 UTC
This is reported as bug 171572. Thanks

*** This bug has been marked as a duplicate of bug 171572 ***