mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #4158] Dunst notifications with Signal-Desktop not working #2557
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#2557
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 @vwheezy on GitHub (Apr 2, 2021).
Original GitHub issue: https://github.com/netblue30/firejail/issues/4158
Bug and expected behavior
sudo firecfgto create profiles for my applications and running signal-desktop, notifications through dunst no longer work.No profile and disabling firejail
--noprofileand through/usr/bin/signal-desktopexhibits the correct behavior.Reproduce
Steps to reproduce the behavior:
firejail signal-desktopEnvironment
Additional context
Tried overriding the profile with some dbus options knowing that dunst uses it (I think).
I have a feeling I just don't know enough about DBus or firejail itself to resolve this myself. Sorry if this belongs in questions and thank you!
debug output
@ghost commented on GitHub (Apr 3, 2021):
From your debug output:
Ignoring "dbus-system.talk org.freedesktop.Notifications".filteringinstead;sessionbus instead of the system bus[...]
Error getpwuid: main.c:236 init_cfg: SuccessTry adding group and passwd to private-etc.
Proposed file for testing: use a .local file for overrides (you can drop including the default signal-desktop.profile this way) e.g. /home/vwheezy/.config/firejail/signal-desktop.local
What happens when you use the above signal-desktop.local?
@vwheezy commented on GitHub (Apr 4, 2021):
Sorry for the late response but it worked perfectly! Thank you so much.
Before I close this though, could you clarify and/or point to where I can get this clarification?
ignore nodbusoption which basically contradictsdbus-system.talk org.freedesktop.Notifications. Is this correct?dbus-userinstead ofdbus-system? I can imagine that it's safer to only allow the user dbus instead of the system-wide one.As I said before, my knowledge on this stuff is definitely lacking. I'll look up a dbus article, but thanks so much again for your help!
@rusty-snake commented on GitHub (Apr 4, 2021):
nodbusis deprecated and no longer used in any upstream profile. Therefore aignore nodbushas no effect as there is nonodbus. You need to useignore dbus-user noneinstead.dbus-user.talk org.freedesktop.Notifications(not-system) has only a effect ifdbus-user filteris set. If there is nodbus-user XXXat all, everything is allowed and ifdbus-user noneis used (as in signal-desktop) everything is forbidden (byblacklisting the socket).@vwheezy commented on GitHub (Apr 4, 2021):
Thanks again!
I was just trying to understand the difference between
dbus-useranddbus-system. As I mentioned before, this is probably outside the scope of this issue. I'll look up an article.@rusty-snake commented on GitHub (Apr 4, 2021):
src: https://pythonhosted.org/txdbus/dbus_overview.html
@ghost commented on GitHub (Apr 4, 2021):
@rusty-snake Should we bring in these changes to allow D-Bus notifications? I took the liberty to prepare a PR to do so.
@vwheezy22 If we decide to integrate the changes into the default signal-desktop.profile you can drop them from your signal-desktop.local when upgrading your firejail in the future, just a FYI