Firefox unable to access amdgpu.ids on snap again on ver 111
Categories
(Firefox Build System :: Third Party Packaging, defect)
Tracking
(Not tracked)
People
(Reporter: kain.centeno, Unassigned)
References
(Blocks 1 open bug)
Details
snap again complaining about amdgpu.ids, see below for output
kain@kain-G5-5505:~$ firefox
ATTENTION: default value of option mesa_glthread overridden by environment.
/usr/share/libdrm/amdgpu.ids: No such file or directory
ATTENTION: default value of option mesa_glthread overridden by environment.
amdgpu: os_same_file_description couldn't determine if two DRM fds reference the same file description.
If they do, bad things may happen!
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
[GFX1-]: Couldn't sanitize RENDERER device: RENOIR
ALSA lib conf.c:4553:(snd_config_update_r) Cannot access file /usr/share/alsa/alsa.conf
ALSA lib seq.c:935:(snd_seq_open_noupdate) Unknown SEQ default
[GFX1-]: Couldn't sanitize RENDERER device: RENOIR
bellow is a clone of the original issue (that happened on ver 89)
+++ This bug was initially created as a clone of Bug #1710326 +++
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:89.0) Gecko/20100101 Firefox/89.0
Steps to reproduce:
Opened the firefox snap via terminal on a machine with an AMD GPU.
Actual results:
[GFX1-]: glxtest: libpci missing
[GFX1-]: No GPUs detected via PCI
/usr/share/libdrm/amdgpu.ids: No such file or directory
amdgpu: unknown (family_id, chip_external_rev): (143, 41)
libEGL warning: DRI2: failed to create dri screen
Expected results:
I expected the snap to be able to access this file.
According to this thread, it should be possible if the following is added into the snapcraft.yaml file.
layout:
/usr/share/libdrm:
bind: $SNAP/usr/share/libdrm
|
||
Updated•1 year ago
|
|
||
Updated•1 year ago
|
|
|
||
Updated•1 year ago
|
|
||
Comment 2•1 year ago
|
||
(In reply to Kain from comment #0)
[...]
According to this thread, it should be possible if the following is added into the snapcraft.yaml file.
layout:
/usr/share/libdrm:
bind: $SNAP/usr/share/libdrm
We actually already have the following in snapcraft.yaml:
layout:
/usr/share/libdrm:
bind: $SNAP/gnome-platform/usr/share/libdrm
So that can't be it. And I don't see any recent changes in snapcraft.yaml that could have caused a breakage here.
That said, I'm told that using the core22 version of the desktop-launcher should work. We have a WIP core22-based version of the Firefox snap on a candidate channel, if you'd like to give it a try and see if it helps: sudo snap refresh --channel=candidate/core22 firefox
(In reply to Amin Bandali [:bandali] from comment #2)
(In reply to Kain from comment #0)
[...]According to this thread, it should be possible if the following is added into the snapcraft.yaml file.
layout:
/usr/share/libdrm:
bind: $SNAP/usr/share/libdrmWe actually already have the following in snapcraft.yaml:
layout: /usr/share/libdrm: bind: $SNAP/gnome-platform/usr/share/libdrmSo that can't be it. And I don't see any recent changes in snapcraft.yaml that could have caused a breakage here.
That said, I'm told that using the core22 version of the desktop-launcher should work. We have a WIP core22-based version of the Firefox snap on a candidate channel, if you'd like to give it a try and see if it helps:
sudo snap refresh --channel=candidate/core22 firefox
replied on the linked ticket as this one is marked closed
Description
•