[Bug 377774] [NEW] Ksysguard crashes when deleting a sensor

ERAZOR daniel_schaeufele at gmx.de
Sun May 17 22:55:02 UTC 2009


Public bug reported:

I'm using ksysguard Version 4:4.2.2-0ubuntu2 on Kubuntu 9.04 (64bit)...

I attached the file that causes this bug for you.
Ksysguard reproducible crashes when I remove the network/interfaces/wlan0/wifi/signal sensor from the bottom display after pressing the OK Button...

The konsole output is following:

======================
ksysguard(6253) Workspace::readProperties: Selected Sheets =  ("ProcessTable.sgrd", "SystemLoad.sgrd")
ksysguard(6253) WorkSheet::replaceDisplay: Found process controller
ksysguard(6253) ProcessController::addSensor: Number of Actions:  15
ksysguard(6253) SensorBrowserModel::addHost: Adding host  "localhost" and sending monitors
ksysguard(6253) SensorBrowserWidget::SensorBrowserWidget: Adding host  "localhost"
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x3c009e8
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x3c07378
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x3c026cd
ksysguard(6253) FancyPlotter::applySettings: Settings changed
KCrash: Application 'ksysguard' crashing...
sock_file=/home/erazor/.kde/socket-erazor-desktop/kdeinit4__0
=============================

This is the debug output from the Crash window, I don't know whether it is helpful for you:
=============================
Eine korrekte Rückverfolgung ist nicht möglich.
Wahrscheinlich sind die Dateien Ihres Systems in einer Weise erstellt worden, die eine solche Rückverfolgung (Backtrace) nicht erlaubt. Oder der so genannte „Stack Frame“ für das Programm wurde durch den Absturz unbrauchbar gemacht.

(no debugging symbols found)
[...]
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f1f68a24760 (LWP 6199)]
[New Thread 0x7f1f5b681950 (LWP 6200)]
(no debugging symbols found)
[...]
(no debugging symbols found)
0x00007f1f6462dd21 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (LWP 6199)]

Thread 2 (Thread 0x7f1f5b681950 (LWP 6200)):
#0  0x00007f1f64664742 in select () from /lib/libc.so.6
#1  0x00007f1f65e13f06 in ?? () from /usr/lib/libQtCore.so.4
#2  0x00007f1f65d4c952 in ?? () from /usr/lib/libQtCore.so.4
#3  0x00007f1f608e83ba in start_thread () from /lib/libpthread.so.0
#4  0x00007f1f6466bfcd in clone () from /lib/libc.so.6
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f1f68a24760 (LWP 6199)):
#0  0x00007f1f6462dd21 in nanosleep () from /lib/libc.so.6
#1  0x00007f1f6462db47 in sleep () from /lib/libc.so.6
#2  0x00007f1f66cceb1f in ?? () from /usr/lib/libkdeui.so.5
#3  0x00007f1f66ccf42a in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#4  <signal handler called>
#5  0x00007f1f6877b6be in ?? () from /usr/lib/libkdeinit4_ksysguard.so
#6  0x00007f1f6876dd1d in ?? () from /usr/lib/libkdeinit4_ksysguard.so
#7  0x00007f1f6877f20e in ?? () from /usr/lib/libkdeinit4_ksysguard.so
#8  0x00007f1f65e4b1f2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#9  0x00007f1f65e454d3 in QObject::event () from /usr/lib/libQtCore.so.4
#10 0x00007f1f6527878d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#11 0x00007f1f6528097a in QApplication::notify () from /usr/lib/libQtGui.so.4
#12 0x00007f1f66c6926b in KApplication::notify () from /usr/lib/libkdeui.so.5
#13 0x00007f1f65e3575c in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#14 0x00007f1f65e627f6 in ?? () from /usr/lib/libQtCore.so.4
#15 0x00007f1f65e5ef0d in ?? () from /usr/lib/libQtCore.so.4
#16 0x00007f1f5f80a20a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#17 0x00007f1f5f80d8e0 in ?? () from /usr/lib/libglib-2.0.so.0
#18 0x00007f1f5f80da7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#19 0x00007f1f65e5ee6f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#20 0x00007f1f65310bef in ?? () from /usr/lib/libQtGui.so.4
#21 0x00007f1f65e34002 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#22 0x00007f1f65e343cd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#23 0x00007f1f65e36694 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#24 0x00007f1f687b4f57 in kdemain () from /usr/lib/libkdeinit4_ksysguard.so
#25 0x00007f1f645a45a6 in __libc_start_main () from /lib/libc.so.6
#26 0x0000000000400769 in _start ()
#0  0x00007f1f6462dd21 in nanosleep () from /lib/libc.so.6
=======================


If you need any further information, please contact me...

** Affects: kdebase-workspace (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Ksysguard crashes when deleting a sensor
https://bugs.launchpad.net/bugs/377774
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in ubuntu.




More information about the kubuntu-bugs mailing list