Image 01


Jan Wedekind Totton, United Kingdom
System Software
Kubuntu Spectrum Theme

KDM4 Themes 6 comments

Score 68.0%
Sep 19 2010
Here is how to get KDM back in Kubuntu 14.04 so you can keep using the spectrum theme: - Mar 09 2015
Kubuntu Spotlight KDM

KDM4 Themes 6 comments

Score 74.3%
Nov 06 2009
Very nice! I'm using it on Kubuntu 10.04 - Jul 29 2010

KDE 4 Splashscreens 21 comments

Score 78.4%
May 06 2010
I'm using it on Kubuntu 10.04. - Jul 29 2010

Database 41 comments

Score 50.0%
Feb 28 2010
Ok, great. Thanks for your feedback. You helped me to fix two bugs!
- Mar 01 2010
You could trace the system calls of AnyMeal and check where it expects the file splash.jpg:

strace anymeal 2>&1 | grep splash.jpg

On my system (Kubuntu 8.04) at some point it reports success:

access("/usr/share/apps/anymeal/pics/splash.jpg", R_OK) = 0
- Mar 01 2010
I hope you managed to get the splash-screen installed. I released AnyMeal-0.31-2 with a modified configuration scripts which checks for and links it if it exists. - Mar 01 2010
You need to run make install from the directory anymeal-0.31-1. If you run make install from the sub-directory anymeal-0.31-1/src, only part of the software will be installed.

If it still doesn't work you can run the following command to check whether pics/splash.jpg was installed:

find `kde-config --prefix`/share/apps/anymeal

It should list splash.jpg among other files. I think under openSuse 10.3 the complete filename would be:

/opt/kde3/share/apps/anymeal/pics/splash.jpg - Feb 25 2010
I'm not sure. I looked up the package contents of libXalan-c-110 at Apparently there is an extra library in that package with the file name ''. Probably you need to link this as well. Please try to run make with this option

make LDFLAGS='-lxalanMsg'

- Feb 24 2010
Well, to my disgrace I must admit that I haven't worked on it lately. Maybe I will try to do something with Qt4QtRuby and CouchDB some time but I won't promise.

Regarding your bug report: One just needs to include cstdio and cstring. I've added the include statements and I uploaded the modified source [1] (I will release it on Sourceforge later). Thanks for letting me know about the problem! Let me know if there are any more problems.

- Feb 24 2010
kmando human computer interface

System Software 163 comments

Score 63.3%
Jun 29 2009
Thanks for letting us know ;) - Aug 17 2009
Maybe you have a more recent version of Ubuntu (not the one the package was compiled for). In that case you need to compile kmando from source:
- Jul 27 2009
Let me clarify what I am saying.
I will do the work.
I just want guidance.
Just an email a day or such, no code.
Are you in?

If you do the project with Ruby and HornetsEye (, I can try to give you some guidance and even write some code if it's not to much work. But note that I can't spend much time on it, since I currently have a lot of work to do ;)

In this case I think it may better to continue the discussion in the general discussion forum of Hornetseye ( As a first step you can try to setup Ruby and Hornetseye on your PC. Let me know if you get stuck. - Apr 22 2009
Ah ok. I currently don't know anybody who has time to do it. Also it sounds like you require investigative work to develop the idea as well.
Maybe you can manage to get Johnny Chung Lee's Wiimote Whiteboard [1] working instead. It requires a Wiimote and infrared LEDs.

- Apr 22 2009
Sorry discuss what? - Apr 22 2009
No. The application uses colour segmentation, i.e. it looks for an object of distinct colour.
To recognise a hand occluding a button, one could implement background subtraction and thresholding. The problem is that when the background changes, a new reference image needs to be acquired.
I currently don't have time for this though. - Apr 09 2009
This is a community project by Juan Roldan, Ushakiran Soutapalli, Julien Faucher, and me.
I am currently working on other things and I don't have time to add translation support to this project. Anybody else?
However you can find documentation about localisation at
Providing language support basically requires to do the following steps:
* Add i18n calls to the sourcecode. Make sure that the user-interface compiler generates i18n calls as well.
* There is a tool to create translation template files (pot) from the C++ source code. I forgot how to do it.
* Use kbabel to do the translation.
* Add the translation to the built process.
- Oct 16 2008
One needs to find out what kernel module is driving the card. What is the name of the card? Maybe you can list the card with "lspci". - Jun 09 2008
What camera are you using (V4L (webcam,framegrabber), firewire)? Did you try to adjust brightness, contrast, ...
Note that kmando currently does not support V4L2. - Jun 08 2008
Oh wait. You are asking whether it works with laser pointer?

I have no laser pointer here. So I don't know whether it will work for sure. Here is a system where it seems to work, but the source code is not available: - May 29 2008
That's awesome :-D
- May 29 2008
The config.log suggests that the header file of libdc1394 is broken either on your computer only or on the distribution itself. Here is an extract of the affected file around the line of code you indicated. I hope you can fix it.

dc1394_set_format7_byte_per_packet(raw1394handle_t handle, nodeid_t node,
unsigned int mode,
unsigned int packet_bytes);

dc1394_query_format7_value_setting(raw1394handle_t handle, nodeid_t node,
unsigned int mode,
unsigned int *present,
unsigned int *setting1,
unsigned int *err_flag1,
unsigned int *err_flag2);
dc1394_set_format7_value_setting(raw1394handle_t handle, nodeid_t node,
unsigned int mode);
- Mar 31 2008
Oops. Didn't know that you don't have a Firewire interface. For USB with V4L1 the Logitech Quickcam Pro 4000 is the only camera I know which works with this software. V4L2 cameras are not yet supported by this software.
Currently I am developing V4L2 software with a Logitech Quickcam Pro 9000. However I don't know when I will find the time to integrate MJPEG streaming support *and* port kmando to Ruby. Plenty of work to do here ...
- Mar 04 2008
Sorry for answering so late. I must have missed your mail in all the spam.
I am hesitant to start a new forum. As I said I am planning to port the whole thing to Ruby/HornetsEye and HornetsEye already has a RubyForge and a SourceForge discussions forum. Juan Roldan may be applying for a Sourceforge project but he didn't have time to do it so far.
I have contributed to Mimas and I am currently working on HornetsEye and in our forums I have *never* received information from users which cameras are working. I only get to hear something if our software or a Linux driver fails ;)
I recommend a Unibrain Fire-I (IIDC/DCAM compatible firewire camera).
- Mar 03 2008
>You mean that the only high resolution usb webcams that works with your software use this driver?
No. The software should work with most or all V4L cameras (not all colourspaces are covered). However if I suggest another camera to you without testing I could get a lot of things wrong. Even when I buy a camera myself, I am never 100% sure:
* Linux driver may not work with your kernel
* Linux driver may only support low frame rates
* Some cameras with the same product name have different chipsets requiring different drivers
* The resolution may be to low to recognise the pointer position with sufficient accuracy
* The resolution may be to high for the CPU to handle the pictures in real-time
* The picture quality may be bad
* ...

If I have the time, I will add V4L2 support. The uvc driver [2] for example supports many cameras. Unfortunately the cameras only work at a high frame-rate when transferring MJPEG which is more sophisticated than the colourspace transformations we have to do already.

> This would provide the users of your software a tool to participate, collaborate with developers and between them sharing useful information.
Well, at the moment noone is really working on this project a lot and I was thinking of porting the thing to Ruby at some point anyway (see HornetsEye project[1]).

> If you need it I can help with that.
I appreciate your offer. However my workload already is high and I don't have the time to start maintaining a forum. If I can port kmando to Ruby, I can use the forums at RubyForge and Sourceforge. Also the software will run with V4L2 cameras and it may even run under Microsoft Windows.

[2] - Feb 23 2008
The entry for the Logitech Quickcam Pro 4000 is here:
It is always a good idea to check the developer-homepage of the particular Linux driver. The homepage for the pwc-driver is here:

There is no camera-manufacturer which provides drivers for GNU/Linux. The third-party drivers are developed by many people around the world. Therefore there is no single web-site which I could point out as a good reference. You are asking me to provide information which I really don't have. Sorry ;)

I could recommend the new Logitech Quickcam Pro 9000 because it has a much higher resolution. But the uvc-driver is a V4L2-driver and our application does not have V4L2 support at the moment. - Feb 22 2008
At the moment I have support for V4L (version 1 only!) and IIDC/DCAM compatible digital firewire cameras. I cannot recommend other cameras without testing, because some cameras are very slow under GNU/Linux, or the resolution or picture quality is insufficient. So far I've tried the Logitech Quickcam Pro 4000 (640x480, 60€ last time I checked) and the Unibrain Fire-i camera (640x480, 120€ as far as I know). Maybe you can order the Fire-i from Unibrain (see
Better get a money back guarantee in case you are not satisfied with the overall system performance.
* (cameras with V4L)
* (cameras with IIDC=yes/1.30/1.31)
- Feb 21 2008
Can you make sure that the following packages are installed: libgl1-mesa-dev, libglu1-mesa-dev, freeglut3-dev?

If this does not help, you can look at the file "config.log" after trying to reconfigure. You need to search for "checking for OpenGL". You can also send me the "config.log" (by e-mail) and I can try to figure out what is going wrong.
- Feb 18 2008
Probably your OpenGL installation is not complete or broken. Try to download and compile a small OpenGL example program. Usually the error-message is conclusive. For example download cube.c ( and try to compile it like this:

gcc -o cube cube.c -lGL -lGLU -lglut
- Feb 17 2008
You need to install the developer package of Qt as well. Depending on your distribution this will be a package with a name like "qt4-dev", "libqt4-dev", "libqt4-devel", "qt-devel-4.3.0" ...
- Feb 11 2008
Thanks for your work! - Feb 08 2008
Thanks for the bug-report. It seems that the template implementation of GCC-4.2 does not like our array operations. I had to change the code quite a bit.
Let me know whether the new version works:
- Feb 07 2008
After e-mail conversation. Here the KDE-apps posting for the public:

When forcing software rendering the problem disappears:


The problem seems to be a bug in the glDrawPixels method of the ATI driver for GNU/Linux (GL_BGRA colourspace display in this case).
- Feb 06 2008
You can try forcing the size by editing the file You can change this

input = VideoPtr( new Video( (const char *)ui.deviceEdit->
ui.channelSpinBox->value() ) );


input = VideoPtr( new Video( (const char *)ui.deviceEdit->
640, 480 ) );

Sorry, but I don't have time currently to add Firewire support. - Feb 03 2008
Cool. Make sure you send us your project report (if there is any) and give us links if you publish something on the web!

The software is a community projects. If you look at the homepage, you will see a list of contributors. For a detailed description on how the software works I refer to Juan's report [1].

I am not sure what the motivation of each person working on this project is/was ;) But I think it is a lot of fun to work on a small piece of software which has a big effect. It took nearly one year to get the project to this point but it was not worked on continuously. Also code from Mimas[2] and Bright[3] was used. The software furthermore is based on Boost, OpenGL, Qt, Lapack, and Fftw. Maybe it could have been done in about two months but the concept was not clear in the beginning and development was not straightforward. Thanks again to all involved for their endurance and motivation.

Delay and sensitivity are two parameters for detecting when the pointer has stopped moving (for issuing mouse clicks). The delay determines the amount of pointer positions to be collected and the sensitivity is a threshold for the allowed variance of the pointer position in this time. If the variance is below the threshold it is assumed that the pointer is stationary and a mouse click is issued.

Thanks for using the software in your project.

- Nov 14 2007
Sigma is the amount of blurring applied to the segmented image before locating the pointer.
I used a bright desktop background because otherwise the pointer is not illuminated and detection becomes unreliable.
Another idea would be to try a laser pointer (see I didn't try this myself and I don't know whether it will work.
The software is just using colour segmentation. So you need to avoid using the same colours for pointer and projected image. Also the illumination of the pointer should not change to much.
I hope you get the results you need. - Oct 29 2007
1. What is the importance of the picture adjustments in the first step?
You need to make sure that the whole projection screen is covered by the camera. Otherwise the calibration will fail.

2. How close should the webcam be when I grab an image of the pointer?
You should use the pointer in a natural position (i.e. close to the screen) because the colour will be used to detect the pointer again later.

3. How much of the pointer should I select to make an accurate color selection?
You need to try this out. It is important that the pointer has a colour which does not appear in the image. It is a trade-off between not detecting the pointer or mistaking some areas on the screen for the pointer.

4. What does the threshold and range do? Should those be adjusted or left at default?
The threshold determines the range of colours being accepted (same trade-off as above). The range defines the size of the region for pointer tracking. It's a trade-off between CPU-load and tracking performance.

5. What are recommendations for the button pressing options in the last step? It seems to adjust it's self but I don't know what it's basing it off of.
The last step is for selecting the motion threshold for mouse-clicks. Mouse-clicks are issued whenever the pointer is nearly stationary for a certain time. The wizard allows you to set the number of samples and a threshold for the root-mean-square of the pointer movement.

If you want to know exactly what the software is doing, you really should read the source-code ;)
- Oct 25 2007
Sorry that I don't have V4L2 support yet. I hope I will get around to do it some time.
Currently I am working on "HornetsEye" which will make implementing an application like "kmando" much easier:
- Oct 17 2007
I am sorry to hear that it is still not working. This error message however is really weird. I looked at the driver homepage (I guess the uvc module is in use here)
Maybe the V4L version 1 support of the driver is not completely developed.
There are two possibilities:
a) Someone adds V4L2 support to kmando
b) You get another camera (we are using Logitech Quickcam Pro 4000) for the moment
I am not sure when someone (probably me ;) ) will get around to add V4L2 support (I am also not 100% sure wether this will solve your problem). I will look into it (see, but I cannot promise to integrate it soon.
- Oct 06 2007
If it says "Mimas-index" it is the old code again!
I mean to comment out the lines in the source file of the new package (with the combo-box for PAL/NTSC/SECAM/AUTO) which I put at
- Oct 04 2007
Sorry to hear that it is still not working.
It looks like the following piece of code in "image_v4linput.tcc" is (still) not working: = channel;
chan.type = VIDEO_TYPE_CAMERA;
chan.norm = channel_norm;
MMERROR( xioctl( VIDIOCSCHAN, &chan ) == 0, mimasexception, ,
"Error setting channel information for channel "
<< << " of device \"" << device << "\": "
<< strerror( errno ) );

This code selects the channel and the signal type. It is only necessary for capture cards with multiple channels or TV tuners with different input signals.
Can you comment this code out, recompile and tell me what happens?
- Oct 04 2007
> I was able to get it to compile and run, but still get an error when trying to use my webcam "Error setting channel information for channel 0 of device "/dev/video0":invalid argument". I have tried different video #'s and channels but my webcam is on video0 and the rest come up no such file or directory (from video1 on).

kmando sets the video-mode to PAL. Maybe the driver does not like this. I have created a package for testing, which allows you to try other modes (PAL/NTSC/SECAM/AUTO). I hope it helps.
Let me know whether this works. You can download the package for testing here:
- Oct 04 2007
Video palette "7" is VIDEO_PALETTE_YUV422 (see /usr/include/linux/videodev.h). I think it is the same as VIDEO_PALETTE_UYVY. Can you replace the source file "" with the following one and recompile mando-1.4?
Let me know whether it works.
- Oct 03 2007
> ID 046d:092e Logitech, Inc.
> I think its Logitech QC Messenger.

No, according to
it is a Logitech Quickcam Chat. This is actually one of the cameras I have at home. I had problems getting it to work with Michel Xhaard's newest gspca driver and I sent him an e-mail on March 1th 2007. I didn't receive a reply so far.

However I got the camera working with his old driver:

su # Login as superuser (or "sudo su")
cd /tmp
tar xvzf gspca-20060930.tar.gz
cd gspca-20060930/gspcav1

I also have to reduce the contrast-value of the camera quite a lot (you need kmando version 1.4 for this), because the default setting will give you an oversaturated picture. The colors are way off, but one can somewhatadjust them using the module-parameters (one can set them by editing /etc/modprobe.conf):

sudo su # Login as superuser
rmmod gspca

Add the following line to /etc/modprobe.conf:
options gspca autoexpo=1 usbgrabber=0 lightfreq=50 GRed=256 GBlue=350 GGreen=256 gamma=4

Then load the gspca-module back:

modprobe gspca

> As far as compiling is concerned, I am a newbie. This is what I got when I compled
> "checking for X... no
> checking for XTestFakeMotionEvent in -lXtst... no

If you still want to compile kmando, uou need to install You can find out which package of your distribution you need to install at
- Apr 25 2007
This is difficult for me to resolve without having access to the camera. Also I don't know, what camera you have. There are different Logitech Quickcam models (Pro 4000, Pro 5000, Chat, Messenger, ... ). You can login as superuser and
type "lsusb" to get the exact device-id.

Furthermore you can configure and compile the project in debug-mode:

./configure --enable-debug=yes

Running the program from the terminal then will give more information about the camera and what's happening.

Maybe the RGB colourspace support of your camera is broken. You can change the order of preferences for colourspaces in line 172-174 to this (you need to build with "make" afterwards):
palette[ 0 ] = VIDEO_PALETTE_YUV420P;
palette[ 1 ] = VIDEO_PALETTE_UYVY;
palette[ 2 ] = VIDEO_PALETTE_RGB24;

Hope it helps.
- Apr 22 2007
Ok. Thanks for your effort. - Apr 19 2007
ucv is a V4L2 (video for linux 2) driver. kmando as of version 1.4 only supports V4L version 1. The uvc driver does not support the old V4L protocol (according to At the moment I am very busy. I will have a look at V4L2 when I get the time to do it.
- Apr 16 2007
Maybe you have a camera with a V4L2 (video for linux version 2) driver. kmando as of version 1.4 only supports V4L1 (version 1). - Apr 16 2007
Make sure to use /dev/video0 (not dev/video0).

If you have another video device (TV-card for example), it is possible that your camera appears on another device (for example /dev/video1).

It is also possible that for some reason the camera driver makes the camera appear on another channel. In this case you need to install the new version of kmando (mando-1.4) which I just uploaded. I have added a new spinbox control which allows you to try different channels. Note that device number and channel are two distinct numbers. You may have to try several combinations to find your camera:
  • device=/dev/video0 channel=0

  • device=/dev/video0 channel=1

  • ...

  • device=/dev/video1 channel=0

  • device=/dev/video1 channel=1

  • ...

  • ...
  • - Apr 14 2007
    I will test kmando with XGL and Beryl later this year. kmando uses Qt4-OpenGL which is well tested. XGL on the other hand has not reached release 1.0 yet.
    Using kmando together with XGL is an exciting idea though ;)
    - Apr 13 2007

    Karamba & Superkaramba 1 comment

    Score 50.0%
    Mar 25 2007
    I downloaded sunwait from and installed your theme.

    Maybe the output format of sunwait was changed, because I had to modify the commands for extracting the time of sunset.
    ... | head -c47 | tail -c2
    ... | head -c49 | tail -c2

    Furthermore under GNU/Linux I had to replace "tail -c 2" with "tail -c2".

    Nice theme by the way! - Apr 25 2007
    Time Keeper

    Plasma 5 Clocks
    by niceway

    Score 86.7%
    9   Sep 13 2015
    zen winter

    Wallpaper Other
    by zenren

    Score 80.2%
    9   Nov 28 2011

    Plasma Themes
    by jmtodaro

    Score 75.9%
    9   Sep 22 2010