One of my all-time most popular posts was how to upgrade to Firefox 3.5 in Ubuntu 9.04. Now it’s Firefox 3.6’s turn to be installed on my system that is now running Ubuntu 9.10.

The team working on Firefox have put a ton of effort into this release and, in order to make our browsing lives safer and faster, rolled a number of features scheduled for 3.7 into this release. Thanks for all the hard work guys.

Read the 3.6 release announcement for details about what is new with this release.

So now onto the installation. Here are the commands that I ran in terminal to install 3.6.

[chris@rommie ~]$ cd /tmp/
[chris@rommie /tmp]$ wget "http://download.mozilla.org/?product=firefox-3.6&os=linux〈=en-US"
--2010-01-21 11:41:08--  http://download.mozilla.org/?product=firefox-3.6&os=linux〈=en-US
Resolving download.mozilla.org... 63.245.209.58
Connecting to download.mozilla.org|63.245.209.58|:80... connected.
...

100%[=============================>] 10,161,471   924K/s   in 11s     

2010-01-21 11:41:20 (899 KB/s) - `firefox-3.6.tar.bz2' saved [10161471/10161471]

[chris@rommie /tmp]$ tar xvjf firefox-*.bz2
tar: Record size = 8 blocks
firefox/
firefox/update.locale
firefox/plugins/
firefox/plugins/libnullplugin.so
...
firefox/defaults/autoconfig/platform.js
firefox/defaults/autoconfig/prefcalls.js
firefox/libmozjs.so
[chris@rommie /tmp]$ sudo cp -r firefox /usr/lib/firefox-3.6
[sudo] password for chris:
[chris@rommie /tmp]$ sudo mv /usr/bin/firefox /usr/bin/firefox.old
[chris@rommie /tmp]$ sudo ln -s /usr/lib/firefox-3.6/firefox /usr/bin/firefox-3.6
[chris@rommie /tmp]$ sudo ln -s /usr/bin/firefox-3.6 /usr/bin/firefox

Simply run each command listed in white in your terminal to upgrade your system with the latest release version of Firefox.

After running these commands, close out Firefox, wait a few seconds to let everything shut down properly, and run Firefox again. If all the steps were executed properly and without error, you should be running 3.6. You can click Help > About Mozilla Firefox to confirm.

Happy browsing.

My dual monitor setup didn’t work properly in Ubuntu 9.04, Jaunty Jackalope. Fortunately, it does work properly in 9.10, Karmic Kaola. However, this newfound dual monitor setup has given me a new problem: how do I move my panels to the secondary monitor?

My office machine is a laptop. When I get in the office, I hook it up to a 24″ LCD. I’d like to use this external monitor as the primary, which means that I definitely want to have my panels display on it. However, as much as I tried to drag the panels around or play around with settings, there just didn’t seem to be a way to get them over there. However, I just figured it out.

By default, panels are set to expand. This means that the panels will span the entire width or height of the section of the window they occupy. If the expand option is disabled, they turn into self-sizing bar that can be dragged to different edges or centered.

Having the expand option disabled also allows you to grab and edge of the panel and drag it to another screen. Once on the screen you want it on, simply re-enable the expand option and you now have the panel on another screen.

Here’s a step-by-step way of moving a panel to another screen:

1. Right-click the panel you wish to move and select “Properties”.
2. Uncheck the “Expand” option under the “General” tab.
3. Grab one of the edges of the panel by clicking on the left or right end (top or bottom end for vertical panels).
4. Drag the bar to the desired screen and position.
5. Check the “Expand” option in the “Panel Properties” window and click “Close”.

PEAR is PHP’s equivalent of Perl’s CPAN. It offers hundreds of ready-to-use code modules that can make projects go much more quickly than having to hand code everything. However, it never seems like PEAR is easy to get running.

Installing the Needed Software

In Ubuntu, installing the following packages will quickly get you started with PEAR: php5-cli, php5-dev, and php-pear.

Make sure that you read the next section about problems with using PEAR to install PEAR packages if you are running 9.10, Karmic Kaola.

Here’s an example of how to quickly install those packages from the terminal.

[chris@rommie ~]$ sudo apt-get install php5-cli php5-dev php-pear
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
autoconf autoconf2.13 automake automake1.4 autotools-dev libltdl-dev libssl-dev libtool m4 php5-common shtool zlib1g-dev
Suggested packages:
autobook autoconf-archive gnu-standards autoconf-doc gettext libtool-doc automaken gfortran fortran95-compiler gcj php5-suhosin
The following NEW packages will be installed:
autoconf autoconf2.13 automake automake1.4 autotools-dev libltdl-dev libssl-dev libtool m4 php-pear php5-cli php5-common php5-dev shtool zlib1g-dev
0 upgraded, 15 newly installed, 0 to remove and 5 not upgraded.
Need to get 0B/8,690kB of archives.
After this operation, 27.7MB of additional disk space will be used.
Do you want to continue [Y/n]? y
Selecting previously deselected package m4.
(Reading database ... 127272 files and directories currently installed.)
Unpacking m4 (from .../archives/m4_1.4.13-2_i386.deb) ...
...

With these packages, you are ready to roll with PHP and PEAR in Ubuntu.

Problem with Ubuntu 9.10 Karmic Kaola

A great thing about PEAR is that you can quickly install packages with a simple command. For example, “sudo pear install PHP_Parser-0.2.1″ will install the PHP_Parser package. However, this doesn’t work properly in Ubuntu 9.10, Karmic Kaola.

Output of the standard PEAR install command can be seen below:

[chris@rommie ~]$ sudo pear install PHP_Parser-0.2.1
downloading PHP_Parser-0.2.1.tgz ...
Starting to download PHP_Parser-0.2.1.tgz (70,782 bytes)
.................done: 70,782 bytes

While this doesn’t look wrong, it has actually failed. Rather than installing the package, it has simply downloaded the archive, encountered an unchecked error, and crashed. A successful installation has a message saying that the installation is successful.

This problem can be easily fixed by giving the install command the “-Z” option. For example:

[chris@rommie ~]$ sudo pear install -Z PHP_Parser-0.2.1
downloading PHP_Parser-0.2.1.tar ...
Starting to download PHP_Parser-0.2.1.tar (Unknown size)
.............................................................................done: 533,504 bytes
install ok: channel://pear.php.net/PHP_Parser-0.2.1

Notice the “install ok: …” portion of the message. That’s what you should see at the end of a successful installation.

For more details on this bug, please check out Bug #451314 on the Ubuntu bug tracker.

I just encountered an odd issue with Ubuntu 9.10, Karmic Kaola. I had music playing in the background, I adjusted the volume, and I noticed that there wasn’t any change in the volume level. Even maxing out the volume and muting it had no effect.

After wondering if the problem was that I went insane, I looked in Sound Preferences (right-click the volume icon and select Sound Preferences) and found that “RV635 Audio device [Radeon HD 3600 Series] Digital Stereo (HDMI)” was selected under the device output. This means that Ubuntu was trying to send audio over my HDMI connection rather than through my headphone jacks.

This wasn’t a problem last night, so it might be due to the fact that my external monitor at the office runs over the HDMI connection, so it automatically switched to the HDMI audio output. In one way, this is nice, in another way, it will frustrate me to no end if it does this every time I’m at the office. If I’m right that it automatically switched upon detecting an active HDMI connection, then wouldn’t it be better to make it easier to provide a notification on where to switch the audio output rather than just switching it and causing confusion?

Switching the option to “Internal Audio Analog Stereo” instantly fixed the problem.

Oddly enough, when I manually selected the HDMI output again, it muted the analog output. So, it seems that it may not be a complete switchover or possibly just a bug. I’ll continue to see how the situation plays out and make a Ubuntu bug report if necessary.

Ubuntu 9.10, Karmic Kaola, launched earlier this week. One of the key new features in this release is Ubuntu One. Unfortunately, from what I’ve seen, this new feature/product launch has been anything but smooth.

Ubuntu One is one of the new ways that Canonical, the creators of Ubuntu, is trying to generate some revenue based on their distro. Ubuntu One is a hosted file storage solution that allows users to keep a folder and all of its content synced between multiple computers. All users get 2GB of storage for free with the option of increasing the store to 50GB for $10/month.

Since this new offering has many Ubuntu users very excited, I thought I’d give it a try as soon as I installed the new release. However, I was instantly met with a very big message telling me that something was wrong.

Launch Day: Problem 1

When I first started Ubuntu One, the following notification appeared:

Capabilities Mismatch
There was a capabilities mismatch while attempting to connect to the Ubuntu One server. You may have installed a newer version of the client, for which the server does not yet provide support. A new version of the server should be accessible soon. Please be patient while we update.

Ubuntu is supposed to be a Linux distro designed for the average computer user. Since this large message appears for a short period of time and it isn’t easily understood, I think that this message could very easily give users a very bad first experience. I believe it would be much more simple to simply say the following:

Server Connection Failed
Please ensure that you have installed all software updates and try again at a later time.

The reason why I believe the software update portion should be included is because the problem wasn’t the server, it was the client. This morning my system told me some updates were available, and a few of these updates got rid of the “Capabilities Mismatch” problem and allowed the software to connect properly.

The packages that fixed this are the following:

• python-ubuntuone-client
• ubuntuone-client
• ubuntuone-client-gnome

Each of these were updated to version 1.0.2-0ubuntu2. After the update, I closed the Ubuntu One software, restarted it, and the folder sync worked as expected. However, this is when another problem became clear.

Houston, We Have a Problem… Again

There are two parts to the Ubuntu One system. The first is the server/client connection that actively syncs the Ubuntu One folder between the computer and the Ubuntu One server. The second is an online system you can access through the browser. This online system allows you to manage folders and files from inside your browser.

When I first started to play with Ubuntu One, even though the folder sync didn’t function, the web access system did. Using this method allowed me to get a feel for what Canonical was aiming to offer its users. As soon as the server/client issue was fixed, I decided to play around with syncing files and then looking at them on the online system. This is when I found Ubuntu One’s second problem.

Disappointingly, as soon as Ubuntu One’s client started to work properly, their online system failed. So, is this out of the kettle and into the fire?

Again, this failed in a manner that is difficult to understand. You set up a Ubuntu One account by using a Launchpad account. I went to one.ubuntu.com, the Ubuntu One site, clicked “Sign In”, input my login details, and was redirected to the home page again with no feedback message. So, I clicked “Sign In” again, and I was once again redirected back to the homepage. Seems like some authentication issues were going on between the Ubuntu One and Launchpad systems.

As with the previous issue, my problem isn’t how the system failed — I’m a programmer, I know how things can go wrong — it’s with the fact that no feedback was given to the user. It simply didn’t work.

Conclusion

As I finish up this post, I see that Ubuntu One’s online system is functional again. However, as I’ve tested this throughout the day, it seems like it was down for at least a few hours. Overall, this is not a bad downtime, but it does tarnish the launch.

To be frank, I feel a bit bad being so harsh to software and services that I am getting access to for free; however, as per Canonical’s own press release, they are extremely-focused on the user experience. As a user, I have to say that my experience with the new Ubuntu One service was less than good.

I know that Mark Shuttleworth, founder of Canonical, believes that Ubuntu can take on Microsoft’s Windows head on. I also believe that Ubuntu has this potential; however, launch experiences like this aren’t going to win any new fans. One of the biggest disappointments that many people have with Microsoft is that many of their products, Windows included, feel like they were rushed out of development just to get a release.

Considering that Ubuntu One and Ubuntu are both Canonical creations, it looks really bad when Canonical can’t even get their own products to work together properly.

I recently tutored a friend in C coding. Since I hadn’t worked with C in at least 8 years, I really needed to have some references to rely on for syntax and other specifics. Fortunately, there are some easy man pages that can be installed in Ubuntu that offer helpful information that I was able to use to help refresh my memory.

These man pages are easily installed by installing the manpages-dev package. You can install this package via Synaptic or directly on the command line. I like the command line method personally, so I ran sudo apt-get install manpages-dev from the command line to quickly install the package.

After installing the package, I’m able to access man pages for functions such as printf, opendir, and putc. For each function, it shows the valid syntax as well as what library is required to make use of the function.

The information isn’t limited to functions as you can also access information on the libraries, such as stdio or string.

To access any of this information, simply run man [function or library name] such as man stdio.

This package isn’t limited to C functions/libraries. It is a general use Linux development suite of man pages. For a full list of what is installed, check out the file list.

I had fun writing about how I work with Git yesterday. I thought I’d continue on that thread.

I have a solid set of code libraries that I’ve written that latch into the WordPress themes we produce at iThemes. Each time code is duplicated across different repositories, I break that code out and make it into a separate repository. I then link it back into the project as a submodule. This makes it extremely-easy to keep duplicated code across numerous repositories updated with little or no fuss.

After cloning a repository, simply run git submodule init followed by git submodule update in order to initialize all the submodules and update their container folder with the content of the submodule’s repository. For a long time, this is exactly what I did when I would clone a theme repository to start working on it. However, this quickly wasn’t enough.

The problem happened as soon as I added a submodule to a repository that was also a submodule of other repositories. Doing the submodule init and update process wouldn’t do everything I needed in this case as there would be submodules in some subfolder that haven’t been set up.

I didn’t want to get into a habit of always switching to other directories and doing the submodule processes there as well since I 1) knew that I would forget all-too-often, thus wasting my time, and 2) knew that this would not be the last time that a submodule had submodules. Heck, there is even the possibility that I’ll have a submodule that has a submodule that has a submodule. It was immediately clear that I needed a script to do all this dirty work for me. The rest of this post will be about the script I created.

The Script

First, I’ll share the script itself. If you are interested in how it works, continue reading.

git-submodule-recursive-update (right-click > “Save Link As…” to download)

The script is written in Perl and should work on most systems. I’ve only tested it on Linux and OS X, so please let me know your results if you try out on Windows.

#!/usr/bin/perl

use strict;
use Cwd;

init_and_update();

exit;

sub init_and_update
{
    my $start_path = cwd();

    my %paths;
    my $updated;

    do
    {
        my $data = `find . -name '.gitmodules'`;
        chomp($data);

        $data =~ s/\/\.gitmodules//g;

        foreach my $path (split(/\n/, $data))
        {
            $paths{$path} = '' if($paths{$path} eq '');
        }

        $updated = 0;

        foreach my $path (sort keys %paths)
        {
            if($paths{$path} eq '')
            {
                chdir($path);
                `git submodule init 2>&1`;
                `git submodule update 2>&1`;
                chdir($start_path);

                if($ARGV[0] eq '--remove-gitmodules')
                {
                    unlink("$path/.gitmodules");
                }

                $paths{$path} = 1;

                $updated++;
            }
        }
    } while($updated);
}

The Description

The functionality should look very straight-forward to anyone that knows Perl.

1. I store the current directory in the $start_path variable in order to always know where home is.
2. I start a wrapper loop that keeps running until all the possible submodules are initialized and updated.
3. Using the find command, I look for all the instances of .gitmodules and store the results in $data. The .gitmodules file exists if a repo has submodules.
4. I remove all the .gitmodules file references from the $data to leave just the paths.
5. I split the paths into an array and initialize the %paths hash to have a blank value for new paths (stored in the key). Setting this value to blank will flag the following loop that the submodules in that path have not been set up yet.
6. I create a tracker variable, $updated, to check if anything happened in the loop.
7. I then loop through the %paths hash to work on each path. If the path’s hash value is blank, I process that path.
8. I cd into the repo path, init and update the submodules, and switch back to the starting folder.
9. If the script is called with the optional --remove-gitmodules argument, I remove the .gitmodules folder while I’m focused on that folder. I use this for other automation scripts, so it may or may not be of value to you.
10. I then set the path’s hash value to 1 to flag it as done.
11. Closing out the loop, I update the $updated variable to show that something was updated in this pass.
12. Finishing up the do loop towards the top, I have while($updated). Basically, as long as something was updated in the core update loop, I’ll run everything again. This means that the loop will keep running until it didn’t find anything else that needed to be updated. When that point is reached, the main loop ends, and the script is finished.

I know that there are a number of things I could have done to make for a much more brief, compact script, but I was going to quick production with solid functionality, not brevity. In addition, there are unnecessary elements such as incrementing the $updated variable rather than just setting it to some value. I thought might want to know how many things were updated at some point, so I left it as a counter.

If you found this script helpful, please leave a comment. The more interest these Git-related posts receive, the more motivated I’ll be to share other processes, developments I’ve made to make working Git easier.

All of the WordPress themes that I work on for iThemes are managed as Git repositories. Recently, we moved past the 100 repositories mark. That’s a lot of repositories to manage, and unfortunately, too many of those repositories contain duplicated information.

Later on, I might delve into how we use Git to manage our theme repos. For today, however, I’d like to focus on how I quickly and easily pushed up changes to more than a dozen repos in a single, albeit long, Bash command.

I had finished making updates to 16 Flexx repos, and I needed to push all of those changes up. Since I had multiple working repos in that folder, I was lucky that each of these repos began with the text “Flexx”. Also, since they are all part of the same series and need to keep the same version number, that simplified the tagging as all could be tagged as 2.5.0.

Given this information, I simply ran the following command from the directory that contained all the repository directories:

There’s a lot going on here, so I’ll break it up and explain what I’m doing.

This is basically a compound command. Bash’s for command is being used to step through the results of ls|grep Flexx. Each result will be stored to the variable i which can be referred to with $i.

In other words, I’m going to loop through each directory that contains the text “Flexx” (technically, it isn’t limited to just directories, but I don’t have any files containing “Flexx”, so I’m safe). For each iteration of the loop, the variable $i will contain the name of the folder I’m interested in.

The most important bit here is do. do simply begins the functional part of the loop and could be followed by any command that I wanted to start the loop with.

The echo command isn’t technically necessary. I simply have it there so that I can better determine what output belongs to which repository.

This is a very important command. It changes the directory to the repository I wish to run commands on.

This is the command that actually does what I want to do in each repo directory. This adds all the modified files, commits them with a message of “2.5.0″, pushes the changes to the remote repository, creates a new tag of 2.5.0, and pushes up the new tag.

I have all of these commands chained together with && so that if one command fails, the other ones won’t run. This prevents tagging in the event that the repository couldn’t be committed or pushed.

It’s a small command but necessary. This switches back to the main directory that holds all the repos, thus returning us back to a state that the next loop iteration can work with.

As with the other echo command, this simply allows me to keep track of what is going on more easily.

The done command finishes out the loop iteration.

I hope that by sharing this you can gain a bit of insight into how I work with repositories while also learning more about how you can do things with Bash.

In Linux, clicking the middle mouse button (or mouse wheel) pastes the most recently highlighted text from any application. This is useful; however, it has an extremely-annoying side-effect in Firefox. Whenever I middle-click outside of entry fields, I get an annoying pop-up that says: “The URL is not valid and cannot be loaded.” This frustrates me to no end. It usually happens when I accidentally nudge my mouse and miss middle-clicking a link in order to open it in a new tab.

So, why is it doing this? Turns out that, by default, Firefox for Linux allows you to use this middle-click to paste functionality to allow you to navigate to a highlighted URL simply by middle-clicking non-editable portions of the page. When an invalid URL is the result of the paste, the annoying popup appears.

Today, I found out how to get rid of this annoyance.

Open a new tab in Firefox and navigate to “about:config”. This will take you to an interface that allows you to tweak and configure very specific functionality of Firefox.

In the “Filter:” text box, enter “middlemouse.contentLoadURL”. This should present a single entry that lists the option as having a value of “true”. Simply double-click the listing to change the value to “false”. The effect is instantaneous.

Now when you middle-click outside of editable areas in Firefox, it will no longer try to navigate to a URL. This change only modifies the navigation to URL functionality; the middle-click to paste in editable areas still functions.

If you like the middle-click to scroll functionality found in other browsers/operating systems, then search for “general.autoScroll” and double-click the listing to change it to true. Now you can middle-click to initiate scrolling.

Firefox 3.5 was released yesterday. This is an exciting new release complete with features such as support for HTML 5, video and audio that works in the browser without the need for plugins, a much faster Javascript engine, a native JSON parser, private browsing mode, support for SVG transformations, and other great enhancements.

I’m sure that you’re just as excited to get started with Firefox 3.5 as I was yesterday when I heard the news. But wait! We’re on Ubuntu, we can’t just install whatever we want, we need to wait for a package. Right? Wrong.

Here’s a really quick way to get 3.5.5 running on your Ubuntu 9.04 system.

Open up Terminal (Applications > Accessories > Terminal) and run the following commands:

1. cd /tmp
2. wget "http://download.mozilla.org/?product=firefox-3.5.5&os=linux&lang=en-US"
   Note: Your download link may be different depending on your country and language. I got the link by clicking the download link, canceling  the automatic download, right-clicking the “Your download should automatically begin in a few seconds, but if not, click here” link, and selecting Copy Link Location.
3. tar xvjf firefox-*.bz2
4. sudo cp -r firefox /usr/lib/firefox-3.5.5
5. sudo mv /usr/bin/firefox /usr/bin/firefox.old
6. sudo ln -s /usr/lib/firefox-3.5.5/firefox /usr/bin/firefox-3.5.5
7. sudo ln -s /usr/bin/firefox-3.5.5 /usr/bin/firefox

Close Firefox and then reopen. You should now be running Firefox 3.5.5.

If for whatever reason you’d like to switch back to your previous version of Firefox, simply run the following commands from Terminal:

1. sudo mv /usr/bin/firefox /usr/bin/firefox.bak
2. sudo mv /usr/bin/firefox.old /usr/bin/firefox

Notice how I even create a backup of the original firefox before replacing it. It is always a good idea to do this if you replace programs yourself. This way you won’t be likely to remove a binary or script that you won’t be able to get back easily.

Now that you are on Firefox 3.5.5, check out some awesome sites that show off some of the new capabilities.

• 3-D cubes built with standard HTML content, including the new native video component.
• Audio player built entirely with HTML, CSS, and Javascript. It doesn’t even use what we commonly think of as images, simply the new Canvas element.
• Video Washing Machine – Add a video to your site, crop it to fit in a circle, put a border around it, have rollover effects that change the filter on the video, and spin the whole thing as it plays. All of this with just the <video> element, CSS 3, SVG, and a bit of JavaScript.
• Add upload progress bars without the use of Flash or insane amounts of scripting.
• Create the illusion of a 3D voxel engine with an image and some creative SVG, scripting, and CSS.
• Apply textures to an animated model.
• Create a text shadow spotlight effect using Javascript and CSS.
• Web developers can now take advantage of custom typography using the new CSS rules.
• Sync page elements with the position in the video. Note that the graphs are canvas elements that are being drawn on.
• Use HTML elements to jump to different positions in audio.