Thank you, that was good.
I had /usr/share/gimp/2.0/, now, after (3 hours of) emerging gimp-help,
I also have help/en/
Unfortunately, I still get the same error msg.
Here are my USE flags:
/* Found these USE flags for media-gfx/gimp-2.10.8-r1://
// U I//
// - - aalib : Add support for media-libs/aalib
(ASCII-Graphics Library)//
// - - alsa : Add support for media-libs/alsa-lib
(Advanced Linux Sound//
// Architecture)//
// + + cpu_flags_x86_mmx : Use the MMX instruction set//
// + + cpu_flags_x86_sse : Use the SSE instruction set//
// - - debug : Enable extra debug codepaths, like
asserts and extra output.//
// If you want to get meaningful
backtraces see https://wiki.ge//
//ntoo.org/wiki/Project:Quality_Assurance/Backtraces//
// + + doc : Add extra documentation (API, Javadoc,
etc). It is//
// recommended to enable per package
instead of globally//
// - - gnome : Add GNOME support//
// - - heif : Enable support for ISO/IEC
23008-12:2017 HEIF files //
// - - jpeg2k : Support for JPEG 2000, a wavelet-based
image compression//
// format//
// - - mng : Add support for libmng (MNG images)//
// - - openexr : Support for the OpenEXR graphics file
format//
// - - postscript : Enable support for the PostScript
language (often with//
// ghostscript-gpl or libspectre)//
// - - python : Add optional support/bindings for the
Python language//
// + + python_targets_python2_7 : Build with Python 2.7//
// - - test : Enable dependencies and/or
preparations necessary to run//
// tests (usually controlled by
FEATURES=test but can be//
// toggled independently)//
// - - udev : Enable virtual/udev integration
(device discovery, power and//
// storage device support, etc)//
// - - unwind : Add support for call stack unwinding
and function name//
// resolution//
// - - vector-icons : Enable support for vector icons
(experimental) //
// - - webp : Add support for the WebP image format//
// - - wmf : Add support for the Windows Metafile
vector image format//
// - - xpm : Add support for XPM graphics format/
I have the feeling that, when gimp didn't see the help/ dir the first
time, it set something, microsoft-like, in persistant storage, and
doesn't even try to look locally anymore.
And why it can't access the xml file, which is there, I have no idea.
But I see no flags that look related to GIO or GVFS.
You have a lot of flags set... I hope I don't have to set those all,
just to see if it helps...
On 2020-04-30 14:31, Dale wrote:
n952162 wrote:
After emerging gimp, I tried to get help (after re-emerging with the
doc USE flag), and got this:
/Could not open 'https://docs.gimp.org/2.10/en/gimp-help.xml' for
reading: Operation not supported//
//
//Perhaps you are missing GIO backends and need to install GVFS?/
Is there anything I can do?
When I open GIMP and go to help, it takes me here:
file:///usr/share/gimp/2.0/help/en/index.html
It opens in Seamonkey for me. Seamonkey is set as my default
browser. This is my USE flag settings.
root@fireball / # emerge -pv app-doc/gimp-help media-gfx/gimp
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] app-doc/gimp-help-2.8.2:2::gentoo 0 KiB
[ebuild R ~] media-gfx/gimp-2.10.18-r1:2::gentoo USE="alsa doc
jpeg2k mng python udev wmf -aalib (-aqua) -debug -gnome -heif -openexr
-postscript -test -unwind -vector-icons -webp -xpm" CPU_FLAGS_X86="mmx
sse" PYTHON_SINGLE_TARGET="python2_7" 0 KiB
Total: 2 packages (2 reinstalls), Size of downloads: 0 KiB
root@fireball / #
Do you have the gimp-help package installed? If so, your USE flags
match mine?
Dale
:-) :-)
