Getting Firefox backspace work on Ubuntu

For some like me who love the keyboard, more than mouse at times, Firefox on Ubuntu could get a little irritating to navigate between already surfed pages. On WinDoze, Firefox by default allows backspace to take you back to last visited page (while shift+backspace takes you one page forward). Of course, this is only with default settings and mostly everything is customizable. However, being the lazy me, I didn't do anything about it thus far.

Today, I did the following simple change to get it working and it didn't even need a browser-restart :)

i) Go to about:config by typing the same in the URL.
ii) Promise to be careful with it :)
iii) Type backspace in the filter-bar.
iv) Change the value of browser.backspace_action to 0 (by default, its 2)

You're done. No need to close the browser. Just press backspace and go back to where you left off before irritating yourself because backspace didn't work! ;)

Firefox Shiretoko

Firefox 3.5, code-named Shiretoko, has a brand new feature called private browsing. Its very useful if you share the laptop with some visitors every now and then, but not often enough for them to have a Firefox profile.

This feature, as some might think, is not proxy-browsing which hides and translates your IP into something else. Its also not really a setting which deletes all your history, cache and cookies when you close the browser. Its some of it and a little more. With Shiretoko, you can privately browse while keeping your old tabs intact. So if your friend drops by and wants to check his mail on your laptop, you just give him private browsing, without actually logging out of your mail and other accounts, while he gets a clean browser and leaves it clean too. Shiretoko continues just where you left off when he's done browsing privately!

Matrix in Windows!

You've to watch this if you liked Matrix and/ or like Ubuntu and/ or dislike Windoze: "Ubuntu. I'm going to learn Ubuntu".

Epson TX101 installation

Update, Jaunty onwards: Epson has a new release with libtdl7 support. Try that first instead of wasting your time doing the following. The following works only for Intrepid 8.10 and perhaps, Hardy 8.04 release with an Epson driver for libtdl3.

(In case you hit this page to find how-to install, skip blabber, jump straight to end of this weblog for stepwise instructions)

I bought Epson TX101 printer-scanner-copier a few days back and was waiting for the Epson chap to install it due to warranty issues that the seller told me of. Needless to say, when he turned up yesterday, not only didn't he know Ubuntu installation, but he hadn't even heard Ubuntu or Linux for that matter! He did some basic Vista install and looking at his "expertise", I had to ask him to just make the installation report and leave.

My efforts on getting it to work on Ubuntu took long U-turns due to my stupidity. First of all, I tried things yesterday night when I was barely keeping myself awake on the chair! Back to technicality, I tried gutenprint, iscan, xsane, CUPS and pips, when things didn't work by default when I plugged in the USB. Of course, I made the mistake of typing in xane instead of xsane earlier on. But today, I started afresh when iscan install cried for libltdll3 in the night! Later I found out that iscan was (perhaps) installed by default on Kubuntu, with a dependency error; same thing as libltld3.

Intrepid, possibly Hardy too, uses libltdl7. So a simple fix is to make a soft link to libltdl3 and I should have been on the way, but it didn't work. It needed a simple replug of USB cable and not only iscan, xsane worked too!

Steps:

1. Download the correct package from http://www.avasys.jp/lx-bin2/linux_e/spc/DL1.do.
2. Make sure you have sane and sane utils installed. Use sudo synaptic to find out.
3. Also make sure you have libltdl7. (Of course, you can't get a libltdl3! :) )
   
4. Install Image Scan and Print system by running sudo dpkg -i --ignore-depends=libltdl3 iscan_2.17.0-3_i386.deb (or whatever the name/version is).
5. Do a sudo find / -name libltdl.so.7. cd there. (Of course, one level higher!!!)
   
6. Create soft link by ln -s libltdl.so.7 libltdl.so.3.
7. For some reason (read above blabber), I did the following too. Do it if you need to.
   
8. Do a sudo find / -name libltdl7. cd there. (Of course, one level higher!!!)
   
9. Create soft link by ln -s libltdl7 libldtl3
10. Create soft link by ln -s libltdl7 libldtl3-dev
11. Plug-out (if plugged in) and plug-in the TX101 USB cable. I didn't do this and wasted a lot of time finding out why iscan and/ or xsane wasn't working. Both were needing me to replug the TX101!
12. You're done.
13. Test printer: Go to http://localhost:631 for CUPS, check if you've the printer right. Do a test print. You'll get the print below.
14. Test scanner: Open iscan or xsane. Scan works as below. :)

Intrepid Ibex on laptop

I've managed to get to Kubuntu on my Toshiba laptop, downloading a wubi based install throughout the day yesterday. Kubuntu kept me awake nearly till 0200 with its vibrant GUI and new apps. I was trying to get all work at once, but succeeded with some till sleep took over.

This morning, I found out that although I got the latest version 8.10 running, I've stumbled upon a non-LTS (Long Term Support) release post Hardy Heron 8.04. The next LTS release is Kubuntu 9.10 way ahead in Oct 2009, while another non-LTS Jaunty Jackalope is scheduled for April 2009.

A few days back, I made a wubi shift on my 64-bit dualcore AMD Anthlon XP2 desktop too, of course on NTFS now, but intend to make it a pure ext3 Linux machine. I want to continue shuffling WinDoze Vista for a while on the laptop alongside Kubuntu, just because I was forced to buy it in the laptop price! ;)

Why's Ubuntu special?

Ubuntu's very special due to simplicity, and absolute simplicity at that, has 32/ 64 bit versions, support for almost all the devices/ peripherals and speedy fixes. But I've a single reason above all those reasons. Its based on the best of the distributions: Debian. I'm not sure I'm loud and clear here, so I'll go on...

Debian was once the most complicated installation, with hardly any other flavor than the German. Its installation was in German, all docs, everything. Not many could install it back then and therefore, very few got to use it. It was still the best distribution then. What is interesting to note is that the makers of Ubuntu built on Debian, the best distribution available then, available in the least user-friendly way and turned it the most user-friendly distribution without messing up the best things.

Whats more, you get to pick between plain vanilla Ubuntu with Gnome, Kubuntu with KDE, Xubuntu which is packaged for speed, Edubuntu for education and Gobuntu thats totally GNU/ FSF!

Not BSNL, Vista blues!

One thing about blogging about Linux is that it contrasts against Microsoft way of doing things. That is, Linux does things in a standard way but Microsoft keeps on contradicting itself.

Now, this one is about setting up the BSNL provided router to let wired access for PC and wireless access for laptop. I suspected BSNL and/ or UTStarcom's stupid router to be the culprit when I'd trouble with DHCP. (I did mention that I moved my PC to Ubuntu yesterday, but I'm still stuck on Vista for my laptop). The wireless adapter on the laptop wasn't getting a DHCP IP 192.168.1.x and somehow got some funny IP 169.254.205.173! Ergo, no LAN or WAN access. Instead, I'd to force a static IP on the laptop to access the router settings, force it to bridge mode and then dial up PPPoE from laptop! This pathetic setting would also mean that I can use either the laptop or the PC, basically one client at a time and also means on-demand connection from that client! I tried almost every setting with the router, including adding MAC filter for wireless access, but made no progress.

I knew there was something fishy about DHCP but didn't know what. So I began on that thread of thinking: why the hell does Vista get me a nonsense IP? Whats 169.254.205.173? Then I searched online on network classes to find that this is a fallback IP if everything else fails! How can DHCP fail for wireless/ Vista and still work for wired/ XP or wired/ Ubuntu? It turns out Vista was the culprit here with the wireless adapter not getting DHCP, it was falling back on 169.254.205.173 which was its autoconfiguration IP, a zeroconfig! More search online led to http://support.microsoft.com/kb/928233 which says "Windows Vista cannot obtain an IP address from certain routers or from certain non-Microsoft DHCP servers"... hmm, interesting, very interesting, note the words "non-Microsoft". What do you mean non-MS DHCP servers? Shouldn't you be saying Vista is non-DHCP OS in some way instead? Be as it may. :) The MS suggested solution is to add a DWORD32 DhcpConnEnableBcastFlagToggle flag set to 1 under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{GUID} where GUID is the network adapter that you want to Vistafy or Vis**-up! :)

I blog this only as a reference for some or even me if I go mad to come back and use Vista ever again. This might work for some, it didn't work for me. But taking hint from the MS article, I'd to finger wireless network properties to "connect even if the network is not broadcasting". This worked, yes! I got a clean DHCP IP and things seem good.