mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #6031] lximage-qt: Could not create AF_NETLINK socket (private-tmp) #3160
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#3160
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 @glu8716 on GitHub (Oct 3, 2023).
Original GitHub issue: https://github.com/netblue30/firejail/issues/6031
Description
LXImage-Qt doesn't start if Firejail is on with a "Could not create AF_NETLINK socket" error.
Steps to Reproduce
firejail lximage-qt.Expected behavior
Actual behavior
Behavior without a profile
If I start the program without Firejail it works.
Additional context
I haven't touched anything in the Firejail configs, it's the standard installation.
Environment
Checklist
/usr/bin/vlc) "fixes" it).https://github.com/netblue30/firejail/issues/1139)browser-allow-drm yes/browser-disable-u2f noinfirejail.configto allow DRM/U2F in browsers.--profile=PROFILENAMEto set the right profile. (Only relevant for AppImages)Log
@ghost commented on GitHub (Oct 3, 2023):
f3fc98499f/etc/profile-a-l/lximage-qt.profile (L31)Please test with the following:
@glu8716 commented on GitHub (Oct 3, 2023):
The error about AF_NETLINK is gone, but the program still doesn't run.
@ghost commented on GitHub (Oct 3, 2023):
So we don't need netlink in the protocol, which is a good thing for a sandbox.
While you were testing I installed lximage-xt on my Arch Linux box. Here it starts and seems to work as expected. I also get those AF_NETLINK warnings but not the D-Bus related last lines from your output:
The lximage-qt profile doesn't restrict dbus (not even the system bus) so I'm not sure what's that about. What happens when you run
firejail --noprofile /usr/bin/lximage-qt?@glu8716 commented on GitHub (Oct 3, 2023):
If I run
firejail --noprofile /usr/bin/lximage-qtthe program starts fine. Those two error messages are still present, but the program works.@ghost commented on GitHub (Oct 3, 2023):
Odd. But I'm not familiar with Artix, especially not regarding its D-Bus functionality. Perhaps @kmk3 can assist, IIRC they're on Artix too. Is DBUS_SESSION_BUS_ADDRESS exported correctly? Is the user socket actually created on your system? Apologies for not being more helpfull, but for now I just cannot reproduce.
@glu8716 commented on GitHub (Oct 3, 2023):
Don't worry, thanks for the help!
The
envoutput shows the following:DBUS_SESSION_BUS_ADDRESS=unix:path=/tmp/dbus-JiaSDiRKLG,guid=5d2afdf9a5c32fa92f9c8cb8651ae04eThe file is actually there. Don't know if this is normal as I'm not an expert user.
@ghost commented on GitHub (Oct 3, 2023):
That might explain things. There's a
private-tmpin lximage-xt.profile. Usually the DBUS_SESSION_BUS_ADDRESS points to /run/user/1000/bus. Well, usually might be to strong, but it is what Firejail assumes AFAICT, in ${RUNUSER}. So tryignore private-tmpto confirm that does fix it. If so I'd suggest trying to change whatever Artix uses to set DBUS_SESSION_BUS_ADDRESS to a path under /tmp. There's probably more profiles that could break similarly.@glu8716 commented on GitHub (Oct 3, 2023):
You are right, adding
ignore private-tmpworks! Thanks a lot =)As for the dbus path I honestly have no idea as I've never dealt with it. It might not be Artix but the init system (I use s6) or SDDM (I know SDDM uses the /tmp folder for the XAUTHORITY file too for example).
Anyway I've only had this problem with the lximage-qt profile so far, so if I only have to add an exception for it it's not a big deal I guess.
@kmk3 commented on GitHub (Oct 4, 2023):
The socket also appears on /tmp for me with dwm on Artix.
My guess: dbus is started before whatever it is that sets up
$XDG_RUNTIME_DIR, so it falls back to /tmp.I think that (e)logind is supposed to do this.
The dbus package appears to depend on (e)logind while the elogind service
depends on (/starts before) dbus, which could explain the issue.
Though I'm not sure and I don't really use dbus.
If anyone finds out more details about this, feel free to post here.
@ghost commented on GitHub (Oct 4, 2023):
That's nice. At least you're aware of this now. Thanks a lot for bringing all this to our attention!