Application: systemsettings (1.0) KDE Platform Version: 4.7.2 (4.7.2) (Compiled from sources) Qt Version: 4.7.4 Operating System: Linux 3.0.0-13-generic i686 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed:Installing the printer Brother-mfc240 and press key for test print and received that crash report - Unusual behavior I noticed: None the printer printed the test page normally - Custom settings of the application: none and did not tried the printer further more. It is installed and working normally. -- Backtrace: Application: Configuration du système (systemsettings), signal: Segmentation fault [Current thread is 1 (Thread 0xb7878930 (LWP 29316))] Thread 2 (Thread 0xb4f5bb70 (LWP 29326)): #0 0x01cf0d10 in clock_gettime () from /lib/i386-linux-gnu/librt.so.1 #1 0x00c717d5 in do_gettime (frac=0xb4f5b020, sec=0xb4f5b018) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0x00d444b6 in QTimerInfoList::updateCurrentTime (this=0x9b79514) at kernel/qeventdispatcher_unix.cpp:339 #4 0x00d4480a in QTimerInfoList::timerWait (this=0x9b79514, tm=...) at kernel/qeventdispatcher_unix.cpp:442 #5 0x00d43053 in timerSourcePrepareHelper (src=<optimized out>, timeout=0xb4f5b12c) at kernel/qeventdispatcher_glib.cpp:136 #6 0x00d430ed in timerSourcePrepare (source=0x9b794e0, timeout=<optimized out>) at kernel/qeventdispatcher_glib.cpp:169 #7 0x058a088c in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0x058a1637 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0x058a1c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #10 0x00d43b37 in QEventDispatcherGlib::processEvents (this=0x9b796f0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #11 0x00d141dd in QEventLoop::processEvents (this=0xb4f5b2b0, flags=...) at kernel/qeventloop.cpp:149 #12 0x00d14421 in QEventLoop::exec (this=0xb4f5b2b0, flags=...) at kernel/qeventloop.cpp:201 #13 0x00c1790b in QThread::exec (this=0x9b78418) at thread/qthread.cpp:498 #14 0x00cf4e2d in QInotifyFileSystemWatcherEngine::run (this=0x9b78418) at io/qfilesystemwatcher_inotify.cpp:248 #15 0x00c1a7b3 in QThreadPrivate::start (arg=0x9b78418) at thread/qthread_unix.cpp:331 #16 0x00394d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #17 0x055f10ce in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 1 (Thread 0xb7878930 (LWP 29316)): [KCrash Handler] #7 0x02b4e30c in QHash<void*, PyQtProxy*>::duplicateNode(QHashData::Node*, void*) () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so #8 0x00c38c99 in QHashData::detach_helper2 (this=0x9dda930, node_duplicate=0x2b4e300 <QHash<void*, PyQtProxy*>::duplicateNode(QHashData::Node*, void*)>, node_delete=0x2b4e2f0 <QHash<void*, PyQtProxy*>::deleteNode2(QHashData::Node*)>, nodeSize=16, nodeAlign=4) at tools/qhash.cpp:235 #9 0x02b5330c in sipQtFindSipslot () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so #10 0x022fdc00 in sipWrapper_traverse (arg=0x0, visit=0x24f6720 <visit_decref>, self=0xb45da77c) at /build/buildd/sip4-4.12.4/siplib/siplib.c:9648 #11 sipWrapper_traverse (self=0xb45da77c, visit=0x24f6720 <visit_decref>, arg=0x0) at /build/buildd/sip4-4.12.4/siplib/siplib.c:9629 #12 0x02472252 in subtype_traverse (self=<QApplication at remote 0xb45da77c>, visit=0x24f6720 <visit_decref>, arg=0x0) at ../Objects/typeobject.c:838 #13 0x024f6990 in subtract_refs (containers=0x266d728) at ../Modules/gcmodule.c:345 #14 collect (generation=2) at ../Modules/gcmodule.c:874 #15 0x024f76bc in PyGC_Collect () at ../Modules/gcmodule.c:1386 #16 0x024e2adb in Py_Finalize () at ../Python/pythonrun.c:437 #17 Py_Finalize () at ../Python/pythonrun.c:393 #18 0x02144f75 in KPythonPluginFactory::~KPythonPluginFactory (this=0x9a613f8, __in_chrg=<optimized out>) at ../../kpythonpluginfactory/kpythonpluginfactory.cpp:262 #19 0x02145002 in KPythonPluginFactory::~KPythonPluginFactory (this=0x9a613f8, __in_chrg=<optimized out>) at ../../kpythonpluginfactory/kpythonpluginfactory.cpp:268 #20 0x00d2fb45 in QObjectCleanupHandler::clear (this=0x99f1a58) at kernel/qobjectcleanuphandler.cpp:140 #21 0x00d2fb8d in QObjectCleanupHandler::~QObjectCleanupHandler (this=0x99f1a58, __in_chrg=<optimized out>) at kernel/qobjectcleanuphandler.cpp:86 #22 0x00d2fc02 in QObjectCleanupHandler::~QObjectCleanupHandler (this=0x99f1a58, __in_chrg=<optimized out>) at kernel/qobjectcleanuphandler.cpp:87 #23 0x0060a992 in destroy () at ../../kdecore/util/kpluginfactory.cpp:29 #24 0x0047e379 in KCleanUpGlobalStatic::~KCleanUpGlobalStatic (this=0x6bb0f0, __in_chrg=<optimized out>) at ../../kdecore/kernel/kglobal.h:62 #25 0x05551981 in ?? () from /lib/i386-linux-gnu/libc.so.6 #26 0x05551a0d in exit () from /lib/i386-linux-gnu/libc.so.6 #27 0x03051d90 in ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0 #28 0x00e8ad6b in _XError () from /usr/lib/i386-linux-gnu/libX11.so.6 #29 0x00e8793d in ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 #30 0x00e88927 in _XReply () from /usr/lib/i386-linux-gnu/libX11.so.6 #31 0x00e6d2b8 in XGetWindowProperty () from /usr/lib/i386-linux-gnu/libX11.so.6 #32 0x00a49510 in NETWinInfo::update (this=0xbfab3f28, dirty_props=0xbfab3ea8) at ../../kdeui/windowmanagement/netwm.cpp:3962 #33 0x00a4adb6 in NETWinInfo::event (this=0xbfab3f28, event=0xbfab400c, properties=0xbfab3f14, properties_size=2) at ../../kdeui/windowmanagement/netwm.cpp:3925 #34 0x00a3f0b0 in KWindowSystemPrivate::x11Event (this=0x9c76c90, ev=0xbfab400c) at ../../kdeui/windowmanagement/kwindowsystem_x11.cpp:198 #35 0x00906fab in publicX11Event (e=0xbfab400c, this=<optimized out>) at ../../kdeui/kernel/ksystemeventfilter.cpp:43 #36 KSystemEventFilterPrivate::filterEvent (this=0x9c712e0, message=0xbfab400c) at ../../kdeui/kernel/ksystemeventfilter.cpp:102 #37 0x00907046 in _k_eventFilter (message=0xbfab400c) at ../../kdeui/kernel/ksystemeventfilter.cpp:91 #38 0x00d077cc in QAbstractEventDispatcher::filterEvent (this=0x973bbc8, message=0xbfab400c) at kernel/qabstracteventdispatcher.cpp:501 #39 0x011e7181 in x11EventSourceDispatch (s=0x975d5b0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:143 #40 0x058a125f in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #41 0x058a1990 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #42 0x058a1c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #43 0x00d43ada in QEventDispatcherGlib::processEvents (this=0x973bbc8, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #44 0x011e6e3a in QGuiEventDispatcherGlib::processEvents (this=0x973bbc8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #45 0x00d141dd in QEventLoop::processEvents (this=0xbfab4314, flags=...) at kernel/qeventloop.cpp:149 #46 0x00d14421 in QEventLoop::exec (this=0xbfab4314, flags=...) at kernel/qeventloop.cpp:201 #47 0x00d1919d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064 #48 0x0112c8f4 in QApplication::exec () at kernel/qapplication.cpp:3760 #49 0x080502b8 in main (argc=161563872, argv=0x19) at ../../../systemsettings/app/main.cpp:49 Possible duplicates by query: bug 287657, bug 287655, bug 287522, bug 287452, bug 287406. Reported using DrKonqi
Created attachment 66168 [details] New crash information added by DrKonqi systemsettings (1.0) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4 I had just switched printer drivers for an HP printer (from the series driver to the specific driver) and printed a test page. Error/failure/crash happened at that point. -- Backtrace (Reduced): #6 0x00007f13cb2740f5 in QHash<void*, PyQtProxy*>::duplicateNode(QHashData::Node*, void*) () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so #7 0x00007f13e464c637 in QHashData::detach_helper2 (this=0x2973890, node_duplicate=0x7f13cb2740f0 <QHash<void*, PyQtProxy*>::duplicateNode(QHashData::Node*, void*)>, node_delete=0x7f13cb2740e0 <QHash<void*, PyQtProxy*>::deleteNode2(QHashData::Node*)>, nodeSize=<optimized out>, nodeAlign=8) at tools/qhash.cpp:235 #8 0x00007f13cb278ca7 in sipQtFindSipslot () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so #9 0x00007f13caeeb71e in sipWrapper_traverse (arg=0x0, visit=0x7f13d018a620 <visit_decref>, self=0x28ca170) at /build/buildd/sip4-4.12.4/siplib/siplib.c:9648 #10 sipWrapper_traverse (self=0x28ca170, visit=0x7f13d018a620 <visit_decref>, arg=0x0) at /build/buildd/sip4-4.12.4/siplib/siplib.c:9629
duplicate of bug 283611
Created attachment 66212 [details] New crash information added by DrKonqi systemsettings (1.0) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4 - What I was doing when the application crashed: Was installing a Brother HL-1450 printer located on LPT#1 of remote Windows computer through SAMBA. Clicked Print Test Page button. Got acknowledgement that test page was sent to printer as Job 1. Clicked OK, and application instantly crashed. Bug is 100% reproducible with this printer and with another installed directly on the network (i.e., with its own IP address). -- Backtrace (Reduced): #7 0x03be530c in QHash<void*, PyQtProxy*>::duplicateNode(QHashData::Node*, void*) () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so #8 0x018f4c99 in QHashData::detach_helper2 (this=0x86dccf8, node_duplicate=0x3be5300 <QHash<void*, PyQtProxy*>::duplicateNode(QHashData::Node*, void*)>, node_delete=0x3be52f0 <QHash<void*, PyQtProxy*>::deleteNode2(QHashData::Node*)>, nodeSize=16, nodeAlign=4) at tools/qhash.cpp:235 #9 0x03bea30c in sipQtFindSipslot () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so #10 0x06c6cc00 in sipWrapper_traverse (arg=0x0, visit=0x26a8720 <visit_decref>, self=0xb4cf877c) at /build/buildd/sip4-4.12.4/siplib/siplib.c:9648 #11 sipWrapper_traverse (self=0xb4cf877c, visit=0x26a8720 <visit_decref>, arg=0x0) at /build/buildd/sip4-4.12.4/siplib/siplib.c:9629
Le 2011-11-29 22:10, DVM a écrit : > https://bugs.kde.org/show_bug.cgi?id=287721 > > > > > > --- Comment #3 from Morton A. Goldberg, DVM<magoldberg thebat net> 2011-11-30 03:10:40 --- > Created an attachment (id=66212) > --> (http://bugs.kde.org/attachment.cgi?id=66212) > New crash information added by DrKonqi > > systemsettings (1.0) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4 > > - What I was doing when the application crashed: Was installing a Brother > HL-1450 printer located on LPT#1 of remote Windows computer through SAMBA. > Clicked Print Test Page button. Got acknowledgement that test page was sent to > printer as Job 1. Clicked OK, and application instantly crashed. Bug is 100% > reproducible with this printer and with another installed directly on the > network (i.e., with its own IP address). > > -- Backtrace (Reduced): > #7 0x03be530c in QHash<void*, PyQtProxy*>::duplicateNode(QHashData::Node*, > void*) () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so > #8 0x018f4c99 in QHashData::detach_helper2 (this=0x86dccf8, > node_duplicate=0x3be5300<QHash<void*, > PyQtProxy*>::duplicateNode(QHashData::Node*, void*)>, node_delete=0x3be52f0 > <QHash<void*, PyQtProxy*>::deleteNode2(QHashData::Node*)>, nodeSize=16, > nodeAlign=4) at tools/qhash.cpp:235 > #9 0x03bea30c in sipQtFindSipslot () from > /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so > #10 0x06c6cc00 in sipWrapper_traverse (arg=0x0, visit=0x26a8720<visit_decref>, > self=0xb4cf877c) at /build/buildd/sip4-4.12.4/siplib/siplib.c:9648 > #11 sipWrapper_traverse (self=0xb4cf877c, visit=0x26a8720<visit_decref>, > arg=0x0) at /build/buildd/sip4-4.12.4/siplib/siplib.c:9629 > Hi I am sending this reply because the report showed above is wrong. The printer is a Brother-Mfc240c located on usb port. As I was responding to the request of printing test page I had that bug report witch I decided to sent it to you.The test page did print OK and so far the printer is working good. I had no crush what so ever and also I only have this printer installed on this machine. The rest of info sent to you by this bug report is garbage to me.. The printer program is on packages muon system. I am running Kubuntu 11.10 in french (with some bugs) along with windows7 on their own partitions. My computer is an EMachine e529-2417 on x86-64, with 320 go hdd with 2gb ddr3 memory. Kubuntu is a 32bits version. Hope these info will help, Andre Tremblay
André, this does not depend on the printer, it is a crash in the printer settings, the backtrace is the same for everyone. *** This bug has been marked as a duplicate of bug 283611 ***