When I have multiple terminal tabs open with various local and remote (via SSH) command lines running it is nice to know which is which. Byobu thoughtfully changes the title as you log in, but Screen does not (I have both configured to automatically launch when I log in). One line added to my .bash_profile does the trick though:


printf "\033]0;${USER}@$(hostname) - screen\007"
screen -xRR


The first printf line is the one that does the trick and tells me who I’ve logged in as and to what machine, as well as reminding me I’m in Screen. The second screen line simply starts Screen if it is not already running, or connects to the existing instance if it is.

                          

I’ve just upgraded my desktop machine, it isn’t exactly state of the art, the new one is only a 3.2GHz P4 and is my first 64 bit desktop, but that’s beside the point. The point is I dropped the old SATA HD into a new box and let Ubuntu get on with the job of sorting out the hardware changes (as an aside Windows 7 put on a bit of a show and then gave up in a huff!).

All went well apart from the graphics, which meant I couldn’t even get the login prompt (I knew I should have stuck with a console and typing startx!! To cut to the chase the solution that worked for me was to boot into the recovery mode kernel and do a one off boot into a safe graphics mode. From here I used the Additional Drivers tool to remove the proprietary ATI driver. This allowed me to reboot into the standard desktop and confirm thins were working, but sadly I couldn’t get above 1024×768 which restricted screen space somewhat.

As it happens I doubt the above was needed because my next action was to boot once more into recovery mode and restore the proprietary driver and reboot. This time when the screen went blank and complained about being ‘out of timing’ I used ALT-F2 to bring up a CLI login and from there used:

sudo aticonfig --initial

This created /etc/X11/xorg.conf, although unfortunately this didn’t make any difference, but it did prepare the ground for:

sudo aticonfig --resolution=0,1280x1024,1024x768

which persuaded the driver to use a more sensible set of parameters that worked with the monitor.

The most notable difference I’ve spotted in the logs so far is that when not working I had the line:

(II) fglrx(0): Setting screen physical size to 423 x 317

whereas when working it is:

(II) fglrx(0): Setting screen physical size to 338 x 270

I’ve not explored whether there is anything else, or what that actually means!

                          

Anyway, the upgrade was largely uneventful, which is always nice, I do like a boring life for some things The only two items of note were:

• For some reason Upstart didn’t automatically start nmbd on boot – I’m not sure whether this was a one off, but I’m now following a bug on Launchpad and will have to find a suitable time to do another reboot and see what happens.
• There was a minor problem with the Dovecot configuration (and this is what started me towards this blog post!) – the sieve plugin has changed.

I’ll elaborate on that one a bit.

Recently I migrated my mail system from a combination of Exim, Procmail and Dovecot to Exim and Dovecot with Sieve. I’ll get round to blogging about that process at some point, but for now suffice it to say that instead of receiving may with Exim and passing it to Procmail to filter into the various mailboxes and then using Dovecot to access it via IMAP, Exim now passes the mail direct to Dovecot which then uses built in Sieve support to filter the mail into the various mailboxes. This has two advantages, firstly Dovecot can index the mail as it comes in, which has a minor performance boost when first accessing new mail from the client, and secondly the Sieve syntax is much easier to follow than Procmail (well I find it is anyway!).

Getting right down to the issue at hand, on this upgrade I found things stopped working, and after a very brief look around the config file and Dovecot plugins directory identified that in the dovecot.conf file the line:

mail_plugins = cmusieve

needed to be changed to:

mail_plugins = sieve

This did get me thinking that it may be nice to manage a do-release-upgrade process in stages rather than hitting all services at once, but having said that the number of dependencies being upgraded at the same time in this process would likely make that impractical to manage – and to be honest I’ve not found a major problem yet

                          

Anyway, today the second account started giving the same error, so I decided something must be wrong, and I should take a look. If nothing else I wanted to find out whether it was me or something that needed raising as a bug. It looks as though this is a general problems and there should be a bug fix to the python-papyon package on the way, but to summarise the details from Ubuntu bug #664570:

Find the file

/usr/share/pyshared/papyon/service/description/SingleSignOn/RequestMultipleSecurityTokens.py

and edit the line

CONTACTS = ("contacts.msn.com", "?fs=1&id=24000&kv=7&rn=93S9SWWw&tw=0&ver=2.1.6000.1")

and replace it with

CONTACTS = ("contacts.msn.com", "MBI")

Personally I always leave the original line there as a comment for reference or backout purposes

Then restart Empathy and you should be fine.

                          

I’m rebuilding my main desktop system at the moment. It isn’t anything spectacularly new, in fact it is based on a Athlon XP 2800+, but it runs Linux (Ubuntu 9.10 currently) with ample performance for my day to day tasks. Windows XP runs on it adequately, when it actually works (I clearly use it too little because it sulks and ‘blue screens’ every few months, requiring a repair or reinstall).

Anyway, as part of this rebuild I decided that it made sense to get everything bang up to date, including the BIOS. The board is obsolete now, so the BIOS was a few years old and should be stable enough – wrong! The board is a Gigabyte GA-7S748-L (GA-7S748 with on board LAN), and was running the F5 revision. Updating was simple enough, just boot of my DOS USB key (yes, I have a USB key with DOS installed!) and run the utility. This brought things up to revision F9, which was the latest, and is where things started to go wrong.

The first thing I noticed was that my Windows 7 installation couldn’t see the HD, so I reached for a driver (Vista was the most up to date) to add during the install process. This didn’t work, and further investigation showed that the BIOS of the PATA PCI card the drives were connected to wasn’t active. It turned out that enabling USB legacy support disabled the card BIOS. Unfortunately, in order to configure the card BIOS you needed a keyboard, and since mine was a USB one, USB legacy support was required to use it – catch 22!! After trying a PCI SATA card instead I found that this was clearly a motherboard issue and not specific to one card or chipset.

So the next thing to do was to back off to the previous BIOS (F8 in this case) to see if the bug had been introduced in the latest BIOS upgrade. Unfortunately it seems that the F8 BIOS was completely bug ridden (so it is a shame it is still available for download). After installing it the computer wouldn’t boot at all, although it would allow use of the BIOS itself. This board has a facility to flash the BIOS from a BIOS based utility (Q-Flash), which sounds pretty handy in this case. Sadly it didn’t work, although thankfully, the failure didn’t damage the installed BIOS any further. After a bit of research with Google, I found that if you disable USB support completely you can boot to a floppy and re-flash the BIOS using a DOS based utility (will DOS ever die?!).

So, with this information I managed to get back to the F5 BIOS and all was working again. Out of curiosity I then tried the F6 BIOS and found that the USB legacy support clash with the PATA card BIOS was introduced there, so presumably exists in F7 too. Back to square one again then, with the original F5 BIOS and a working PC!

                          

I note from recent news that Microsoft and Yahoo! have been given the go ahead for their search deal, which means that Microsoft Bing should be providing the search results for Yahoo! by the end of the year.

Interesting times, since that would appear to indicate that the average new user of Ubuntu will be using a Microsoft search engine, and one that may not be as good for searching for information on Linux and Open Source software – although it has to be said I’ve not experimented with this myself.

                          

That said, let’s move on…

The other day my son came home and asked if he could use the computer. Nothing spectacularly unusual there, but shortly after logging on he came back to me asking if we had “the big blue W” on it somewhere. After a brief to and fro I ascertained that what he meant was Microsoft Word and that he wanted to show me something that he had done at school.

There’s a few points here. Firstly there is the comparison with when I was his age (he is seven). Back then I still had around 6 years until the ZX81 was launched and I got my first taste of computers. Now they are not only everywhere, but interconnected to the point where it didn’t even occur to him that the work he had been doing at school wouldn’t be accessible from home – bless him.

Secondly there’s the annoyance that from such an early age the ‘big blue W’ and Microsoft Word are synonymous with word processing. I keep trying to tell myself that he is only seven and they need to keep things simple, but it is still irritating. The end result of this was that I sat down and explained what a word processor was, and that even though I didn’t have the one he used at school I did have another one. I was encouraged by the fact that, when presented with OpenOffice he set straight to work trying to reproduce the same sort of document he had at school, and did so with no help at all – beyond a brief grumble that there wasn’t much clipart! (actually I did show him where that was).

The next question baffled me a bit, “do we have the internet?”. My response was to tell him that we did, and that he used it regularly! Then we headed down a familiar road, “no I mean the big blue e” So off we went down the explanation of what a browser was and that he was already quite comfortable using both Opera and Firefox, as was his younger brother (who is 3). In fact they are both rather too good at some of the games on the CBeebies, Nick Jr and BBC Dr Who websites! Still, they are also quite happy playing with Frozen Bubble or Tux Paint

                          

To start with it is worth noting that I’ve only installed the Windows version, since I’m suffering using Microsoft on the desktop for a while. This is partly due to a couple of hardware failures, partly office reorganisations that are as yet unfinished, and partly forcing myself to keep my hand in – unfortunately I have to.

The first thing I noticed was that it was much faster and more responsive. Firefox 2 has, particularly in the past few weeks, been pausing for periods for no apparent reason. The second observation was that the memory footprint was much, much smaller, so this may well be linked. I tend to use a reasonable number of tabs when browsing and have been keeping an eye on the memory usage recently. I’ve been trimming things down to around 12 open tabs at a time and was amazed that Firefox was using between 200M and 260M, with no sign of reducing when tabs were closed. After installing Firefox 3 I checked and found that it was running at pretty much exactly half that, around 100M to 130M with the same 12 tabs as before the upgrade!

Part of this reduced footprint may be down to the few extensions that are now disabled due to incompatibility. With a major upgrade it is probably time to take a look through the extensions I’m using to see if any are no longer relevant. A few quick highlights of my extension usage are…

Bookmark Sync and Sort – sadly this is no longer compatible, and from a quick investigation it hasn’t been updated for a good while now, and the referenced home page has gone. Time to look for an alternative it seems. All this was doing was backing up my bookmarks to a WebDav folder on my intranet server, and at first glance there seems to be no obvious alternative. With a bit more digging I’ve found two, or perhaps just the one, options:

• Foxmarks – I ignored this first time round since it was linked to a service, but further investigation shows that you can use it with either WebDav or FTP, as well as install a server component. The original Foxmarks was based on the OSAF Cosmo server, but it looks as though this has been replaced by the Chandler project, so a little more investigation is required.
• Sitebar – another one I passed over when finding Bookmark Sync and Sort. Again it is linked to a service, but it seems that you can download the server component if you want to. Sadly, according the the Mozilla Addons site it doesn’t currently support Firefox 3, but it does have the advantage of being open source which Foxmarks doesn’t seem to be. Again, more investigation is required.

Firebug, IE Tab (remember this is on Windows!), It’s All Text!, Speed Dial and Web Developer are all available for Firefox 3, so that just leaves…

Tab Mix Plus – not having this one is a bit painful, although partly because I’m not sure what features I’m missing that were part of it and what may now be officially available that I haven’t found yet! That said, I’ve just noted that there is a newer version, just not listed on the Mozilla Addons site. I’ll have to give it a try and then work out what options I’m using that it provides – the session manager, the new tab button and undo closed tabs spring to mind.

There are a couple of other incompatible ones listed on my install. Google Photos Screensaver I think I had disabled anyway and RealPlayer Browser Plugin I hadn’t noticed before – although is probably responsible for blindingly easy downloads from YouTube etc.

That’s what leaps out at me, bar the slight interface changes. No doubt more differences will become obvious over time.

                          

OK, with that out the way, I thought that I’d do a quick blog about the ease of installing .deb packages within Ubuntu (clearly I’m in a bit of a blogging mood today – something of a rarity!). I first stumbled across this a while ago when I decided to install the Opera browser alongside my usual Firefox install. I headed off to the Opera website to download the .deb file that I knew, from previous Debian installs, would be there. What I was expecting to do was download it, do a test install run with aptitude -s to check for any missing dependencies and then, after installing any missing items, install Opera – all via the trusty, familiar command line.

Things didn’t go as expected though. When I clicked on the .deb file that was provided I was given the option to ‘Open with’ the GDebi Package Installer. Even though I’ve been using Debian for some years now I’ve not come across this piece of software before. This is just another reminder, as if
one were needed, that there is always something new to learn however familiar you are with something, and however long you’ve been using it. Anyway, I decided to let GDebi do its stuff, and after downloading the .deb file it added a couple of dependency packages to the install list and proceeded (after a couple of confirmation prompts) to install Opera and the required extra packages – all nice and easy, and one more demonstration that, certainly to my mind, Windows has a long way to go to catch up with Linux in terms of ease of use

Today I was reminded of this easy install path for non standard software once again. Not to say that I had forgotten about it, but it isn’t often used. I was reminded, however, in a rather unexpected place. Once again I was off to download a piece of software to install, and yes, another proprietary piece, but some of us have to live and work in the real world where, unpalatable though it may be to some, we have to use proprietary software – and to be honest, I have to concede that there is likely to have to be a place for it in some cases, but that is getting off topic. I was off to the Adobe website to download the latest copy of the Adobe Reader (or Acrobat as it was once called). What I was expecting was to download the tar.gz file, extract it and then use the installer. I’ve done this before, and have tested pre-release versions in the past. One of my feedback comments was that it would be nice to have a .deb package version as well as the .rpm one. Well I can’t say how much impact that feedback had, but I can report that there is now a .deb package for the Adobe Reader. I suspect that the rise and rise of Ubuntu probably has at least something to do with this. Whatever the reason, I was presented with a .deb file, which then installed with ease using the GDebi Package Installer. Once again had a pain free installation on Linux – no battling with dependencies (as per the ‘olden days’ of Red Hat), no bits of my system being over written with different versions of files that break existing applications (as can happen with Windows, mfc42.dll anyone?), just a few clicks and a pain free install.

                          

After using a pretty standard Ubuntu install with Gnome for a while I decided to switch back to my preferred XFCE desktop. This was fairly straightforward, although the xubuntu-desktop package pulled in a few things I didn’t want, so I used it to populate the new install list (in Synaptic) and then trimmed the packages I didn’t want (mainly the office applications since I prefer to stick with OpenOffice). One thing I noted after making the switch back was that there was no Network Manager applet running, and a quick check of the package details seemed to indicate that it was part of Gnome, so I decided to look elsewhere for an equivalent. I experimented briefly with Wicd, but whilst doing that I found out that, although Network Manager is part of Gnome it is pretty free of Gnome dependencies and is largely independent, so I decided to switch back. Having done that I needed to look for a way of getting the applet running. This seemed simple enough, I just needed to add an entry into the Autostarted applications list as accessed from Applications -> Settings. Having done this all seemed well until, after a few reboots I noticed that I had multiple copies of the nm-applet in the panel – oops!

After a bit of digging around my file system in directories like /etc and ~/.config with the grep command I finally came up with some likely files, mainly /etc/xdg/autostart/nm-applet.desktop. Then with a bit of help from Google I came up with a couple of good references, mainly a bug report for Ubuntu [1], a reference on the Ubuntu forums [2] and another discussion linked from there [3]. With the aid of those and a bit of experimentation I came up with the following fix:

1. First off I got rid of all the nm-applet instances running with pkill nm-applet
2. Next I got rid of my hand installed autostart entry for the nm-applet, so to do this I deleted the file ~/.config/autostart/nm-applet.desktop
3. Then I made an edit to the system wide autostart entry for nm-applet, for this I need to change a line in the /etc/xdg/autostart/nm-applet.desktop
   file from OnlyShowIn=GNOME; to OnlyShowIn=GNOME;XFCE;. This lets the nm-applet configuration show in the Autostarted applications utility when you’re running XFCE.
4. Finally I needed to clear out any information relating to nm-applet in the cached sessions. This was a case of editing two files in the ~/.cache/sessions/ directory.
• These were xfce4-session-dusky:0 and xfce4-session-dusky:0.bak dusky is the name of my machine, so your files will have your machine name instead).
• These files have a number of lines, the majority of which are grouped with the prefix Client0, Client1, etc., so I looked for the groups with an entry for CloneCommand of nm-applet and removed the groups.
• I then had to renumber the Client groups so they were consecutive again starting at 0 and amend the Count entry towards the end of the file to match the number of groups I had (so one more than the last number used, remembering that you started at 0!).
5. After the editing I could perform a reboot to confirm that all was well. I actually did a few of these, firstly with the Save session for future logins disabled to ensure that any cache information was completely clear. Next was another with the session disabled, just to be sure, and then one with
   it enabled again.

All now appears fine with just a single nm-applet on my panel.

[1] https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/95064
[2] http://ubuntuforums.org/archive/index.php/t-191708.html
[3] http://www.nabble.com/Multiple-Instances-of-nm-applet-t4114321.html