Hi,

I resolved my problem by deleting the hidden directory
/home/<username>/.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 <[EMAIL PROTECTED]> wrote:
>   
>> Hi Julien,
>>
>>
>>  On Tue, Apr 22, 2008 at 7:22 PM, julien <[EMAIL PROTECTED]> 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
>
>
>   


_______________________________________________
Gimp-user mailing list
Gimp-user@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user

Reply via email to