chromium-browser crashed with SIGABRT
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
the error occurred when you started session
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: chromium-browser 65.0.3325.
ProcVersionSign
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64: AP/////
modes: 1920x1080
Date: Sun Mar 18 00:39:29 2018
Desktop-Session:
'ubuntu'
'/etc/
'/usr/
DetectedPlugins:
Env:
'None'
'None'
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2018-03-11 (6 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
Load-Avg-1min: 0.92
Load-Processes-
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2a Intel Corp.
Bus 001 Device 002: ID 13d3:5654 IMC Networks
Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. GL553VD
ProcCmdline: /usr/lib/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: chromium-browser
StacktraceTop:
()
()
()
dbus_connectio
()
Title: chromium-browser crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 01/02/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL553VD.306
dmi.board.
dmi.board.name: GL553VD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: GL
dmi.product.name: GL553VD
dmi.product.
dmi.sys.vendor: ASUSTeK COMPUTER INC.
modified.
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 #1756655, 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.