mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1615] Enabling AppArmor support for Chrome disables hardware accelerated rendering #1081
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#1081
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jwittlincohen on GitHub (Oct 25, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1615
I'm not sure if this is a bug or an inevitable consequence of enabling AppArmor support. However, I noticed that after enabling AppArmor support in google-chrome.local, I suffered terrible tearing, regardless of the "Smooth Scroll" setting in chrome:/flags. The issue appears to be that enabling AppArmor disables all hardware accelerated rendering. I made this bug report as I wasn't able to find any discussion of this issue on the Issue tracker or Google.
I did not change the google-chrome.profile at all. My only changes were made to google-chrome.local, and they are the following:
System Information:
Debian Testing (Buster)
Kernel 4.13.0-1-amd64 #1 SMP Debian 4.13.4-2 (2017-10-15) x86_64 GNU/Linux
Firejail Version 0.9.50-3
Chrome Version 62.0.3202.62
Nvidia Driver 375.82-5 (GTX 1070)
#With AppArmor
Graphics Feature Status
• Canvas: Software only, hardware acceleration unavailable
• CheckerImaging: Disabled
• Flash: Software only, hardware acceleration unavailable
• Flash Stage3D: Software only, hardware acceleration unavailable
• Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable
• Compositing: Software only, hardware acceleration unavailable
• Multiple Raster Threads: Enabled
• Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
• Rasterization: Software only, hardware acceleration unavailable
• Video Decode: Software only, hardware acceleration unavailable
• Video Encode: Software only, hardware acceleration unavailable
• WebGL: Hardware accelerated but at reduced performance
• WebGL2: Unavailable
##Without AppArmor
Graphics Feature Status
• Canvas: Hardware accelerated
• CheckerImaging: Disabled
• Flash: Hardware accelerated
• Flash Stage3D: Hardware accelerated
• Flash Stage3D Baseline profile: Hardware accelerated
• Compositing: Hardware accelerated
• Multiple Raster Threads: Enabled
• Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
• Rasterization: Software only. Hardware acceleration disabled
• Video Decode: Software only, hardware acceleration unavailable
• Video Encode: Software only, hardware acceleration unavailable
• WebGL: Hardware accelerated
• WebGL2: Hardware accelerated
@jwittlincohen commented on GitHub (Oct 27, 2017):
Here are the apparmor logs when I enable apparmor integration in Chrome profile:
In particular, this one looks particularly interesting:
Oct 27 10:33:40 kernel: audit: type=1400 audit(1509114820.794:2972): apparmor="DENIED" operation="open" profile="firejail-default" name="/proc/modules" pid=26067 comm="nvidia-modprobe" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0I suffered an unrelated issue with apparmor in which running Totem with the respective apparmor profile enforced resulted in a segmentation fault. One of the Apparmor errors was this:
One of the Debian AppArmor maintainers helped resolve the issue. I just had to add
#include <abstractions/nvidia>to the usr.bin.totem profile. Perhaps his solution may help with this issue?The full bug report is here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879900
@rusty-snake commented on GitHub (Jun 26, 2019):
Should we do anything here or should we close.
@Vincent43 commented on GitHub (Jun 27, 2019):
This report is quite dated. Firejail apparmor profile allows reading
/procnow. I don't see anything from<abstractions/nvidia>not already covered.