Summary: | >=www-client/chromium-16.0.912.21 cannot run any NaCl binaries | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andrew Udvare <audvare> |
Component: | Current packages | Assignee: | Chromium Project <chromium> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | mads |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | http://code.google.com/p/chromium/issues/detail?id=103377 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge --info chromium:0 google-chrome |
Description
Andrew Udvare
2011-11-04 10:36:24 UTC
Tried another machine, same error. I have the same issue with both chromium and google-chrome 17.0.928.0. Created attachment 291721 [details]
emerge --info chromium:0 google-chrome
(In reply to comment #2) > I have the same issue with both chromium and google-chrome 17.0.928.0. Isn't it "NaCl will not run on Windows" known issue from http://googlechromereleases.blogspot.com/2011/11/dev-channel-update_03.html ? Apparently Linux is also affected (or it's something different). I think it's http://code.google.com/p/chromium/issues/detail?id=102934 I think I was wrong, there are several clues suggesting it's a different bug. Taking a closer look. I reported this upstream. Please star that report if you see this issue, and help by answering upstream's questions. Fixed upstream. http://crbug.com/103377 (In reply to comment #7) > Fixed upstream. http://crbug.com/103377 I'm considering backporting the patches, let's keep the bug open. (In reply to comment #8) > I'm considering backporting the patches, let's keep the bug open. Patches don't backport cleanly, I don't think it's feasible. Closing. |