[Touch-packages] [Bug 1300235] Re: init (chromium-browser) crashed with SIGSEGV

2017-04-25 Thread Olivier Tilloy
Closing now as this report wasn’t investigated timely and is now too old to be meaningful. Please do not hesitate to report crashes occurring with recent releases of chromium-browser, they will hopefully be investigated and acted upon in a more timely manner. ** Changed in: chromium-browser

[Touch-packages] [Bug 1300235] Re: init (chromium-browser) crashed with SIGSEGV

2015-04-14 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.17.1-0ubuntu1 --- apport (2.17.1-0ubuntu1) vivid; urgency=medium * New upstream bug fix release: - SECURITY UPDATE: Fix root privilege escalation through crash forwarding to containers. Version 2.13 introduced forwarding

[Touch-packages] [Bug 1300235] Re: init (chromium-browser) crashed with SIGSEGV

2015-04-01 Thread Martin Pitt
Apport fixed upstream in r2941, thanks Brian! ** Changed in: apport (Ubuntu) Status: Triaged = Fix Committed ** Changed in: apport (Ubuntu) Assignee: (unassigned) = Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1300235] Re: init (chromium-browser) crashed with SIGSEGV

2015-04-01 Thread Launchpad Bug Tracker
** Branch linked: lp:apport -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1300235 Title: init (chromium-browser) crashed with SIGSEGV Status in apport package in Ubuntu:

[Touch-packages] [Bug 1300235] Re: init (chromium-browser) crashed with SIGSEGV

2015-03-17 Thread Brian Murray
There is an issue here with apport and how it launches apport if the pid does not equal the global pid. # Check if we received a valid global PID (kernel = 3.12). If we do, # then compare it with the local PID. If they don't match, it's an # indication that the crash originated from another PID

[Touch-packages] [Bug 1300235] Re: init (chromium-browser) crashed with SIGSEGV

2015-03-17 Thread Launchpad Bug Tracker
** Branch linked: lp:~brian-murray/apport/bug-1300235 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1300235 Title: init (chromium-browser) crashed with SIGSEGV Status in

[Touch-packages] [Bug 1300235] Re: init (chromium-browser) crashed with SIGSEGV

2015-03-16 Thread James Hunt
** Package changed: upstart (Ubuntu) = chromium-browser (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1300235 Title: init (chromium-browser) crashed with

[Touch-packages] [Bug 1300235] Re: init (chromium-browser) crashed with SIGSEGV

2015-03-12 Thread Brian Murray
** Summary changed: - init crashed with SIGSEGV + init (chromium-browser) crashed with SIGSEGV -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1300235 Title: init

[Touch-packages] [Bug 1300235] Re: init (chromium-browser) crashed with SIGSEGV

2015-03-12 Thread James Hunt
Playing around with strings(1), I've found this: $ strings /usr/lib/chromium-browser/libs/libcontent.so|egrep \init\ init The SUID sandbox created a new PID namespace but Zygote is not the init process. Please, make sure the SUID binary is up to date. Error creating an init process to reap