snap: glxtest: libEGL initialize failed
Categories
(Firefox Build System :: Third Party Packaging, defect)
Tracking
(Not tracked)
People
(Reporter: rojtberg, Unassigned)
References
(Blocks 3 open bugs, )
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:122.0) Gecko/20100101 Firefox/122.0
Steps to reproduce:
use firefox snap on:
- Ubuntu 22.04
- 6.5.0-15-generic #15~22.04.1-Ubuntu
- NVIDIA-SMI 545.29.06
Actual results:
apparmor="DENIED" operation="symlink" class="file" profile="snap.firefox.firefox" name="/dev/char/195:255" pid=9680 comm="glxtest" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
leads to firefox running on software rendering in about:support:
GPU1: llvmpipe (LLVM 15.0.7, 256 bits)
Expected results:
firefox running on the GPU:
GPU1: NVIDIA GeForce GTX 1080/PCIe/SSE2
output of the firefox-122.0.tar.bz2 version.
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
ok, this seems to be rather a snap bug as none of my installed snaps get GPU access right now
Updated•2 years ago
|
Comment 4•2 years ago
|
||
Do you have multiple GPUs ? Can you share about:support ?
(In reply to rojtberg from comment #2)
ok, this seems to be rather a snap bug as none of my installed snaps get GPU access right now
Can you elaborate what are those Snaps? Firefox versions or other software ?
Updated•2 years ago
|
Comment 5•2 years ago
|
||
The product::component has been changed since the backlog priority was decided, so we're resetting it.
For more information, please visit BugBot documentation.
Updated•2 years ago
|
Do you have multiple GPUs ?
no, only a single GPU. Its a desktop machine. I have downgraded the driver so I dont think about:support would create anything but noise.
Can you elaborate what are those Snaps?
Anything really. e.g. https://snapcraft.io/ogre crashed with some EGL init error.
Updated•1 year ago
|
Comment 7•1 year ago
|
||
Unfortunately, this is a distro level issue. I'm not sure it is still relevant ? Upstream bug is still marked as Confirmed
Comment 8•1 year ago
|
||
It would be interesting to know if this still happens, and if so whether it is fixed in nightly, which, being based on core24, connects to gpu-2404, which is much more recent.
If you are willing to give it a try, first create a snapshot of your current Firefox data:
snap save firefox
Then switch to the nightly Firefox:
snap refresh --edge firefox
See what about:support says now.
Then, if you wish to return to stable, do
snap refresh --stable firefox
snap restore {ID} firefox
If you don't remember it, you can always retrieve the ID number from 'snap saved'.
Not the person who originally filed the bug, and I can't easily go back and test anymore, but my personal recollection is that the issue was originally fixed under the 545 driver at some point, but it broke again in a similar way after upgrading to Ubuntu 24.10, which notably upgraded to Nvidia 560 (currently 560.35.03) and switched to Wayland by default for Nvidia. I'm not sure if it broke for the same reason (I've also been following Bug 1928754, which seems potentially relevant), but the end result is pretty similar.
For what it's worth, I performed the test in the above comment, and switching to Nightly does seem to address whatever issue is occurring for me:
stable: llvmpipe (LLVM 15.0.7, 256 bits)
edge: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
Updated•11 months ago
|
Comment 10•11 months ago
|
||
It's been a while and IIUC the official nvidia driver in the meantime has become 570.x. Do you still experience problems in an updated configuration?
For now I am downgrading severity as of comment 9 (what was nightly then should be in release now) and for the fact, that a workaround (old driver version) seems to exist.
Thank you for your help in diagnosing.
Comment 11•11 months ago
|
||
Adding the qe-verify flag to confirm if this problem is still reproducible with the latest stable Nvidia driver on Ubuntu 24 with the Firefox snap.
Comment 12•11 months ago
|
||
For what it's worth, I'm still experiencing the same GPU issues I reported in comment 9 with Firefox 141, Ubuntu 25.04, and Nvidia driver 570.169. I think the specific change that appears to fix this (moving to the core24 base snap), appears to still be stuck in nightly.
Comment 13•11 months ago
|
||
You can use stable core24 by e.g.: sudo snap install --channel=latest/candidate/core24 firefox_core24 or sudo snap refresh --channel=latest/candidate/core24 firefox, though it's not yet default
Updated•11 months ago
|
| Reporter | ||
Comment 14•11 months ago
|
||
it is working with both Nvidia 570 and Nvidia 575 on Ubuntu 24 for me now. But I briefly got the issue again when Nvidia 575 was released. I think driver updates are whitelisted in some gpu related snap like: https://discourse.ubuntu.com/t/the-graphics-core22-snap-interface/34663
Comment 15•11 months ago
|
||
(In reply to :gerard-majax from comment #13)
You can use stable
core24by e.g.:sudo snap install --channel=latest/candidate/core24 firefox_core24orsudo snap refresh --channel=latest/candidate/core24 firefox, though it's not yet default
Unfortunately, this installs Firefox 140, which I can't use with my profile since I'm already on Firefox 141.
I did also try upgrading to the Nvidia 575 driver, but that doesn't seem to help. A potentially relevant detail is that I'm on Wayland.
Comment 16•11 months ago
|
||
(In reply to aroskuski from comment #15)
(In reply to :gerard-majax from comment #13)
You can use stable
core24by e.g.:sudo snap install --channel=latest/candidate/core24 firefox_core24orsudo snap refresh --channel=latest/candidate/core24 firefox, though it's not yet defaultUnfortunately, this installs Firefox 140, which I can't use with my profile since I'm already on Firefox 141.
I did also try upgrading to the Nvidia 575 driver, but that doesn't seem to help. A potentially relevant detail is that I'm on Wayland.
Nathan, was there no core24 build updated? Or am I once again getting the channel wrong ?
Comment 17•11 months ago
|
||
Oof, correct, doing that and then submitting the builds, should be there by the end of the day.
Comment 18•10 months ago
|
||
I was just getting around to checking if there was a new build, but it looks like the stable channel finally switched to core24 this morning and fixed my GPU issues.
Comment 19•10 months ago
|
||
Well it was fixed, but stable is seemingly back to core22 (I guess it was an accident?). The latest/candidate/core24 channel seems to work as a workaround for now (though it doesn't have the 141.0.2 patch that just got pushed to stable it seems), though it would also be helpful to know if there's a bug or something somewhere I can track as to when core24 will finally be pushed out to stable.
Description
•