cannot enable webgl for chromium in virtualbox - google-chrome

I'm trying to run webgl in chromium browser in virtualbox on Ubuntu 14.04.
First I set in chrome://settings hardware acceleration when available to checked,
then in chrome://flags I enabled everything about webgl,
but in chrome://gpu I still have status WebGL: Unavailable.
In virtualbox setting I checked 3D acceleration, not 2D acceleration.
Please, don't you have any idea how to solve it?

Have you tried enable the flag of "Override software rendering list" in chrome://flags, or append command line switch "--ignore-gpu-blacklist"?

Related

Does headless Chrome auto update?

Does Chrome update itself when running in headless mode by selenium?
It seems, it is not updating, probably because of --disable-background-networking switch set by Selenium by default. I want to ensure that's indeed the case. If there any reference in documentation explaining either auto-update behavior or meaning of switches and their impact? So far best I've found is list with all command line Chrome switches with some comments, but it is still not clear.
No, Chrome Browser Client doesn't update itself when running in headless mode by selenium.
As per Getting Started with Headless Chrome the Headless Chrome is the server environment where you don't need a visible UI shell.
If you've got Chrome 59+ installed, you start Chrome with the --headless flag as follows:
chrome \
--headless \ # Runs Chrome in headless mode.
--disable-gpu \ # Temporarily needed if running on Windows.
chrome should always point to your installation of Chrome. Of course, the exact location varies from platform to platform.
So until and unless the original Chrome Browser is automatically/manually updated, Chrome Browser Client doesn't get updated.
TL;DR
--disable-background-networking is configured to disable several subsystems which run network requests in the background. This is used when performing network performance testing in order to avoid noise in the measurements.

How can i turn on Developer Mode on ChromeOS launched on VirtualBox?

I have launched ChromeOS on VirtualBox. Now I want to turn on Developer Mode to disable the verification of rootfs (root file system). How can I turn on this mode without pressing buttons on laptop, because it`s launched virtually?
Maybe there are some solutions using command line (crosh/shell)
If you can run "shell" from crosh, then the system is already in developer mode.
For non-Chrome OS devices, typically developer mode is turned on by adding cros_debug to the kernel command line, and the default Chromium OS builds include that automatically.

webGL is not working in Chromium, but it is in Firefox

I have installed Chromium Version 31.0.1650.63 on CentOS release 6.5.
I also have firefox 24.6.0 installed
when I visit a web page in chromium that needs webGL, it says
Uncaught RuntimeError: The browser supports WebGL, but initialization failed.
I have checked the about:flags page the 'disable WebGL' attribute is NOT enabled
I visted
http://get.webgl.org/
Which said: Hmm. While your browser seems to support WebGL, it is disabled or unavailable. If possible, please ensure that you are running the latest drivers for your video card.
Visiting that same sight in firefox gave me the nice spinning cube 'success' page.
I visited
chrome://gpu/
and it said
WebGL: Unavailable. Hardware acceleration unavailable
WebGL multisampling: Unavailable. Hardware acceleration unavailable
Which I find hard to square with the same video card providing webgl support in firefox just fine.
Is this truly a video card driver issue or should I look elsewhere?
Most likely this is because Firefox and Chrome use different GPU blacklists.
Please try debugging tips provided here:
WebGL not working for same spec system in chrome. How to fix?
If you have an Intel integrated graphics chip, you might have to enable hardware acceleration (i.e. exposing the GPU functionality directly to certain software) for the X.org server of the X11 window system.
To do this edit or create the configuration file /etc/X11/xorg.conf.d/20-intel.conf and put the following in there:
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "sna"
Option "TearFree" "true"
Option "DRI" "3"
EndSection
Sources
https://wiki.archlinux.org/index.php/intel_graphics#Configuration
https://bbs.archlinux.org/viewtopic.php?pid=1595276#p1595276
I had this issue after switching from the proprietary Nvidia to the nouveau drivers, a change which does not seem to have been picked up in the chromium GPU config of my profile. The fix is running chromium-browser --single-process once to reset the GPU configuration.

WebGL not working for same spec system in chrome. How to fix?

Using info from chrome://gpu and chrome://version
Both on Chrome version: 35.0.1916.153 (Official Build 274914) m
Both using an Nvidia 670 GTX
My driver: 9.18.13.3523
His driver: 9.18.13.4043
My webGL works perfectly, and my driver is slightly behind his. His webGL doesn't work even though in the settings it says all hardware accelerated, webGL enabled etc.
When he goes on page with webGL things they don't work - he can't see them just like you wouldn't see them with old browsers.
Why is this happening? How to diagnose/fix?
Most likely Google has blacklisted the graphics driver because of the bugs.
You need to find out how start Chrome so that it ignores GPU blacklist. On some system it is this command line:
google-chrome --enable-webgl --ignore-gpu-blacklist
... and if it still doesn't work, the relevant console output etc. is needed.
More about blacklist:
http://www.khronos.org/webgl/wiki/BlacklistsAndWhitelists

How to use software webgl engine in Chrome 18

I'd like to test out the new SwiftShader-based software WebGL engine which is allegedly in Chrome 18. I'm running 18.0.1025.165 on Mac OS X 10.7.3. I tried this command line (suggested here), but when I visit something with WebGL, it just says that it is disabled:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --blacklist-accelerated-compositing --blacklist-webgl
Is SwiftShader in the Mac version of Chrome 18? Is there a different trick I should use to enable it?
Currently SwiftShader is only available for Chrome under Windows. Is there any particular reason why you need it on Mac OS? Apple typically has adequate graphics hardware and OpenGL drivers.