Hi,

I downloaded gimp-2.4.5.tar.bz2 and verified that the md5check sum is OK. I un- compressed it and ran the usual ./configure --prefix=/usr/gimp-2.4.5/ make
#make install
without any visible problem.

When I run gimp I get

/usr/gimp-2.4.5/bin/gimp-2.4 Unable to read initialization file script-fu.init

Gimp looks OK. I can work with it, but I can't find the "decor" and "Alpha-to-logo" filters, and in Xtns, Logos and other items are absent.

What is wrong?

Hi,

On Sat, 2008-04-19 at 22:40 +0200, julien wrote:

I downloaded gimp-2.4.5.tar.bz2 and verified that the md5check sum is OK. I un- compressed it and ran the usual ./configure --prefix=/usr/gimp-2.4.5/ make
#make install
without any visible problem.

When I run gimp I get

/usr/gimp-2.4.5/bin/gimp-2.4

Do you set LD_LIBRARY_PATH to /usr/gimp-2.4.5/lib when running gimp? Otherwise this can't work. You can't just install to some non-standard prefix and run the binary there. You also need to adjust the library search path accordingly.

Sven

Hi,

On Sat, 2008-04-19 at 15:40 -0500, Jim Sabatke wrote:

Things have been moved about since 2.4 was initially released and it confused me for a bit too.

Nothing has been moved in the 2.4 series since 2.4.0 was released. We only do bug-fixes in the stable 2.4 tree. The menu locations are stable. The only changes you might have seen in the menus are due to translation updates.

Sven

Misunderstanding.

I actually don't have, in my GIMP-2.4.5, "decor" and "Alpha-to-logo" filters which are normally present.
Why that?

julien wrote:

I downloaded gimp-2.4.5.tar.bz2 and verified that the md5check sum is OK.

[snip]

When I run gimp I get

/usr/gimp-2.4.5/bin/gimp-2.4 Unable to read initialization file script-fu.init

Your install is broken. None of the Script-Fu scripts will work without the script-fu.init file.

When I run gimp I get

/usr/gimp-2.4.5/bin/gimp-2.4 Unable to read initialization file script-fu.init

Your install is broken. None of the Script-Fu scripts will work without the script-fu.init file.

I un-installed GIMP-2.4.5 then I re-installed it after verifying the md5 sum.
The problem is the same.
What can I do else?

(I installed many GIMP versions before, without that kind of problem. OpenSuse 10.2)

Hi, maybe you have re-download the installation. Because can be a data transfer error

When I run gimp I get

/usr/gimp-2.4.5/bin/gimp-2.4 Unable to read initialization file script-fu.init

Your install is broken. None of the Script-Fu scripts will work without the
script-fu.init file.

I un-installed GIMP-2.4.5 then I re-installed it after verifying the md5 sum.
The problem is the same.
What can I do else?

(I installed many GIMP versions before, without that kind of problem. OpenSuse 10.2)

Hi,

Hi, maybe you have re-download the installation. Because can be a data transfer error

This morning, I 'make clean', #make uninstall, and deleted my source directory (where gimp-2.4.5 was un-compressed).

Then I uncompressed gimp-2.4.5.tar.bz2 into telechar/gimp-2.4.5/ Created /usr/local/gimp-2.4.5/ directory. ./configure --prefix=/usr/local/gimp-2.4.5/ make
#make install

No problem while processing, but my problem remains: no Decor and Alpha-to-logo filters and this
Unable to read initialization file script-fu.init message.

Yet, script-fu.init is in /usr/local/gimp-2.4.5/share/gimp/2.0/scripts/

Here --verbose:

INIT: gimp_load_config Parsing '/home/julien/.gimp-2.4/unitrc' Parsing '/usr/local/gimp-2.4.5/etc/gimp/2.0/gimprc' Parsing '/home/julien/.gimp-2.4/gimprc' gimp_composite: use=yes, verbose=no
Processor instruction sets: +mmx +sse -sse2 -3dnow -altivec -vis Adding theme 'Default' (/usr/local/gimp-2.4.5/share/gimp/2.0/themes/Default) Adding theme 'Small' (/usr/local/gimp-2.4.5/share/gimp/2.0/themes/Small) Writing '/home/julien/.gimp-2.4/themerc' Trying splash '/home/julien/.gimp-2.4/gimp-splash.png' ... failed Trying splash '/usr/local/gimp-2.4.5/share/gimp/2.0/images/gimp-splash.png' ... OK INIT: gimp_initialize
INIT: gimp_real_initialize
INIT: gui_initialize_after_callback
INIT: gimp_restore
Parsing '/home/julien/.gimp-2.4/parasiterc' Loading 'brush factory' data
Loading 'pattern factory' data
Loading 'palette factory' data
Loading 'gradient factory' data
Loading fonts
Parsing '/home/julien/.gimp-2.4/documents' Parsing '/home/julien/.gimp-2.4/templaterc' Parsing '/home/julien/.gimp-2.4/modulerc' INIT: gui_restore_callback
clipboard: writable pixbuf format: image/png clipboard: writable pixbuf format: image/x-icon clipboard: writable pixbuf format: image/x-ico clipboard: writable pixbuf format: image/bmp clipboard: writable pixbuf format: image/x-bmp clipboard: writable pixbuf format: image/x-MS-bmp clipboard: writable pixbuf format: image/tiff clipboard: writable pixbuf format: image/jpeg Parsing '/home/julien/.gimp-2.4/sessionrc' Parsing '/home/julien/.gimp-2.4/toolrc' Parsing '/home/julien/.gimp-2.4/contextrc' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-rect-select-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-rect-select-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-ellipse-select-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-ellipse-select-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-free-select-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-free-select-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-fuzzy-select-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-fuzzy-select-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-by-color-select-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-by-color-select-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-iscissors-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-iscissors-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-foreground-select-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-foreground-select-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-vector-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-vector-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-color-picker-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-color-picker-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-zoom-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-zoom-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-measure-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-measure-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-move-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-move-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-align-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-align-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-crop-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-crop-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-rotate-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-rotate-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-scale-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-scale-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-shear-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-shear-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-perspective-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-perspective-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-flip-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-flip-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-text-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-text-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-bucket-fill-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-bucket-fill-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-blend-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-blend-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-pencil-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-pencil-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-paintbrush-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-paintbrush-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-eraser-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-eraser-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-airbrush-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-airbrush-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-ink-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-ink-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-clone-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-clone-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-heal-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-heal-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-perspective-clone-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-perspective-clone-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-convolve-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-convolve-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-smudge-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-smudge-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-dodge-burn-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-dodge-burn-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-color-balance-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-color-balance-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-hue-saturation-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-hue-saturation-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-colorize-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-colorize-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-brightness-contrast-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-brightness-contrast-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-threshold-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-threshold-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-levels-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-levels-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-curves-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-curves-tool.presets' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-posterize-tool' Parsing '/home/julien/.gimp-2.4/tool-options/gimp-posterize-tool.presets' INIT: gimp_real_restore
Parsing '/home/julien/.gimp-2.4/pluginrc' Starting extension: 'extension-script-fu' Unable to read initialization file script-fu.init INIT: gui_restore_after_callback
Parsing '/home/julien/.gimp-2.4/menurc' Parsing '/home/julien/.gimp-2.4/devicerc' Parsing '/home/julien/.gimp-2.4/controllerrc' Parsing '/home/julien/.gimp-2.4/colorrc' loading menu '/usr/local/gimp-2.4.5/share/gimp/2.0/menus/toolbox-menu.xml' for /toolbox-menubar

Julien

julien wrote:

Hi,

This morning, I 'make clean', #make uninstall, and deleted my source directory (where gimp-2.4.5 was un-compressed).

Then I uncompressed gimp-2.4.5.tar.bz2 into telechar/gimp-2.4.5/ Created /usr/local/gimp-2.4.5/ directory. ./configure --prefix=/usr/local/gimp-2.4.5/ make
#make install

Hello

I can imagine that some parsing mechanism gets confused of the '.' in the prefix. Does it work if you use the prefix /usr/local/gimp-2-4-5 instead?

BR,
Martin Nordholts

Hi all,

All files in my /usr/local/gimp-2.4.5/ are root. Is this normal?

If I run gimp-2.4.5 in root mode, I have Decor, Alpha-to-logo and all items in Xtns!

And a new error message:

# /usr/local/gimp-2.4.5/bin/gimp-2.4 Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

My computer is connected to the Internet... GIMP seems to work normally in root mode...

How could I get the 'scripts' directory in root mode?

Martin Nordholts wrote:

I can imagine that some parsing mechanism gets confused of the '.' in the prefix. Does it work if you use the prefix /usr/local/gimp-2-4-5 instead?

The '.' characters in the prefix are not a problem. I have directories whose names end in gimp-2.2 and gimp-2.4 as targets for test installs on my machine.

Hi Julien!

On Mon, Apr 21, 2008 at 11:18 PM, julien wrote:

Hi all,

All files in my /usr/local/gimp-2.4.5/ are root. Is this normal?

You mean they belong to root?
That's okay, it's normal.

If I run gimp-2.4.5 in root mode, I have Decor, Alpha-to-logo and all items in Xtns!

In this case, the problem seems to be that normal users don't have permission to read the files in scripts/ directory (or permission to enter the scripts directory).
You should check that scripts/ directory has execute permission for all users, and that all files in scripts/ have read permission for all users.

In my installation, scripts/ directory has permissions 755, and its contents have permissions 644. This happens automatically upon installation, so I believe something strange has happened on your system to alter the permissions. I admit I do not try altering the prefix in the way you have, it may be an unaccounted bug. Anyway you can work around it by making sure the scripts/ directory has appropriate permissions, and executing 'chmod +x -R *' inside the scripts/ directory

One other possibility is that the script-fu plugin executable does not allow any user to execute it (only root), which can be fixed just as readily

If one of the above turns out to be the case, we need to work out the origin of the bug and a bug report needs to be filed later.

Hope that helps,

David

julien wrote:

All files in my /usr/local/gimp-2.4.5/ are root. Is this normal?

If I run gimp-2.4.5 in root mode, I have Decor, Alpha-to-logo and all items in Xtns!

Yes, it is normal. What is more important is the permissions on the files and directories. If everything is working properly when you are logged in as root but not when you are logged in as a normal user, you have the wrong permissions on the GIMP files and directories.

Hi David,

In my installation, scripts/ directory has permissions 755, and its contents have permissions 644. This happens automatically upon installation, so I believe something strange has happened on your system to alter the permissions. I admit I do not try altering the prefix in the way you have, it may be an unaccounted bug. Anyway you can work around it by making sure the scripts/ directory has appropriate permissions, and executing 'chmod +x -R *' inside the scripts/ directory

In my installation also, scripts/directory has permissions drwx r-x r-x (755)
and files in it have permissions rw- r-- r-- (644). I ran 'chmod +x -R *' inside the scripts/ directory and now all files are rwx r-x r-x

But my problem is unchanged.

One other possibility is that the script-fu plugin executable does not allow any user to execute it (only root), which can be fixed just as readily

I don't understand this. Which script-fu plug-in? Where is it?

Thank you for your help,

Julien

Hi Julien,

On Tue, Apr 22, 2008 at 7:22 PM, julien wrote:

Hi David,

> In my installation, scripts/ directory has permissions 755, and its > contents have permissions 644. This happens automatically upon > installation, so I believe something strange has happened on your > system to alter the permissions. I admit I do not try altering the > prefix in the way you have, it may be an unaccounted bug. > Anyway you can work around it by making sure the scripts/ directory > has appropriate permissions, and executing 'chmod +x -R *' inside the > scripts/ directory
>

In my installation also, scripts/directory has permissions drwx r-x r-x (755)
and files in it have permissions rw- r-- r-- (644). I ran 'chmod +x -R *' inside the scripts/ directory and now all files are rwx r-x r-x

But my problem is unchanged.

One other possibility is that the script-fu plugin executable does not

> allow any user to execute it (only root), which can be fixed just as > readily
>
I don't understand this. Which script-fu plug-in? Where is it?

The script-fu plugin that hosts all the scripts and runs them as requested; script-fu is only a plug-in, it is not built into gimp. it's in the system wide gimp plugins directory, which in your case may be /usr/local/gimp-2.4.5/lib/gimp/2.0/plug-ins/

David

On Tue, Apr 22, 2008 at 11:32 PM, David Gowers wrote:

Hi Julien,

On Tue, Apr 22, 2008 at 7:22 PM, julien wrote: > Hi David,
>
>
> > In my installation, scripts/ directory has permissions 755, and its > > contents have permissions 644. This happens automatically upon > > installation, so I believe something strange has happened on your > > system to alter the permissions. I admit I do not try altering the > > prefix in the way you have, it may be an unaccounted bug. > > Anyway you can work around it by making sure the scripts/ directory > > has appropriate permissions, and executing 'chmod +x -R *' inside the > > scripts/ directory
> >
>
> In my installation also, scripts/directory has permissions drwx r-x r-x > (755)
> and files in it have permissions rw- r-- r-- (644). > I ran 'chmod +x -R *' inside the scripts/ directory and now all files are > rwx r-x r-x
>
> But my problem is unchanged.
>
> > One other possibility is that the script-fu plugin executable does not > > allow any user to execute it (only root), which can be fixed just as > > readily
> >
> I don't understand this. Which script-fu plug-in? Where is it? The script-fu plugin that hosts all the scripts and runs them as requested; script-fu is only a plug-in, it is not built into gimp. it's in the system wide gimp plugins directory, which in your case may be /usr/local/gimp-2.4.5/lib/gimp/2.0/plug-ins/

Oops, sorry Julien, it can't be that, actually, looking at your results from --verbose it seems clear that script-fu.init is the culprit.

So, are the following files:

/usr/local/gimp-2.4.5/share/gimp/2.0/scripts/script-fu-compat.init /usr/local/gimp-2.4.5/share/gimp/2.0/scripts/script-fu.init

readable by everyone? If not, they should be.

David

Hi,

So, are the following files:

/usr/local/gimp-2.4.5/share/gimp/2.0/scripts/script-fu-compat.init /usr/local/gimp-2.4.5/share/gimp/2.0/scripts/script-fu.init

readable by everyone? If not, they should be.

As all files in

/usr/local/gimp-2.4.5/share/gimp/2.0/scripts/ , these two files are now rwx r-x r-x

I tried after putting them julien-users instead of root-root : problem unchanged.

I add, if this could be a clue, that #umask gives 0022.

Julien

Hi,

I resolved my problem by deleting the hidden directory /home//.gimp-2.4.

This directory, that contains gimp settings, is not deleted when uninstalling gimp. A new installation uses it. That's interesting if you install a new version, but, if it contains an error, this error persists in all new installations.

GIMP re-creates this directory on starting again.

Julien

On Tue, Apr 22, 2008 at 11:32 PM, David Gowers wrote:

Hi Julien,

On Tue, Apr 22, 2008 at 7:22 PM, julien wrote: > Hi David,
>
>
> > In my installation, scripts/ directory has permissions 755, and its > > contents have permissions 644. This happens automatically upon > > installation, so I believe something strange has happened on your > > system to alter the permissions. I admit I do not try altering the > > prefix in the way you have, it may be an unaccounted bug. > > Anyway you can work around it by making sure the scripts/ directory > > has appropriate permissions, and executing 'chmod +x -R *' inside the > > scripts/ directory
> >
>
> In my installation also, scripts/directory has permissions drwx r-x r-x > (755)
> and files in it have permissions rw- r-- r-- (644). > I ran 'chmod +x -R *' inside the scripts/ directory and now all files are > rwx r-x r-x
>
> But my problem is unchanged.
>
> > One other possibility is that the script-fu plugin executable does not > > allow any user to execute it (only root), which can be fixed just as > > readily
> >
> I don't understand this. Which script-fu plug-in? Where is it? The script-fu plugin that hosts all the scripts and runs them as requested; script-fu is only a plug-in, it is not built into gimp. it's in the system wide gimp plugins directory, which in your case may be /usr/local/gimp-2.4.5/lib/gimp/2.0/plug-ins/

Oops, sorry Julien, it can't be that, actually, looking at your results from --verbose it seems clear that script-fu.init is the culprit.

So, are the following files:

/usr/local/gimp-2.4.5/share/gimp/2.0/scripts/script-fu-compat.init /usr/local/gimp-2.4.5/share/gimp/2.0/scripts/script-fu.init

readable by everyone? If not, they should be.

David