Home > Internet > Chromium Browser : Now Stable

Chromium Browser : Now Stable

The other day I decided I would try out the Chromium Browser again on Linux. It has been some time since I tried it–the last time it hardly rendered text properly–so I was very happy to see that it has improved significantly! When I say significantly I mean it is now my default browser, and has been for over a week. I don’t believe I have had any crashes (I can’t recall any as I write this), and everything that I expect to work has worked just fine. This includes flash, javascript, tabs, https, etc, etc. I trust it enough to write this post and not crash and lose my progress.

For those that haven’t tried it out yet, I would invite you to do so. I’ve outlined instructions below on how to use the chromium-daily PPA to update and use the latest nightly builds.

Configure PPA

Append the following line to your /etc/apt/sources.list:

deb http://ppa.launchpad.net/chromium-daily/ppa/ubuntu jaunty main

You can also import the package signing key using the command:

sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 4E5E17B5

You’ll have to refresh your package list, but then you’ll be able to install the Chromium Browser and you’ll receive updates daily.

sudo aptitude update && sudo aptitude install chromium-browser

Thoughts?

What are your thoughts on Chromium? Do you like it? Is it faster? I’m sure many of you will mention that its lack of plugins as compared to Firefox is holding you back, but that is on the horizon. Let me know what you like and what you don’t like, and if you’ve had as much success as I have.

If this article has been helpful, please consider linking to it.

Categories: Internet Tags: , , ,

Related Posts

  1. Jeff
    September 7th, 2009 at 15:53 | #1

    I was just wondering, as I've been running Chromium on Linux for a while now, but when you say that flash and javascript work for you, do you mean when you run it through terminal using the –enable-plugins parameter, or does it have the plugins normally? Right now, I've been running it with –enable-plugins, but if I run it normally, I still don't get flash, etc.

  2. September 7th, 2009 at 16:38 | #2

    I launch it normally via the Applications menu. I haven't added any special options.

  3. September 7th, 2009 at 17:20 | #3

    I've been using as my default browser for a while in 9.04 now. It's so much faster to start and pages seem to render quicker than through FF. All in all have been very happy with it :)

  4. ktp
    September 8th, 2009 at 02:48 | #4

    I have to been using chromium (native 64) for while now, with the –enable-plugins flag, which is put in /etc/chromium-browser/default so I don't have to worry about passing it on start (PPA feature). Overall it is great…still has few minor issues (totem plugin not working), but well worth the speed. I can't wait until bookmark sync works in linux.

  5. phoenyx
    September 8th, 2009 at 07:13 | #5

    I haven't tried it yet, and I'm not sure if I want to after reading this thread: http://groups.google.com/group/chromium-dev/brows...

    Summary: they clobber the paste buffer, they know that they are breaking conventions, they don't care

  6. Jason
    September 8th, 2009 at 09:09 | #6

    Anyone know if there are plans for Chromium to support FF plugins?

  7. September 8th, 2009 at 13:46 | #7

    Been using it for a couple weeks now…seems very fast to me..much faster than FF3.5.
    rt

  8. September 12th, 2009 at 14:59 | #8

    I use: chromium-browser –enable-plugins –enable-greasemonkey –enable-user-scripts

    • blink4blog
      September 8th, 2009 at 02:46 | #9

      is that –enable-greasemonkey with missing 'e'?

  9. renggunux
    September 13th, 2009 at 14:14 | #10

    Is something wrong with this:

    sudo apt-key adv –recv-keys –keyserver keyserver.ubuntu.com 4E5E17B5

    i copy pasted it on my terminal and it produces error messages

  10. September 13th, 2009 at 16:54 | #11

    I've updated the post with proper formatting, please try again. The problem is the — turned into – in the original.

    The command should work now.