[gimp-web-devel/pat/bootstrap] content: edit further the problems and solutions page.
- From: Jehan <jehanp src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gimp-web-devel/pat/bootstrap] content: edit further the problems and solutions page.
- Date: Wed, 7 Sep 2022 16:27:20 +0000 (UTC)
commit 4c10d562da1bca7745f85d25b8d64cb24646879a
Author: Jehan <jehan girinstud io>
Date: Wed Sep 7 18:19:35 2022 +0200
content: edit further the problems and solutions page.
- Move it one level higher under setup/ as it's not only about build
issues.
- More markdown syntax fixes.
- Remove outdated entry about GEGL versions needed by GIMP 2.8 or 2.9.
These days all versions of GIMP requires GEGL 0.4 and that's what is
packaged by modern distributions too now.
- Remove the whole "Jenkins" section as we don't use this CI system
anymore.
- Remove the "Templates" section at the end. People can just look how
other items are written and reuse the markdown syntax.
.../setup/{build => }/Problems_and_solutions.md | 317 +++++++++------------
content/core/setup/build/_index.md | 3 +-
2 files changed, 129 insertions(+), 191 deletions(-)
---
diff --git a/content/core/setup/build/Problems_and_solutions.md b/content/core/setup/Problems_and_solutions.md
similarity index 77%
rename from content/core/setup/build/Problems_and_solutions.md
rename to content/core/setup/Problems_and_solutions.md
index 47eb847..a9c9dd5 100644
--- a/content/core/setup/build/Problems_and_solutions.md
+++ b/content/core/setup/Problems_and_solutions.md
@@ -1,5 +1,5 @@
---
-title: "Building: problems and solutions"
+title: "Common development problems and solutions"
Author: "GIMP team"
Date: 2021-08-18
weight: 5
@@ -8,7 +8,6 @@ weight: 5
This page describes problems/solutions that hamper GIMP developers. It's a knowledge base for developers.
Feel free to add your own findings and don't be shy. It makes the work easier for all of us.
-
## Build
### General
@@ -139,20 +138,22 @@ rgba to hsva failed #1[0] got 0.166667 expected 0.000000
```
Cause
-: The tested code doesn't take into account that strict equality comparisons (==) will most often lead to
different results on different platforms.
+: The tested code doesn't take into account that strict equality
+comparisons (`==`) will most often lead to different results on
+different platforms.
Solution
: The code must take this fact into account. This means: don't use `==` for floating point comparisons!
The following lines show alternatives.
-1. Make sure to have defined EPSILON first:
+1. Make sure to have defined `EPSILON` first:
```C
#define EPSILON 1.0e-10
```
-2. Use EPSILON instead of == :
+2. Use `EPSILON` instead of `==` :
| wrong | right |
@@ -205,7 +206,9 @@ Problem
GEGL builds and works anyway, because it is only an optional dependency.
Cause
-: The package of your distribution doesn't contain the link libspiro.so to the actual SPIRO library. On a
Debian testing system this concerns the package libspiro0.
+: The package of your distribution doesn't contain the link
+`libspiro.so` to the actual SPIRO library. On a Debian testing system
+this concerns the package libspiro0.
Solution
: You have to set that link yourself.
@@ -257,8 +260,8 @@ Cause
Solution
: * Clean your build directory:
- + If you have built in the GEGL source directory, run '''git clean -xdf'''
- + If you have built in another directory than your source directory: '''cd $build_directory && rm -rf
*'''
+ + If you have built in the GEGL source directory, run `git clean -xdf`
+ + If you have built in another directory than your source directory: `cd $build_directory && rm -rf *`
* Build GEGL again.
### GIMP
@@ -296,32 +299,6 @@ Solution
Some more information on building can be found at [[Hacking:Building| the building tutorials]].
-#### GIMP build breaks for missing dependency gegl-0.2 > 0.2.0
-
-Problem
-: Building GIMP fails with a message, that the dependency gegl-0.2 > 0.2.0 is not met. But in $prefix I
see the GEGL files, for instance gegl-0.3.pc in $prefix/lib/pkgconfig.
-
-Cause
-: You have mismatched the versions:
-
-GIMP 2.8 needs GEGL from the branch gegl-0-2.
-
-GIMP 2.9 (=master) needs GEGL from the branch master.
-
-Obviously you have mixed GIMP 2.8 with GEGL master.
-
-Solution
-: If you want to build GIMP 2.8:
-
-* In GEGLs build directory run `make uninstall`.
-* For GEGL checkout gegl-0-2, run `make` and `make install`.
-* Go to the GIMP build directory and run `autogen.sh` again, run `make` and `make install`.
-
-If you want to build GIMP master:
-
-* In GIMPs workspace run `git checkout master`.
-* Run `autogen.sh` again, run `make` and `make install`.
-
#### Building development GIMP 2.99 breaks for missing dependency gegl-0.4 > 0.4.xx
Problem
@@ -332,12 +309,20 @@ Cause
development version (bleeding edge) GEGL. In other words, the GIMP
unstable version can depend on the GEGL unstable version.
-Cloning the GEGL repository will get the development version of GEGL. (But the latest commit may not be
tagged yet in the repository, so you can't ask git for the tagged commit. The meson.build file in the
repository will usually show the *next* version that gegl.org will soon tag and release as stable.)
+Cloning the GEGL repository will get the development version of GEGL.
+(But the latest commit may not be tagged yet in the repository, so you
+can't ask git for the tagged commit. The `meson.build` file in the
+repository will usually show the *next* version that gegl.org will soon
+tag and release as stable)
-Tagged versions of GEGL are captured by gimp.org in a tarball at [https://download.gimp.org/pub/gegl/0.4/
https://download.gimp.org/pub/gegl/0.4/], but not always the unstable, development version that a build of
unstable GIMP requires.
+Tagged versions of GEGL are captured by gimp.org in a tarball at
+[https://download.gimp.org/pub/gegl/0.4/](https://download.gimp.org/pub/gegl/0.4/),
+but not the development version that a development build of GIMP
+may require.
Solution
-: After you have downloaded, built, and installed gegl, to check the installed version, run: `pkg-config
gegl-0.4 --modversion`
+: After you have downloaded, built, and installed GEGL, to check the
+installed version, run: `pkg-config gegl-0.4 --modversion`
#### Configure fails with a syntax error near unexpected token `x11,'
@@ -352,15 +337,15 @@ Example:
```
Cause
-: You're missing /usr/share/aclocal/gtk-3.0.m4, which is part of the GTK3 development package.
+: You're missing `/usr/share/aclocal/gtk-3.0.m4`, which is part of the GTK3 development package.
Solution
-: Make sure you have libgtk-3-0 installed, including any associated -dev or -devel package.
+: Make sure you have `libgtk-3-0` installed, including any associated `-dev` or `-devel` package.
-#### GIMP build fails for missing BABL function
+#### GIMP build fails for missing babl function
Problem
-: GIMP build fails for missing BABL function
+: GIMP build fails for missing babl function
Example:
@@ -379,17 +364,30 @@ Example:
```
Cause
-: You have an older version of babl installed on your system, either in your local installation prefix
-or by a package. In this case the package libbabl-dev 0.1.10-1 was installed. Although the build environment
-variables were set to rely on the local installation prefix, the linker checked this old version and failed
for
-not finding the symbol `babl_format_get_model` in BABL.
+: You have an older version of babl installed on your system, either in
+your local installation prefix or by a package. In this case the package
+`libbabl-dev 0.1.10-1` was installed. Although the build environment
+variables were set to rely on the local installation prefix, the linker
+checked this old version and failed for not finding the symbol
+`babl_format_get_model` in BABL.
Solution
-: * Check the file '''$prefix/lib/pkgconfig/babl.pc'''. If you find a line with 'Version: 0.1.10' or older,
then your BABL library is too old. In this case, goto step 2, otherwise to step 4.
- * Change into your BABL source directory. Fetch the latest BABL source code, i.e. from git (branch
'master').
- * Clean and rebuild BABL from scratch: run '''autogen.sh''' or '''config''', '''make clean && make
uninstall && make && make install'''
- * In your package manager check the version of the BABL development library (on Debian systems:
libbabl-dev, on Mandriva: libbabl-devel, on Red Hat systems:babl*src, on openSuSE systems:babl-devel). If you
find version 0.1.10 or older, then your BABL library is too old. In your package manager remove it completely
and also the GEGL development package depending on it.
- * Also clean and rebuild GEGL from scratch to avoid version mismatch between GEGL and GIMP.
+: * Check the file `$prefix/lib/pkgconfig/babl.pc`. If you find a line
+ with `Version: 0.1.10` or older, then your babl library is too old.
+ In this case, goto step 2, otherwise to step 4.
+ * Change into your babl source directory. Fetch the latest babl source
+ code, i.e. from git (branch `master`).
+ * Clean and rebuild babl from scratch: run `autogen.sh` or
+ `configure`, then `make clean && make uninstall && make && make
+ install`
+ * In your package manager check the version of the babl development
+ library (on Debian systems: `libbabl-dev`, on Mandriva: `libbabl-devel`,
+ on Red Hat systems: `babl*src`, on openSuSE systems: `babl-devel`).
+ If you find version 0.1.10 or older, then your babl library is too
+ old. In your package manager remove it completely and also the GEGL
+ development package depending on it.
+ * Also clean and rebuild GEGL from scratch to avoid version mismatch
+ between GEGL and GIMP.
* Clean and rebuild GIMP from scratch.
#### Build of GIMP master fails in gimpcursor.c
@@ -413,21 +411,19 @@ Error messages:
Cause
: It's probably a gdk-pixbuf issue. It is for instance known to update the system loaders cache instead the
cache of its local installation, if it's installed in a prefix which is in the PATH variable.
-Workarounds:
-
Workaround A (the short tour)
-: * '''cd cursors'''
- * '''make clean'''
- * '''cd ..'''
- * '''make'''
+: * `cd cursors`
+ * `make clean`
+ * `cd ..`
+ * `make`
Workaround B (the big tour)
-: * '''gdk-pixbuf-query-loaders --update-cache''' (in case this doesnt work run it with sudo)
- * add the Pkgconfigpath of libgdk-pixbuf2.0-dev to the PKG_CONFIG_PATH environment variable
- * '''configure/autogen''' with your prefix
- * '''make clean'''
- * '''make'''
+: * `gdk-pixbuf-query-loaders --update-cache` (in case this doesnt work run it with sudo)
+ * add the pkg-config path of `libgdk-pixbuf2.0-dev` to the `PKG_CONFIG_PATH` environment variable
+ * `configure/autogen` with your prefix
+ * `make clean`
+ * `make`
Anyway, these are just workarounds. If you know the cause and a proper solution, feel free to edit this
article.
@@ -451,11 +447,10 @@ The output of <code>make V=1</code> produces a message like this:
Cause
: You have not a shared (=dynamic) binary version, but a static binary of that particular library. Linking
static binaries of most libraries is not supported by GIMP.
-You can recognize this by the file file extensions:
+You can recognize this by the file extensions:
-Dynamic libraries have the extensions: '''so''' on Linux, '''dylib''' on OS X, '''dll''' on Windows.
-
-Static libraries have the extensions: '''a''' on Linux and OS X, '''lib''' on Windows.
+* Dynamic libraries have the extensions: `so` on Linux, `dylib` on OS X, `dll` on Windows.
+* Static libraries have the extensions: `a` on Linux and OS X, `lib` on Windows.
Solution
: 1. Get a dynamic binary version of that library. Either the package manager of your distribution or the
web holds one or you
@@ -479,14 +474,16 @@ failed to load "./cursor-bad.png": Couldn't recognize the image file format for
```
Cause
-: The environment variable XDG_DATA_DIRS is modified in your build environment, which confuses the GLib
library (GDK-Pixbuf).
+: The environment variable `XDG_DATA_DIRS` is modified in your build environment, which confuses the GLib
library (GDK-Pixbuf).
Solution
-: * Don't modify the environment variable XDG_DATA_DIRS in your build environment. I.e. if you build from a
build script, don't set this variable there.
- * make distclean
- * autogen.sh or configure
- * make
- * make install
+: * Don't modify the environment variable `XDG_DATA_DIRS` in your build
+ environment. I.e. if you build from a build script, don't set this
+ variable there.
+ * `make distclean`
+ * `autogen.sh` or `configure`
+ * `make`
+ * `make install`
#### GIMP master refuses to start with error 'GIMP requires the GEGL operation "gegl:alien-map"'
@@ -631,83 +628,40 @@ Problem
Cause
: Some step in the build did not complete.
-The default for meson is '-j 3', meaning build in parallel, so the last step shown in the console might not
be the step that hung.
+The default for meson is `-j 3`, meaning build in parallel, so the last step shown in the console might not
be the step that hung.
Solution
: Use `ps -ef` to determine which process is hung, and debug that build step.
-Sometimes it is the g-ir-scanner tool.
+Sometimes it is the `g-ir-scanner` tool.
Or use `-j 1` so that the last step shown is the step that hung.
#### build configure step stops: missing gtk-encode-symbolic-svg
Problem
-: The executable tool gtk-encode-symbolic-svg could not be found.
+: The executable tool `gtk-encode-symbolic-svg` could not be found.
Cause
: You have not installed the package containing the tool.
Solution
-: Use tools provided by your distribution to find which package contains gtk-encode-symbolic-svg, and
install that package.
-Since Ubuntu 20.04 focal, the tool gtk-encode-symbolic-svg is in Ubuntu package libgtk-3-bin.
-Formerly in Ubuntu package gtk-3-examples.
-
-### Jenkins
-
-#### The compiler fails for a missing directory, although that directory exists
-
-Problem
-: The compiler fails for a missing directory, although that directory exists
-
-The file config.log contains the lines
-
-```sh
-configure:3796: checking whether the C compiler works
-configure:3818: gcc ... "-L/usr/lib/x86_64-linux-gnu" ... >&5
-gcc: error: "-L: No such file or directory
-gcc: error: /usr/lib/x86_64-linux-gnu": No such file or directory
-```
-
-Cause
-: In Jenkins' global configuration you set the environment variable LDFLAGS="-L/usr/lib/x86_64-linux-gnu".
-
-The quotes are not necessary here.
-
-Solution
-: Remove the quotes, save the global configuration and restart the job.
-
-If the environment variable PKG_CONFIG_PATH also contains that directory, you can omit it in LDFLAGS.
-
-#### Jenkins cannot access the Git repository
-
-Problem
-: Jenkins cannot access the Git repository
-
-The console log contains the lines:
-
-```sh
-stderr: fatal: unable to connect to git.gnome.org:
-git.gnome.org[...]: errno=Connection timed out
-```
-
-Cause
-: The Gnome Git server is down for maintenance.
-
-Solution
-: Try again later.
+: Use tools provided by your distribution to find which package contains
+`gtk-encode-symbolic-svg`, and install that package. Since Ubuntu 20.04
+focal, the tool `gtk-encode-symbolic-svg` is in Ubuntu package
+`libgtk-3-bin`.
+Formerly in Ubuntu package `gtk-3-examples`.
### JHBuild
#### JHBuild ignores autogenargs
Problem
-: JHBuild ignores the '''autogenargs''' parameter for a target.
+: JHBuild ignores the `autogenargs` parameter for a target.
Cause
: A simple typo. In this case it ended with duplicated quotes and was after the closing bracket of the
autotools tag.
Solution
-: * Use the proper syntax: <autotools ....="" autogenargs="...">
-</autotools>
+: * Use the proper syntax: `<autotools ....="" autogenargs="..."> </autotools>`
* If the options in the JHBuild menu on the command line don't help, cancel the JHBuild process (option
'3'-give up on module') and run it again.
### See also
@@ -744,20 +698,17 @@ Neither cleaning or make distclean bring them back.
Cause
: Your project configuration is perhaps garbled.
-Solution
-: `Alt. A`
-
-In a terminal window change to the project's workspace folder, enter
+Solution A
+: In a terminal window change to the project's workspace folder, enter
`make distclean` and `./autogen.sh` resp. `./configure`. Every time you
want to reconfigure your project repeat this step. Subsequently building
the project in Eclipse works despite the disabled Reconfigure/Autotools
menu items.
-`Alt. B`
-
-* Delete the project (but '''don't tick''' 'Delete project contents on disk (cannot be undone)'!!)
-* Create the project again: Makefile project from existing sources, then New/Convert to Autotools project
-* In the project's properties configure the Autotools, Paths and Symbols (Include Path, Referenced projects)
+Solution B
+: * Delete the project (but **don't tick** "*Delete project contents on disk (cannot be undone)*"!!)
+ * Create the project again: Makefile project from existing sources, then New/Convert to Autotools project
+ * In the project's properties configure the Autotools, Paths and Symbols (Include Path, Referenced
projects)
#### Reconfigure fails with message 'aclocal: error: non-option arguments are not accepted: '-I'
@@ -777,22 +728,22 @@ Problem
: Trying to build, clean or reconfigure the project ends with an error, that either sh, make, gcc or g++
could not be found although they are there.
Cause
-: Eclipse doesn't find them in the PATH variable. Either you didn't include ${PATH} in your PATH settings or
you included it, but Eclipse doesn't resolve it.
+: Eclipse doesn't find them in the `PATH` variable. Either you didn't include `${PATH}` in your `PATH`
settings or you included it, but Eclipse doesn't resolve it.
Solution
-: * Edit the project's environments settings (Properties/ C/C++ Build / Environment). If the PATH variable
doesn't appear here or is not printed boldly, then cancel that dialog and edit them in Window / Preferences /
C/C++ Build / Environment).
- * Make sure your PATH variable setting contains the string ':${PATH}'. It must have the curly braces
around it! If the variable is already there and isn't resolved anyway, then get its value from your operating
system and replace ${PATH} with that value.
+: * Edit the project's environments settings (Properties/ C/C++ Build / Environment). If the `PATH` variable
doesn't appear here or is not printed boldly, then cancel that dialog and edit them in Window / Preferences /
C/C++ Build / Environment).
+ * Make sure your `PATH` variable setting contains the string `:${PATH}`. It must have the curly braces
around it! If the variable is already there and isn't resolved anyway, then get its value from your operating
system and replace `${PATH}` with that value.
#### Eclipse doesn't recognize CDT/Autotools project anymore
Problem
-: After starting Eclipse has closed my CDT project. When trying to reopen it I get the message 'The project
description file (.project) for '${My project}' is missing. This file contains important information about
the project. The project will not function properly until this file is restored.'
+: After starting Eclipse has closed my CDT project. When trying to reopen it I get the message "*The project
description file (.project) for '${My project}' is missing. This file contains important information about
the project. The project will not function properly until this file is restored.*"
Problem
: Eclipse tells in the project's properties that the project is not a CDT project (anymore).
Cause
-: Eclipse's projects settings got lost. One candidate is having run 'git clean -xdf' in the workspace (in
the first case when
+: Eclipse's projects settings got lost. One candidate is having run `git clean -xdf` in the workspace.
Solution
: If you have a backup of the files .project, .cproject, .autotools, then restore them now to the project's
folder. If you don't have them at hand:
@@ -846,14 +797,14 @@ Solution
## Manage versions
-### Git
+### git
#### I'm a few commits behind
Problem
-: After checking out a particular branch, Git tells me, that I'm a few commits behind,
-
-for example: 'Your branch is behind 'origin/gimp-2-8' by 2 commits, and can be fast-forwarded.'
+: After checking out a particular branch, git tells me, that I'm a few
+commits behind, for example: '*Your branch is behind 'origin/gimp-2-10'
+by 2 commits, and can be fast-forwarded.*'
Cause
: On `git pull`, git didn't update the HEAD on your local branch for whatever reason.
@@ -861,10 +812,10 @@ Cause
Solution
: Try `git pull origin` to update your local branch.
-#### Git marks untouched files as dirty
+#### git marks untouched files as dirty
Problem
-: git status shows that there are untracked files I haven't touched at all
+: `git status` shows that there are untracked files I haven't touched at all
For instance this:
@@ -881,34 +832,36 @@ Untracked files:
plug-ins/metadata/
```
-These files are not in the current branch, but in another (for instance gimp-2-8).
+These files are not in the current branch, but in another (for instance `gimp-2-10`).
Cause
-: For some reasons a recent '''git checkout''' did not delete them. Now these zombies lie around to frighten
poor developers.
+: For some reasons a recent `git checkout` did not delete them. Now these zombies lie around to frighten
poor developers.
Solution
: * Remove them from your disk.
- * If you noticed this error in your IDE then refresh your workspace there (in Eclipse: right click on your
project, then click '''Refresh''').
+ * If you noticed this error in your IDE then refresh your workspace there (in Eclipse: right click on your
project, then click "Refresh").
#### Pull error: 'Insufficient permission for adding an object to repository database .git/objects'
Problem
-: On pulling Git shows me the aforementioned error.
+: On pulling git shows me the aforementioned error.
Cause
: Permission issues in your file system.
Solution
-: * Change into your directory where the project's .git folder resides. Usually this is the working
directory.
- * On Linux or OS X run '''sudo chown -R gituser:gituser .git/objects''' (replace gituser with your user
name). On Windows right click on the .git/objects folder, choose 'Properties', choose the 'Security' tab,
click the 'Advanced' button, choose the 'Owner' tab, click the 'Edit...' button. Set the file owner for that
folder and all files and subdirectories in it. See also the
[http://www.techotopia.com/index.php/Understanding_Windows_Server_2008_File_and_Folder_Ownership_and_Permissions#Taking_and_Transferring_Windows_Server_2008_File_and_Folder_Ownership
Techotopia tutorial]
+: * Change into your directory where the project's `.git/` folder resides. Usually this is the working
directory.
+ * On Linux or OS X run `sudo chown -R gituser:gituser .git/objects` (replace gituser with your user name).
+ On Windows right click on the `.git/objects` folder, choose 'Properties', choose the 'Security' tab,
click the 'Advanced' button, choose the 'Owner' tab, click the 'Edit...' button. Set the file owner for that
folder and all files and subdirectories in it. See also the [Techotopia
tutorial](http://www.techotopia.com/index.php/Understanding_Windows_Server_2008_File_and_Folder_Ownership_and_Permissions#Taking_and_Transferring_Windows_Server_2008_File_and_Folder_Ownership)
### Eclipse
#### Eclipse marks untouched files as dirty
Problem
-: Eclipse shows dirty files and folders I have never touched
-<a href="#Git_marks_untouched_files_as_dirty"> See the related Git error.</a>
+: Eclipse shows dirty files and folders I have never touched.
+
+[See the related Git error](#git-marks-untouched-files-as-dirty)
### See also
@@ -931,7 +884,7 @@ Problem
#### Lots of merge conflicts in GIMP master
Problem
-: I'm translating on the current production branch of GIMP (2-8 etc.) and on master. I'd like to cherry-pick
my changes from the production branch to the master branch. But I get lots of merge conflicts and changes I
never introduced.
+: I'm translating on the current production branch of GIMP (`gimp-2-10`, etc.) and on `master`. I'd like to
cherry-pick my changes from the production branch to the master branch. But I get lots of merge conflicts and
changes I never introduced.
Cause
: Cherry-picking translations from the production branch into the master branch doesn't work.
@@ -973,8 +926,10 @@ Cause
: Missing environment variables.
Solution
-: See above under 'Building'. The environment variable GEGL_PATH must reference the top gegl directory, not
just its parent.
-Referencing the parent is sufficient for GIMP to start, but not for plugins to load without these warnings.
+: See above under 'Building'. The environment variable `GEGL_PATH` must
+reference the top GEGL directory, not just its parent. Referencing the
+parent is sufficient for GIMP to start, but not for plugins to load
+without these warnings.
#### GIMP fails to start with error, 'GIMP requires the GEGL operation "gegl:alien-map"'
@@ -999,11 +954,11 @@ If the plugin crashes or fails to respond, Gimp gives the error above.
You probably installed a plugin that is fatally flawed.
Solution
-: Remove the plugin. To see which plugin to remove, start Gimp with the '--verbose' flag, and it will print
the pathname of plugin files as it queries them.
+: Remove the plugin. To see which plugin to remove, start GIMP with the `--verbose` flag, and it will print
the pathname of plugin files as it queries them.
To debug the flawed plugin, you can use print statements.
-An interpreted plugin may fail very early in its text, for example in the hashbang i.e. '#!/usr/bin/env
python' statement on the first line,
+An interpreted plugin may fail very early in its text, for example in the hashbang i.e. `#!/usr/bin/env
python3` statement on the first line,
or in an import statement.
#### Chain of python exceptions beginning with gi.RepositoryError: Typelib file for namespace 'Gegl',
version '0.4' not found
@@ -1012,12 +967,16 @@ Problem
: On startup, GIMP starts but shows a long chain of Python exceptions. The root exception (the first in the
list) is as above. Affects loading of plugins.
Cause
-: Python is using GLib introspection, but can't find the typelibs for GIMP. Typelibs are in a directory
named girepository-1.0. The GIMP typelib is named like "Gimp-3.0.typelib".
+: Python is using GOBject introspection, but can't find the typelibs for GIMP. Typelibs are in a directory
named `girepository-1.0`. The GIMP typelib is named `Gimp-3.0.typelib`.
Solution
-: Define environment variable GI_TYPELIB_PATH. For example, export
GI_TYPELIB_PATH=/usr/local/lib/x86_64-linux-gnu/girepository-1.0:/usr/local/lib/girepository-1.0 . The
example is for Ubuntu 19.10. You may want to change the prefix of the paths, for example using the
GIMP_PREFIX environment variable (if you use it.)
+: Define environment variable `GI_TYPELIB_PATH`. For example, `export
+GI_TYPELIB_PATH=/usr/local/lib/x86_64-linux-gnu/girepository-1.0:/usr/local/lib/girepository-1.0`.
+The example is for Ubuntu 19.10. You may want to change the prefix of
+the paths, for example using the `GIMP_PREFIX` environment variable (if
+you use it.)
-The typelibs for GIMP, Gegl, and Babl might be on different paths (as in the example.)
+The typelibs for GIMP, GEGL, and babl might be on different paths (as in the example).
#### Gtk-Message: 19:04:46.797: Failed to load module "canberra-gtk-module"
@@ -1025,10 +984,10 @@ Problem
: Terminal often displays message like above. Does not affect operation, except sounds may be missing?
Cause
-: Package libcanberra-gtk3-module is missing.
+: Package `libcanberra-gtk3-module` is missing.
Solution
-: Install missing package, for example: sudo apt-get install libcanberra-gtk3-module
+: Install missing package, for example: `sudo apt-get install libcanberra-gtk3-module`
#### (gimp-2.99:xx): dbind-WARNING **: 09:35:43.023: Couldn't register with accessibility bus:
@@ -1039,7 +998,7 @@ Cause
: Seems to be a long-standing bug in Linux distributions.
Solution
-: In your environment, export NO_AT_BRIDGE=1
+: In your environment: `export NO_AT_BRIDGE=1`
#### luajit: ...mp/2.99/plug-ins/goat-exercise-lua/goat-exercise-lua.lua:22: module 'lgi' not found:
@@ -1049,7 +1008,7 @@ Affects loading of lua language plugins.
In the development branch of GIMP, a set of "goat-exercise-foo" plugins exercise some GObject Introspection
language bindings (C, Python, Lua, JS, Scheme, Perl ?)
Cause
-: Package lua-lgi is missing.
+: Package `lua-lgi` is missing.
Solution
: Install the package.
@@ -1060,38 +1019,18 @@ Problem
: On Ubuntu (only?), when using a plugin that opens a Gtk3 file chooser widget, terminal shows a message as
above, and plugin crashes.
Cause
-: Package gnome-icon-theme is missing. See [https://gitlab.gnome.org/GNOME/gimp/-/issues/2029
https://gitlab.gnome.org/GNOME/gimp/-/issues/2029].
+: Package `gnome-icon-theme` is missing. See [#2029](https://gitlab.gnome.org/GNOME/gimp/-/issues/2029).
Solution
-: Install the package. If you are not building Gimp yourself, apparently this issue is fixed by the
packaging of Gimp having a dependency on package gnome-icon-theme.
+: Install the package. If you are not building GIMP yourself, apparently this issue is fixed by the
packaging of GIMP having a dependency on package `gnome-icon-theme`.
#### (gimp-2.99:xx): dconf-WARNING **: 13:59:42.430: failed to commit changes to dconf: Failed to execute
child process ?dbus-launch? (No such file or directory)
Problem
-: The message appears as you start a plugin. It seems harmless unless you have configured GLib to stop on
warnings, or if you want to use the services of [https://en.wikipedia.org/wiki/D-Bus dbus]
+: The message appears as you start a plugin. It seems harmless unless you have configured GLib to stop on
warnings, or if you want to use the services of [dbus](https://en.wikipedia.org/wiki/D-Bus)
Cause
-: This is a warning from GLib. Gimp is usually built to support dbus (but can be configured without that
support?) The message means that when Gimp attempted to execute the command 'dbus-launch', it could not be
found on the system.
-
-Solution
-: Install package dbug-x11, or whichever package contains the executable command dbus-launch.
-
-## Templates
-
-#### Template for investigated solutions
+: This is a warning from GLib. GIMP is usually built to support dbus (but can be configured without that
support?). The message means that when GIMP attempted to execute the command `dbus-launch`, it could not be
found on the system.
-Problem
-:
-Cause
-:
Solution
-:
-
-#### Template for workarounds
-
-Problem
-:
-
-'''Workaround:'''
-
-Anyway, this is just a workaround. If you know the cause and a proper solution, feel free to edit this
posting.
+: Install package `dbus-x11`, or whichever package contains the executable command dbus-launch.
diff --git a/content/core/setup/build/_index.md b/content/core/setup/build/_index.md
index ec322c9..66ce0f1 100644
--- a/content/core/setup/build/_index.md
+++ b/content/core/setup/build/_index.md
@@ -288,8 +288,7 @@ You can customize the directory where GIMP stores settings. This prevents any in
## Problems?
Most problems will occur during the configure stage, and with any luck it's just a missing package and the
error message will make it clear what package you need. But there are more subtle problems that can occur. If
you have a difficult error, look in:
-
-[Problems and Solutions](problems_and_solutions)
+[Problems and Solutions](../problems_and_solutions#build)
## Running Your New GIMP
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
