Bug 211374 - printer-applet crashes at startup
Summary: printer-applet crashes at startup
Status: RESOLVED DUPLICATE of bug 209095
Alias: None
Product: printer-applet
Classification: Unmaintained
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-21 21:46 UTC by Peter Möller
Modified: 2009-10-21 22:07 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 Peter Möller 2009-10-21 21:46:26 UTC
Application that crashed: printer-applet
Version of the application: 1.3
KDE Version: 4.3.1 (KDE 4.3.1) "release 179"
Qt Version: 4.5.3
Operating System: Linux 2.6.27.29-0.1-pae i686
Distribution: "openSUSE 11.1 (i586)"

What I was doing when the application crashed:
Every boot leads to a crash of printer-applet - since a minimum of 6 weeks. 
i did not change printer settings, but sometimes there is an update from KDE4 Factory (OSS 11.1, KDE 4.3.1)

 -- Backtrace:
Application: Drucker-Miniprogramm (printer-applet), signal: Segmentation fault
[KCrash Handler]
#6  0xb7f8fe87 in PyDict_GetItem () from /usr/lib/libpython2.6.so.1.0
#7  0xb7c33d20 in ?? () from /usr/lib/python2.6/site-packages/sip.so
#8  0xb7b3e42f in ?? () from /usr/lib/python2.6/site-packages/PyQt4/QtCore.so
#9  0xb648676c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#10 0xb648ea5e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#11 0xb514417d in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#12 0xb572c3ee in sipKApplication::notify(QObject*, QEvent*) () from /usr/lib/python2.6/site-packages/PyKDE4/kdeui.so
#13 0xb79158fb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#14 0xb792da7e in QCoreApplication::sendEvent(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#15 0xb792537a in QObjectPrivate::setParent_helper(QObject*) () from /usr/lib/libQtCore.so.4
#16 0xb7925457 in QObject::setParent(QObject*) () from /usr/lib/libQtCore.so.4
#17 0xb7929a24 in QObject::QObject(QObject*) () from /usr/lib/libQtCore.so.4
#18 0xb7931139 in QTimer::QTimer(QObject*) () from /usr/lib/libQtCore.so.4
#19 0xb7a7a939 in ?? () from /usr/lib/python2.6/site-packages/PyQt4/QtCore.so
#20 0xb7a7aa14 in ?? () from /usr/lib/python2.6/site-packages/PyQt4/QtCore.so
#21 0xb7c33127 in ?? () from /usr/lib/python2.6/site-packages/sip.so
#22 0xb7fab9b5 in ?? () from /usr/lib/libpython2.6.so.1.0
#23 0xb7f5ac1c in PyObject_Call () from /usr/lib/libpython2.6.so.1.0
#24 0xb7fe5d20 in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0
#25 0xb7fead7f in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0
#26 0xb7f7fa29 in ?? () from /usr/lib/libpython2.6.so.1.0
#27 0xb7f5ac1c in PyObject_Call () from /usr/lib/libpython2.6.so.1.0
#28 0xb7f689fe in ?? () from /usr/lib/libpython2.6.so.1.0
#29 0xb7f5ac1c in PyObject_Call () from /usr/lib/libpython2.6.so.1.0
#30 0xb7fadc55 in ?? () from /usr/lib/libpython2.6.so.1.0
#31 0xb7fab9b5 in ?? () from /usr/lib/libpython2.6.so.1.0
#32 0xb7f5ac1c in PyObject_Call () from /usr/lib/libpython2.6.so.1.0
#33 0xb7fe5d20 in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0
#34 0xb7fead7f in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0
#35 0xb7fe2c73 in PyEval_EvalCode () from /usr/lib/libpython2.6.so.1.0
#36 0xb8004adc in ?? () from /usr/lib/libpython2.6.so.1.0
#37 0xb8004b9b in PyRun_FileExFlags () from /usr/lib/libpython2.6.so.1.0
#38 0xb800558f in PyRun_SimpleFileExFlags () from /usr/lib/libpython2.6.so.1.0
#39 0xb8005818 in PyRun_AnyFileExFlags () from /usr/lib/libpython2.6.so.1.0
#40 0xb8011e12 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 211042

Reported using DrKonqi
Comment 1 Dario Andres 2009-10-21 22:07:00 UTC
Check bug 209095. Thanks

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