Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

flameshot: MESA: error: Failed to query drm device (intel/no3d) #6465

Open
5 of 7 tasks
Dieterbe opened this issue Sep 8, 2024 · 3 comments
Open
5 of 7 tasks

flameshot: MESA: error: Failed to query drm device (intel/no3d) #6465

Dieterbe opened this issue Sep 8, 2024 · 3 comments
Labels
graphics Issues related to GPU acceleration and drivers (mesa, nvidia, etc) notourbug The issue is valid, but it isn't directly caused by (or cannot be fixed by) firejail

Comments

@Dieterbe
Copy link
Contributor

Dieterbe commented Sep 8, 2024

Description

flameshot doesn't seem to start under firejail. although i think it may create an invisible task applet icon which doesn't respond to clicks.

Steps to Reproduce

~ ❯❯❯ LC_ALL=C firejail /usr/bin/flameshot
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)
MESA: error: Failed to query drm device.
glx: failed to create dri3 screen
failed to load driver: iris
failed to open /dev/dri/card1: No such file or directory
failed to load driver: iris
Could not create AF_NETLINK socket (Operation not supported)
Could not create AF_NETLINK socket (Operation not supported)

Behavior without a profile

~ ❯❯❯ LC_ALL=C firejail --noprofile /usr/bin/flameshot
firejail version 0.9.73

Parent pid 22504, child pid 22505
Base filesystem installed in 0.03 ms
Child process initialized in 11.18 ms

now the app works fine. applet icon shows and responds and the app takes screenshots

Environment

I use arch, btw

~ ❯❯❯ uname -a
Linux xps17 6.10.6-arch1-1 #1 SMP PREEMPT_DYNAMIC Mon, 19 Aug 2024 17:02:39 +0000 x86_64 GNU/Linux
~ ❯❯❯ firejail --version
firejail version 0.9.73

Compile time support:
	- always force nonewprivs support is disabled
	- AppArmor support is enabled
	- AppImage support is enabled
	- chroot support is enabled
	- D-BUS proxy support is enabled
	- file transfer support is enabled
	- IDS support is disabled
	- Landlock support is enabled
	- networking support is enabled
	- output logging is enabled
	- overlayfs support is disabled
	- private-home support is enabled
	- private-lib support is disabled
	- private-cache and tmpfs as user enabled
	- SELinux support is disabled
	- user namespace support is enabled
	- X11 sandboxing support is enabled

  • Linux distribution and version (e.g. "Ubuntu 20.04" or "Arch Linux")
  • Firejail version (firejail --version).
  • If you use a development version of firejail, also the commit from which it
    was compiled (git rev-parse HEAD).

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)

Log

Output of LC_ALL=C firejail --debug /path/to/program

hmm this shows a lot of stuff from my system. is this necessary?

@rusty-snake
Copy link
Collaborator

rusty-snake commented Sep 8, 2024

Related/Duplicated:

TL;DR: ignore no3d


I guess there was some recent mesa update breaking software fallback on iris systems.

@kmk3 kmk3 changed the title flameshot doesn't start anymore flameshot: program does not start Sep 8, 2024
@Dieterbe
Copy link
Contributor Author

Dieterbe commented Sep 8, 2024

bingo, added that in a new .config/firejail/flameshot.local file and that fixes it.

@kmk3 kmk3 added the notourbug The issue is valid, but it isn't directly caused by (or cannot be fixed by) firejail label Sep 8, 2024
@kmk3 kmk3 changed the title flameshot: program does not start flameshot: MESA: error: Failed to query drm device (iris/no3d) Sep 8, 2024
@kmk3
Copy link
Collaborator

kmk3 commented Sep 8, 2024

@Dieterbe

As mentioned, this issue seems to affect multiple programs.

I'd expect most programs to just fallback to CPU rendering and work normally
when a GPU is not available.

Please consider reporting this to mesa and linking it here.

@kmk3 kmk3 changed the title flameshot: MESA: error: Failed to query drm device (iris/no3d) flameshot: MESA: error: Failed to query drm device (intel/no3d) Sep 10, 2024
@kmk3 kmk3 added the graphics Issues related to GPU acceleration and drivers (mesa, nvidia, etc) label Sep 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
graphics Issues related to GPU acceleration and drivers (mesa, nvidia, etc) notourbug The issue is valid, but it isn't directly caused by (or cannot be fixed by) firejail
Projects
None yet
Development

No branches or pull requests

3 participants