Thanks for the quick reply. As you saw, I've also submitted this issue to
http://code.google.com/p/chromium/issues/detail?id=439795&thanks=439795&ts=1417965276
I need the hardware acceleration that is provided by the nvidia driver so
couldn't lose that
just to use a new version of chromium.
At some point I'll upgrade the kernel but this is a significant issue when
using the nvidia driver;
if this problem continues until then and is solved by the kernel upgrade, I'll
update the bug.
I think there are two issues to consider:
1. this problem did not arise with chromium 38.0.2125.101-2, to which I have
now reverted
2. this problem does not arise with google-chrome-stable 39.0.2171.71-1, the
same version
as the chromium in this bug report.
These two issues indicate that related software works with the nvidia driver
and kernel 3.14,
so more likely is caused by changes that are specific to just this new version
of chromium.
thanks,
--jack
________________________________
From: Michael Gilbert <mgilb...@debian.org>
To: 772...@bugs.debian.org; 772471-submit...@bugs.debian.org
Sent: Sunday, December 7, 2014 6:14 PM
Subject: Bug#772471: chromium crash on startup
control: tag -1 moreinfo
control: severity -1 minor
control: retitle -1 chromium: sandbox issue with nvidia driver
> Kernel: Linux 3.14-1-686-pae (SMP w/6 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8
> Shell: /bin/sh linked to /bin/dash
Not sure if it matters, but your kernel is quite out of date. jessie
currently has 3.16.0-4, so you could try updating.
Also, since this was with the proprietary driver please try nouveau instead.
Best wishes,
Mike
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
