Give Firefox Fangs

Fangs logo

Fangs is a Firefox extension that presents a web page in a manner similar to how it would be read by a screen reader. I’m not an accessibility guru, nor am I and accessibility geek. I try to hit the high points of accessibility like employing skip navigation, alt tags, meaningful link text, etc. when I build sites, but at the same time I have to confess that I’ve never dug much deeper than that. As far as I can tell, Fangs doesn’t offer much in the way of education, but what I really like is that it provides another way of visualizing the structure of my content. Moreover, it’s a practical visualization since it emulates the way a screen reader will read that content rather than some kind of basic block diagram.

Although, my impression so far is that Fangs doesn’t offer much in the way of accessibility information or evaluation, there are some hints about how to effectively use Fang on the FAQ. Even with limited use so far, I’ve seen enough to know that there’s a place in my development toolbox for this extension.

Make Linux Just a Little Sexier

Granted, I’m a Mac user, at least at home, but I like to think I’m not a total fanboy. When I moved to Linux at work and began customizing my machine, I saw countless recipes with instructions for skinning Linux to look like a Mac (or maybe there’s just one and everyone in the free world is linking to it). I don’t get that. Linux isn’t a Mac. A penguin in a tux is still a penguin, right? The fact is, I like my operating systems to look like what they are and, besides, I’ve never had much luck with Linux themes. There’s always something that gets left out and kind of ruins the whole effect.

The honest truth is, I kind of like the Linux aesthetic. Most of it, anyway. I’m not, however, a fan of the default fonts and I thought that installing Mac fonts might be just the thing to dress up the penguin without overdoing it. Turns out that they are.

Try it. Here are my settings:

My Ubuntu font settings

Fix Title Bar Issues in Ubuntu 8.10 (Intrepid Ibex)

Towards the end of November, I upgraded (read: completely rebuilt) my Linux partition from 8.04 (Hardy Heron) to 8.10 (Intrepid Ibex). I’ll have more to say about the latter in a future post, but after the upgrade I was immediately faced with two problems. One, the inability to establish a VPN connection, that was critical to my ability to use this as my primary work computer and the second, an issue with my title bars that, though extremely annoying, was really just aesthetic.

The solution to the VPN issue is detailed in an earlier post and today I finally got around to fixing the title bar issue. It took me a while because, though the solution itself is relatively simple, I had a lot of trouble finding the entire solution in one place. Thus, the birth of this post.

The Problem

They say that a picture is worth a thousand words, but unfortunately I neglected to take a screenshot before fixing the problem. Nonetheless, I’ll try to keep my description well under a thousand words.

Frequently and inconsistently, my active title bar would go grey and the appearance would fracture. I don’t know how to describe it any better except to say that if Picasso himself had painted a title bar in shades of grey, it would have probably looked much like mine. Cubist, indeed.

The problem, in a nutshell, is with the NVIDIA video driver. If you don’t have an NVIDIA video driver, you probably don’t have this problem. Intrepid Ibex ships with three proprietary NVIDIA driver versions: 96, 173 and 177. I don’t remember which was installed by default, but I encourage you to trust me when I say that not one of them worked.

The Solution

First, of course, you need the right driver. I read somewhere that version 180.06 worked as expected so that’s the one I downloaded. I’ll save you the suspense and tell you that this version did work for me. It can be downloaded from the NVIDIA site, but be sure to select the 32 bit or 64 bit version, as appropriate. I downloaded it to my desktop. Once you have the appropriate driver:

  1. Close everything except for a terminal window. I do mean everything because you’re about to stop the X Windows process.
  2. In the terminal window, type sudo killall gdm and hit Enter.
  3. Once the screen goes black, hit Ctrl+Alt+F1 to switch to a new terminal.
  4. You should see a terminal prompt so switch to the directory where you downloaded the driver file. My command was cd ~/Desktop.
  5. It may be sufficient to just use sudo here, but just to be sure, I dropped into a root shell by typing sudo -s and hitting Enter.
  6. Execute the driver file. If you didn’t rename the file, the terminal command should look something like this: ./NVIDIA-Linux-x86_64-180.06-pkg2.run.
  7. Follow the prompts through the installation process. You may see some scary messages about the driver having “no precompiled kernel interface”, but allow the install to do what it needs to do (it’ll ask to check for one and, failing that, it will ask to compile its own). I let it go about its business and had no problems at all.
  8. Once the install is complete, you can probably just type startx and hit Enter, but again, I wanted to be really, really sure, so I did a full reboot. If you used sudo -s as I did and choose to simply restart X, I’d recommend logging out of the root shell first or else you’ll start X as root.

That’s all there is to it. So far, everything looks good, but I have noticed one thing that looks odd to me:

Ubuntu Hardware Drivers Window

Seems Ubuntu thinks I’m still using version 177. As I said in my last post, Ubuntu is pretty solid, but not everything “just works”.

Dropbox is Smart

Rands in Repose on just what makes Dropbox so special:

The magic of Dropbox is that it doesn’t ask you to think about what you do. You care about one thing: do I have access to the most recent version of my files? And with Dropbox, yes, you do. Wherever you are, so are your files.

I’ve been espousing Dropbox for a while now, but this is a well-articulated macro view.

Intrepid Ibex VPN Connection Fails

At the end of last week, I performed an upgrade from Ubuntu 8.04 (Hardy Heron) to 8.10 (Intrepid Ibex). Although it’s not really part of this story, I should specify that I tried to perform an upgrade. The upgrade was so catastrophically botched somehow, that it ended up being a complete repartitioning of my work laptop. Nonetheless, over the weekend I got back to a reasonable level of stability and productivity except that I was completely unable to connect to my office VPN.

Evidently this is a pretty well-reported bug affecting a number of folks. My attempts to connect to VPN “out of the box” were greeted with a complaint that “no valid VPN secrets were found.” A number of folks reported success if they simply removed their password from the configuration dialog, but that didn’t work for me. After doing so, I got a spectacularly unhelpful message that my “Connection to [my network] failed.” Super. Thanks for playing.

I spent hours searching and trying various “solutions” before finally stumbling on a clearly articulated set of instructions that worked. They did, however, require updated network-manager packages. In case I ever have to do this again, I don’t want to spend those same hours, so I’m going to try to document the steps I took so I can reflect on them later. Maybe they’ll help someone else too.

To get those add the following source to /etc/apt/sources.list:

deb http://ppa.launchpad.net/network-manager/ubuntu intrepid main

Once done, update:

$ sudo apt-get update

Once updated, system updates should be reported and they should include network-manager and network-manager-pptp. Those need to be installed. Once everything is installed, these instructions should finish the job and provide a working VPN connection.

Ubuntu is pretty solid, but not everything “just works”. Quite.