Created attachment 568326 [details]
Compilation fails with access violation reported.
Comment on attachment 568326 [details]
Why do you attach a single file in a compressed tar? You can just compress the file itself and do away with tar entirely.
Created attachment 568392 [details]
I don't know how to remove my last submitted attachment that went in tar unnecessarily.
Any help to remove it would be appreciated.
With current portage sync I could compile and install gimp 2.10.8-r1.
Open it and tested and everything seems to be working fine, including graphic acceleration.
Created attachment 573856 [details]
media-gfx/gimp-2.10.10 build log
This has returned in media-gfx/gimp-2.10.10
Created attachment 582162 [details]
gimp-2.10.12 build log
It seems gimp-2.10.12 is also affected. Offending fonts seem to come from various Texlive packages like dev-texlive/texlive-mathscience-2019 or dev-texlive/texlive-fontsextra-2019.
media-gfx/krita-4.1.8-r1 is also affected by the same thing.
I've experienced the same thing, though with media-fonts/monafont instead.
It seems a build system variable should probably be set to point tempfiles to write to $D instead of the live filesystem.
I'm getting the same behavior on ~amd64 with media-gfx/gimp-2.10.12. All of the access violations are all of texlive fonts:
grep -c "ACCESS DENIED" gimp-build.log
grep "ACCESS DENIED" gimp-build.log |grep -v texmf -c
I recently enabled texlive fonts as an experiment to see if more glyphs rendered in Emacs, and this fontconfig seems to be causing the access violation problem:
eselect fontconfig list |grep tex
 09-texlive.conf *
Deactivating the texlive fontconfig allows media-gfx/gimp-2.10.12 to emerge successfully:
eselect fontconfig list |grep tex
@graphics could you have a look if there is a chance that media-libs/openimageio is causing this?
The same problem was affecting me at some time without having OpenImageIO installed (see build log attached above in Comment 5).
I'm starting to think that maybe the gimp ebuild should update the font cache during pkg_setup even when the fonts are causing the problem. It would save everyone having to deal with the same thing again and again.
(In reply to Sebastian Pipping from comment #11)
> I'm starting to think that maybe the gimp ebuild should update the font
> cache during pkg_setup even when the fonts are causing the problem. It
> would save everyone having to deal with the same thing again and again.
(In reply to Conrad Kostecki from comment #12)
> packages also do not rebuild the font cache, this could leave to unfixed
That's a good point!
Had this issue upgrading gimp... following it, I found bug https://bugs.gentoo.org/666418
Upgrading to =media-libs/fontconfig-2.13.1-r2 solved the problem.
Have a nice day,
Just bumped into this problem today. As previous comments mention - the font cache needs to be rebuilt. It's a missing hook somewhere.
I already had the latest version of media-libs/fontconfig but it still failed for some reason with access violations. So I re-emerged media-libs/fontconfig and then media-gfx/gimp. I believe the re-emerge forces a font cache refresh. Now it is working.
Seems to have been resolved by upgrading fontconfig (shouldn't have been a bug for openimageio).
Marking fixed and resolved.
apologies, I prematurely closed this x(
The bug has been closed via the following commit(s):
Author: Aisha Tammy <firstname.lastname@example.org>
AuthorDate: 2020-11-16 22:43:50 +0000
Commit: Sam James <email@example.com>
CommitDate: 2020-12-03 05:09:58 +0000
media-libs/openimageio: fix font installation
Package-Manager: Portage-3.0.8, Repoman-3.0.1
Signed-off-by: Aisha Tammy <firstname.lastname@example.org>
Signed-off-by: Sam James <email@example.com>
...o-22.214.171.124.ebuild => openimageio-126.96.36.199-r1.ebuild} | 19 ++++++++++++++++++-
1 file changed, 18 insertions(+), 1 deletion(-)