Maybe i discover the application that "kick" kicker ;)

if iremove the kickerrc file in ~/.kde/share/config/ kicker run very well, so i rebuild my usual bar with all my favourite applet, and when i try to add "System Monitor" kicker die!

What do you think the problem is kicker bug or applet bug!?

yes, this is certainly a plugin bug. perhaps you could rebuild the plugin with debug support?

Well, here is one crash in the sysguard applet. Could be unrelated to this BR, of course. If someone feels like tracking it down, go nuts. Otherwise, I'll do it sooner or later.

Invalid read of size 8
   at 0xDD0C79F: SignalPlotter::paintEvent(QPaintEvent*) (SignalPlotter.cc:439)
   by 0x6ED71D8: QWidget::event(QEvent*) (in /opt/qt3/lib/libqt-mt.so.3.3.6)
   by 0x6E3F754: QApplication::internalNotify(QObject*, QEvent*) (in /opt/qt3/lib/libqt-mt.so.3.3.6)
   by 0x6E405C3: QApplication::notify(QObject*, QEvent*) (in /opt/qt3/lib/libqt-mt.so.3.3.6)
   by 0x61CDA7F: KApplication::notify(QObject*, QEvent*) (kapplication.cpp:550)
   by 0x6DD52C8: QETWidget::translatePaintEvent(_XEvent const*) (in /opt/qt3/lib/libqt-mt.so.3.3.6)
   by 0x6DDE8AA: QApplication::x11ProcessEvent(_XEvent*) (in /opt/qt3/lib/libqt-mt.so.3.3.6)
   by 0x6DEE6FC: QEventLoop::processEvents(unsigned) (in /opt/qt3/lib/libqt-mt.so.3.3.6)
   by 0x6E57533: QEventLoop::enterLoop() (in /opt/qt3/lib/libqt-mt.so.3.3.6)
   by 0x6E57421: QEventLoop::exec() (in /opt/qt3/lib/libqt-mt.so.3.3.6)
   by 0x4BCD588: kdemain (main.cpp:146)
   by 0x8FA30E2: (below main) (in /lib64/libc-2.4.so)
 Address 0x9787A98 is 5 bytes after a block of size 11 free'd
   at 0x4A21B9E: free (in /usr/lib64/valgrind/amd64-linux/vgpreload_memcheck.so)
   by 0x716AAC2: QGArray::~QGArray() (in /opt/qt3/lib/libqt-mt.so.3.3.6)
   by 0x61E4FA1: KConfigBase::readNumEntry(QString const&, int) const (kconfigbase.cpp:583)
   by 0x61D2B16: kDebugBackend(unsigned short, unsigned, char const*) (kdebug.cpp:241)
   by 0x61D2E81: kdbgstream::flush() (kdebug.cpp:336)
   by 0x4BCD9A7: kdbgstream::operator<<(char const*) (kdebug.h:232)
   by 0x628C6E3: KCheckAccelerators::eventFilter(QObject*, QEvent*) (kcheckaccelerators.cpp:117)
   by 0x6E3F719: QApplication::internalNotify(QObject*, QEvent*) (in /opt/qt3/lib/libqt-mt.so.3.3.6)
   by 0x6E405C3: QApplication::notify(QObject*, QEvent*) (in /opt/qt3/lib/libqt-mt.so.3.3.6)
   by 0x61CDA7F: KApplication::notify(QObject*, QEvent*) (kapplication.cpp:550)
   by 0x6ED7140: QWidget::event(QEvent*) (in /opt/qt3/lib/libqt-mt.so.3.3.6)
   by 0x6E3F754: QApplication::internalNotify(QObject*, QEvent*) (in /opt/qt3/lib/libqt-mt.so.3.3.6)

Yes in my italian version of kde the apps that kill kicker is the sysguard applet, but if you dont start it kicker is ok!!

I think is a sysgard problem, maybe ;)

Molding this into something more tangible.

*** Bug 129063 has been marked as a duplicate of this bug. ***

SVN commit 574018 by kling:

Fixed crash when resizing a plot view with "top bar" enabled.
Affects both standalone program and panel applet.

BUG: 130100
CCMAIL: johnflux@gmail.com


 M  +1 -1      SignalPlotter.cc  


--- branches/KDE/3.5/kdebase/ksysguard/gui/SensorDisplayLib/SignalPlotter.cc #574017:574018
@@ -436,7 +436,7 @@
     col = mBeamColor.begin();
     for ( double* d = mBeamData.first(); d; d = mBeamData.next(), ++col ) {
       int start = x0 + (int)( bias * scaleFac );
-      int end = x0 + (int)( ( bias += d[ w - 3 ] ) * scaleFac );
+      int end = x0 + (int)( ( bias += d[ mSamples - 1 ] ) * scaleFac );
       /* If the rect is wider than 2 pixels we draw only the last
        * pixels with the bright color. The rest is painted with
        * a 50% darker color. */