When evince is executed, an additional process (evinced) is started via dbus. This makes it quite difficult to jail evince in applications like firejail, since the evinced process is started not as a child but as its own process outside of the jail. Although this is not an issue for evince on its own, I would like to know why evince behaves like this. From experiments I found out that if I remove the evince.service file or block access to the dbus socket, evince still seems to works as expected without evinced. Another way to prevent this seems to be to use the --disable-dbus flag. Please explain why evince uses a daemon process and what exactly evinced does. Thank you
Attachment:
signature.asc
Description: OpenPGP digital signature