I can't see exactly why it's doing this. I have the same version of gimp for windows with the same scripts(they are identical in size, etc). Yet the windows version works just fine and the gimp version see's the script box crash. This has happened when using: Xtns -< Script-Fu -> Web Page Themes -> Alien Glow -> <any> I tried reinstalling gimp and also fiddilng with the file permissions of the scripts in question however none of that did any good. Reproducible: Always Steps to Reproduce:
It would be helpful to know the Gimp version, and also if there is any output to the console when Gimp 'crashes'.
Resolving this bug, I've encountered no problems similar to this on 3 different systems running gimp-1.3.13. Feel free to reopen when you can provide necessary information for debugging.
Sorry it took me awhile to get back to you. I've been dealing with hardware problems with my router/firewall. I found the problem and tho it only showed during that one particular script part it seems to be related to the xsane plugin. I've reciently got a hp 2300c scanjet and some of the sane backends on the dll.conf were making things odd at least for the plugins. The kernel now supports the 2300c with the pre 6 2.4.21 patch(but oddly that patch messed up my usb so I had to copy the scanner patch over to a fresh 2.4.20 tree). Though that scanner isn't supported by sane and hp isn't very cooperative I've found it responds to one scanner listed in the list in dll.conf.(now I just need to find the windows firmware file for that specific printer) Anyways. Depending on the scanner a person has some of those listed in the dll.conf seem to have an effect on the xsane plugin in gimp. Which causes gimp to run but certain scripts to freeze.
I can't replicate this problem, and I'm not sure if it is even an issue with the new versions of gimp that have come out since this bug was filed.
