Application that crashed: ksysguard Version of the application: 4.3.00 (KDE 4.3.0) KDE Version: 4.3.00 (KDE 4.3.0) Qt Version: 4.5.2 Operating System: Linux 2.6.28-15-generic i686 Distribution: Linux Mint 7 Gloria - KDE Community Edition What I was doing when the application crashed: starts up, crashed immediately. no unusual computer activity -- just some web browsing. crashes after 2 seconds. gnome system monitor works ok. -- Backtrace: Application: System Monitor (kdeinit4), signal: Segmentation fault [KCrash Handler] #6 QWingedEdge::addEdge (this=0xbfe1f5f8, fi=-1, si=4, bezier=0x909dd70, t0=0, t1=-nan(0x8000000000000)) at painting/qpathclipper.cpp:1154 #7 0xb6a02cf4 in QWingedEdge::addBezierEdge (this=0xbfe1f5f8, bezier=0x909dd70, vertexA=-1, vertexB=-1, alphaA=0, alphaB=-nan(0x8000000000000), path=0) at painting/qpathclipper.cpp:1341 #8 0xb6a0602e in QWingedEdge::intersectAndAdd (this=0xbfe1f5f8) at painting/qpathclipper.cpp:731 #9 0xb6a07b0c in QWingedEdge (this=0xbfe1f5f8, subject=@0xbfe1f6f8, clip=@0xbfe1f6fc) at painting/qpathclipper.cpp:781 #10 0xb6a07e66 in QPathClipper::clip (this=0xbfe1f6f8, operation=QPathClipper::BoolAnd) at painting/qpathclipper.cpp:1761 #11 0xb69faaca in QPainterPath::intersected (this=0xbfe1f774, p=@0xbfe1f770) at painting/qpainterpath.cpp:3123 #12 0xb69ce34d in QOutlineMapper::clipElements (this=0x9070050, elements=0x9070250, types=0x9070148, element_count=5) at painting/qoutlinemapper.cpp:402 #13 0xb69cebb5 in QOutlineMapper::endOutline (this=0x9070050) at painting/qoutlinemapper.cpp:263 #14 0xb69cfcd2 in QOutlineMapper::convertPath (this=0x9070050, path=@0x909a82c) at painting/qoutlinemapper.cpp:162 #15 0xb6a5e9a3 in QRasterPaintEngine::fill (this=0x8ebfe30, path=@0x909a82c, brush=@0xbfe1fd78) at painting/qpaintengine_raster.cpp:1836 #16 0xb69f04c2 in QPainter::fillPath (this=0xbfe1fe24, path=@0xbfe1fd7c, brush=@0xbfe1fd78) at painting/qpainter.cpp:3158 #17 0xb5dd39f8 in ?? () from /usr/lib/libkdeinit4_ksysguard.so #18 0xb5dd3c52 in ?? () from /usr/lib/libkdeinit4_ksysguard.so #19 0xb5dd4afb in ?? () from /usr/lib/libkdeinit4_ksysguard.so #20 0xb5dad5e9 in ?? () from /usr/lib/libkdeinit4_ksysguard.so #21 0xb5d9f7a6 in ?? () from /usr/lib/libkdeinit4_ksysguard.so #22 0xb5db2dda in ?? () from /usr/lib/libkdeinit4_ksysguard.so #23 0xb7e081b8 in QMetaObject::activate (sender=0x8ecc13c, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113 #24 0xb7e08e42 in QMetaObject::activate (sender=0x8ecc13c, m=0xb7ee5904, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187 #25 0xb7e44687 in QTimer::timeout (this=0x8ecc13c) at .moc/release-shared/moc_qtimer.cpp:128 #26 0xb7e0e5ce in QTimer::timerEvent (this=0x8ecc13c, e=0xbfe2049c) at kernel/qtimer.cpp:261 #27 0xb7e0316f in QObject::event (this=0x8ecc13c, e=0xbfe2049c) at kernel/qobject.cpp:1075 #28 0xb68b3d3c in QApplicationPrivate::notify_helper (this=0x8dc9760, receiver=0x8ecc13c, e=0xbfe2049c) at kernel/qapplication.cpp:4056 #29 0xb68bc03e in QApplication::notify (this=0x8dc96f0, receiver=0x8ecc13c, e=0xbfe2049c) at kernel/qapplication.cpp:3603 #30 0xb73c45cd in KApplication::notify (this=0x8dc96f0, receiver=0x8ecc13c, event=0xbfe2049c) at /build/buildd/kde4libs-4.3.0/kdeui/kernel/kapplication.cpp:302 #31 0xb7df2bcb in QCoreApplication::notifyInternal (this=0x8dc96f0, receiver=0x8ecc13c, event=0xbfe2049c) at kernel/qcoreapplication.cpp:610 #32 0xb7e21d51 in QTimerInfoList::activateTimers (this=0x8dcb934) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #33 0xb7e1e3a0 in timerSourceDispatch (source=0x8dcb900) at kernel/qeventdispatcher_glib.cpp:165 #34 0xb6466b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #35 0xb646a0eb in ?? () from /usr/lib/libglib-2.0.so.0 #36 0xb646a268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #37 0xb7e1e2f8 in QEventDispatcherGlib::processEvents (this=0x8d6bd40, flags={i = -1075706344}) at kernel/qeventdispatcher_glib.cpp:327 #38 0xb6955a75 in QGuiEventDispatcherGlib::processEvents (this=0x8d6bd40, flags={i = -1075706296}) at kernel/qguieventdispatcher_glib.cpp:202 #39 0xb7df11fa in QEventLoop::processEvents (this=0xbfe206c0, flags={i = -1075706232}) at kernel/qeventloop.cpp:149 #40 0xb7df1642 in QEventLoop::exec (this=0xbfe206c0, flags={i = -1075706168}) at kernel/qeventloop.cpp:201 #41 0xb7df3ae9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #42 0xb68b3bb7 in QApplication::exec () at kernel/qapplication.cpp:3525 #43 0xb5deffa4 in kdemain () from /usr/lib/libkdeinit4_ksysguard.so #44 0x0804e27d in launch (argc=1, _name=0x8db9074 "/usr/bin/ksysguard", args=0x8db9087 "\001", cwd=0x0, envc=1, envs=0x8db908b "DISPLAY=:0.0", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8db909c "david-desktop;1251520340;237852;4377_TIME6883953") at /build/buildd/kde4libs-4.3.0/kinit/kinit.cpp:676 #45 0x0804ea5d in handle_launcher_request (sock=7, who=<value optimized out>) at /build/buildd/kde4libs-4.3.0/kinit/kinit.cpp:1168 #46 0x0804efe5 in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.3.0/kinit/kinit.cpp:1361 #47 0x0804fbca in main (argc=2, argv=0xbfe20f74, envp=0xbfe20f80) at /build/buildd/kde4libs-4.3.0/kinit/kinit.cpp:1788 Reported using DrKonqi
If you can reproduce the crash at will (or you experience this regularly), can you install the "kdebase-workspace-dbg" package and post a complete backtrace here? Thanks
kdebase-workspace-dgb installed but output of bug report on developer information same as above.
*** Bug 205995 has been marked as a duplicate of this bug. ***
*** Bug 205994 has been marked as a duplicate of this bug. ***
@David: weird, installing that package should provide better info. @Reporters: please read comment 1. Thanks
*** Bug 206694 has been marked as a duplicate of this bug. ***
*** Bug 208712 has been marked as a duplicate of this bug. ***
Bug 208712 got a complete backtrace
*** Bug 208759 has been marked as a duplicate of this bug. ***
From bug 216643: --- What I was doing when the application crashed: I started 'Ksysguard' in a normal window (not maximized), and when clicked on the 'System Load' tab, it crashed. Maybe it's crashed, because the window was too small (640*300), and the graphicons causes a draw fail. (the 3 basic graphicons where there: the CPU, the memory, and the net monitor)
*** Bug 216643 has been marked as a duplicate of this bug. ***
From bug 218338: --- What I was doing when the application crashed: I start ksysguard program and swiched to "System Load" tab. Then I changed height of the window several times (by mouse, left button was not released), so sometimes view was unreadable (too small height). Program crashed.
*** Bug 218338 has been marked as a duplicate of this bug. ***
*** Bug 218749 has been marked as a duplicate of this bug. ***
From bug 219789: --- What I was doing when the application crashed: Ubuntu 9.10: I was using KDE system monitor in Gnome. I had 3 Virtual Machines loaded into Sun Virtualbox (XP, Win7, OpenSolaris) and I was checking how much of my 3 GB of RAM I was using. I saw 2.5 GB in use at the bottom of ksysguard, then I clicked on the header for RAM usage to sort them in descending order, and it crashed.
*** Bug 219789 has been marked as a duplicate of this bug. ***
*** Bug 221227 has been marked as a duplicate of this bug. ***
I think this is fixed now. Please reopen if it occurs in KDE 4.4 RC2 or newer.
We just got two dupes of this crash happening with KDE 4.4.0. Looks like it could be a Qt issue, though.
*** Bug 228310 has been marked as a duplicate of this bug. ***
*** Bug 228313 has been marked as a duplicate of this bug. ***
[Comment from a bug triager] From bug 229869: What I was doing when the application crashed: While investigating problem with Google Chrome Web Browser i.e. several processes show as started, I filtered out all other running processes by typing chrome in the filter field. When clicking on the tab to view the graphs of how the system was running with the filter set, System Monitor crashed. This was replicated every time I used the same process. (and bug 229869 comment 1): Further to the above bug report. I also had the ksysguard window squeezed down to a size that meant it was not possible to fully view the whole graphs. Eventually, I was unable to restart ksysguard without it crashing immediately. In an attempt to try and rectify this I reinstalled ksysguard. That was unsuccessful, and I had to open the application several times while trying to grab the resize window handles to make it bigger. Eventually I was able to resize the window before it crashed again. This made it obvious that the actual cause of the crash was the size of the window, rather than the filtering which I was carrying out. This is further confirmed by the fact that I have now the ksysguard window maximised and filters set, and can swap between the Process Table and System Load tabs without crashing. Apologies if this report duplicates any others, but my initial thoughts on the reason for the crashes did seem valid at the time. I will now get back to looking at why Google Chrome is misbehaving.
*** Bug 229869 has been marked as a duplicate of this bug. ***
I think this has been fixed for some time now.