Github messages for voidlinux
 help / color / mirror / Atom feed
From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Firejail: Firefox profile broken
Date: Wed, 29 Jul 2020 19:00:09 +0200	[thread overview]
Message-ID: <20200729170009.CgtG5bDoNoELxjOjoey7cZMgnYaFzwjnnf23zmJ4wUw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20226@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 2659 bytes --]

Closed issue by howtologinquickwiththirtyninecharacters on void-packages repository

https://github.com/void-linux/void-packages/issues/20226

Description:
### System

* xuname:  
  *Void 5.4.26_1 x86_64 GenuineIntel uptodate rrFFFF*
* package:  
  *firejail-0.9.62_1*

### Expected behavior

Upon executing `firejail firefox` Firefox starts and remains listed in the output of `firejail --top`

### Actual behavior

Firefox starts, appears for a brief moment in the output of `firejail --top`, then closes without ever opening a window. See footnote for the output of the command.

### Steps to reproduce the behavior

1. Install Firejail and Firefox (*firefox-74.0_1* at the time of writing this)
2. (important) Make sure no other Firefox process is running
3. Run `firejail --top` on a terminal
4. (optional) Run `firejail watch echo 1` on a different terminal and confirm that it appears in the `firejail --top` output to make sure Firejail works as expected for other software
4. Run `firejail firefox` on a different terminal, confirm that Firefox does not start and examine the output of the command

### Footnotes

Installing AppArmor to silence the Firejail warnings doesn't fix this issue. Other X software such as HexChat and Chromium can run inside Firejail with no issues.

This was working some time ago but I can't remember the exact Firefox and Firejail versions. I think it may have been around the time of Firefox 70.

Output of the command:

~~~
Reading profile /etc/firejail/firefox.profile
Reading profile /etc/firejail/whitelist-usr-share-common.inc
Reading profile /etc/firejail/firefox-common.profile
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-devel.inc
Reading profile /etc/firejail/disable-exec.inc
Reading profile /etc/firejail/disable-interpreters.inc
Reading profile /etc/firejail/disable-programs.inc
Reading profile /etc/firejail/whitelist-common.inc
Reading profile /etc/firejail/whitelist-var-common.inc
Parent pid 4188, child pid 4189
Warning: An abstract unix socket for session D-BUS might still be available. Use --net or remove unix from --protocol set.
Warning: /sbin directory link was not blacklisted
Warning: /usr/sbin directory link was not blacklisted
Post-exec seccomp protector enabled
Seccomp list in: !chroot, check list: @default-keep, prelist: unknown,
Warning: Cannot confine the application using AppArmor.
Maybe firejail-default AppArmor profile is not loaded into the kernel.
As root, run "aa-enforce firejail-default" to load it.
Child process initialized in 118.78 ms

Parent is shutting down, bye...
~~~

      parent reply	other threads:[~2020-07-29 17:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-20  2:40 [ISSUE] " howtologinquickwiththirtyninecharacters
2020-03-20 13:04 ` daniel-eys
2020-07-29 17:00 ` Duncaen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200729170009.CgtG5bDoNoELxjOjoey7cZMgnYaFzwjnnf23zmJ4wUw@z \
    --to=duncaen@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).