[Bug 2100483] Re: amdgpu.ids path is fixed

[Launchpad Bug Tracker]

This bug was fixed in the package libdrm - 2.4.124-2

---------------
libdrm (2.4.124-2) unstable; urgency=medium

  [ Daniel van Vugt ]
  * Add xf86drm-Handle-NULL-in-drmCopyVersion.patch (LP: #2104352)

  [ Bo YU ]
  * Enable building libdrm-intel1 for riscv64 (Closes: #1085314)

 -- Timo Aaltonen <tjaalton at debian.org>  Tue, 01 Apr 2025 11:08:19 +0300

** Changed in: libdrm (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/2100483

Title:
  amdgpu.ids path is fixed

Status in libdrm package in Ubuntu:
  Fix Released

Bug description:
  The AMD driver expects the file `amdgpu.ids` in a fixed place (/usr/share/libdrm); this means that, when building a Snap application, the amdgpu.ids file isn't directly available there, but inside a mounted folder. This forces either each application, or each extension snap (gnome-extension, mesa-2404...) to link/bind the file from the current place (usually at $SNAP/gnome-platform/usr/share/libdrm/amdgpu.ids)
  into the original path. The problem is that, currently, it fails, and the file isn't being binded, no matter the correct statement is specified in the snap.

  There is a patch for libdrm that allows to set an environment
  variable, called AMDGPU_ASIC_ID_TABLE_PATH, where the file will be
  searched for instead of the default, meson-configured, path.
  Unfortunately, it still hasn't been merged. But applying it into the
  .deb packages would allow to fix this problem, and with the extra
  advantage or reducing the number of binded files/folders in the snaps
  (each bind consumes resources, and in fact, snapd limits the number of
  binds that a snap can do, so being able to use an environment variable
  for this would allow to save one).

  The patch:
  https://gitlab.freedesktop.org/mesa/drm/-/merge_requests/273

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/2100483/+subscriptions