GNOME Bugzilla – Bug 490326
Add Border...does not work
Last modified: 2008-10-30 20:02:36 UTC
Please describe the problem: Trying to apply a border to a jpg stops and presents the error: Plug-In 'Add Border' left image undo in inconsistent state, closing open undo groups. Steps to reproduce: 1. Load an jpg image 2. Right click image and select Filters -> Decor -> Add Border... 3. Accept the default settings from the dialgo and press ok. Actual results: Error is presented in a dialog. Expected results: The border should be applied. Does this happen every time? Yes Other information:
Seems to work for me. Please give more details so that we can try to reproduce the problem. How large was your image? Did it have an alpha channel? Did you have a selection active?
I used a .jpg file size 2592x1944 72dpi right from mysony camera. No selection. Just like the instructions said. I'm running on Vista. Channels R,B,G
Getting the same bug with a 1680x1050 PNG and JPG, a 1605x1102 XCF, and an 800x556 XCF exported in the current version of GIMP. and in fact every kind of image I can throw at it. I just did a reinstall over 2.2.17 if that's any help. Attempted to add border from both from top menu and right-click menu. I'm running on XP, and channels are also RGB.
Please attach a small example file in the XCF format that shows the problem.
*** Bug 492638 has been marked as a duplicate of this bug. ***
I'm having exact same problem - happens to me when have no alpha channels open & no other layers present in image/jpg file. OS Windows XP - in version 2.2 had no problems w/ executing "border" plug-in - dunno if that will be of any assistance to trouble-shoot cause of error but i hope it might help :) Thank you for time & energy you spend on GIMP for all of us!!!!
The problem gets worse in version 2.4.1. The image is converted to a series of little blocks scattered across the image.
Just tried it, and it works fine for me.
Created attachment 98594 [details] jpg split zip 1 of 3
Created attachment 98595 [details] jpg split zip 2 of 3
Created attachment 98596 [details] jpg split zip 3 of 3 I used 7-zip (SourceForge) to create these split zip files of a jpg from my camera. Should reproduce the bug for you.
I run GIMP under Linux. I was able to run the Add Border script on the image provided without any problems.
Created attachment 98622 [details] ZIP file containing a crappy unmanipulated 420x300 XCF for test purposes. This is from 2.4.1, not 2.4.0, just be aware. Nothing fancy just a basic XCF image with some text to aid in finding the cause of the "Add Border" bug.
*** Bug 494016 has been marked as a duplicate of this bug. ***
Exactly zero problems adding a border to the image here.
I can't believe i am about to offer this - but since replicating the error has been close to impossible for folks - if a developer wanted to contact me directly & do a remote connection to my pc for bout 1/2 hr to see first-hand the error, I am willing to try that. Just at a loss on how to provide more/useful info since the attachments to date sent by other folks encountering same problem I am having have not worked. Email is paperstsoapc0@yahoo.com, or am available via YIM w/ same ID. Just am stumped on what else we can do to enable y'all to help us.
*** Bug 494026 has been marked as a duplicate of this bug. ***
Folks, we need some more info to make any progress on this. Since it seems to be OS specific (in fact, Windows specific), it would help to know what version of Windows each of you is using. Are all of you with the problem using XP? Also, could somebody please insert *exactly* the error message you get when it fails? Lisa, in comment #4, are you saying that it *only* happens when there is no alpha and no other layers? That would be important information. Thanks.
(In reply to comment #18) > Folks, we need some more info to make any progress on this. Since it seems to > be OS specific (in fact, Windows specific), it would help to know what version > of Windows each of you is using. Are all of you with the problem using XP? > Also, could somebody please insert *exactly* the error message you get when it > fails? > Lisa, in comment #4, are you saying that it *only* happens when there is no > alpha and no other layers? That would be important information. > Thanks. >>Hi..I had to un-install vs 2.4.1 and wait for your next release but yes I am >using Windows XP Home Office and the image of the Gimp dog up came up after >trying to create a border and choose black as the color and then change my x >and y to 12 and 36 for an effective border on a 1360 x 2000 dpi image from a >Nikon D1 . The gimp dog said Plug In failed to complete its actions and must >close now and inserted a grey and black blocks around the image on the owrk >box and once I saved it it was a white border 12 x by 36 y so it is >making a border but only in white ..I hope this helps
I can't reproduce this on XP. Neither with the installer version nor with my own builds.
Thank you for your help/attention to this first of all :) My OS is Windows XP Home Edition. The error occurs for me in every possible scenario (image work in progress/several layers present, after flattening image, opening an image & attempting to do nothing more than add a border to existing image). The error message reads every time: "Plug-In 'Add Border' left image undo in inconsistent state, closing open undo groups." & once that error message occurs - none of the other script-fu commands will work until restart GIMP program. In the previous version of GIMP, didnt have any problems executing script-fu commands. I do have a slightly older pc - could the problem possibly be less w/ OS & instead be a RAM issue???
I still have the same exact problems every time the scripft fu commands wont execute and the browser has to be closed and re-opened i un-installed put GTK + 2.2.17 back in ..every thing worked ..un-installed that went back to the new 2-4-1 and tried again...and its hopelessly vbreaking all the script fu commandments ..so again I have un inastalled returned to 2.2.17 and will stay with this now until all this is resolved The hyperthreading compatability is finally truly a blessing withy the new GIMP ..but again for now..I will stay with 2.2.17
Thanks for the patient responses. Several aspects of this are still unclear to me: 1) Is the problem specific to "add border", or are all filters that are implemented as scripts broken? For example, does Filters->Decor->"Add Bevel" break in the same way? 2) Could this have something to do with hyperthreading or parallelism? Michael, Lisa, what sort of processor are you using?
The problem is specific to the "add border" script - the other scripts execute without error/incident just so long as i don't previously in session attempt an "add border" command. (hope that makes sense) My processor is (plz dont start laughing when u see RAM - know its pathetic & i need to get new hard-drive): Intel(R) Celeron(TM) CPU, 1200 MHz, 1.20 GHz, 128 MB RAM
(In reply to comment #23) > Thanks for the patient responses. Several aspects of this are still unclear to > me: > 1) Is the problem specific to "add border", or are all filters that are > implemented as scripts broken? For example, does Filters->Decor->"Add Bevel" > break in the same way? > 2) Could this have something to do with hyperthreading or parallelism? > Michael, Lisa, what sort of processor are you using? Hi Mark here the Filters->Decor->"Add Bevel" breaks in the Windows version but not on my Linux distro so...again seems to be hyperthreading issue as..my board is =ASUS PV800R 3.2ghz 1gb ram and i am running 2 separate hard drives through a hot swapping system as opposed to my older debian build when I ran SuSe 9.1 and 9.2 in Gimp 2.0 days So everything works in Linux didtro but NOT in Win332 version
Well, there seem to be multiple problems here. Mahatmark, would it be possible for you to open a new bug report for yours? It seems to be a different issue than what the other comments in this bug report are describing, and probably an important one. Lisa: I didn't even know XP would run in 128 MB! Based on your other comments, I think this is probably not going to help, but here's a thought. "Add Border" creates several new layers while it is working, and if it can't find memory for them, it will fail. How about creating a tiny little image, say 100x100, and trying it on that? (With no other images open in GIMP.) Incidentally, the fact that no other script-fu will work after you get this error is significant: normally even if a script is broken, the "closing undo groups" thing will clean things up enough to remove any damage. It looks like maybe on your system "Add Border" is actually crashing script-fu, which shouldn't result from just a problem with the individual script.
I tried on plain 100x100 image "add border" - unfortunately same thing happens. I will understand 100% if problem i am experiencing is due to my hardware - the older version of gimp works great & with no problems. While i really like the more "user friendly" aspects of new version - it would be unfair & selfish of me to abuse y'alls (the developers) time, energy & resources in trying to fix an incompatibility that while similiar to original bug submitted is actually very specific to me/my pc. I really was hoping there was just some crazy easy (tho subtle) fix since i dont have any script problems w/ older version. I wont be offended/pissy/cranky if you inform me that there is nothing u can do & remove me from this bugs forum - & do really appreciate all of the energy y'all have expended up to this point :)
Lisa, as the comments show, you aren't the only one having this problem. Unfortunately, I am now officially clueless about what is causing it. What we really need is to figure out what is different between systems that have problems and systems that don't. For the moment, I've run out of ideas, though.
When y'all are trying to "replicate" an error, is there a separate program you run that "catalogs" or documents commands executed by hard-drive to help u pin-point where the problem is occuring. Or if you don't - is there some program/trick out there to do such a thing?? If so, i will happily try to run that at same time so can report more specific information on nature of error. Or would attempting to run a DxDiag on system help? Quite obviously i am not a programmer - just trying to help come up w/ some ideas :)
I am running 32bit Vista on a Gateway Pentium Dual Core with 1GB of RAM. Can offer two things at this point... Is there a debug log file I could enable to track the problem? What are the developer tools used for the Windows build. I have VC++2005 and could run something on my machine if that would help. Or you could send me a debug build of something with logging and I could run that and send you the output.
I can confirm the bug. In the scrpt addborder.scm, I commented out and in again successivly the relevant statements. It turned out that the first call to gimp-free-select in the script triggers the error: (gimp-free-select img 10 (gen_top_array xsize ysize owidth oheight width height) CHANNEL-OP-REPLACE 0 0 0.0) I'm using Windows XP Professional (Windows 5.1 (Build 2600.xpsp_sp2_qdr.070227-2245 : Service Pack 2) Steps to reproduce: Select File -> New... Create Image with default settings Select Filter -> Decoration -> Add Border... Give focus to the dialog (which doesn't pop up in foreground) Just click ok. "Plug-In 'Rand hinzufügen ' left image undo in inconsistent state, closing open undo groups." When I searched for the documentation of gimp-free-select, I stumbled across another border-adding script (frame-it.scm) at http://td-e.com/soft-de/frame-it.php , which also uses gimp-free-select. It worked and the surprise was, that afterwards, I could not reproduce the bug anymore with the original addborder.scm script even after several restarts of gimp. Then I closed gimp removed all my settings (*rc files) in my .gimp-2.4 directory and renamed the frame-it.scm script to frame-it.scm___. Now I could again reproduce the error. I renamed the frame-it.scm script back, restarted gimp and the error occured also with this previously working script. I restarted again, clicked script-fu refresh scripts and tried the new script again. It worked again and afterwards also the addborder.script from gimp. I hope, I could give you eventually a hint to find the problem.
(In reply to comment #31) > I can confirm the bug. In the scrpt addborder.scm, I commented out and in > again successivly the relevant statements. It turned out that the first call to > gimp-free-select in the script triggers the error: > (gimp-free-select img > 10 > (gen_top_array xsize ysize owidth oheight width height) > CHANNEL-OP-REPLACE > 0 > 0 > 0.0) > > I'm using Windows XP Professional (Windows 5.1 (Build > 2600.xpsp_sp2_qdr.070227-2245 : Service Pack 2) > > Steps to reproduce: > Select File -> New... > Create Image with default settings > Select Filter -> Decoration -> Add Border... > Give focus to the dialog (which doesn't pop up in foreground) > Just click ok. > "Plug-In 'Rand hinzufügen ' left image undo in inconsistent state, closing > open undo groups." > > When I searched for the documentation of gimp-free-select, I stumbled across > another border-adding script (frame-it.scm) at > http://td-e.com/soft-de/frame-it.php , which also uses gimp-free-select. It > worked and the surprise was, that afterwards, I could not reproduce the bug > anymore with the original addborder.scm script even after several restarts of > gimp. > > Then I closed gimp removed all my settings (*rc files) in my .gimp-2.4 > directory and renamed the frame-it.scm script to frame-it.scm___. Now I could > again reproduce the error. I renamed the frame-it.scm script back, restarted > gimp and the error occured also with this previously working script. I > restarted again, clicked script-fu refresh scripts and tried the new script > again. It worked again and afterwards also the addborder.script from gimp. > > I hope, I could give you eventually a hint to find the problem. > > >Thank-you I was mentioning in my first bug report 4 days ago that I was having problems with the .scm and I was trying to access the plug-in registry and add extended borders as a temp solution until this add borders prob is solved ..btw I am on the new Kubuntu now...and migrate back and forth between here and windows as its been the only way I can continure my current web projects http://mark-harrington.photos.us.com Linux distro works win32 stil wont here
I can reproduce the bug here with Ubuntu - Gutsy Gibbon ang Gimp 2.4rc3 and even with Gimp 2.5(svn).
Tobias, anything special about your system? Is it perhaps 64bit?
I can reproduce it too. Reliably, it fails each time. Will look into it tomorrow.
I can reproduce this bug. Here is my system: [spc@tesenca ~]$ uname -a Linux tesenca.domicile 2.6.22.9-61.fc6 #1 SMP Thu Sep 27 18:07:59 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux The bug happens with 2.4.1 and 2.5.0. I can confirm comment #31. With my 2.5.0 configuration, I am using scripts from 2.4.1 version (/usr/local/share/gimp/2.0/scripts/). (I hope I'm clear) My tests with 2.5.0 (new set of configuration files automatically imported from 2.4.1): a) copy of frame-it.scm in .gimp-2.5/scripts b) gimp launched c) add border works without any problem and without launching frame-it.scm d) gimp stopped e) frame-it-scm removed f) gimp launched g) add border does not work h) gimp stopped I can loop as many times with always the same result. I have done the same tests with a copy of addborder.scm in my .gimp-2.5/scripts directory (renaming as addborder2.scm and similar modification for the names in the code). I have the same results: add border script works when addborder2 is present and add border script does not work when addborder2 is not present. I have tried with another script that I have just copied into .gimp-2.5/scripts with the same result. I have made some tests with my 2.4.1 configuration. Under .gimp-2.4/scripts, I have 3 scripts; addborder does not work. If I add one script (whatever it is), add border works. In fact, add border works if I have 0, 2 or 4 scripts in .gimp-2.4/scripts and does not work if I have 1 or 3 scripts. But it works with 5 scripts. My last test was only to create an empty file named test.scm in .gimp-2.4/scripts and .gimp-2.5/scripts (4 scripts inside for both with test.scm). It is sufficient to have addborder working again! Sorry to have been so long. I hope that can help. If needed, I can do more tests but please tell me what to test.
I have the same issue : Gimp 2.4.1 on Windows XP. I can confirm the last test indicated in the previous comment : - Create a file named "test.scm" in .gimp-2.4\scripts (this directory is empty on my machine) - Start Gimp - Add border works - Delete the "test.scm" file (Gimp still running) - Add border works - Restart Gimp - Add border does not work I find this so strange, so I thought a confirmation might be useful...
I can confirm this. Running Fedora 8 (x86_64) on a Core2Duo processor. It only seems to happen on Windowd and on 64 bit Linux systems. Or am I wrong here? # uname -a Linux localhost.localdomain 2.6.23.1-49.fc8 #1 SMP Thu Nov 8 22:14:09 EST 2007 x86_64 x86_64 x86_64 GNU/Linux # rpm -q gimp gimp-2.4.1-1.fc8
I had the same issue with Gimp 2.4.1 on Windows. But now, since I have updated Gimp to 2.4.2., the script-fu "Add border" works fine.
(In reply to comment #39) > I had the same issue with Gimp 2.4.1 on Windows. But now, since I have updated > Gimp to 2.4.2., the script-fu "Add border" works fine. > > >I have also now updated to 2.4.2 and no longer find the bug as described , in >this string of comments. Seems fine and working great Thanks-you all >mark
Just for the record I've upgraded to 2.4.2 and I still get the same error. This is on a Fedora x86_64 system. I've got another Fedora system though which is 32 bits, the add border function works just fine there.
(In reply to comment #41) > Just for the record I've upgraded to 2.4.2 and I still get the same error. This > is on a Fedora x86_64 system. I've got another Fedora system though which is 32 > bits, the add border function works just fine there. > >I could not get to to behave on Kubuntu Gutsy..I have not rec'd my Fedora 8 DVD >from Thomas yet so can offer no input there but as I said earlier it seems to >finally be working on the Windows XP x86 drive and all aspects that I have >experimented with behaving as they should >Mark
I've just removed gimp from my disk and I've also removed my .gimp-2.4. I've compiled 2.4.2 and I still get the error. But now, with 0 and 1 script in my .gimp-2.4/scripts, I do not have any problem; with 2 or 3, the problem appears. Adding one empty file, test.scm, does not suppress the problem.
It is possible there is a problem when running under a 64-bit OS. However, I would expect 64-bit related problems to affect other scripts and not just Add Border. Adding/removing scripts in ~/.gimp-2.4/scripts should not fix or break Add Border unless there is some sort of name collision taking place. I will do some testing using a 64-bit version of Linux I have available on my computer to see if I can reproduce the problem.
Using the Gimp 2.4.1 on win xp 32 bit, i had the same problem. Upgrading just now to the 2.4.2 and deleting config files in "documents and settings" resolved the problem!
I just re-upgraded to 2.4.2 (due to 2.2.17 deciding to not see installed fonts, a far more critical error) and this error (as well as the other one) fixed itself. Odd. Uninstalling 2.2.17 with its dedicated uninstaller before installing 2.4.2 seems to get rid of the problem, at least it did in my case.
I can confirm this bug for 2.4.2 as shipped with Ubuntu 7.10 i386 (32 Bit!) (Ubuntu package version is 2.4.2-0ubuntu0.7.10.1). As reported touching test.scm in ~/.gimp-2.4/scripts let's the filter work.
Touching a file in the local user scripts directory will make no difference to whether a Script-Fu script will run or not. The contents of ~/.gimp-2.4/scripts will have an effect. Remove all scripts you have added to your user scripts directory. If the Add Border script runs after doing that, you can add your own scripts to the ~/.gimp-2.4/scripts directory one at a time until you find which one is breaking scripts supplied with GIMP. You can then either delete the offending script or fix it to avoid the conflict with GIMP supplied scripts.
Has this problem been seen in the recent 2.6.0 release of GIMP 2.6.0 or can this bug be closed as OBSOLETE?
I wasn't able to reproduce the problem with 2.6.0.
Let's close as OBSOLETE then.