[trusty] [regression] chromium-browser crashed with SIGABRT in base::debug::BreakDebugger()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | apparmor (Ubuntu) |
Medium
|
Unassigned | ||
| | chromium-browser (Ubuntu) |
Medium
|
Unassigned | ||
Bug Description
This bug report concerns chromium-browser version 43.0.2357.
Previously, this system had 41.0.2272.
If run in a terminal, the program produces the following output:
[8622:
Aborted (core dumped)
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: chromium-browser 43.0.2357.
ProcVersionSign
Uname: Linux 3.13.0-55-generic i686
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: i386
CrashCounter: 1
Date: Sun Jul 5 23:47:06 2015
Desktop-Session:
'xubuntu'
'/etc/
'/usr/
DetectedPlugins:
Env:
'None'
'None'
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2014-10-23 (256 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
InstalledPlugins:
Load-Avg-1min: 0.44
Load-Processes-
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: IBM 23739XU
PccardctlIdent:
Socket 0:
no product info available
Socket 1:
no product info available
PccardctlStatus:
Socket 0:
no card
Socket 1:
no card
ProcCmdline: chromium-browser\ --enable-pinch\ https:/
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: chromium-browser
StacktraceTop:
base::
logging:
content:
content:
?? () from /usr/lib/
Title: chromium-browser crashed with SIGABRT in base::debug:
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 05/14/2004
dmi.bios.vendor: IBM
dmi.bios.version: 1RETC6WW (3.05a)
dmi.board.name: 23739XU
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.
dmi.modalias: dmi:bvnIBM:
dmi.product.name: 23739XU
dmi.product.
dmi.sys.vendor: IBM
gconf-keys: /desktop/
modified.
| Daniel Richard G. (skunk) wrote : | #1 |
| Apport retracing service (apport) wrote : | #2 |
| Changed in chromium-browser (Ubuntu): | |
| importance: | Undecided → Medium |
| tags: | removed: need-i386-retrace |
| Daniel Richard G. (skunk) wrote : | #6 |
The crash is due to AppArmor. Adding the following to the profile for /usr/lib/
capability sys_admin,
capability sys_chroot,
owner @{PROC}
owner @{PROC}
owner @{PROC}
@{PROC}
| Changed in chromium-browser (Ubuntu): | |
| status: | New → Invalid |
| information type: | Private → Public |
| Launchpad Janitor (janitor) wrote : | #7 |
Status changed to 'Confirmed' because the bug affects multiple users.
| Changed in apparmor (Ubuntu): | |
| status: | New → Confirmed |
| cooloutac (cooloutac) wrote : | #8 |
I have the same problem on Lubuntu 15.04. Firefox profile works but chromium does not.
Adding the suggested lines to the usr.bin.
[3622:3622:
Aborted (core dumped)
| cooloutac (cooloutac) wrote : | #9 |
sorry it actually fixed the issue, this time i downloaded the profile from github and added the lines to the top, before i added them towards the bottom. Thankyou.
| tags: | added: wily |
| Changed in apparmor (Ubuntu): | |
| importance: | Undecided → Medium |
| Chad Miller (cmiller) wrote : | #10 |
Please paste the output of this run in a Terminal.
dpkg -S $(grep -l /etc/apparmor.d/*)
| Changed in apparmor (Ubuntu): | |
| status: | Confirmed → Incomplete |
| Daniel Richard G. (skunk) wrote : | #11 |
Chad, what is the intended purpose of that command? Because it's mistranscribed:
$ dpkg -S $(grep -l /etc/apparmor.d/*)
grep: /etc/apparmor.
grep: /etc/apparmor.
grep: /etc/apparmor.
grep: /etc/apparmor.
grep: /etc/apparmor.
grep: /etc/apparmor.
grep: /etc/apparmor.
dpkg-query: error: --search needs at least one file name pattern argument
Use --help for help about querying packages.
Do you want to know which package owns the Chromium profile?
$ dpkg -S /etc/apparmor.
apparmor-
| Changed in apparmor (Ubuntu): | |
| status: | Incomplete → Confirmed |
| hda_launchpad (hda-me) wrote : | #12 |
This should be fixed, but fixed wisely. Consider this first: https:/
| tags: | added: xenial |
| Daniel Richard G. (skunk) wrote : | #13 |
Chromium continues to fail on Xenial with the title error message when the currently-shipped AppArmor profile is enforced.
I've updated my profile adjustments to address some new issues that have cropped up in recent builds of Chromium.
Everyone who wants to get things working again, please add the following lines to /etc/apparmor.
# From https:/
#include <abstractions/dbus>
capability sys_admin,
capability sys_chroot,
capability sys_ptrace,
owner @{PROC}
owner @{PROC}
owner @{PROC}
@{PROC}/[0-9]*/stat r,
@{PROC}
/bin/which ixr,


StacktraceTop: debug:: BreakDebugger () at ../../base/ debug/debugger_ posix.cc: 241 :LogMessage: :~LogMessage (this=0xbfb0235c, __in_chrg= <optimized out>) at ../../base/ logging. cc:639 :ZygoteHostImpl ::Init (this=0xb7d74d48, sandbox_cmd=...) at ../../content/ browser/ zygote_ host/zygote_ host_impl_ linux.cc: 182 command_ line=.. .) at ../../content/ browser/ browser_ main_loop. cc:178 :BrowserMainLoo p::EarlyInitial ization (this=0xb7d74ae8) at ../../content/ browser/ browser_ main_loop. cc:396
base::
logging:
content:
SetupSandbox (parsed_
content: