Added Area-Editor, OpSys-Linux, Triaged labels.

Set owner to @danrubel.
Added this to the M5 milestone.

This comment was originally written by gerald.holzinger.p...@gmail.com

Please merge issue #2052 and #1870 with this one.

yesterday i downloaded the 64 bit version for linux. (opensuse12.3/64 bit/KDE)

Dartium didn't start.

The solution was found in issue #2052.
(make link to the libraries, install patchelf with yast, and run the "patchelf --set-rpath /opt/dart/chromium /opt/dart/chromium/chrome" command.)

a rpm repository for opensuse would be nice too.

This comment was originally written by @butlermatt

Running into this issue now with Ubuntu Gnome 13.04 Beta2 (64-bit).

This is a known issue as all Ubuntu variants no longer support (not in the repositories at all) libudev0, and instead use libudev1. The dev builds of chromium should have this fix in place, not yet pushed out to beta or stable. See chromium bug:

http://code.google.com/p/chromium/issues/detail?id=226002

This is going to become a big issue tomorrow, April 25th, when Ubuntu 13.04 launches, and the general population (of ubuntu users) starts to run into this issue.

This comment was originally written by @butlermatt

A fix for this has been released in Chrome dev and Beta, yet with the latest build I'm still continuing to receive this error when trying to launch dartium from the editor:

"Could not launch browser - process terminated on startup"

Dartium stdout: <path-to-dartium-chrome>: error while loading shared libraries: libudev.so.0 cannot open shared object file. No such file or directory.

If dartium is based off of the dev build, why didn't that patch also resolve this issue?

This does not appear to be an editor issue. Reassigning to Dartium.

Removed the owner.
Removed Area-Editor label.
Added Area-Dartium label.

This comment was originally written by antonm@google.com

We roll Chromium changes on approx. weekly basis.

Added NotPlanned label.

This comment was originally written by @butlermatt

Just to follow up, are you pulling from the continuous build? I ask because apparently that version will not receive the fix per this comment:

https://code.google.com/p/chromium/issues/detail?id=226002#c66

This is again in respects to libudev.so.0 This will affect any users with Ubuntu 13.04. While there is a work around to create a link from libudev.so.1 to libudev.so.0, I'm concerned it will give new developers to dart a bad experience if Dartium doesn't work to run the samples as dart code.