random crash of ksysguard in XFillPolygon

Bug #239414 reported by LimCore
4
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

ksysguard was running as always, nothing special; Crash occurred when I was away from computer.
ii ksysguard 4:3.5.9-0ubunt system guard for KDE
Linux limcore 2.6.24-16-generic #1 SMP Thu Apr 10 12:47:45 UTC 2008 x86_64 GNU/Linux

ubuntu 8.04 amd64 up-to-date, dual core,
nvidia on binary driver (glx-new)

[Thread debugging using libthread_db enabled]
[New Thread 0x7ffb75f9f6f0 (LWP 26103)]
[KCrash handler]
#5 0x00007ffb6f3f5095 in raise () from /lib/libc.so.6
#6 0x00007ffb6f3f6af0 in abort () from /lib/libc.so.6
#7 0x00007ffb6f3ee2df in __assert_fail () from /lib/libc.so.6
#8 0x00007ffb71b242d3 in ?? () from /usr/lib/libX11.so.6
#9 0x00007ffb71afe4ec in XFillPolygon () from /usr/lib/libX11.so.6
#10 0x00007ffb73d2d68d in QPainter::drawPolygon (this=0x7fff7dfe1b30,
    a=@0x7fff7dfe1d30, winding=false, index=0, npoints=5)
    at kernel/qpainter_x11.cpp:2453
#11 0x0000000000445b4e in SignalPlotter::paintEvent (this=0x9845b0)
    at /build/buildd/kdebase-3.5.9/./ksysguard/gui/SensorDisplayLib/SignalPlotter.cc:575
#12 0x00007ffb73e0f858 in QWidget::event (this=0x9845b0, e=0x7fff7dfe23c0)
    at kernel/qwidget.cpp:4808
#13 0x00007ffb73d7333a in QApplication::internalNotify (this=0x69f380,
    receiver=0x9845b0, e=0x7fff7dfe23c0) at kernel/qapplication.cpp:2638
#14 0x00007ffb73d75be3 in QApplication::notify (this=0x69f380,
    receiver=0x9845b0, e=0x7fff7dfe23c0) at kernel/qapplication.cpp:2526
#15 0x00007ffb754a940d in KApplication::notify (this=0x69f380,
    receiver=0x9845b0, event=0x7fff7dfe23c0)
    at /build/buildd/kdelibs-3.5.9/./kdecore/kapplication.cpp:550
#16 0x00007ffb73d0420e in QApplication::sendEvent (receiver=0x9845b0,
    event=0x7fff7dfe23c0) at ../include/qapplication.h:523
#17 0x00007ffb73d3e6d7 in QWidget::repaint (this=0x9845b0, reg=@0xa655d0,
    erase=true) at kernel/qwidget_x11.cpp:1627
#18 0x00007ffb73d7433e in QApplication::sendPostedEvents (receiver=0x0,
    event_type=0) at kernel/qapplication.cpp:3299
#19 0x00007ffb73d74449 in QApplication::sendPostedEvents ()
    at kernel/qapplication.cpp:3213
#20 0x00007ffb73d18054 in QEventLoop::processEvents (this=0x6e5ec0, flags=4)
    at kernel/qeventloop_x11.cpp:147
#21 0x00007ffb73d8d5bf in QEventLoop::enterLoop (this=0x6e5ec0)
    at kernel/qeventloop.cpp:201
#22 0x00007ffb73d8d2ab in QEventLoop::exec (this=0x6e5ec0)
    at kernel/qeventloop.cpp:148
#23 0x00007ffb73d74e00 in QApplication::exec (this=0x69f380)
    at kernel/qapplication.cpp:2761
#24 0x000000000042ca0b in main (argc=<value optimized out>,
    argv=<value optimized out>)
    at /build/buildd/kdebase-3.5.9/./ksysguard/gui/ksysguard.cc:640

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Changing to proper package.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Is this still an issue in KDE 4.1?

Changed in kdebase:
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kdebase:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.