[Pkg-chromium-maint] Bug#776388: chromium does not start at all
nicolas at deffayet.com
Sat Oct 17 18:10:53 UTC 2015
On Tue, 27 Jan 2015 16:13:00 +0100 (CET) Santiago Vila <sanvila at unex.es> wrote:
> Package: chromium
> Version: 40.0.2214.91-1
> Severity: serious
> chromium does not start at all in my machine.
> Instead, when started from a terminal, it writes tons of messages like this:
> [2755:2755:0127/145321:ERROR:gles2_cmd_decoder.cc(3952)] Error: 5 for Command kResizeCHROMIUM
> ^C[2755:2755:0127/145322:ERROR:gles2_cmd_decoder.cc(3823)] GLES2DecoderImpl: Context lost because context no longer current after resize callback.
> in an endless loop.
> The only "special" thing about my system is that 3D acceletarion does
> not work properly and I have to use libgl1-mesa-swx11 instead of
> libgl1-mesa-glx (see Bug#763890).
When libgl1-mesa-swx11 is used, chromium should be started with
$ chromium --disable-gpu
libgl1-mesa-swx11 should NOT be marked as conflict because it broke
usage of chromium under X2Go/FreeNX.
X2Go/FreeNX users are required to use libgl1-mesa-swx11 due to lack of
3D support and so can't use libgl1-mesa-glx.
Please remove libgl1-mesa-swx11 in conflict list of chromium package.
More information about the Pkg-chromium-maint