One of the big changes (besides window button placement, another facepalm that I won’t even get in to) in Lucid is the introduction of the new Indicator area. This area is supposed to merge and standardize various icons from the system tray (system tray: an area of the taskbar where various applications can place status and function icons) into an area on the taskbar where various applications can place status and function icons. Brilliant!

The first bit of joy is the messaging menu, a small envelope. It merges email, instant messaging, and social garbage like Twitter into a single clickable menu. But of course since this is Ubuntu, it only supports one email client, Evolution, and one instant messenger, Empathy. Both of which are pure shit. (Update: Shawn in the comments informs me that Pidgin is compatible with the messaging menu.) At least Evolution has the decency to be fairly stable; Empathy is still a half-baked piece of junk that doesn’t deserve the label of Beta. I’m assuming Gwibber is the only client Ubuntu supports for the social aspect, but I’m not interested in broadcasting my latest dump on Twitter, so I didn’t bother setting Gwibber up. But we’re not talking about the applications themselves, just the indicator, so let me get back on track.

Back in the halcyon days of yore, I had one icon for Pidgin and one icon for Thunderbird in my system tray. You would left click on either one of those to restore the windows; closing the windows would return them to the tray. Pidgin changed icons when I had a message waiting, and Thunderbird showed me the number of unread mails in my account. I could tell whether or not I had an IM queued or new mail, and a single click would open the right window so that I could get on top of it. Pure bliss.

Now, there’s a single envelope to tell me whether I have a new IM, mail message, Twitter trackback, or whatever. Which one do I have? Fuck me, I have no idea. It’s just a green envelope. How do I find out? I have to click the envelope to open a menu, scan the menu, and figure out what’s waiting for me. Then I have to click again to open the right application. We’ve moved from two clear icons that clearly represent the state of two different applications, and behave consistently when left-clicked, to a single icon that represents many applications, and whose state is unclear unless the user refocuses their attention and clicks on it to open a menu to read, then clicks again to open the right app. Brilliant job guys! Way to reduce the number of clicks and attention shifts I have to do to understand the state of my system! Oh, and too bad Evolution doesn’t minimize to the tray on close–you have to have it open in your taskbar at all times if you want to have your mail checked.

I don’t use Rhythmbox, because it’s terrible. I use Banshee, a far superior program. Banshee has it’s own plugin for the indicator applet. The old Banshee tray icon behaved this way: single left click opens Banshee (just like a single left click opens every single app in my system tray), hover shows you what’s playing, and right click opens a context menu with some handy options. Perfect.

The indicator applet for Banshee does this: left click opens a context menu with far fewer options. Right click opens the panel options menu (remove indicator applet from panel, lock to panel, etc.). Hover does nothing. To open the Banshee window I have to click twice. I can no longer tell what song is currently playing without opening the Banshee window. I still have an icon at the top of my screen, but now it’s called an indicator instead of a tray icon. How is this more clear or more useful? More to the point, HOW IS THIS DIFFERENT FROM THE REGULAR TRAY ICON, BESIDES IT SUCKING WAY MORE?

It’s not different. In his blind zeal, Shuttleworth has unwittingly re-created the system tray under the guise of “shiny,” “new,” “usable,” and “consistent.” Unfortunately for us, “usability” and “consistancy” aren’t the result.

The old system tray was consistent. It had a clear HIG from Gnome that all the Gnome apps I use adhere to. Deluge, Transmission, Thunderbird, Banshee, Dropbox, Pidgin, Empathy–all of these apps open on left click, menu on right click, and info on hover. There is no ambiguity. THE SYSTEM TRAY WAS ALREADY CONSISTENT. Now, the indicator app does many things: left-click on Banshee to open a menu. Left click on the envelope to open a list of apps. Left click on Volume to open a volume bar. Left click on Battery to tell you that it’s charged. The indicator app is actually LESS consistent than the system tray. And it’s still a bunch of icons at the top of the screen. Way to lead the revolution, guys.

Today I had a near-disaster. I was at a coffee shop doing a little work. The software updater came up showing there some updates available, including a kernel update. I said OK, let it do its thing, and dismissed a message telling me to restart because I had some work open. An hour or two later, I shut the laptop lid, stashed it in my laptop sleeve, and went home.

Unfortunately for me, I forgot that I had to do a restart. I have my laptop set to hibernate when the lid is shut. But apparently, when a restart is required in Ubuntu, your system will restart come hell or high water–and that’s just what it did instead of hibernating, zipped up nice and snug in my neoprene laptop sleeve.

In case you haven’t heard of neoprene, it’s the material that wetsuits are made of: water resistant and able to keep a body warm while surrounded in freezing waters. They’re made to retain heat. Needless to say, they retain heat pretty damn well when there’s a running laptop zipped inside. A few hours later, I went to get my laptop out of the bag. My bag was pretty warm, and I instantly realized what had happened. I scrambled to pull the laptop out of the neoprene oven—my bag stank of burning plastic and the laptop was so hot I couldn’t hold it. Sure that it been damaged, I turned it off and put it under a floor fan to cool down.

Not only did it cool down in a few minutes, but it emerged unscathed from the neoprene oven. Everything is working perfectly. I’ve carried this laptop around the world in all sorts of environments, and it’s still alive.

There’s no stupid media keys, there’s 2 USB ports on either side for easy accessibility, there’s a Home button that I map to my home folder, the keyboard is responsive and the touchpad buttons are satisfyingly clicky. The screen is matte so I can use it in the sun. In short, I love this laptop.

Ubuntu, on the other hand, can go fuck itself for restarting when I told it to hibernate. At the very least it could have just shut down completely.

Update: this doesn’t appear to solve the problem 100%, but I am experiencing it much less often.

Enhancing my love/hate relationship (towards the ‘hate’ side) with Ubuntu is a nasty audio glitch introduced in Karmic for some Intel sound cards. Different people describe it differently: I’ve heard it described as random ‘popping,’ but my symptom is more like ‘laptop randomly starts sounding like a garbage disposal until you run $>killall pulseaudio’. I’ll be listening to an MP3 through Banshee, and randomly when it goes to the next track, every subsequent sound will sound like a train wreck until I kill the pulseaudio process. Some MP3s are more consistent than others with this problem.

Either way, I’ve found a potential fix for this problem. Here goes:

1. Open the ALSA configuration file using GEdit as root from the terminal:

   user@computer:$ gksudo gedit /etc/modprobe.d/alsa-base.conf
   

2. At the very end, you should find a line that looks like this:

   # Power down HDA controllers after 10 idle seconds
   options snd-hda-intel power_save=10 power_save_controller=N

   You want to comment out the line starting with ‘options,’ so that it looks like this:

   # Power down HDA controllers after 10 idle seconds
   #options snd-hda-intel power_save=10 power_save_controller=N

3. Save the file and restart Pulseaudio by running:

   user@computer:$ killall pulseaudio
   

That should solve your sound problems.

Back in the pre-Karmic days (or, the good ole’ days, as I call them) you could turn your laptop screen off by issuing this simple command:

I had a nice script set up and mapped to a keyboard shortcut to turn my screen off whenever I wanted (say if I was using my laptop to play music and wanted to save some battery life). In Karmic, however, a regression causes this command to turn your screen off only briefly. After a few seconds, your screen will turn back on, on its own. This might be an Intel-specific problem—I have the misfortune of having an Intel video card on my Ubuntu install—but I’m not sure.

To get around this problem, I created a slightly different (and slightly less ideal) script that turns the screen off when a shortcut key is pressed, and then turns it back on after they same key is pressed again. Here’s how to get it for your own laptop:

1. Create a new file using Nano. I put it in a directory called .scripts, you can put it wherever you like:
   user@computer:$ nano ~/.scripts/screen-off
   
2. Paste the following into your new file using ctrl+shift+v:
   #!/bin/bash
   screenOffLockFile=/tmp/screen-off-lock

   if [ -f $screenOffLockFile ];
   then
           rm $screenOffLockFile
   else
           touch $screenOffLockFile
           sleep .5
           while [ -f  $screenOffLockFile ]
           do
                   xset dpms force off
                   sleep 2
           done
           xset dpms force on
   fi

   (An explanation follows). Press ctrl+x to quit Nano, then y to save your script.

3. Make the script executable:
   user@computer:$ chmod u+x ~/.scripts/screen-off
   
4. Open the System menu, go to Preferences, then Keyboard Shortcuts (or press alt+f2) and run gnome-keybinding-properties.
5. Click Add, enter ‘Turn Off Screen’ under Name and ‘~/.scripts/screen-off’ (without quotes) under Command.
6. After you’ve added the command, it will appear under the Custom Shortcuts header. Click on your new command to assign it a shortcut key of your choice (I use ctrl+alt+shift+s).

And that’s it. Press your shortcut key to turn your screen off, and press the shortcut key again to turn it back on.

What the script does

When you first press the shortcut key with your screen on, the script will check if there’s a certain file in your /tmp/ directory. If it doesn’t find it, it will create it and then enter an infinite loop that turns your screen off every 2 seconds if the special file still exists (thus working around Karmic’s regression). When you press the shortcut key with your screen already off, it will delete the file and do nothing else, causing the first instance of the script to exit its infinite loop (since it no longer sees the special file) and turn your screen back on again.

It’s as simple as that. It’s not as ideal as the pre-Karmic solution, but it’ll have to do until Canonical QA gets their act together.

After a clean install of Ubuntu Karmic on my plain vanilla Dell Vostro 1400 laptop, I found that (as usual) a lot of stuff that used to work fine in Jaunty has broken in Karmic:

1. My Broadcom wireless card is completely unrecognized. Hardy was polite enough to recognize it but let me know that there were no drivers. Intrepid recognized it and automatically installed the right drivers. So did Jaunty. Karmic, however, just plain old doesn’t see it. Not even in lspci.
2. Resume from Hibernate hard crashes about half the time.
3. The Firefox spell check dictionary defaults to en_AU instead of en_US. This is great if you live in Australia, but I happen to be from California.
4. The famous IPv6 issues. DNS lookups take forever unless I specify a DNS server to use. With all of my traveling, the last thing I want to be doing is setting the DNS server for every single new wireless connection I encounter.
5. I use a script to turn off my laptop’s screen when I want to save power (say if I’m playing music for a group at a hostel). I’ve mapped this short but handy script to ctrl+alt+shift+s:
   #!/bin/bash
   #turn the screen off after half a second.
   sleep .5 && xset dpms force off

   This used to work like a dream in previous distros. Now the screen turns off, but turns back on after a few seconds.

6. My Intel GM965 (heinously borked in Jaunty, see this lovely section in the Jaunty release notes) now works at least, but with horrible slowness. Key presses and mouse clicks register slowly, there’s tearing when scrolling in any application, and things are generally dog slow. And I’m not the only one with this problem.

Come on, Canonical. How do you expect to be taken seriously when the OS you release next to Windows 7 has so many shamefully amateur problems? I can guarantee you that Windows 7 can at least resume from fucking hibernate and perform a fucking DNS request.

The thing that really pisses me off is that for a lot of these issues, we won’t be seeing a fix for another 6 months. That’s the pain of the fast release cycle: no time to do QA, so beta-quality software gets shipped. But no time to fix the problems, because to make the next release by the deadline, they have to start work yesterday.

Year of the Linux desktop? I’m not holding my breath.

Apparently Intel, in all of their brilliance, have decided that people using Ubuntu (and Linux in general) on laptops with an Intel wireless card simply must know when data is being transferred over wireless. It is of such paramount importance that you know this that Intel has decided to alert you by constantly blinking the wifi LED whenever data is being transferred. I think every other wireless card on the planet just has a solid LED light to indicate the wireless is on (or off, using the physical switch), but no, that’s not good enough for Intel. (Can you guess that the blinking light really annoys me?)

There’s no easy-to-find setting to change the LED to solid. But there is a solution: create a little script to change the LED to solid whenever you connect to a new wireless network. It’s pretty easy to do, too. Here we go:

1. Create a new file using Nano:
   user@computer:$ sudo nano /etc/network/if-up.d/wifi-led-noblink
   
2. Paste the following into your new file using ctrl+shift+v:
   #!/bin/sh
   #this script will prevent the wifi light from blinking when on.
   #to activate this script, create a soft link to it in /etc/network/if-up.d/
   echo none > /sys/class/leds/iwl-phy0::RX/trigger
   echo none > /sys/class/leds/iwl-phy0::TX/trigger
   echo none > /sys/class/leds/iwl-phy0::radio/trigger
   echo none > /sys/class/leds/iwl-phy0::assoc/trigger

   Press ctrl+x to quit Nano, then y to save your script.

3. Make the script executable:
   user@computer:$ sudo chmod u+x /etc/network/if-up.d/wifi-led-noblink
   

That’s it! Next time you connect to a network, your wifi LED should remain solid. This works in Karmic. And next time you find yourself cursing the guys at Intel, just remember: at least you don’t have a Broadcom wireless card!

2010-07-21 Update!

As of kernel 2.6.34 this solution no longer works for me. However, commenter DM has suggested an alternative that does seem to work again.

1. Create a new file using Nano:
   user@computer:$ sudo nano /etc/modprobe.d/wlan.conf
   
2. Paste the following into your new file using ctrl+shift+v:
   #1 means do not blink
   options iwlcore led_mode=1

   Press ctrl+x to quit Nano, then y to save your script.

3. Restart your laptop.

This different solution should work if the above solution doesn’t.