This bug was fixed in the package chromium-browser -
40.0.2214.94-0ubuntu1.1120

---------------
chromium-browser (40.0.2214.94-0ubuntu1.1120) vivid; urgency=medium

  * Upstream release 40.0.2214.94.
  * Upstream release 40.0.2214.93.
  * Upstream release 40.0.2214.91. (LP: #1414753)
    - CVE-2014-7923: Memory corruption in ICU.
    - CVE-2014-7924: Use-after-free in IndexedDB.
    - CVE-2014-7925: Use-after-free in WebAudio.
    - CVE-2014-7926: Memory corruption in ICU.
    - CVE-2014-7927: Memory corruption in V8.
    - CVE-2014-7928: Memory corruption in V8.
    - CVE-2014-7930: Use-after-free in DOM.
    - CVE-2014-7931: Memory corruption in V8.
    - CVE-2014-7929: Use-after-free in DOM.
    - CVE-2014-7932: Use-after-free in DOM.
    - CVE-2014-7933: Use-after-free in FFmpeg.
    - CVE-2014-7934: Use-after-free in DOM.
    - CVE-2014-7935: Use-after-free in Speech.
    - CVE-2014-7936: Use-after-free in Views.
    - CVE-2014-7937: Use-after-free in FFmpeg.
    - CVE-2014-7938: Memory corruption in Fonts.
    - CVE-2014-7939: Same-origin-bypass in V8.
    - CVE-2014-7940: Uninitialized-value in ICU.
    - CVE-2014-7941: Out-of-bounds read in UI.
    - CVE-2014-7942: Uninitialized-value in Fonts.
    - CVE-2014-7943: Out-of-bounds read in Skia.
    - CVE-2014-7944: Out-of-bounds read in PDFium.
    - CVE-2014-7945: Out-of-bounds read in PDFium.
    - CVE-2014-7946: Out-of-bounds read in Fonts.
    - CVE-2014-7947: Out-of-bounds read in PDFium.
    - CVE-2014-7948: Caching error in AppCache.
  * debian/patch/search-credit: Don't force client in GOOG suggestions search.
    (LP: #1398900)
  * debian/patches/dri3-within-sandbox: Backport V41 sandbox, fixing DRI3.
    (LP: #1378627)
  * debian/patches/macro-templates-not-match: Remove. No longer necessary.
  * debian/patches/arm-neon.patch: Kill armv7=neon assumption. Fix typos.
  * debian/rules: chrpath for all packages.  (LP: #1415555)
 -- Chad MILLER <chad.mil...@canonical.com>   Fri, 30 Jan 2015 15:48:09 -0500

** Changed in: chromium-browser (Ubuntu)
       Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7923

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7924

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7925

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7926

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7927

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7928

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7929

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7930

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7931

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7932

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7933

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7934

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7935

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7936

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7937

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7938

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7939

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7940

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7941

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7942

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7943

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7944

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7945

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7946

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7947

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7948

-- 
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/1378627

Title:
  chromium-browser crashed with SIGSEGV

Status in Chromium Browser:
  Unknown
Status in Mesa:
  Won't Fix
Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser package in Debian:
  Confirmed
Status in chromium-browser package in Fedora:
  Unknown

Bug description:
  No idea what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 37.0.2062.94-0ubuntu1~pkg1065
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Wed Oct  8 07:12:48 2014
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2013-12-22 (289 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221)
  ProcCmdline: chromium-browser\ --type=gpu-process\ 
--channel=3043.0.199670400\ --supports-dual-gpus=false\ 
--gpu-driver-bug-workarounds=1,11,15\ --disable-accelerated-video-decode\ 
--gpu-vendor-id=0x8086\ --gpu-device-id=0x0126\ --gpu-driver-vendor\ 
--gpu-driver-versi
  SegvAnalysis:
   Segfault happened at: 0x7fc0e6b1963f:        mov    0x1f8(%rax),%r15
   PC (0x7fc0e6b1963f) ok
   source "0x1f8(%rax)" (0x000001f8) not located in a known VMA region (needed 
readable region)!
   destination "%r15" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/chromium-browser/libs/libgpu.so
   ?? () from /usr/lib/chromium-browser/libs/libcontent.so
   ?? () from /usr/lib/chromium-browser/libs/libcontent.so
  Title: chromium-browser crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-09-14T18:16:36.315577

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to