Bug 248346 - Printer Applet Crashed When DBus Services Was Restarted
Summary: Printer Applet Crashed When DBus Services Was Restarted
Status: RESOLVED DUPLICATE of bug 171572
Alias: None
Product: printer-applet
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Jonathan Riddell
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-19 10:04 UTC by Roman Kulikov
Modified: 2010-12-12 15:35 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Kulikov 2010-08-19 10:04:49 UTC
Application: python2 (1.4)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-24-generic i686
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
0. Run sudo service dbus restart
1. Get Printer Applet crash.

 -- Backtrace:
Application: Апплет принтера (python2.6), signal: Segmentation fault
[KCrash Handler]
#6  0x0097875f in QSocketNotifier::setEnabled (this=0x9b81770, enable=true) at kernel/qsocketnotifier.cpp:293
#7  0x00df60a7 in ?? () from /usr/lib/pymodules/python2.6/dbus/mainloop/qt.so
#8  0x00df6707 in ?? () from /usr/lib/pymodules/python2.6/dbus/mainloop/qt.so
#9  0x00962c9a in QMetaObject::metacall (object=0x9b8cec0, cl=QMetaObject::ReadProperty, idx=4, argv=0xbfacaf78) at kernel/qmetaobject.cpp:237
#10 0x009713d5 in QMetaObject::activate (sender=0x9b81770, m=0xa71550, local_signal_index=0, argv=0xbfacaf78) at kernel/qobject.cpp:3293
#11 0x009c2933 in QSocketNotifier::activated (this=0x9b81770, _t1=11) at .moc/release-shared/moc_qsocketnotifier.cpp:89
#12 0x009788e7 in QSocketNotifier::event (this=0x9b81770, e=0xbfacb454) at kernel/qsocketnotifier.cpp:317
#13 0x04ab04dc in QApplicationPrivate::notify_helper (this=0x998a1d8, receiver=0x9b81770, e=0xbfacb454) at kernel/qapplication.cpp:4300
#14 0x04ab705e in QApplication::notify (this=0x998a128, receiver=0x9b81770, e=0xbfacb454) at kernel/qapplication.cpp:3704
#15 0x02a51f2a in KApplication::notify (this=0x998a128, receiver=0x9b81770, event=0xbfacb454) at ../../kdeui/kernel/kapplication.cpp:302
#16 0x06f73db3 in sipKApplication::notify(QObject*, QEvent*) () from /usr/lib/pymodules/python2.6/PyKDE4/kdeui.so
#17 0x0095da3b in QCoreApplication::notifyInternal (this=0x998a128, receiver=0x9b81770, event=0xbfacb454) at kernel/qcoreapplication.cpp:704
#18 0x009899aa in QCoreApplication::sendEvent (source=0x998c510) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 socketNotifierSourceDispatch (source=0x998c510) at kernel/qeventdispatcher_glib.cpp:110
#20 0x005a65e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#21 0x005aa2d8 in ?? () from /lib/libglib-2.0.so.0
#22 0x005aa4b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#23 0x009895d5 in QEventDispatcherGlib::processEvents (this=0x97799d8, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#24 0x04b70135 in QGuiEventDispatcherGlib::processEvents (this=0x97799d8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#25 0x0095c059 in QEventLoop::processEvents (this=0xbfacb6f4, flags=) at kernel/qeventloop.cpp:149
#26 0x0095c4aa in QEventLoop::exec (this=0xbfacb6f4, flags=...) at kernel/qeventloop.cpp:201
#27 0x0096069f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#28 0x04ab0577 in QApplication::exec () at kernel/qapplication.cpp:3579
#29 0x01349d70 in ?? () from /usr/lib/pymodules/python2.6/PyQt4/QtGui.so
#30 0x080e0a21 in PyEval_EvalFrameEx ()
#31 0x080e2807 in PyEval_EvalCodeEx ()
#32 0x080e2907 in PyEval_EvalCode ()
#33 0x081005ad in PyRun_FileExFlags ()
#34 0x08100812 in PyRun_SimpleFileExFlags ()
#35 0x0805de5c in Py_Main ()
#36 0x0805d03b in main ()

Reported using DrKonqi
Comment 1 Dario Andres 2010-12-12 15:35:48 UTC
[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 ***