Next Previous Table of Contents
Troubleshooting
General
If something goes wrong, start Babygimp from the command line. For example
the config file is read before the main window is built, so all error
messages concerning it are printed only to stderr.
Problems and Solutions
- Problem : I call Babygimp and nothing happens.
Solution: Start Babygimp from the command line and check the error
messages.
Check also if you have crashed instance of babygimp running in the
background. In this case try the following (see the internals section for an
explanation):
:> killall -9 babygimp
:> rm ~/.babygimp/babygimp.fifo
- Problem: When using the floodfill function i see the warning ``Deep
recursion on subroutine "main::recursive_floodfill" at ... ``.
Solution: Ignore this message. This is not really a bug, just perhaps a
bad implementation of the floodfill function. Floodfill is implemented
recursive, and perl generates a warning if the recursion depth is larger
than 100.
- Problem: Babygimp cannot read xpm files created by the Gimp!
Solution: There is no solution; this is probably a bug in the
Tk::Photo method (or in the Gimp? I do not know the official xpm format
specification)
Workaround: Load the image e.g. with xv and save it again.
- Problem: xpm files generated by Babygimp cannot be included in C
programms.
Solution: There is no solution; this is a bug in the Photo::put()
method of Perl/Tk. When i have time, i will incorporate a workaround into
Babygimp.
Workaround: Load and save the image with xv.
Next Previous Table of Contents