desktop-packages team mailing list archive

[Daniel Lezcano <1498954@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Hi,

when launching chromium, every page shows 'aw ! snap' and all extensions
crash (segfault).

The dmesg shows:

[ 5390.555398] chromium-browse[11974]: segfault at 410 ip 00000410 sp ab7febc0 error 14
[ 6100.170017] chromium-browse[12308]: segfault at 410 ip 00000410 sp a85febc0 error 14
[ 6100.365223] chromium-browse[12342]: segfault at 410 ip 00000410 sp a85febc0 error 14
[ 6100.378622] chromium-browse[12248]: segfault at 410 ip 00000410 sp bfff4a00 error 14
[ 6100.396981] chromium-browse[12364]: segfault at 410 ip 00000410 sp a87f5bc0 error 14
[ 6100.417267] chromium-browse[12376]: segfault at 410 ip 00000410 sp a85febc0 error 14
[ 6100.482647] chromium-browse[12381]: segfault at 410 ip 00000410 sp a87f5bc0 error 14
[ 6100.575302] chromium-browse[12389]: segfault at 410 ip 00000410 sp a85febc0 error 14
[ 6100.606053] chromium-browse[12394]: segfault at 410 ip 00000410 sp a87f5bc0 error 14
[ 6100.626080] chromium-browse[12399]: segfault at 410 ip 00000410 sp a85febc0 error 14
....

That wasn't happening before the update I did for the system.

If I launch the browser from the command line I have the error:

[12517:12517:0923/074300:ERROR:nss_util.cc(845)] After loading Root
Certs, loaded==false: NSS error code: -8018


And finally if launch the browser with the option: "--disable-seccomp-filter-sandbox", it does not show up the error and the extensions still work.

** Affects: chromium-browser (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1498954

Title:
  Chromium shows 'aw ! snap' on every page after updating the system

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Hi,

  when launching chromium, every page shows 'aw ! snap' and all
  extensions crash (segfault).

  The dmesg shows:

  [ 5390.555398] chromium-browse[11974]: segfault at 410 ip 00000410 sp ab7febc0 error 14
  [ 6100.170017] chromium-browse[12308]: segfault at 410 ip 00000410 sp a85febc0 error 14
  [ 6100.365223] chromium-browse[12342]: segfault at 410 ip 00000410 sp a85febc0 error 14
  [ 6100.378622] chromium-browse[12248]: segfault at 410 ip 00000410 sp bfff4a00 error 14
  [ 6100.396981] chromium-browse[12364]: segfault at 410 ip 00000410 sp a87f5bc0 error 14
  [ 6100.417267] chromium-browse[12376]: segfault at 410 ip 00000410 sp a85febc0 error 14
  [ 6100.482647] chromium-browse[12381]: segfault at 410 ip 00000410 sp a87f5bc0 error 14
  [ 6100.575302] chromium-browse[12389]: segfault at 410 ip 00000410 sp a85febc0 error 14
  [ 6100.606053] chromium-browse[12394]: segfault at 410 ip 00000410 sp a87f5bc0 error 14
  [ 6100.626080] chromium-browse[12399]: segfault at 410 ip 00000410 sp a85febc0 error 14
  ....

  That wasn't happening before the update I did for the system.

  If I launch the browser from the command line I have the error:

  [12517:12517:0923/074300:ERROR:nss_util.cc(845)] After loading Root
  Certs, loaded==false: NSS error code: -8018

  
  And finally if launch the browser with the option: "--disable-seccomp-filter-sandbox", it does not show up the error and the extensions still work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions