mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2028] Chrome native notifications are broken #1368
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#1368
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 @infokiller on GitHub (Jul 5, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2028
Chrome supports native Linux notifications for some time (article), and they worked for me before starting it with firejail.
Now it seems that Chrome uses its own notification system, even if I force it to use native Linux notifications.
After doing some testing, I think the issue is that chrome has
nodbusin its profile (via chromium-common.profile).Is there a way for me to disable the
nodbuscommand using a local chrome profile (~/.config/firejail/chrome.profile)?I know that I can rewrite the whole profile locally, but I would much rather have something like:
Or something similar.
Thanks!
@Fred-Barclay commented on GitHub (Jul 5, 2018):
Hi @infokiller Yes, you can create the file
/etc/firejail/chrome.localwith the lineand this should allow dbus access in the sandbox and (hopefully) native notifications for Chrome.
However, it's worthwhile noting that dbus can be used to escape the firejail sandbox, so hypothetically this lowers your security. You still have all the other features of firejail, but if the sandbox were successfully escaped then they might have little or no effect.
@infokiller commented on GitHub (Jul 5, 2018):
Thanks a lot @Fred-Barclay!
@Fred-Barclay commented on GitHub (Jul 5, 2018):
UPDATE: I'm sorry, the file name should be
/etc/firejail/chromium-common.localthat way no matter if you use chromium, or google-chrome stable, beta, or unstable, you'll get native notifications.If you want Chrome-only, then
/etc/firejail/google-chrome.localis the way to go.