None of these lines are working. Instead I receive mails, complaining about “unexpected EOF while looking for matching “” \ “syntax error: unexpected end of file”.
Referring to the man pages (man 5 crontab), “%” are “newline characters” and needs to be escaped with backslash:

The “sixth” field (the rest of the line) specifies the command to be run. The entire command portion of the line, up to a new-
line or % character, will be executed by /bin/sh or by the shell specified in the SHELL variable of the crontab file. Percent-
signs (%) in the command, unless escaped with backslash (\), will be changed into newline characters, and all data after the first
% will be sent to the command as standard input. There is no way to split a single command line onto multiple lines, like the
shell’s trailing “\”.

In other words, to get it working, add backslashes (\) in front of your “%”s and your fine:

To make sure, you got the right cam, plug it into your computer.
Check if your camera matches my ID by running:

There should be something like this:

If your ID matches, please continue, otherwise you might be lucky and can start installing Gstfakevideo straight away. However this “Howto” was only tested for a QuickCam Messenger with the ID above. For other IDs please take a look here: https://wiki.ubuntu.com/SkypeWebCams

All you need before we start:

Remove the old quickcam_messenger module because it will not deliver the correct colors for our cam. If you do find a solution for this problem, please leave a comment! Thanks. Anyway removing the installed module:

To make sure it is not going to be loaded again we add the following line at the end of /etc/modprobe.d/blacklist.conf

Download the new qcmessener module:

Apply this patch:

Continue installing:

Ignore the “Kernel configuration is invalid.” errors.

Give it a test:

If every thing works go on and install Gstfakevideo:

Create a new file (i.e. in your home directory) called skype.sh and add these lines:

And run:

Now reload the module

Info: run

to view more options.

Create a new file /etc/modprobe.d/qcmessenger.conf and add:

This makes sure, that your webcam will always be /dev/video1 (as /dev/vidoe0 is needed for gstfakevideo) and uses “dblbuf” (correct colors).

Add your account to the “video” group:

Finally fire up Skype by running skype.sh. That’s it!

Please leave a comment if you got some problems or want to give me feedback.

Here is a test image.

Serverseitig
In der /etc/ssh/sshd_config folgende Zeile hinzufügen:

Restart des SSH Dienstes nicht vergessen.

Clientseitig
In der /etc/ssh/ssh_config folgende Zeile hinzufügen:

Persönlich favorisiere ich die serverseitige Variante, da das Verbindungsproblem sowohl client- also auch standortunabhängig heben lässt. Wem der Zugriff auf den Server verwehrt wird, dem bleibt halt nur die clientseitige Version.

If it is not woking after a restart, make sure you installed mingetty.

Dazu erstellen wir eine Schleife in der wir die Variablen $i und $x definieren. $i sind alle Dateien, die ein Prefix der Form ????_* haben und $x ist nichts anders als $i (unsere Dateien) mit dem Unterschied, dass wir erst nach dem sechsten Zeichen anfangen zu lesen. Mit anderen Worten, wäre $i z.B 0323_MeineDatei.txt dann ist $x MeineDatei.txt.
Im letzten Schritt werden die Datein dann mit mv umbenannt.

So einfach kann das sein.

I am surprised how many people visit my site because their looking for a solution to get a Logitech QuickCam Messenger (046d:08f0) running on Linux using Skype

Since my last post seems to be a bit buggy for newer kernels, I updated my system to Debian (Lenny, 2.6.26-1-686) and gave it try.

All you need before we start:

Plug in your webcam.
Remove the old quickcam_messenger module:

To make sure it is not going to be loaded again we add

at the end of /etc/modprobe.d/blacklist

Download the new qcmessener module:

Now if you are running kernel 2.6.26 or newer , it is necessary to patch some files.

Continue installing:

Remember to be root when running make install

Give it a test:

If every thing works go on and install Gstfakevideo:

Create a new file called skype.sh and add these lines:

And run:

Now reload the module

Create a new file /etc/modprobe.d/qcmessenger and add:

This makes sure, that your webcam will always be /dev/video1 and uses “dblbuf”.

Finally fire up Skype by running skype.sh. That’s it!

Please leave a comment if you got some problems or want to give me feedback.

Update:
Here is a test image.

I assume you change the BIOS settings already. All you need to do now, is to tell you Debian not to turn off your Ethernet controller while shutting down your system.

Create a new file /etc/modprobe.d/3c59x and add following line:

and run

Now you are done.
I use wakeonlan to start my computers.

Dies eignet sich auch besonders gut, um die aus Windows stammende Thumbs.db aus Fotoalben zu löschen. Das würde dann so aussehen:

Wer über alte Subversion-Projekte stolpert und die .svn Ordner loswerden möchte, kann folgendes in seine Konsole eintippen:

If you want to use evdev just add (keep your Configured Mouse block) these lines to your xorg.conf

And this line into ServerLayout:

Just make sure you replace the device with the path to your mouse.
Otherwise you can run

to get the right device. That’s it! Your done.

Step 2 for Laptop users
If you are running Linux on a Laptop you might have a InputDevice called something like Synaptics Touchpad. If that is the case, go ahead and remove your Configured Mouse InputDevie block and remove the “Option SendCoreEvents true” line in your Touchpad Device.
Now add Corepointer behind the Touchpad InputDevice in the ServerLayout like here:

It is important that the Touchpad becomes CorePointer even though you use an external mouse the whole time, because otherwise your X-System will not boot if your mouse is not connected.

Now your are all set and can use all your mouse buttons. Use xev and xbindkeys to map you new buttons to other functions.

Nach einem Restart von X waren zwar alle Fonts wieder auf Normalgröße, aber Firefox hatte da wohl noch so seine Probleme.
Dort öffnen wir about:config und setzen layout.css.dpi von -1 auf 0.

Was letzendlich zu dieser Verunstaltung führt, ist mir unbegreiflich.