Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 43 |
Nodes: | 6 (0 / 6) |
Uptime: | 97:24:30 |
Calls: | 290 |
Files: | 904 |
Messages: | 76,468 |
On Sat, 17 Aug 2024, Paul Zander wrote:...
Check the logfile at ${T}/Xvfb.logRecently I've upgraded mesa to 24.2.0. Can this problem be related to this upgrade?
Can anybody with the current mesa try to emerge fricas[doc] and tell us if it works (any lisp will do, probably, sbcl is the most reasonable one; by the way, clozurecl compiles fricas very quickly).Yes; I reproduced it.
On Mon, 19 Aug 2024, Robin H Johnson wrote:
On Sun, Aug 18, 2024 at 04:20:05PM +0000, Andrey Grozin wrote:
Can anybody with the current mesa try to emerge fricas[doc] and tell us if >> it works (any lisp will do, probably, sbcl is the most reasonable one; by >> the way, clozurecl compiles fricas very quickly).Yes; I reproduced it.
- started w/ mesa-24.0.7 installed.
- emerge sbcl => success
- USE=doc emerge fricas => success
- emerge =mesa-24.2.0* => success
- USE=doc emerge fricas => fail w/ sandbox
- patch virtualx.eclass
- USE=doc emerge fricas => success
So Mesa's behavior changed, trying to accelerate Xvfb.
I pushed a fix to virtualx.eclass for you.
It's a fix in that it correctly tells Sandbox that upstream mesas use a predictive fopen(..., RDWR) and Gentoo expects it to *NOT* actually use the device in the ebuild context.I pushed a fix to virtualx.eclass for you.That addpredict looks like a workaround, not like a real fix of the
problem.
Especially, the many warnings mentioned by grozin are stillThe manual does correctly build despite that warning from mesa, because it correctly falls back.
there. With the patched virtualx.eclass, I still see more than thousand messages in Xvfb.log:
libEGL warning: failed to open /dev/dri/card0: Permission denied
Also, was this so urgent that you had to push the eclass change withoutLow impact, fixes blockage.
prior mailing list review?
Hiding the errors also isn't a fix - it's just picking a different code path.This is the hallmark of a workaround.Especially, the many warnings mentioned by grozin are stillThe manual does correctly build despite that warning from mesa, because it correctly falls back.
there. With the patched virtualx.eclass, I still see more than thousand
messages in Xvfb.log:
libEGL warning: failed to open /dev/dri/card0: Permission denied
Who was affected by the breakage? Grozin.The impact of changing an eclass willy nilly without asking anyone forAlso, was this so urgent that you had to push the eclass change withoutLow impact, fixes blockage.
prior mailing list review?
@X11 or anyone affected?
We've had mesa-24.2.0* in the tree for a while now. We had plenty of tinderbox runs testing. This is the only package that fails with those sandbox violations. No other @sci stuff, no @kde stuff.See below about libeproxy - it's failing because of the same files.
The "Low impact, fixes blockage." fix would have been to add thatIf I didn't know about mesa, why do you think I commented on this thread, and provided bisect showing where upstream introduced the change in behavior?
addpredict line to the affected package, file a bug and ask the people
that actually know about mesa.
Oddly enough fricas also has an automagic dependency on xvfb-run...@grozin: please do fix the automagic behavior in fricas; it's clearly not fatal either, because my test environment does not have xvfb-run installed at all.
FYI: this actually fixes the access for fricas:Your patch would "fix" fricas, but I think it will break anything else