chromium-browser crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Got this crash when trying to open a hyperlink in a PDF file in evince. happens every time with multiple different PDF files.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: chromium-browser 43.0.2357.
ProcVersionSign
Uname: Linux 3.19.0-25-generic x86_64
NonfreeKernelMo
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Aug 19 05:45:43 2015
Desktop-Session:
'gnome-fallback'
'/etc/
'/usr/
Env:
'None'
'/usr/lib32'
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-02-13 (917 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
Load-Avg-1min: 3.66
Load-Processes-
MachineType: System manufacturer System Product Name
ProcCmdline: chromium-browser\ --ppapi-
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: chromium-browser
StacktraceTop:
raise () from /lib/x86_
abort () from /lib/x86_
base::
logging:
content:
Title: chromium-browser crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to trusty on 2014-05-12 (464 days ago)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
dmi.bios.date: 05/22/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5601
dmi.board.
dmi.board.name: F1A75-M-PRO R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
gconf-keys: /desktop/
modified.
mtime.conffile.
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1471645, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.