Image 01


Joe Istead Waterloo, Canada
Karamba & Superkaramba
simple weather forecast

Plasma 4 Extensions 204 comments

Score 62.5%
Dec 26 2009
Applying this patch to version 0.5 of the code allows the user to select the font using a dialog (by clicking a button in the config menu).

The pastebin expires Feb 6, 2009. However, the changes might be included in v0.6 of the code. Feel free to email me for the patch/code after that time, if all else fails. - Jan 07 2009

Karamba & Superkaramba 6 comments

Score 50.0%
Dec 29 2008
Hi Roly,

Quick fix: try using "cat /proc/cpuinfo"... this should give you a ton of information, CPU MHz should be buried in there somewhere. The Oxygen system monitor uses this command:

"cat /proc/cpuinfo | grep 'cpu MHz' | sed -e 's/.*: //'| sed -e 's/\..../ MHz/' | head -n 1"

My complaint about this is that it's a little bit more difficult to parse frequency on a *per core* basis. In particular, the Oxygen command blindly looks for the first "cpu MHz" it can find... I guess that can be worked around by removing the "head -n 1" bit... however, using this command still seems inelegant compared to what cpufreq-info gives you.

I don't want to speculate too much since I'm unfamiliar with gentoo systems. However, when I run "cpufreq-info", I see

analyzing CPU 0:
driver: acpi-cpufreq
current CPU frequency is 800 MHz.

I tried apt-get'ting a few things, but I really don't remember where acpi-cpufreq came from. By chance, your system might already have it... try "modprobe acpi-cpufreq" as per

That website is a decent intro. The following websites may also be helpful...

Note that step 3 contains a list of CPU-specific kernel modules which may be helpful to you.

Last but not least... it was a while ago when I installed cpufrequtils... it might have worked out of the box for me because I had previously installed lm-sensors. I guess I'm just wondering if installing lm-sensors pulled in some common dependencies that allowed cpufrequtils to work properly. - Dec 30 2008
Don't quote me on the SLI w/ one GPU disabled behaviour. It was just an initial observation. - Dec 30 2008
Hi Roly, thanks for the comment.

I'm looking at making this widget configurable (think: menu). I think this might be possible if I write some Python code. Your suggestions should be possible if this works out.

As for a quick fix to your SLI and CPU frequency problems... use "unzip" to expand the .skz file, edit the .theme file. It should be easy to remove the extra GPU (don't forget to change the widget height... ugh... I agree, autoconfiguration would make this much easier).

The CPU frequency requires the cpufrequtils package (sudo apt-get install cpufrequtils). Try typing "cpufreq-info" into the console, see if you get anything. I use the "-f -m" tags to print pretty, and "-c" to pick CPU core.

One last thing about SLI. My laptop has SLI, but the second card is disabled in the BIOS. I noticed that nvidia-settings (the command that gets called by my widget) uses the temperature from the active GPU for both GPU's in this case. - Dec 30 2008
Liquid Weather ++

Karamba & Superkaramba 1797 comments

by Matti
Score 46.0%
Jun 01 2008
Hi Matti,

Thanks for clearing this situation up. Sure do appreciate your hard work. - Dec 30 2008
Hi Matti,

From what I'm seeing, there's two problems. Some packages need to be installed (kross, pyqt etc)... the one that got me was libkrosspython0, even after everything else was installed.

The second problem seems to be the "from qt import *"... inside checkDependencies, Python complains about importing *... outside of checkDependencies (i.e. at the module level), there's "Import of the PyQt3 module is not allowed."

So quick question. To port liquid weather to KDE 4, is it just a matter of working around this one difficulty that you know of? I'm willing to poke around in the code, maybe try to do the port, if you can spare a bit of guidance. Your widget is the best weather widget out there from what I see... - Dec 30 2008
I commented out the "from qt import *" ... but that only gets me a console version of the widget, it almost looks like debug functionality.

There seems to be two problems. When "from qt import *" is inside the checkDependencies function, the runtime complains that import * only works at the module level (I think this might be an issue for Python 2.2 and later). If the import is moved to the module level, then we get the "Import of the PyQt3 module is not allowed" error.

So just a quick thought. What if we get rid of the import *? Would this make a difference? - Dec 30 2008
More on this here... - Dec 30 2008
Cpu Frequency Selector Ruby

Plasma 4 Extensions 20 comments

Score 77.7%
May 01 2010
I get the same problem. Did you have any luck getting the Python version of Cpu Frequency Selector to work? (it works for me... maybe better luck there?) - Dec 06 2008
Score 85.8%
Jan 07 2009
simple weather forecast

Plasma 4 Extensions
by biophysics

Score 62.5%
Jan 06 2009