Re: [Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 o n trusty/xenial/yakkety

I tried this so as to be ready for the next problem, but install does not like the armhf bit - wants amd64. -- Original Message -- From: Olivier Tilloy To: rbayer...@juno.com Subject: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on trusty/xenial/yakkety Date:

Re: [Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 o n xenial

That seems to have fixed the problem - Chromium is running as before the update. -- Original Message -- From: Olivier Tilloy To: rbayer...@juno.com Subject: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial Date: Thu, 06 Jul 2017 20:48:42 - Thanks fo

Re: [Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 o n xenial

Turned off WiFi, Chromium browser comes up with home page (google). Seems OK. Turn on WiFi, and it crashes. -- Original Message -- From: Olivier Tilloy To: rbayer...@juno.com Subject: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial Date: Thu, 06 Jul 20

Re: [Desktop-packages] [Bug 1702501] Re: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 000000000010

No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename:xenial Linux rohan-T500 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux chromium-browser: Installed: 59.0.3071.109-0ubuntu0.16.04

[Desktop-packages] [Bug 1702501] Re: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 000000000010

I cannot believe I am the only one to experience this bug. Is there anything I should try which I have not yet tried? ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/64625

[Desktop-packages] [Bug 1702501] [NEW] chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 000000000010

Public bug reported: After I updated Chromium to the latest version today, it crashed as soon as executed. When executed from a terminal, I got: Received signal 11 SEGV_MAPERR 0010 #0 0x7f5c4b92d425 base::debug::StackTrace::StackTrace() #1 0x7f5c4b92d80b #2 0x7f5c4bc58390 #3 0x55ae23b4