[GH-ISSUE #5227] librewolf: cannot open new URLs into running instance 2 #2924

Closed
opened 2026-05-05 09:35:21 -06:00 by gitea-mirror · 7 comments
Owner

Originally created by @Lonniebiz on GitHub (Jul 1, 2022).
Original GitHub issue: https://github.com/netblue30/firejail/issues/5227

Firejail Version: 0.9.64.4
Debian 11
LibreWolf (AppImage): v101.0.1-1

This issue, that was previously fixed, is broken again after I updated Debian 11 early this morning:
https://github.com/netblue30/firejail/issues/4891

I noticed the firejail profiles package got updated and now this problem is back.

I was unable to open that "fixed" issue, so I created this new bug report to give it attention.

Originally created by @Lonniebiz on GitHub (Jul 1, 2022). Original GitHub issue: https://github.com/netblue30/firejail/issues/5227 Firejail Version: 0.9.64.4 Debian 11 LibreWolf (AppImage): [v101.0.1-1](https://gitlab.com/librewolf-community/browser/appimage/-/releases/v101.0.1-1) This issue, that was previously fixed, is broken again after I updated Debian 11 early this morning: https://github.com/netblue30/firejail/issues/4891 I noticed the firejail profiles package got updated and now this problem is back. I was unable to open that "fixed" issue, so I created this new bug report to give it attention.
gitea-mirror 2026-05-05 09:35:21 -06:00
Author
Owner

@rusty-snake commented on GitHub (Jul 1, 2022):

If you edit a .profile in /etc/firejail (against your advise) it's expected that it get overridden during update. Your custom changes should always go into a .local.

<!-- gh-comment-id:1172512067 --> @rusty-snake commented on GitHub (Jul 1, 2022): If you edit a .profile in /etc/firejail (against your advise) it's expected that it get overridden during update. Your custom changes should always go into a .local.
Author
Owner

@rusty-snake commented on GitHub (Jul 1, 2022):

0.9.64.4 is out of date and does not contain the fix. Update firejail (e.g. install it from backports) and report again.

<!-- gh-comment-id:1172513427 --> @rusty-snake commented on GitHub (Jul 1, 2022): 0.9.64.4 is out of date and does not contain the fix. Update firejail (e.g. install it from backports) and report again.
Author
Owner

@kmk3 commented on GitHub (Jul 1, 2022):

Closing in favor of #4891.

<!-- gh-comment-id:1172664521 --> @kmk3 commented on GitHub (Jul 1, 2022): Closing in favor of #4891.
Author
Owner

@kmk3 commented on GitHub (Jul 1, 2022):

@Lonniebiz commented on Jul 1:

I was unable to open that "fixed" issue, so I created this new bug report to
give it attention.

That's weird; please post a screenshot of that if it happens again.

<!-- gh-comment-id:1172664585 --> @kmk3 commented on GitHub (Jul 1, 2022): @Lonniebiz commented [on Jul 1](https://github.com/netblue30/firejail/issues/5227#issue-1291570016): > I was unable to open that "fixed" issue, so I created this new bug report to > give it attention. That's weird; please post a screenshot of that if it happens again.
Author
Owner

@rusty-snake commented on GitHub (Jul 1, 2022):

@mkm3 Only the author of an issue and accounts with write access to the repo can close issues. An closed issue can always be reopened by accounts with write access or by the the author if the issue was closed by the author.

<!-- gh-comment-id:1172667021 --> @rusty-snake commented on GitHub (Jul 1, 2022): @mkm3 Only the author of an issue and accounts with write access to the repo can close issues. An closed issue can always be reopened by accounts with write access or by the the author *if* the issue was closed by the author.
Author
Owner

@kmk3 commented on GitHub (Jul 1, 2022):

@rusty-snake commented on Jul 1:

Only the author of an issue and accounts with write access to the repo can
close issues. An closed issue can always be reopened by accounts with write
access or by the the author if the issue was closed by the author.

Interesting, I wasn't aware of the last part; thanks.

<!-- gh-comment-id:1172669401 --> @kmk3 commented on GitHub (Jul 1, 2022): @rusty-snake commented [on Jul 1](https://github.com/netblue30/firejail/issues/5227#issuecomment-1172667021): > Only the author of an issue and accounts with write access to the repo can > close issues. An closed issue can always be reopened by accounts with write > access or by the the author _if_ the issue was closed by the author. Interesting, I wasn't aware of the last part; thanks.
Author
Owner

@Lonniebiz commented on GitHub (Jul 1, 2022):

@rusty-snake : Thanks.

In Debian 11, I opened this file:
/etc/apt/sources.list

And added this line to it:
deb http://deb.debian.org/debian bullseye-backports main

Then, I upgraded filejail to version 0.9.70 :
sudo apt update ; sudo apt install firejail/bullseye-backports firejail-profiles/bullseye-backports

After, this I relaunched the LibreWolf AppImage using firejail and now the issue is resolved; I can launch additional pages in new tabs.

<!-- gh-comment-id:1172703949 --> @Lonniebiz commented on GitHub (Jul 1, 2022): @rusty-snake : Thanks. **In Debian 11, I opened this file:** /etc/apt/sources.list **And added this line to it:** deb http://deb.debian.org/debian bullseye-backports main **Then, I upgraded filejail to version 0.9.70 :** sudo apt update ; sudo apt install firejail/bullseye-backports firejail-profiles/bullseye-backports After, this I relaunched the LibreWolf [AppImage](https://gitlab.com/librewolf-community/browser/appimage/-/releases/v101.0.1-1) using firejail and now the issue is resolved; I can launch additional pages in new tabs.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#2924
No description provided.