profile-image

kenws

Ken Werner , Germany
Kima - kicker monitoring applet

KDE 1.-4. Improvements 360 comments

by kenws
Score 82%
82 Likes
18 Dislikes
Aug 20 2007
Janet,
There are no news on that topic. I haven't found the time to implement a plasmoid and haven't heard anything from Johannes in a while. I'm quite suprised that there is still interest in that. : ) Have you considered using Petri Damsténs system-monitor applet which is part of KDE4?
Regards
Ken - Jun 09 2010
Hello Blackdog7,

the current SVN version of Kima already has a CPU usage source. The devel section describes how to build Kima from the sources: http://kima.sourceforge.net/#development

Regards
Ken - Jun 04 2008
darko,
I looked at the code and if the netcat output really matches to the string you sent it should just work. In your case Kima should list three HDDTemp sources. Did you enable them at the preferences?
regards
ken - Apr 03 2008
Hi Harvest,
it depends on your hardware and the Linux distribution you are using. The features section at http://kima.sourceforge.net/#features lists some kernel modules supported by Kima. If you post some information regarding the distribution and hardware you're using, some users here might be able help.
regards
ken - Apr 03 2008
Hi darko,
the string you sent seems ok to me. Could you post the output of `netcat 127.0.0.1 7634`? I'll look into the source meanwhile.
regards
ken - Apr 03 2008
Hello William,

thanks for asking and sorry for the delay. I wasn't able to check all my mails for the last weeks. Making a Kima plasmoid sounds funny but currently I have no concrete plans to do so. Some month ago we briefly discussed a possible KDE4-Kima. I think a port to Qt4 and KDE4 is possible but not the best solution. There are some new exciting frameworks out there (such as Solid and Plasma) that legimitates a rewrite. It really sounds attractive but I'm pretty busy with my day job and other projects. I can't speak for Johannes but I might met him (physically in a few weeks) and we might find some time to hack something. All I can say is that I haven't started developmet on a KDE4-Kima yet and I'm not willing to make empty promises. : )

Regards
Ken - Jan 15 2008
piricoco,
one problem is that there is no easy way for Kima to detect if a thermal sensor doesn't report a temperature value but a fan speed. Thats a really strange behaviour isn't it? :)
Regards
Ken - Nov 06 2007
Hello piricoco,
thanks for digging into this. I'm afraid I can't help in this case. I think the right place to fix that would be the Kernel (module). Fan values are usually reported to /proc/acpi/fan/. You might want to contact the Kernel people and ask why fan speed is reported as temperature value. It sounds really strange. But I think it's outside kimas scope.
Regards
Ken
- Nov 06 2007
Hello Corinna,
thanks for investigating. Hundred wakeups per second for three sources sounds pretty much. On my system I get about 5-6 wakeups per source and this still sounds too much. Most source are updated every second - so I would expect one wakeup per second per source. We're actively discussing alternate implementation ideas to optimize the powertop ranking.
Regards
Ken - Nov 04 2007
Hello piricoco,
unfortunately the user can't change the suffix yet. So there is no way to do that except from changing the source. But let me understand your case first. Are you saying that a kernel module posts a fan speed value as thermal source? Which thermal source provides the fan value? For example the omnibook kernel module or the linux ACPI thermal zone driver. The heading line of the preferences dialog of that source gives a hint. Could you post the appropriate /proc values too? For example /proc/omnibook/temperature or /proc/acpi/thermal_zone/*/temperature.
Regards
Ken - Nov 04 2007
Hello szotsaki,
just start hddtemp in daemon mode with appropriate parameters. i.e. hddtemp -d /dev/sda
Depending on your distri there might be a config file at /etc/default/hddtemp.
regards
ken - Oct 26 2007
Hello,
as litb said, we haven't found the reason yet, but it seems to be outside of Kimas source code. Some threads are not notified anymore so they don't return to running state. Thus some of the sources are not updated.
Which kernel are you using? You may be able to avoid that problem by disabling the "Dynamic Ticks" feature or something else timing related in your kernel (see http://lkml.org/lkml/2007/3/12/72).
Regards
Ken - Sep 02 2007
Hello,
I didn't try it yet. I Guess the code needs little tweaking until it compiles against the Qt3Support lib. Just give it a try and let us know. : )
Regards
Ken - Sep 02 2007
Hello freefred,

the current development version has got two new checkboxes to exclude system and nice load. Checkout the development version from svn at http://kima.sourceforge.net/#development

Regards
Ken - Aug 28 2007
Hello,

thanks for your suggestions. We're working on such features. The latest release has a new source that displays the CPU usage.

Regards
Ken - Aug 28 2007
Hello devsk,
Johannes implemented a CPU usage source. Currently it's only available in the SVN trunk. We might add the other sources later. Feel free to checkout the current development version: http://www.elliptique.net/~ken/kima/#development
regards
Ken - Jul 04 2007
Hello,
are you sure the tooltip works for other applets (i.e. the System Monitor)? There is a strange bug debian based systems where no kicker applet tooltips are shown after a while. Kima uses the standard mechanism to show its tooltip.
Regards
Ken - Jun 22 2007
Hello Bleedinge,
the changes are now in the svn repository. (http://www.elliptique.net/~ken/kima/#development) Let us know whether the development version of kima improves the situation. Thanks.
Ken
- Jun 20 2007
It seems there are only a few users who are affected. We tried really hard to find the bug. Unfortunately it doesn't crash on my systems so its hard to make a fix. A potential glitch might be the source scanning routine where multiple threads are created. I serialized that and made a workaround package. It would be great if as many users as possible could test this one and give short feedback. Thank you.

Ken

http://www.elliptique.net/~ken/kima/kima-0.7.3.1-workaround.tar.gz - Jun 18 2007
Hello marseillai,
thanks for reporting that. Could you provide a stack trace of the crash? You can follow the instructions on
http://www.elliptique.net/~ken/kima/#development
but add --enable-debug=full as a configure argument. Feel free to contact me via Jabber.
Regards
Ken - Jun 12 2007
Hello Robert,
thanks for reporting the glitch. Which sources/sensors do you have? We found a bug in the nVidia source that might lead to a memory leak. In the SVN trunk we already fixed that. Feel free to contact me via Jabber: ken@elliptique.net.
Regards
Ken - May 17 2007
Thanks for reporting that. The typo is fixed in the svn repository. Next release will include the fix.
Regards
Ken - Apr 28 2007
Hello,
we would like to support the sensors of multiple nvidia boards. Since we don't have the appropriate hardware we are looking for people who are willing to provide the necessary infos and test beta releases. You are welcome to contact me via Jabber.
Regards
Ken - Apr 12 2007
yes. it seems your idea triggered the other developers. :)
Regards
Ken - Apr 05 2007
Hello,
Transparency: Since the transparency on kde3 is not native there might be issues. I just tested it on my system (KDE 3.5.6) and it worked.
Showing performance profile: Adding a source that displays the current profile would be easy. I'll keep that in mind.
Regards
Ken - Mar 25 2007
Hello,
I'm afraid that I do not understand your question. What do you mean by "2° VGA"?
Regards
Ken
- Mar 25 2007
Hello,
I've got your stack trace - thanks. We have been looked to the code for some hours and now we are pretty sure its
not Kimas fault. It crashes while a string needs to grow but we don't know exactly why it crashes then. Maybe it's caused by ABI problems (g++, kde, qt) or defective hardware.

Here is the demangled stack trace with some code:
/lib/tls/i686/cmov/libc.so.6[0x4db0688f]
/lib/tls/i686/cmov/libc.so.6(malloc+0x7f)[0x4db0783f]
operator new(unsigned int)
operator new[](unsigned int)
QString::setLength(unsigned int)
QString::grow(unsigned int)
QString::operator+=(QString const&)
Source::formatTemperature(QString const&) const || return temp + QString::fromUtf8(" °C");
ACPIThermalSrc::fetchValue() || s = formatTemperature(s.left(s.length()-1));
ThreadedTrigger::run()
QThreadInstance::start(void*)

This is the involved C++ code:
src/sources/acpithermalsrc.cpp: formatTemperature(s.left(s.length()-1));
src/sources/source.cpp: return temp + QString::fromUtf8(" °C");

If anyone has an idea whats wrong with that, please let us know.
Regards
Ken - Mar 25 2007
Hello,
an uptime source is not our highest priority currently. However I've heard that Manfred is working on that.
Regards
Ken - Mar 16 2007
Hello,
thanks for reporting this. Johannes skimmed through the source and found a glitch in the new hddtemp source. Maybe thats the problem. We are working on 0.7.1 that will include a fix. Meanwhile you could try to disable the hddtemp source. Please let us know if that worky for you. Feel free to contact me via Jabber.
Regards
Ken - Mar 16 2007
Hello,
kima takes what the hddtemp daemon provides. If you configue hddtemp properly it will show your sda drive too. : )
On a debian based system this can be done at /etc/default/hddtemp.
Regards
Ken - Mar 16 2007
Hello,
thanks for your hint. I built the deb on kubutnu 6.10 but with updated KDE (http://kubuntu.org/announcements/kde-356.php).
I just build a new deb (same url) that should fix your problems. Please try again and sorry for inconvenience.
- Mar 14 2007
Hi,
kima 0.7 support values provided by hddtemp in daemon mode. Make sure hddtemp runs on 127.0.0.1 port 7634 before kima starts.
Regards
Ken - Mar 11 2007
Hi,
I could try to build one if someone provides a ssh-login to a feisty-box. I think it could be done in less than an hour. Feel free to contact me via Jabber.
Regards
Ken - Feb 26 2007
You can switch to metric/imperial system via kcontrol: "Regional & Accessibility"->"Country/Region & Language"->"Other"->"Measure system"->"Metric"/"Imperial" and restart the applet (dcop kicker Panel restart). - Feb 11 2007
Hi,
thanks for reporting the bug. We figured out that KGlobal::locale()->measureSystem() isn't thread safe and changed Kimas code. I would really like to thank Johannes and Peter who helped me debugging this all night long. Kima 0.6.3 is now on its way. - Jan 28 2007
I noticed that too and its because Kima is a non-unique applet currently (you could add multiple instances of Kima to your kicker). I'll change Kima to a unique applet so that the preferences are stored without the instance ID. See http://api.kde.org/3.5-api/kdelibs-apidocs/kdeui/html/classKPanelApplet.html#a4 for details. The next release should solve your issue. - Jan 19 2007
Kima is not necessarily limited to temperatures, frequency and fan speed. As the changelog suggests Kima adds more and more sensors that hopefully includes battery sensors too in the future. The next release brings a new NVidia source and some internal structural changes. - Jan 19 2007
What happens if you perform the following command:
cat /proc/i8k && appletproxy `kde-config --prefix`/share/apps/kicker/applets/kima.desktop
It should first read your i8k values (just to ensure the module is loaded) and then a small window should pop up containing the Kima applet showing all available sources. - Jan 18 2007
From what I can see here I have no indication why it shouldn't work. If the kernel module is loaded before Kima starts and you have the i8k sources in the preferences dialog enabled it should display your CPU temperature and Fan speed. - Jan 18 2007
You can switch to metric system per kcontrol: "Regional & Accessibility"->"Country/Region & Language"->"Other"->"Measure system"->"Metric" and restart the applet. - Jan 16 2007
Hello,
the output looks not too bad. I took a closer look to your /proc/i8k value which says your machine runs Bios A14. Which model do you have? Knowing that one could check whether the fan speed is supported on your notebook (see http://people.debian.org/~dz/i8k/00-README). The fan status shows valid values but the fan seems not to be rotating (which should be reported as 0 rpm). However Kima should at least provide a Source named "CPU". The provider of the source is shown in the preferences dialog that should state: "This source is provided by i8k kernel module.". - Jan 16 2007
Hello Stephane,
Kima needs the i8k kernel module loaded before it starts. Otherwise the source can't be detected. Please modprobe the i8k module. Then a 'cat /proc/i8k' should give you some values. If so, you could start the applet via: appletproxy `kde-config --prefix`/share/apps/kicker/applets/kima.desktop - Jan 15 2007
Yes, you are right. It is updated if the value changes. I'll try to improve this. Thanks. - Jan 05 2007
thanks for your input. as discussed via IM it seems to be lm_sensors related because a cat /sys/bus/i2c/devices/*/fan1_input also hangs for a while. i'll try to find a workaround for that - Dec 06 2006
if you computer is not a notebook you could try lm_sensors to gain more sources. - Dec 06 2006
As I said above - try again with the installed X devel packages or use the binary .deb package. - Dec 06 2006
Hmm, maybe you need some *-devel packets first. I guess the dapper debian package above should work out of the box. - Dec 04 2006
You can switch to the Imperial/Metric system via kcontrol: "Regional & Accessibility"->"Country/Region & Language"->"Other". - Sep 20 2006
CPU Info (with lm_sensors)

KDE 1.-4. Improvements 16 comments

by ectb
Score 71%
71 Likes
29 Dislikes
Feb 09 2006
"CPU Info (with lm_sensors)" is a fork of CPU Info that was recently renamed to Kima. I guess this one here is not developed anymore. You could try kima instead: http://kde-apps.org/content/show.php?content=33257 - Jan 01 2007