1. Options -> Advanced -> Config Editor
2. mail.trusteddomains = *.oracle.com

However, when not using one of the monitors, Gnome does not know what to do with the panel normally displayed on that monitor and places it on the default monitor, resulting in two gnome-panels on one monitor. This is not so useful!

To circumvent this default Gnome behavior use the following procedure:

• Download gnome-panel-switch.sh script and put it somewhere you like:

#!/bin/bash
#
# Auto adjust the number of pannels based on the number of
# connected monitors.
#
# Author : Amain 2010
# Website: blog.zoomeren.nl
 
# Monitor states:
#   - connected 1440x900+0+0  ( connected and used )
#   - connected               ( connected not used )
#   - disconnected            ( disconnected       )
#
NR_OF_MONITORS=$( /usr/bin/xrandr -q | /bin/grep " connected [0-9]\+x[0-9]\+" | /usr/bin/wc -l )
 
# Second panel name
#
# note: retrieve the panel name using gconf-editor
#
SECOND_PANEL_NAME="panel_0"     
 
case $NR_OF_MONITORS in
        1)
                # Disable external monitor ( setting screen to -1 )
                #
                gconftool-2 --type int --set  /apps/panel/toplevels/$SECOND_PANEL_NAME/screen -- -1
        ;;
 
        2)
                # Enable external monitor ( restart is needed after setting screen to -1 )
                #
                gconftool-2 --type int --set  /apps/panel/toplevels/$SECOND_PANEL_NAME/screen 0
                /usr/bin/killall gnome-panel
        ;;
 
        *)
                # no action
        ;;
esac

• sudo chmod +x gnome-panel-switch.sh
• sudo mv /usr/bin/gnome-display-properties /usr/bin/gnome-display-properties.bin
• sudo vi /usr/bin/gnome-display-properties and paste the following script ( don’t forget to adjust the path in line where gnome-panel-switch.sh is called! ):

#!/bin/bash
#
# Auto adjust the number of pannels based on the number of
# connected monitors.
#
# Author : Amain 2010
# Website: blog.zoomeren.nl
 
# Open gnome-display-properties dialog
#
/usr/bin/gnome-display-properties.bin
 
# Auto enable/disable gnome-panels
#
YOURPATH/gnome-panel-switch.sh

• sudo chmod +x /usr/bin/gnome-display-properties
• Start gnome-panel-switch.sh every time Gnome starts to auto disable/enable the correct number of gnome-panels per display. Use Gnome Startup in the System Settings menu and add the invocation for this script.
• Important note: when /usr/bin/gnome-display-properties is replaced during a Ubuntu upgrade one looses the changes!

Karmic:

• https://launchpad.net/~ubuntu-mozilla-daily/+archive/ppa/+packages ( Will install also firefox 3.5 daily build by default!! )
• http://blog.thomas-lauria.de/archives/9-Mozilla-Lightning-1.0b1-for-Thunderbird-3-on-linux-amd64.html
• Download Dutch 32 bit tar version from http://download.mozilla.org/?product=thunderbird-3.0&os=linux&lang=nl
  • Extract tar
  • cp thunderbird-3.0/dictionaries/nl.* /usr/lib/thunderbird-3.0*/dictionaries/

Update:

• https://help.ubuntu.com/community/ThunderbirdLightning
• http://themikecam.com/blog/2009/10/05/64-bit-lightning-builds-for-linux/
  • http://www.secudb.de/~seuffert/mozilla/2010-01-12%20-%20lightning%201.0pre%20×86_64%20linux%20english/

post-up /usr/sbin/ethtool -s eth0 wol g
post-down /usr/sbin/ethtool -s eth0 wol g

Write down the MAC-ADDRESS. Powerdown the computer. Only when the computer is powered down to S3 or STR(Suspend to ram), the computer can be woken up. A sudden power-failure might mess with everything so the computer might not respond then to WOL requests. For STR some additional action are necessary, because STR in Linux might/will totaly power-off the ethernet device. See this link for more info on that subject.

On another computer install a wake-on-lan package:

dpkg -i wakeonlan

and wake up the sleeping computer:

wakeonlan MAC-ADDRESS

note: create a small shell script in for example ~/bin/wol_dev.sh to make life easier and to not forget the MAC-ADDRESS:

#!/bin/sh
#
# Wake on lan server: dev
#
# dev eth0 00:02:44:57:dc:33
# dev eth1 00:10:4b:0e:ce:13
 
wakeonlan 00:02:44:57:dc:33

That’s all!

Links:

• http://xlife.zuavra.net/index.php/60/
• http://linux-tipps.blogspot.com/2008/11/fixing-wake-on-lan-in-ubuntu-810.html

Download: nzbget_0.7.0-2_mips

It seems to be that VirtualBox has a problem switching between multiple core’s on the host and therefore causing high CPU load on the host, even while the Guests are idle. This is of course not good. There are a couple of solutions / workarounds:

1. Adjust the CPU affinity for the Guest’s VirtualBox process
2. Configure multiple CPU’s in the Guest’s VM settings
3. Run another small idle/dummy Guest VM besides the one you want to use

I use the second option with success. I have an Intel(R) Core(TM)2 Duo CPU laptop and I assigned 2 CPU’s in the Guest’s settings and now the host CPU usage is back to normal, luckily. Also note that it’ has been reported, that VirtualBox is not very well handling tickless kernels ( CONFIG_NO_HZ=y ) or has higher CPU usage with high resolution timers like 1000 Hz ( CONFIG_HZ_1000 ). Ubuntu Jaunty has for example a tickless kernel and OEL 5.3 ahs a timer tick of 1000 Hz.

Links:

• http://tech.shantanugoel.com/2009/07/07/virtualbox-high-cpu-usage-problem-solved.html

1. Avalon Compiz Emerald Theme
2. Humanity Gnome Icon Theme
3. Yellow U-Flower background image

Click on the image to enlarge.