AppArmor && Chromium - what's breaking? (Trusty)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
AppArmor |
New
|
Undecided
|
Unassigned |
Bug Description
Currently running on Linux Mint, 17.3; uname -a -> Linux 3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu Oct 22 09:41:40 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
By default, I almost always enable AppArmor and all of the profiles it ships with.
With the AppArmor profile for chromium-browser ENABLED, Chromium fails to run; debugging presents the following:
Starting program: /usr/lib/
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_
[New Thread 0x7f6de7667700 (LWP 12978)]
[12968:
Program received signal SIGABRT, Aborted.
0x00007f6df2b42cc9 in __GI_raise (sig=sig@entry=6)
at ../nptl/
56 ../nptl/
While the AppArmor profile for Chromium is DISABLED, the browser opens normally:
Starting program: /usr/lib/
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_
[New Thread 0x7fdaadd1b700 (LWP 17588)]
...
[New Thread 0x7fda9af15700 (LWP 17649)]
Created new window in existing browser session.
...
[Thread 0x7fdad435ea00 (LWP 17584) exited]
[Inferior 1 (process 17584) exited normally]
If I try to generate a WORKING AppArmor profile (not the default shipped with apparmor-profiles) for Chromium, things break:
sudo aa-genprof chromium-browser
Traceback (most recent call last):
File "/usr/sbin/
apparmor.
File "/usr/lib/
raise AppArmorExcepti
apparmor.
Grepping for "DENIED" logs in syslog returns:
"kernel: [ 501.053368] audit: type=1400 audit(146048963
Apr 12 15:33:55 void kernel: [ 501.053474] audit: type=1400 audit(146048963
Apr 12 15:33:55 void kernel: [ 501.057446] audit: type=1400 audit(146048963
Apr 12 15:33:55 void kernel: [ 501.087666] audit: type=1400 audit(146048963
description: | updated |
description: | updated |
tags: | added: aa-tools |
description: | updated |
description: | updated |
Hi Emily,
This issue appears to be a duplicate of
https:/ /bugs.launchpad .net/bugs/ 1471645
Could you review that report, and see if the fix suggested therein addresses the issue for you?