[GH-ISSUE #4925] flameshot complaining about AF_NETLINK socket #2819

Closed
opened 2026-05-05 09:28:19 -06:00 by gitea-mirror · 8 comments
Owner

Originally created by @jose1711 on GitHub (Feb 9, 2022).
Original GitHub issue: https://github.com/netblue30/firejail/issues/4925

Description

flameshot generates the following errors while running:

Could not create AF_NETLINK socket (Operation not supported)

Steps to Reproduce

  1. Install and run flameshot from terminal emulator
  2. Watch the terminal output

Expected behavior

No errors should appear.

Actual behavior

Could not create AF_NETLINK socket (Operation not supported)
Could not create AF_NETLINK socket (Operation not supported)
Could not create AF_NETLINK socket (Operation not supported)
Could not create AF_NETLINK socket (Operation not supported)
Could not create AF_NETLINK socket (Operation not supported)

Messages are also written to systemd's journal:

$ journalctl -b 0 | grep -c NETLINK
Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.
      Pass -q to turn off this notice.
491

Behavior without a profile

If run with --noprofile the issue disappears. Another way is to add netlink to protocol list.

Environment

  • Arch Linux x86_64
  • Firejail version = current master

Checklist

  • The issues is caused by firejail (i.e. running the program by path (e.g. /usr/bin/vlc) "fixes" it).
  • I can reproduce the issue without custom modifications (e.g. globals.local).
  • The program has a profile. (If not, request one in https://github.com/netblue30/firejail/issues/1139)
  • The profile (and redirect profile if exists) hasn't already been fixed upstream.
  • I have performed a short search for similar issues (to avoid opening a duplicate).
    • I'm aware of browser-allow-drm yes/browser-disable-u2f no in firejail.config to allow DRM/U2F in browsers.
  • I used --profile=PROFILENAME to set the right profile. (Only relevant for AppImages)
Originally created by @jose1711 on GitHub (Feb 9, 2022). Original GitHub issue: https://github.com/netblue30/firejail/issues/4925 ### Description `flameshot` generates the following errors while running: ``` Could not create AF_NETLINK socket (Operation not supported) ``` ### Steps to Reproduce 1. Install and run `flameshot` from terminal emulator 2. Watch the terminal output ### Expected behavior No errors should appear. ### Actual behavior ``` Could not create AF_NETLINK socket (Operation not supported) Could not create AF_NETLINK socket (Operation not supported) Could not create AF_NETLINK socket (Operation not supported) Could not create AF_NETLINK socket (Operation not supported) Could not create AF_NETLINK socket (Operation not supported) ``` Messages are also written to `systemd`'s journal: ``` $ journalctl -b 0 | grep -c NETLINK Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages. Pass -q to turn off this notice. 491 ``` ### Behavior without a profile If run with `--noprofile` the issue disappears. Another way is to add `netlink` to protocol list. ### Environment - Arch Linux x86_64 - Firejail version = current master ### Checklist <!-- Note: Items are checked with an "x", like so: - [x] This is a checked item. --> - [x] The issues is caused by firejail (i.e. running the program by path (e.g. `/usr/bin/vlc`) "fixes" it). - [x] I can reproduce the issue without custom modifications (e.g. globals.local). - [x] The program has a profile. (If not, request one in `https://github.com/netblue30/firejail/issues/1139`) - [x] The profile (and redirect profile if exists) hasn't already been fixed [upstream](https://github.com/netblue30/firejail/tree/master/etc). - [x] I have performed a short search for similar issues (to avoid opening a duplicate). - [ ] I'm aware of `browser-allow-drm yes`/`browser-disable-u2f no` in `firejail.config` to allow DRM/U2F in browsers. - [ ] I used `--profile=PROFILENAME` to set the right profile. (Only relevant for AppImages)
gitea-mirror 2026-05-05 09:28:19 -06:00
  • closed this issue
  • added the
    notourbug
    label
Author
Owner

@rusty-snake commented on GitHub (Feb 9, 2022):

Is anything broken?

<!-- gh-comment-id:1034316438 --> @rusty-snake commented on GitHub (Feb 9, 2022): Is anything broken?
Author
Owner

@jose1711 commented on GitHub (Feb 9, 2022):

No, it looks to be working just fine.

<!-- gh-comment-id:1034323299 --> @jose1711 commented on GitHub (Feb 9, 2022): No, it looks to be working just fine.
Author
Owner

@netblue30 commented on GitHub (Feb 14, 2022):

We disable netlink socket on all sort of programs. Some of them are still trying to access it for whatever reasons. Unless the program functionality is breaking, we'll keep it disabled. Closing the bug for now.

<!-- gh-comment-id:1039199543 --> @netblue30 commented on GitHub (Feb 14, 2022): We disable netlink socket on all sort of programs. Some of them are still trying to access it for whatever reasons. Unless the program functionality is breaking, we'll keep it disabled. Closing the bug for now.
Author
Owner

@kmk3 commented on GitHub (Feb 14, 2022):

@jose1711 commented on Feb 9:

Expected behavior

No errors should appear.

Actual behavior

Could not create AF_NETLINK socket (Operation not supported)
Could not create AF_NETLINK socket (Operation not supported)
Could not create AF_NETLINK socket (Operation not supported)
Could not create AF_NETLINK socket (Operation not supported)
Could not create AF_NETLINK socket (Operation not supported)

I'd suggest reporting this to flameshot; maybe it can be changed to try once at
startup to use netlink and if it doesn't work, ignore it or always try
something else instead (to reduce the amount of error messages).

Messages are also written to systemd's journal:

$ journalctl -b 0 | grep -c NETLINK
Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.
      Pass -q to turn off this notice.
491

Maybe also change it to log this error only once per instance (or not at all).

<!-- gh-comment-id:1039459951 --> @kmk3 commented on GitHub (Feb 14, 2022): @jose1711 commented [on Feb 9](https://github.com/netblue30/firejail/issues/4925#issue-1129200262): > ### Expected behavior > > No errors should appear. > > ### Actual behavior > > ``` > Could not create AF_NETLINK socket (Operation not supported) > Could not create AF_NETLINK socket (Operation not supported) > Could not create AF_NETLINK socket (Operation not supported) > Could not create AF_NETLINK socket (Operation not supported) > Could not create AF_NETLINK socket (Operation not supported) > ``` I'd suggest reporting this to flameshot; maybe it can be changed to try once at startup to use netlink and if it doesn't work, ignore it or always try something else instead (to reduce the amount of error messages). > Messages are also written to `systemd`'s journal: > > ``` > $ journalctl -b 0 | grep -c NETLINK > Hint: You are currently not seeing messages from other users and the system. > Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages. > Pass -q to turn off this notice. > 491 > ``` Maybe also change it to log this error only once per instance (or not at all).
Author
Owner

@rusty-snake commented on GitHub (Feb 14, 2022):

I'd suggest reporting this to flameshot;

IIRC this is Qt.

<!-- gh-comment-id:1039467552 --> @rusty-snake commented on GitHub (Feb 14, 2022): > I'd suggest reporting this to flameshot; IIRC this is Qt.
Author
Owner

@Pictor13 commented on GitHub (Jun 11, 2023):

I'm getting this error even after flameshot was removed...

<!-- gh-comment-id:1586170802 --> @Pictor13 commented on GitHub (Jun 11, 2023): I'm getting this error even after `flameshot` was removed...
Author
Owner

@rusty-snake commented on GitHub (Jun 11, 2023):

This is over one year old. Please open a new issue.

And BTW how do you start flameshot if it is removed.

<!-- gh-comment-id:1586178291 --> @rusty-snake commented on GitHub (Jun 11, 2023): This is over one year old. Please open a new issue. And BTW how do you start flameshot if it is removed.
Author
Owner

@Pictor13 commented on GitHub (Jun 11, 2023):

And BTW how do you start flameshot if it is removed.

I was wondering as well exactly why I got logs, for a software that was removed.

Apparently a reboot of Ubuntu cleared up dangling processes or binds and now the log doesn't appear anymore.

<!-- gh-comment-id:1586235058 --> @Pictor13 commented on GitHub (Jun 11, 2023): > And BTW how do you start flameshot if it is removed. I was wondering as well exactly why I got logs, for a software that was removed. Apparently a reboot of Ubuntu cleared up dangling processes or binds and now the log doesn't appear anymore.
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#2819
No description provided.