[Ubuntu-x-swat] [Bug 1371834] Re: Chrome causes segfault in i965_dri.so

2018-08-22 Thread Timo Aaltonen
should be fixed by now ** Changed in: mesa (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1371834 Title: Chrome causes segfault in i965_dri.so

[Ubuntu-x-swat] [Bug 1371834] Re: Chrome causes segfault in i965_dri.so

2015-09-01 Thread Bug Watch Updater
** Changed in: debian Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1371834 Title: Chrome causes segfault in i965_dri.so To manage notifications about

[Ubuntu-x-swat] [Bug 1371834] Re: Chrome causes segfault in i965_dri.so

2014-12-06 Thread Bug Watch Updater
** Changed in: debian Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1371834 Title: Chrome causes segfault in i965_dri.so To manage notifications about this bug

[Ubuntu-x-swat] [Bug 1371834] Re: Chrome causes segfault in i965_dri.so

2014-11-10 Thread zob
Someone is fixing this elsewhere: https://code.google.com/p/chromium/issues/detail?id=415681 ** Bug watch added: code.google.com/p/chromium/issues #415681 http://code.google.com/p/chromium/issues/detail?id=415681 -- You received this bug notification because you are a member of Ubuntu-X,

[Ubuntu-x-swat] [Bug 1371834] Re: Chrome causes segfault in i965_dri.so

2014-11-08 Thread zob
Just tested this with the kernel from vivid (3.18rc2): http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc2-vivid/ On my system the bug is no longer present in that kernel, i.e. Chrome 38+ doesn't segfault when opening chrome webshop. -- You received this bug notification because you are a

[Ubuntu-x-swat] [Bug 1371834] Re: Chrome causes segfault in i965_dri.so

2014-11-08 Thread zob
Ok. Just tested quite a few kernels. Chrome 38+ does not segfault when browsing to chrome webshop with the following: linux-image-3.16.0-031600-generic linux-image-3.16.1-031601-generic linux-image-3.16.7-031607-generic linux-image-3.17.1-031701-generic linux-image-3.18.0-031800rc2-generic Chrome

[Ubuntu-x-swat] [Bug 1371834] Re: Chrome causes segfault in i965_dri.so

2014-11-07 Thread zob
I get this on a Toshiba satellite A200. vera@vera-Satellite-A200:~$ lsb_release -a uname -a lspci | grep VGA sudo lshw -C display sudo tail -n 500 /var/log/syslog | grep segfault No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.10 Release:14.10 Codename:

[Ubuntu-x-swat] [Bug 1371834] Re: Chrome causes segfault in i965_dri.so

2014-11-07 Thread zob
This happens in chrome-stable 38.0.2125.111-1, chrome-beta 39.0.2171.52-1, and chrome unstable 40.0.2209.0-1 when browsing chrome webstore (with this graphics card). It does not happen when browsing chrome webstore with chromium 37.0.2062.120 or firefox 33.

[Ubuntu-x-swat] [Bug 1371834] Re: Chrome causes segfault in i965_dri.so

2014-11-07 Thread zob
Btw. Those result were from a test in ubuntu 12.04.5 on both the 3.13 (trusty) and the 3.2 (precise) kernel and libgl1-mesa-dri 8.0.4-0ubuntu0.7 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu.

[Ubuntu-x-swat] [Bug 1371834] Re: Chrome causes segfault in i965_dri.so

2014-11-05 Thread Alberto Salvia Novella
** Changed in: mesa (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1371834 Title: Chrome causes segfault in i965_dri.so To manage notifications about

[Ubuntu-x-swat] [Bug 1371834] Re: Chrome causes segfault in i965_dri.so

2014-10-30 Thread william fischer
I tried the fix described in #3 and sure enough, I was able to use Google Maps with Earth view. With out the export, it just Satellite view and regular map view only. [ 1240.775010] chromium-browse[6013]: segfault at 1f8 ip 7f255e9ae63f sp 7fffc5d9a490 error 4 in

[Ubuntu-x-swat] [Bug 1371834] Re: Chrome causes segfault in i965_dri.so

2014-10-22 Thread Tito
I can confirm this very annoying bug with i915 driver (on Lenovo x220). It creates all sorts of graphical difficulties in Chromium (no vsync, no interpolation of fullscreen videos, and of course no WebGL) LIBGL_DRI3_DISABLE=1 is a good fix. -- You received this bug notification because you

[Ubuntu-x-swat] [Bug 1371834] Re: Chrome causes segfault in i965_dri.so

2014-09-27 Thread mangouste06
Found [1] here a workaround : run chrome with : LIBGL_DRI3_DISABLE=1 google-chrome makes webgl come back. [1]:https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757435 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu.

[Ubuntu-x-swat] [Bug 1371834] Re: Chrome causes segfault in i965_dri.so

2014-09-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1371834 Title:

[Ubuntu-x-swat] [Bug 1371834] Re: Chrome causes segfault in i965_dri.so

2014-09-22 Thread Karma Dorje
** Bug watch added: Debian Bug tracker #757435 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757435 ** Also affects: debian via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757435 Importance: Unknown Status: Unknown ** Bug watch added: code.google.com/p/chromium/issues

[Ubuntu-x-swat] [Bug 1371834] Re: Chrome causes segfault in i965_dri.so

2014-09-22 Thread Bug Watch Updater
** Changed in: debian Status: Unknown = New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1371834 Title: Chrome causes segfault in i965_dri.so To manage notifications about this bug go