NaCL is missing

Bug #882942 reported by Micah Gersten
252
This bug affects 55 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Triaged
Low
Unassigned
Lucid
Won't Fix
Low
Unassigned
Maverick
Invalid
Low
Unassigned
Natty
Invalid
Low
Unassigned
Oneiric
Invalid
Low
Unassigned

Bug Description

Even though is was disabled by default, not shipping it is a regression. There are currently some build issues with it enabled in the build.

Micah Gersten (micahg)
Changed in chromium-browser (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Changed in chromium-browser (Ubuntu Lucid):
status: New → Triaged
importance: Undecided → Low
Changed in chromium-browser (Ubuntu Oneiric):
status: New → Triaged
Changed in chromium-browser (Ubuntu Maverick):
importance: Undecided → Low
Changed in chromium-browser (Ubuntu Natty):
importance: Undecided → Low
Changed in chromium-browser (Ubuntu Oneiric):
importance: Undecided → Low
Micah Gersten (micahg)
description: updated
Changed in chromium-browser (Ubuntu Natty):
status: New → Triaged
Changed in chromium-browser (Ubuntu Maverick):
status: New → Triaged
Revision history for this message
Moritz Naumann (mnaumann) wrote :

This is becoming more of an issue now that NACL is becoming a somewhat popular platform. Unless this is already being monitored, it might be worth re-examining whether NACL builds fine on current Chromium versions (such as available in the beta, dev and daily PPAs) now, so that there can be support in Precise?

Revision history for this message
shawnlandden (shawnlandden) wrote :

as NaCl is its own toolchain, and upstream ships it by shipping a binary version of it, which is not OK IMHO.

Someone would need to contribute, and maintain bootstrap build support for NaCl, so it can be built entirely from packages in the main archive from source.

Revision history for this message
rogerdpack (rogerdpack) wrote :

Just ran into this problem today myself...hope they can add real NaCl support at some point. Or possibly repackage the google releases as rpm's instead?

Revision history for this message
Luke Yelavich (themuso) wrote :

Not including NaCL has accessibility implications as well. It is currently not possible for users to install and use the ChromeVox extension to provide web accessibility and screen reading of web pages via the use of Chrome.

Revision history for this message
dino99 (9d9) wrote :
Changed in chromium-browser (Ubuntu Maverick):
status: Triaged → Invalid
Changed in chromium-browser (Ubuntu Natty):
status: Triaged → Invalid
Changed in chromium-browser (Ubuntu Oneiric):
status: Triaged → Invalid
tags: removed: maverick natty oneiric
Revision history for this message
Gabriel de Perthuis (g2p) wrote :

Google is pushing NaCl apps, we are missing out:
http://chrome.blogspot.com/2013/09/a-new-breed-of-chrome-apps.html

tags: added: raring saucy
Revision history for this message
Simon Eisenmann (longsleep) wrote :

Is there any new son this. Seems to be a share that Ubuntu should be the only distro which does not ship NaCL with chromium and thus forcing users to use Google Chrome.

Revision history for this message
Or Schiro (orschiro) wrote :

I am interested in this one as well. Any news on including NaCL support in Ubuntu's Chromium builds?

Revision history for this message
dino99 (9d9) wrote :
Revision history for this message
bademux (bademux) wrote :
Revision history for this message
Rolf Leggewie (r0lf) wrote :

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".

Changed in chromium-browser (Ubuntu Lucid):
status: Triaged → Won't Fix
Revision history for this message
Tomasz Struczyński (t-struczynski) wrote :

The very same problem still occurrs, even on 14.10 edition (Utopic). Seriously??? This is certainly not LOW priority, as Chromium is default browser for Ubuntu!

Revision history for this message
Timo Palomaa (timppis) wrote :

> as Chromium is default browser for Ubuntu!

It is not?

Revision history for this message
Or Schiro (orschiro) wrote :

Is there an inofficial Chromium built for Ubuntu with enabled NaCL?

Revision history for this message
Timo Palomaa (timppis) wrote :

@Robert: "... building the Native Client plugin into Chromium requires the use of a separate toolchain. While the toolchain is open-source, I'm having some trouble building it locally. When I do have it built successfully, I'll include Native Client using that toolchain."

https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1462647/comments/3
(https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1462647)

https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-beta
https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev

On the other hand, those builds do not have API keys (can't use e.g. Chrome Sync).

Revision history for this message
Or Schiro (orschiro) wrote :

Dear Timo,

Thanks for your comment. I need Chrome Sync as much as I need NaCL support.

Thus the best solution I see for now is to use both, Ubuntu Chromium built (Chrome Sync) and Chrome (for NaCL).

Warmly,

Robert

Revision history for this message
Saikrishna Arcot (saiarcot895) wrote :

Chromium with Native Client is now working for Trusty and newer on both the Chromium Beta and Dev PPAs.

https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-beta
https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev

As for the API keys, yes, there are no API keys included in this build, but there are instructions on how to add in API keys. Note that you need to have a Google account.

Revision history for this message
Or Schiro (orschiro) wrote :

Dear @saiarcot895,

Thanks for your work!

Just to clarify. If I were to install this version, then NACL would work out of the box. However, Google Account Sync would not be supported out of the box, correct?

How difficult is the process of adding own API keys?

Thankfully,

~ Robert

Revision history for this message
Saikrishna Arcot (saiarcot895) wrote :

Correct.

I don't think it's too hard. Getting and adding API keys should take about 15-20 minutes. The steps are outlined in the PPA description, and the process of getting the API keys is outlined at https://www.chromium.org/developers/how-tos/api-keys.

In your case, you only need to enable the Chrome Sync API if that's all you want to use.

Revision history for this message
Or Schiro (orschiro) wrote :

Excellent. Thank you very much for your guidance!

Robert

Revision history for this message
Olivier Tilloy (osomon) wrote :

Still valid. The packages are built with enable_nacl=false.

Olivier Tilloy (osomon)
tags: removed: lucid raring saucy
Revision history for this message
Willy Nolan (optonox) wrote :

So I am unclear: Is there any way to get Native Client to work with Chromium?

Most information on the internet (for one example https://askubuntu.com/questions/91789/why-is-nacl-disabled-for-chromium) makes it seem like it doesn't work.

If I install it from the Beta channel than Native Client will work but Google Sync will not?

Revision history for this message
Viktor Engelmann (viktor-engelmann) wrote :

Don't bother with NaCL, it is deprecated and will be removed from chrome/chromium in Q1 2018. Use WASM (that is already supported by chromium-browser)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.