Bug 209287 - printer-arplet crash before start kde4
Summary: printer-arplet crash before start kde4
Status: RESOLVED DUPLICATE of bug 209095
Alias: None
Product: printer-applet
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Jonathan Riddell
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-03 11:31 UTC by Marcin "WMP" Janowski
Modified: 2009-10-03 16:16 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 Marcin "WMP" Janowski 2009-10-03 11:31:30 UTC
Application that crashed: printer-applet
Version of the application: 1.3
KDE Version: 4.3.1 (KDE 4.3.1) "release 168"
Qt Version: 4.5.2
Operating System: Linux 2.6.30.1-9-pae i686
Distribution: "openSUSE 11.1 (i586)"

What I was doing when the application crashed:
Qt: 4.5.2
KDE: 4.3.1 (KDE 4.3.1) "release 168"
kde4-config: 1.0

uname -a
Linux linux-uqnc 2.6.30.1-9-pae #6 SMP Wed Sep 23 22:29:42 CEST 2009 i686 i686 i386 GNU/Linux
cups: 1.3.9



 -- Backtrace:
Application: Aplet drukarki (printer-applet), signal: Segmentation fault
[KCrash Handler]
#6  0xb7e15e87 in PyDict_GetItem () from /usr/lib/libpython2.6.so.1.0
#7  0xb7abed20 in ?? () from /usr/lib/python2.6/site-packages/sip.so
#8  0xb79c440f in ?? () from /usr/lib/python2.6/site-packages/PyQt4/QtCore.so
#9  0xb63137bc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#10 0xb631baae in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#11 0xb509717d in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#12 0xb567f3ee in sipKApplication::notify(QObject*, QEvent*) () from /usr/lib/python2.6/site-packages/PyKDE4/kdeui.so
#13 0xb779b16b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#14 0xb77b331e in QCoreApplication::sendEvent(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#15 0xb77aac1a in QObjectPrivate::setParent_helper(QObject*) () from /usr/lib/libQtCore.so.4
#16 0xb77aacf7 in QObject::setParent(QObject*) () from /usr/lib/libQtCore.so.4
#17 0xb77af2c4 in QObject::QObject(QObject*) () from /usr/lib/libQtCore.so.4
#18 0xb77b69d9 in QTimer::QTimer(QObject*) () from /usr/lib/libQtCore.so.4
#19 0xb7900939 in ?? () from /usr/lib/python2.6/site-packages/PyQt4/QtCore.so
#20 0xb7900a14 in ?? () from /usr/lib/python2.6/site-packages/PyQt4/QtCore.so
#21 0xb7abe127 in ?? () from /usr/lib/python2.6/site-packages/sip.so
#22 0xb7e319b5 in ?? () from /usr/lib/libpython2.6.so.1.0
#23 0xb7de0c1c in PyObject_Call () from /usr/lib/libpython2.6.so.1.0
#24 0xb7e6bd20 in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0
#25 0xb7e70d7f in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0
#26 0xb7e05a29 in ?? () from /usr/lib/libpython2.6.so.1.0
#27 0xb7de0c1c in PyObject_Call () from /usr/lib/libpython2.6.so.1.0
#28 0xb7dee9fe in ?? () from /usr/lib/libpython2.6.so.1.0
#29 0xb7de0c1c in PyObject_Call () from /usr/lib/libpython2.6.so.1.0
#30 0xb7e33c55 in ?? () from /usr/lib/libpython2.6.so.1.0
#31 0xb7e319b5 in ?? () from /usr/lib/libpython2.6.so.1.0
#32 0xb7de0c1c in PyObject_Call () from /usr/lib/libpython2.6.so.1.0
#33 0xb7e6bd20 in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0
#34 0xb7e70d7f in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0
#35 0xb7e68c73 in PyEval_EvalCode () from /usr/lib/libpython2.6.so.1.0
#36 0xb7e8aadc in ?? () from /usr/lib/libpython2.6.so.1.0
#37 0xb7e8ab9b in PyRun_FileExFlags () from /usr/lib/libpython2.6.so.1.0
#38 0xb7e8b58f in PyRun_SimpleFileExFlags () from /usr/lib/libpython2.6.so.1.0
#39 0xb7e8b818 in PyRun_AnyFileExFlags () from /usr/lib/libpython2.6.so.1.0
#40 0xb7e97e12 in Py_Main () from /usr/lib/libpython2.6.so.1.0
#41 0x08048692 in main ()

This bug may be a duplicate of or related to bug 167125

Reported using DrKonqi
Comment 1 Dario Andres 2009-10-03 16:16:56 UTC
Merging with bug 209095. Thanks

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