MySQL headache of the day

When using mysqldump with the --tab option, triggers for the table you're dumping get printed to stdout instead of the {TABLE}.sql file. Oh Joy!

Rockband

and Here Comes Spring

We can now see the ground in a few spots in the backyard!
And we're getting all sorts of delicious veggies ready to stick in it soon!

Here Comes Hardy

gears on the n810??!?

finally! (via this) (just found this, ill post how it goes after i get it going...)

maemo-mapper and google

So I've been using maemo-mapper to record tracks when we've been showshoeing and cross-country skiing the last couple of weekends. I was hoping I'd be able to do something fun with them eventually. Tonight, I finally sat down to see what I could do. I installed google earth (which, the Linux version seems to have a memory leak or something because it starts out running ok, but gets slower and slower till its unusable and I have to kill it), and tried just opening the track file from mapper. No such luck, it seemed to just silently fail. A couple google's later, and I found gpsbabel, a  nice little app that can speak many forms of gps. Low and behold, it's even in ubuntus repos! So, apt-get install gpsbabel and then "gpsbabel -i gpx -f trackfile -o kml -F kmlfile". Bam. Now I opened the kml file with google earth and there was my track. Thanks for your help, open source!

On a related note, I had been using a crappy workaround to get maemo-mapper to work with the internal bt on the n810. I had been starting the built in map software, which started the gps, then starting mapper and leaving the other map running. I read on the maemo-mapper forum that with the newest version, you can just set it to the bluetooth gps setting and leave it blank, restart it, and it will work. Sure enough, now I can use it without starting the other gps. Which is nice. Nice. 

Changing your password on the Gnome Keyring

So I noticed this annoying bug in Gutsy where when you change your password, gnome-keyring starts prompting you for a password, and you have to put your old one in there to satisfy it. I believe this is because what happens is, when you setup your account, Ubuntu sets the password on the keyring to be the same as your login password and sets up pam to try your login password on the keyring. This makes things nice and smooth when your account is new. If, however, you change your password (say, because you were using synergy and not paying attention and accidently typed it into an IRC channel...), your login password no longer satisfys the keyring, which is still set to your old password. So, this is an improvement, because you used to *always* have to put in your password, but its kind of half-assed.  (Now, maybe I changed my password from the command line, rather then through the gui (is there a change password gui? probably), and maybe the gui would have changed the keyring password and kept everything solid, I don't know).  

Anyways, this wasn't a show stopper, just a small annoyance, so I let it ride for a while, and just put my old password in whenever I logged in and connected to a private network. Then I got sick enough of it to poke around. I found this bug. I installed  seahorse ( sudo apt-get install seahorse ), ran it (shows up in Accessories and its called "Passwords and Encryption Keys"), went to Edit->Preferences, hit up the GNOME Keyring tab, and voila! theres the change password dialoge for the keyring. I set it to my new passwords and things are right again. 

Edit, woops, someone else already figured this out, with illustrations!