github-starred/firejail
2
0
Fork 0
mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00
Code Issues 531 Projects Packages Wiki Activity Actions 6

[GH-ISSUE #3817] playonlinux in firejail - internet connection issues? #2409

New issue
Closed
opened 2026-05-05 09:05:07 -06:00 by gitea-mirror · 8 comments
gitea-mirror commented 2026-05-05 09:05:07 -06:00
Owner
Copy link

Originally created by @Rosika2 on GitHub (Dec 14, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3817

Environment

Linux distribution and version: Lubuntu 18.04.5 KTS, 64 bit
Firejail version 0.9.64

Hello @rusty-snake,

so sorry to bother you again but there seems to be another problem when I run playonlinux within firejail.

On https://github.com/netblue30/firejail/issues/3800 you have me a good piece of advice running the command
firejail '--noblacklist=/tmp/.wine-*' --private=media/rosika/f14a27c2-0b49-4607-94ea-2e56bbf76fe1/DATEN-PARTITION/PLAYONLINUX playonlinux
which worked well.
Yet what I did at the time was running the programme "Notepad++". No problems there.

Now I wanted to install a tax-programme which didn´t go well.
In fact the installation process stopped at a certain point.

When I needed to insert the respective activation key the installation stopped - apparently because no internet connection could be established.
The key needs to be checked by the server of the tax programme I think.

As a consequence I tried the command
firejail '--noblacklist=/tmp/.wine-*' --noprofile --private=/home/rosika/Desktop/DATEN-PARTITION/Dokumente/versuch_für_playonlinux/ playonlinux

, so basically the same command plus "--noprofile".
That one did work. After inserting the registration code the installation proceeded as the code got checked by the server.
So internet connection was o.k.

The issue of internet connection is a mere guess of mine. But I couldn´t explain the difference of the two commands otherwise.

On https://gist.github.com/Rosika2/61f82c51565e48c89ad7d7aaa7ae7bfe I posted the output of the two commands as seen by the terminal. I hope it may be of some help.

I´d be glad if this issue could be solved as well.

Thank you so much in advance.

Many greetings.
Rosika

Originally created by @Rosika2 on GitHub (Dec 14, 2020). Original GitHub issue: https://github.com/netblue30/firejail/issues/3817 Environment Linux distribution and version: Lubuntu 18.04.5 KTS, 64 bit Firejail version 0.9.64 Hello @rusty-snake, so sorry to bother you again but there seems to be another problem when I run playonlinux within firejail. On https://github.com/netblue30/firejail/issues/3800 you have me a good piece of advice running the command `firejail '--noblacklist=/tmp/.wine-*' --private=media/rosika/f14a27c2-0b49-4607-94ea-2e56bbf76fe1/DATEN-PARTITION/PLAYONLINUX playonlinux ` which worked well. Yet what I did at the time was running the programme "Notepad++". No problems there. Now I wanted to install a tax-programme which didn´t go well. In fact the installation process stopped at a certain point. When I needed to insert the respective activation key the installation stopped - **apparently** because no internet connection could be established. The key needs to be checked by the server of the tax programme I think. As a consequence I tried the command `firejail '--noblacklist=/tmp/.wine-*' --noprofile --private=/home/rosika/Desktop/DATEN-PARTITION/Dokumente/versuch_für_playonlinux/ playonlinux` , so basically the same command plus "**--noprofile**". That one did work. After inserting the registration code the installation proceeded as the code got checked by the server. So internet connection was o.k. The issue of internet connection is a mere guess of mine. But I couldn´t explain the difference of the two commands otherwise. On https://gist.github.com/Rosika2/61f82c51565e48c89ad7d7aaa7ae7bfe I posted the output of the two commands as seen by the terminal. I hope it may be of some help. I´d be glad if this issue could be solved as well. Thank you so much in advance. Many greetings. Rosika
gitea-mirror commented 2026-05-05 09:05:10 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (Dec 14, 2020):

This time I unfortunately have no idea what it could be 😞 . Because --noprofile works, the issues is in the profile. Can you copy the profile (cp /etc/firejail/playonlinux.profile ~/playonlinux.profile) and comment everything (noblacklist * and include allow-*.inc can be left uncommented). Then use firejail '--noblacklist=/tmp/.wine-*' --private=/home/rosika/Desktop/DATEN-PARTITION/Dokumente/versuch_für_playonlinux/ --profile=~/playonlinux.profile playonlinux to start and test it. Now uncomment line for line (or a block of lines) to see which line is causing it (and don't forget to save before testing ;) ).

If it is seccomp, journalctl --reverse | grep SECCOMP will show errors containg "playonlinux".

(Maybe it is here better to try from the other direction, meaning from a failing uncommented profile to a commented profile, as IDK if such activation-server like many tries with one key in a short time range.)

<!-- gh-comment-id:744452411 --> @rusty-snake commented on GitHub (Dec 14, 2020): This time I unfortunately have no idea what it could be :disappointed: . Because `--noprofile` works, the issues is in the profile. Can you copy the profile (`cp /etc/firejail/playonlinux.profile ~/playonlinux.profile`) and comment everything (`noblacklist *` and `include allow-*.inc` can be left uncommented). Then use `firejail '--noblacklist=/tmp/.wine-*' --private=/home/rosika/Desktop/DATEN-PARTITION/Dokumente/versuch_für_playonlinux/ --profile=~/playonlinux.profile playonlinux` to start and test it. Now uncomment line for line (or a block of lines) to see which line is causing it (and don't forget to save before testing ;) ). If it is `seccomp`, `journalctl --reverse | grep SECCOMP` will show errors containg "playonlinux". (Maybe it is here better to try from the other direction, meaning from a failing uncommented profile to a commented profile, as IDK if such activation-server like many tries with one key in a short time range.)
gitea-mirror commented 2026-05-05 09:05:11 -06:00
Author
Owner
Copy link

@Rosika2 commented on GitHub (Dec 14, 2020):

@rusty-snake:

Hello once again and thank you so much for your help.

Following your instructions (it took quite a while) I found out that it is seccomp which has to be commented.
Any other entry may stay as they are in the /etc/firejail/playonlinux.profile.
And indeed I found the following:

journalctl --reverse | grep SECCOMP
Dez 14 15:26:23 rosika-Lenovo-H520e audit[32287]: SECCOMP auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=32287 comm="wineserver" exe="/home/rosika/.PlayOnLinux/wine/linux-x86/4.0.4/bin/wineserver" sig=31 arch=40000003 syscall=26 compat=1 ip=0xf7f42079 code=0x0

So thanks a lot again for making things work alright.

Many greetings abd stay safe.
Rosika

<!-- gh-comment-id:744515466 --> @Rosika2 commented on GitHub (Dec 14, 2020): @rusty-snake: Hello once again and thank you so much for your help. Following your instructions (it took quite a while) I found out that it is `seccomp` which has to be commented. Any other entry may stay as they are in the `/etc/firejail/playonlinux.profile`. And indeed I found the following: ``` journalctl --reverse | grep SECCOMP Dez 14 15:26:23 rosika-Lenovo-H520e audit[32287]: SECCOMP auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=32287 comm="wineserver" exe="/home/rosika/.PlayOnLinux/wine/linux-x86/4.0.4/bin/wineserver" sig=31 arch=40000003 syscall=26 compat=1 ip=0xf7f42079 code=0x0 ``` So thanks a lot again for making things work alright. Many greetings abd stay safe. Rosika
gitea-mirror commented 2026-05-05 09:05:12 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (Dec 14, 2020):

More secure is to whitelist only this syscall and keep the seccomp blacklist. firejail --debug-syscalls | grep 26 shows msync, but arch=40000003 is 32bit IIRC so ausyscall i686 26 shows ptrace. seccomp !ptrace or allow-debuggers (as in wine) should be the way to go.

<!-- gh-comment-id:744530527 --> @rusty-snake commented on GitHub (Dec 14, 2020): More secure is to whitelist only this syscall and keep the seccomp blacklist. `firejail --debug-syscalls | grep 26` shows `msync`, but `arch=40000003` is 32bit IIRC so `ausyscall i686 26` shows `ptrace`. `seccomp !ptrace` or `allow-debuggers` (as in wine) should be the way to go.
gitea-mirror commented 2026-05-05 09:05:12 -06:00
Author
Owner
Copy link

@Rosika2 commented on GitHub (Dec 14, 2020):

@rusty-snake:

Hi, thanks for the additional info which sounds very interesting.
But you got me here. I´m afraid I lack the respective knowledge to proceed in a way you suggested.

Yet I read up a bit on the matter consulting the man-pages and could follow to a certain extent.

−−allow-debuggers
Allow tools such as strace and gdb inside the sandbox by whitelisting system calls ptrace and
process_vm_readv.

So might the following command be the right one?

firejail --allow-debuggers '--noblacklist=/tmp/.wine-*' --private=/home/rosika/Desktop/DATEN-PARTITION/Dokumente/versuch_für_playonlinux/ playonlinux

Thanks a lot.
Greetings.
Rosika

<!-- gh-comment-id:744563831 --> @Rosika2 commented on GitHub (Dec 14, 2020): @rusty-snake: Hi, thanks for the additional info which sounds very interesting. But you got me here. I´m afraid I lack the respective knowledge to proceed in a way you suggested. Yet I read up a bit on the matter consulting the man-pages and could follow to a certain extent. ``` −−allow-debuggers Allow tools such as strace and gdb inside the sandbox by whitelisting system calls ptrace and process_vm_readv. ``` So might the following command be the right one? `firejail --allow-debuggers '--noblacklist=/tmp/.wine-*' --private=/home/rosika/Desktop/DATEN-PARTITION/Dokumente/versuch_für_playonlinux/ playonlinux` Thanks a lot. Greetings. Rosika
gitea-mirror commented 2026-05-05 09:05:13 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (Dec 14, 2020):

Yes, looks good.

You can also create a playonlinux.local for all these additions.

<!-- gh-comment-id:744567994 --> @rusty-snake commented on GitHub (Dec 14, 2020): Yes, looks good. You can also create a playonlinux.local for all these additions.
gitea-mirror commented 2026-05-05 09:05:14 -06:00
Author
Owner
Copy link

@Rosika2 commented on GitHub (Dec 14, 2020):

Hi,

firejail --allow-debuggers '--noblacklist=/tmp/.wine-*' --private=/home/rosika/Desktop/DATEN-PARTITION/Dokumente/versuch_für_playonlinux/ playonlinux
didn´t work after all.
The same problem seems to be there. The setup stops at the entry of the code. So internet connection seems to be refused once again.
Sorry about that.

Cheers.
Rosika

<!-- gh-comment-id:744574336 --> @Rosika2 commented on GitHub (Dec 14, 2020): Hi, `firejail --allow-debuggers '--noblacklist=/tmp/.wine-*' --private=/home/rosika/Desktop/DATEN-PARTITION/Dokumente/versuch_für_playonlinux/ playonlinux` didn´t work after all. The same problem seems to be there. The setup stops at the entry of the code. So internet connection seems to be refused once again. Sorry about that. Cheers. Rosika
gitea-mirror commented 2026-05-05 09:05:14 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (Dec 14, 2020):

Hmmm, assuming that there are still seccomp errors in the syslog. Either allow-debuggers didn't applied (maybe because of the 32bit syscalls) or something else. Anyway --ignore=seccomp --seccomp.drop=@default would be fine if it works.

<!-- gh-comment-id:744634983 --> @rusty-snake commented on GitHub (Dec 14, 2020): Hmmm, assuming that there are still seccomp errors in the syslog. Either allow-debuggers didn't applied (maybe because of the 32bit syscalls) or something else. Anyway `--ignore=seccomp --seccomp.drop=@default` would be fine if it works.
gitea-mirror commented 2026-05-05 09:05:14 -06:00
Author
Owner
Copy link

@Rosika2 commented on GitHub (Dec 15, 2020):

Hello @rusty-snake:

Thank you so much for your patience.

In fact your latest command works as desired. Perfect.
So I punched in
firejail --ignore=seccomp --seccomp.drop=@default '--noblacklist=/tmp/.wine-*' --private=/media/rosika/f14a27c2-0b49-4607-94ea-2e56bbf76fe1/DATEN-PARTITION/Dokumente/versuch_für_playonlinux/ playonlinux

The playonlinux GUI opened up alright and this time the installation process of the tax programme would have proceeded (I aborted as it was a test now). The registration code I typed in was checked indeed which means internet connectivity is alright now.

So that´s the command I will stick to in the future.

Thanks again for your really great help. I´m so glad now.

All the best and have nice and healthy holidays.
Many greetings from Rosika

<!-- gh-comment-id:745333525 --> @Rosika2 commented on GitHub (Dec 15, 2020): Hello @rusty-snake: Thank you so much for your patience. In fact your latest command works as desired. Perfect. So I punched in `firejail --ignore=seccomp --seccomp.drop=@default '--noblacklist=/tmp/.wine-*' --private=/media/rosika/f14a27c2-0b49-4607-94ea-2e56bbf76fe1/DATEN-PARTITION/Dokumente/versuch_für_playonlinux/ playonlinux` The playonlinux GUI opened up alright and this time the installation process of the tax programme would have proceeded (I aborted as it was a test now). The registration code I typed in was checked indeed which means internet connectivity is alright now. So that´s the command I will stick to in the future. Thanks again for your really great help. I´m so glad now. All the best and have nice and healthy holidays. Many greetings from Rosika
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
serialize_remounts_v2
landlock_v4
landlock
release-0.9.64
release-0.9.62
gitlab_ci
LTSbase
fred_ctests
docs
0.9.80
0.9.80-rc1
0.9.78
0.9.76
0.9.76-rc4
0.9.76-rc3
0.9.76-rc2
0.9.76-rc1
0.9.74
landlock-split
0.9.72
0.9.72rc1
0.9.70
0.9.68
0.9.68rc1
0.9.66
0.9.66rc1
0.9.64.4
0.9.64.2
0.9.64
0.9.64rc1
0.9.62.4
0.9.62.2
0.9.62
0.9.56.2-LTS
0.9.60
0.9.60-rc1
0.9.58.2
0.9.58
0.9.58-rc1
0.9.56-LTS-release
0.9.56-LTS
0.9.56
0.9.56-rc1
0.9.54
0.9.54-rc2
0.9.54-rc1
0.9.52
0.9.38.12
0.9.50
0.9.50-rc1
0.9.48
0.9.46
0.9.46-rc1
0.9.44.10
0.9.44.8
0.9.44.6
0.9.38.10
0.9.44.4
0.9.38.8
0.9.44.2
0.9.44
0.9.44-rc1
0.9.38.4
0.9.42
0.9.42-rc2
0.9.38.2
0.9.42-rc1
disable-globalcfg
0.9.40
0.9.40-rc1
0.9.38
0.9.38-rc1
0.9.36
0.9.36-rc1
0.9.34
0.9.34-rc1
0.9.32
0.9.32-rc1
0.9.30
0.9.30-rc1
Labels
Clear 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

Mirrored from GitHub Pull Request

  
question

   
question_old

   
removal

   
runtime-permissions

   
sandbox-ipc

   
security

   
stale

   
wiki

   
wiki

   
wontfix

   
wordpress

   
workaround
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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#2409
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?