Thunderbird “invalid security certificate” error

I recently upgraded my Ubuntu installation to 11.10 after not having used it in a while. Part of the upgrade to this new version (Oneiric Ocelot) is that automatically (I believe) adds Thunderbird to your installation, intending that you use it rather than previous client Evolution.

Now, I haven’t used Thunderbird in a while so its fancy new “detect my mail server settings” functionality was all new to me. It all actually went quite well, detecting my mail server name and ports by checking “common server names” based on my email address of (in my case

However my providers SSL certificate isn’t mapped to my domain so the certificate is flagged as “invalid”. There’s no option to accept this certificate so you have to go digging around in Preferences (Options on Windows versions).

What you need to do is go to Edit -> Preferences and go to Advanced -> Certificates -> View Certificates, From here, Add an Exception giving your server (e.g. Click ok and go back to account setup and it should allow you to proceed. Hope this helps and thanks to leepa at Mozzilazine Forums and also bpat1434.

Why is Windows being such a dick?

I recently bought a netbook on eBay that had come with Windows 7 starter but the owner had wiped this and replaced it with Linux.  I needed a new netbook and figured the fact this one came without Windows would keep the price down.  I was right and I purchased a netbook for £68, now all I had to do was get a copy of Windows 7 to install using the product-key which was still stuck underneath.

In the mean time I installed the new Ubuntu 11.04 and set up a number of partitions to get it ready. I set up a /boot partition of about 500MB (for Grub etc.?), a / partition for Ubuntu and a /home partition for my documents.  I also set up a “Win” partition to leave a space for Windows and a final NTFS partition to use for documents etc. when I was booted into Windows or to share across to Linux.  Linux seemed to be working fine and I got on the internet etc.  It was all very smooth, much more so than when I installed Ubuntu 9.10 or whatever it was back in the day.

I got hold of a copy of Windows and began trying to install it from SD card.  When it came to selecting a partition for Windows to live on, I picked my 40GB Win partition but Windows started throwing a strop and told me something it seems to have told a few others before me:

Setup was unable to create a new system partition or locate an existing system partition. See the Setup log files for more information.

Not impressed, I booted into Linux and tried to set a boot flag on this partition.  That took it off my original boot partition though, as a hard drive can only have one boot partition.

In the end I gave up and wiped all the partitions using the Windows installer.  I then created a 40GB partition for Windows, which proceeded to also create a 100MB “system” partition at the start of the drive.  I’m wondering if I’d left my room for Windows at the start of the drive in the first place if maybe I would have avoided this, but as it is – I now have to install Ubuntu all over again.  Fail!!  Thanks Micro$oft!

Skype Installation Shows Ubuntu Not Ready for Masses

The horrifically footery and niggly process I’ve just gone through to install Skype is sad proof that Ubuntu, and Linux, is still not ready for prime time.

The fact you have to get a bit hacky to get a product as mainstream as Skype working is a sad indictment of the state of the OS.

Step 1: Add the Ubuntu Partner Repository following the instructions from Ubuntu’s wiki.

As my installation was Ubuntu 10.04 (Lucid Lynx) upgraded from 9.10 (Karmic Koala) I had to edit the repository information and change the distribution from ‘karmic’ to ‘lucid’ as for some reason this had not been automatically updated as part of the upgrade.

After doing this, and reloading the package information, the Synaptic Package Manager still didn’t find Skype when I searched, so I had to follow

Step 2: Revert to the terminal and enter

sudo apt-get update && sudo apt-get install skype

This was a command I’d picked up from Googling previously and finding this guide.  I figured it was worth a shot.  This seemed to work, gave me a lot of information and asked me if I wanted to continue. I did.

The terminal did a lot of stuff in the background as I’ve been typing this, eventually telling me:

Setting up skype ( ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place

and returning me to the command prompt. Umm… ok? Still not sure this had worked I started looking for Skype and guessed (correctly) that it would be under Internet (I’m using Ubuntu Netbook Edition).  I opened it, accepted the Licence Agreement and signed in. Very slowly.

A good 2-3 minutes later I’m signed in.  Unfortunately, I only use Skype for talking to my girlfriend who’s currently studying in Malaysia and as it is currently 5:40 am there, she’s not online for me to test it out properly on a call.  However I don’t need to do that to ask this question:

How many ordinary users are going to go through all that just to install Skype, and how many will give up and go back to Windows?

SOLVED: No sound after login on Ubuntu Eee PC / Ubuntu Linux

I’ve posted twice recently about my problems following an upgrade of Ubuntu Netbook Remix to Lucid Lynx (10.04).  In short, I upgraded both the BIOS of the netbook (an Asus Eee PC 1008HA) and upgraded Ubuntu from 9.10 (Karmic Koala) to 10.04 (Lucid Lynx).  Once I did this the sound would disappear after the first time I logged in following each boot, and only work properly if I logged out and in again.

One kind commenter (thank you “ThrasherC”) suggested routing code

352732 – Problem in Pulse Audio” href=”″>a solution to a similar problem.  I haven’t followed the story of the bug report and probably don’t know enough about Linux to understand it so I’m not taking responsibility for anyone else doing this. This is a statement of what I did, not advice 🙂

  1. Open a new terminal
  2. Issue command “sudo gedit /etc/pulse/”
  3. Find the line that says “load-module module-device-restore” and comment it out by adding a hash at the start so it reads “#load-module module-device-restore”
  4. Restart

Hope this helps someone – be that you, or me in the future.