Chromium 50 fails to start

Louis Santillan lpsantil at gmail.com
Sat Apr 30 18:08:13 UTC 2016


The v8 and/or chrome libraries need an icu engine to link against.  V8 can
usually bring its own icu engine.  However, the system icu can work though
sometimes.

On Saturday, April 30, 2016, Alex Matviychuk <alexmat at gmail.com> wrote:

> Is anyone getting this output when they run a build of chromium
> 50.0.2661.86-1?
>
> ----------------------------------------------------
>
> $ chromium
> [0430/104320:ERROR:icu_util.cc(157)] Invalid file descriptor to ICU data received.
> [0430/104320:FATAL:content_main_runner.cc(677)] Check failed: base::i18n::InitializeICU().
> #0 0x5620fa60b62e <unknown>
> #1 0x5620fa62277e <unknown>
> #2 0x5620fa5db7da <unknown>
> #3 0x5620fa5d9f4d <unknown>
> #4 0x5620fa194aea ChromeMain
> #5 0x7f4d5615e5e0 __libc_start_main
> #6 0x5620fa1949a9 _start
>
> Aborted
>
> --------------------------------------
>
> 49 works fine for me.
>
> Thanks,
>
> Alex
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.crux.nu/pipermail/crux/attachments/20160430/0239ecf6/attachment.html>


More information about the CRUX mailing list