mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1690] firejail 0.9.52 breaks qbittorrent 4.0.3 (qt5-base 5.10.0) #1143
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#1143
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 @trytip on GitHub (Dec 22, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1690
` ~ $ firejail qbittorrent
Reading profile /etc/firejail/qbittorrent.profile
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-devel.inc
Reading profile /etc/firejail/disable-passwdmgr.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 12775, child pid 12776
Warning: /sbin directory link was not blacklisted
Warning: /usr/sbin directory link was not blacklisted
Child process initialized in 111.25 ms
Parent is shutting down, bye...
`
worked fine with firejail 0.9.50 which i had to downgrade to for now. not sure what other info you would need. firejail --noprofile qbittorrent works with 0.9.52. it is broke in arch linux latest xfce and also in mint linux mate 17.3
@Vincent43 commented on GitHub (Dec 22, 2017):
Works for me without issues.
@Vincent43 commented on GitHub (Dec 22, 2017):
I believe you but info that you provided is insufficient to reproduce it on my machine (Archlinux, qt5-base 5.10.0, qbittorrent 4.0.3, firejail 0.9.52.) I see some errors you have on terminal. What's your desktop environment? Can you test in different DE? It works for me in KDE plasma 5.11.4.
@trytip commented on GitHub (Dec 23, 2017):
firejail 0.9.52 also breaks qbittorrent 3.3.16 (qt5 5.2.1) in mint mate 17.3
replacing the /etc/firejail/qbittorrent.profile from 9.50 to 9.52 makes it work. i get the same errors in both arch/xfce as in mint/mate17.3
for now i will stick with 9.50 until i can figure out why /etc/firejail/qbittorrent.profile works in 9.50 and not in 9.52
@Vincent43 commented on GitHub (Dec 23, 2017):
Try disabling options from
/etc/firejail/qbittorrent.profileone by one until you find those which brakes stuff.@Fred-Barclay commented on GitHub (Dec 24, 2017):
G'day @trytip . This isn't a case of no interest but little time. 😄 I at any rate have already been trying to replicate and fix this, but I haven't been able to duplicate it on my main Arch box (using MATE). I've already downloaded a Mint 17.3 MATE 64-bit iso but haven't been able to set up a virtual machine for it yet.
27/12/2017 update - unable to replicate on Mint 17.3 MATE either (qbittorrent 3.1.8, qt 4.8.6).
I suspect, though, that the line
memory-deny-write-executeis to blame, since it was added to the qbittorrent profile by me after the release of firejail 0.9.50, and you say that the qbittorrent 0.9.50 profile works even in firejail 0.9.52.memory-deny-write-executeis one of those features that can be a bit tricky to implement properly and may cause issues for others even if we don't catch them in testing.If you don't mind, I've reopened this. It's something we need to get fixed if possible.
@Vincent43 commented on GitHub (Dec 24, 2017):
@trytip Developers are waiting for you to provide more info as nobody has reproduced your issue yet and they don't have crystal ball. It's possible that it something specific to your system config. I told you what to do. The ball is on your side.
@trytip commented on GitHub (Dec 25, 2017):
@Fred-Barclay thanx for the interest. i'm told to provide more info but not sure what else to input i use arch/xfce updated latest and linux mint mate/17.3 arch is qbittorrent 4.0.3 and in mint is 3.3.16 (x64 system for both)
in both systems if i use qbittorrent.profile from 9.50 it works with 9.52. made a video for the mint session but i can reproduce it identically in arch/xfce
https://youtu.be/Mu6T1J09eWQ
i don't use system wide firejail configuration only for chrome/palemoon/qbittorrent and both browsers work with 9.52
not sure if it's relevant but i use an ipfilter.dat in qbittorrent loaded from .local/share/data/qBittorrent/ makes no difference if i start with or without
@Fred-Barclay commented on GitHub (Dec 27, 2017):
If you had time to work through the profile from 0.9.52 by commenting out the lines:
and then uncomment them one-by-one, starting qbittorrent each time until you find the line that kills it. That would be a huge help. 😄
(To comment, add a
#to the beginning of the line - for instance,shell nonewould become# shell none.)Cheers!
Fred
@GSF1200S commented on GitHub (Dec 27, 2017):
I'm not the OP but I also have firejail and qbittorrent on Arch Linux. I too found that qbittorrent failed to load with firejail 0.9.52.
First I checked when I updated Firejail and then went to a btrfs snapshot prior to that date checking qbittorrent.profile (which was 0.9.50's profile). I commented out the changes in the later profile and it worked, so then went one by one re-enabling them. For me memory-deny-write-execute prevented qbittorrent's interface from showing up, though terminal output didnt suggest anything catastrophic. Firejail's debug output didn't help me right off- I planned to dig through things more when I had time. @Fred-Barclay I can post firejails debug output later when I am home if that would help.
I had one other issue with the later profile- the python search function of qbittorrent didnt work if I had private-bin qbittorrent enabled in the profile- commenting it out saw that feature work again. I don't know if I should file a new bug report for this, whether its a known tradeoff for security, or if a bug report already exists- I haven't had a chance to look.
@Fred-Barclay commented on GitHub (Dec 27, 2017):
Thanks @GSF1200S ! That debug output would certainly be helpful.
Can you try adding
python*to the private-bin filter?@GSF1200S commented on GitHub (Dec 28, 2017):
Had to create another private-bin line for python*, but it works fine now.
Going to use a Debian pastebin because it isn't crap, but to clarify I am on Arch with this run: https://paste.debian.net/1002690/
@Fred-Barclay commented on GitHub (Dec 28, 2017):
Okay, can you copy this to ~/.config/firejail/qbittorrent.profile and see if everything works?
Thanks!
@GSF1200S commented on GitHub (Dec 28, 2017):
I just edited /etc/firejail/qbittorrent.profile directly (and made sure nothing existed in ~/.config/firejail)- works fine! Application loads, python search functions work, and everything else I tested.
@Fred-Barclay commented on GitHub (Dec 29, 2017):
Awesome, thanks @GSF1200S !
@trytip I think this should get everything so I'll close for now, but feel to comment/reopen if this doesn't work for you (or just to say that it does work). 😄 I would recommend you move back to 0.9.52 (if you haven't already) - you can use the updated, working qbittorrent profile by copying https://raw.githubusercontent.com/netblue30/firejail/281ad508084018c34acef505412450bfde0a6ab7/etc/qbittorrent.profile to ~./config/firejail/qbittorrent.profile (or editing the profile in /etc/).
Cheers and thanks for the report!
Fred
@trytip commented on GitHub (Dec 30, 2017):
thank you @Fred-Barclay and @GSF1200S the new qbittorrent.profile works. i also replaced it in etc/firejail of my ARCH Linux install.
thanx again for your patience and for the sandbox. this issue can remain CLOSED
@Fred-Barclay commented on GitHub (Dec 30, 2017):
That's great! Cheers!