Create a shell script /usr/local/bin/magnet containing:

#!/bin/sh
/usr/bin/transmission-remote --add "$1"

chmod +x /usr/local/bin/magnet

In Firefox go to about:config

Right-click on any link and select "New->Boolean".

Boolean name: network.protocol-handler.expose.magnet
Boolean value: false

Right-click on any link and select "New->Boolean"

Boolean name: network.protocol-handler.handler.external.magnet
Boolean value: true

Restart Firefox

I don't know why Python applications are so verbose with deprecation warnings. Either the apps should be fixed, or the system should be configured to not emit those pesky warnings in production. Since the former is not happening, I found a way to do the latter. So, if you are sick and tired of warnings like this:

/usr/lib/pymodules/python2.6/rdiff_backup/SetConnections.py:148: DeprecationWarning: os.popen2 is deprecated. Use the subprocess module.
stdin, stdout = os.popen2(remote_cmd)

edit your /etc/python2.6/sitecustomize.py file and append these two lines at the very end of the file:

import warnings
warnings.simplefilter("ignore", DeprecationWarning)


Of course, look for sitecustomize.py elsewhere if it's not in the same directory as on my system (check /etc/pythonX.Y, /usr/lib/pythonX.Y and /usr/lib/pythonX.Y/site-packages directories). The correct location obviously depends on the Python version.

If you have a windows share with a space character in it's name, e.g. something like \\server\my share, to properly mount it from /etc/fstab you need to use the octal code instead of a space character. Otherwise parsing /etc/fstab would produce an error, because space character is a delimiter.

The octal code for space character is \040 (don't forget the leading zero!), so you'd put //server/my\040share in the /etc/fstab for the example above.

Current default for X servers as shipped in various distributions is to not enable the traditional Ctrl-Alt-Backspace key combination to kill the X server. If you would like to re-enable this feature, you may do so in your desktop's Keyboard Preferences application. You may also enable it for the current session using the command "setxkbmap -option terminate:ctrl_alt_bksp".

If you upgrade GTK library to the newest 2.18 version (comes with the new Gnome 2.28) your VMware Workstation 6.5.3 won't work well. Even if you have "Grab when cursor enters window" option set, VMware won't grab your pointer when you move mouse into the VMware window. Also, if you use ctrl-G to capture the pointer, VMware window will release it as soon as you move mouse around a little bit. Quite annoying behavior...

If you have trouble maximizing those YouTube videos when run under compiz-fusion, here's what you can do to fix it.

Go to CompizConfigSettingsManager, choose General Options and unclick 'Unredirect Fullscreen Windows' option under General tab. Then click Back and select 'Workarounds'. Turn on 'Legacy Fullscreen Support'. Of course, 'Workarounds' plugin must be enabled on the front page for this to come in effect.

And that should be it!

Now try maximizing flash videos again and report you success below.

This morning, hardworking Debian developers pushed the remaining pieces of the brand new X.Org 7.3 to Debian sid (unstable) distribution. And it must be said, a well done job!

ii  x11-apps            7.3+1      X applications
ii  x11-common          1:7.3+2    X Window System (X.Org)
ii  x11-session-utils   7.3+1      X session utilities
ii  x11-utils           7.3+1      X11 utilities
ii  x11-xfs-utils       7.3+1      X font server utilities
ii  x11-xkb-utils       7.3+1      X11 XKB utilities
ii  x11-xserver-utils   7.3+1      X server utilities
ii  xbase-clients       1:7.3+2    miscellaneous X clients - metapackage
ii  xorg                1:7.3+2    X.Org X Window System
ii  xorg-dev            1:7.3+2    the X.Org X Window System development
ii  xserver-xorg        1:7.3+2    the X.Org X server
ii  xutils              1:7.3+2    X Window System utility programs


Referencing the post Nvidia Linux driver 100.14.11 and Linux kernel 2.6.23. Here I have attached the patches for the older versions of Nvidia drivers. The procedure to follow is the same as described in the above document.

Due to software or hardware (network switch or ethernet card) error it may be possible that you need to restart auto-negotiation on the ethernet device. Here's how to do it:

mii-tool -r eth0

or

ethtool -r eth0


Then check the kernel log to see what happens:

% dmesg
eth0: link down
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1


Thanks for this tip goes to Vivek.

Well, they're not working together. Unless you're not willing to tweak it a little bit. So, out of the box, you won't be able to test brand new Linux CFS scheduler, merged in the 2.6.23-rc1 release, if you drive your Nvidia card with the proprietary driver. I guess that's what we get for running binary drivers.