Code: Select all
Failed to create /home for shader cache (Permission denied)---disabling.
With Firefox 129 I saw them sometimes, but it referenced .cache that it couldn't create. It's lazy programmatic directory creation, it's typical to create the full path (writing through if present).
I didn't know where it was coming from at first, but it's firefox causing it. Strange, I don't have webgl shader cache enabled (it's force disabled according to env)
It was not happening on Gentoo, and it's the same profile (copied from here originally). I thought maybe it was because I was forcing some graphics settings (webrender, hw compositing) so, seeing as it's no longer necessary to do that to use webrender, I reverted them. That wasn't it (and the browser in Gentoo has those same forced settings... still)
I also deleted ~/.cache/mozilla and renamed my ~/.mozilla profile directory to start with a fresh one. The shader cache messages did not occur.
The messages don't start until Firefox does something, like loading up a youtube video for a hover preview...
It turned out to be:
media.ffmpeg.vaapi.enabled true
How I figured that out was by comparing pasted output from about:support between my gentoo and arch, and noting a subtle difference in hardware video decoding support in the output. On arch it was showing as force enabled, though the setting is disabled by env. On gentoo it was showing it force enabled, but disabled by gfxinfo (actually fails because of ffmpeg)
That's bugged, it shouldn't be trying to cache shaders and shouldn't be trying to write through /home in any case.
Why only here do I get those floods of errors, and not on Gentoo with the same setting enabled? Because a test fails there, and it gets disabled (Firefox's gfxinfo function) so it doesn't go there. It actually works here (probably something on gentoo wasn't compiled with libva)

P.S. Yes, that was it. My ffmpeg on Gentoo doesn't have a lot of functionality enabled... including "-vaapi" in the USE flags it was built with. So that's why I wasn't getting the errors, it was just not initializing. I'm going to fix that.
So now that I have it figured out, I'm going to enable vaapi again and just ignore the console messages for now. (If they don't fix that, I'll find the error in the source and get firefox to stop printing it)