...using sample colorize with current chosen gradient as option? Before I submit a bugzilla, I want comfirmation or better yet, let someone else do so since I tire of getting chewed out. lol

Bonjour,

@lylejk
I have the same problem with many versions of Gimp.

It seems that the error only applies to the Windows version, under Linux operating properly.

Thanks samj/Popo; submitted the bug for the curious.

https://bugzilla.gnome.org/show_bug.cgi?id=693797

I just have windows and have the same error.
So what is the desired effect?
Can someone (linux user) can post a sreenshot of the plug-in with a gradient selected?

For Win XP 32 Gimp 2.8.1 works well - for 2.8.4 also the same error

Also, the choice of Sample: gradients ?

I know, what the problem is...
But I have to think about it.
When building the box, where the gradients can be choosen, gimp tests, if the items in the list are valid layers.
If not, there will be the message, and the box is rebuild just with the valid layers. But the two gradient entries are no valid layers. That is the reason, why the two gradient entries disappear after the error.
There are two ways to make the plug-in work:
1. The test is cancelled. Thats not good, because if there is a plugin with the layer box and while running the plug-in, a layer is deleted, the plug-in will crash when choosing the deleted layer.
2. The plug-in is rewritten without the gradients, the gradients could be choosen by an other way. Thats good, but it does solve the problem just for this plug-in. Other plug-ins may use valid functions of gimp (like the sample-colorize plugin), and the problem will appear again.

1. I can give you a libgimp.dll with the cancelled test. It will work, but you have to be careful with deleting layers when a plugin is running.
2. I don't have the knowledge for rewriting the plugin. For that purpose I need a lot of time...
3. I have to think about, how to tell the problem to the bug report. And not today (it's late in germany). The problem is deeper than I thought...

I can not believe, that the problem does not exist with linux. It MUST exist or the problem is even deeper...

Sorry for the confusion. I use Xubuntu and still I have versions of GIMP 2.8.2,and it works good. Tonight I'd like to do updates to version 2.8.4, if it works good under 2.8.4? I say tomorrow. see ya

Yeah; can always create an image of a gradient then run Sample Colorize. Also, this is, as far as I care, a low priorty, but and unexpectent error since I didn't remember seeing it in 2.8.0 (around the last time I used Sample Colorize with an internal gradient).

The change was between 2.8.1 and 2.8.2. It was a fixed bug, where plug-ins (python) crashed, if there were layers deleted while the plugin was still open.

Joined: Sep 24, 2010
Posts: 4630 Ah; fixed one bug only to create another one aye Onkel? lol

Makes sense then. Again, not sure if the developers will even patch this one based on what I'm inferring with the conversation at Buzilla. Rarely, if ever, used the gradient option with Sample Colorize anyway and not sure why I wanted too when I did so earlier today. lol

I did a screenshot before updating, sample colorize runs still in Gimp 2.8.2,after the upgrade to 2.8.4 option "from gradient" is not available.L.o.L
-xubuntu 12.10 32-bit

I proposed a patch for the error.
We will see, what Mitch will say to it...

The error is not in the plug-in, but a function in libgimp/libgimpui. It's not a real error, but it is 'not nice'.
My suggestion for gimp programmers is:
If there is used a selection box with entries for layers, drawables, etc., DON'T mix it with own entries. With my patch, it should be possible, but again, it is 'not nice'.

It's just as well because it doesn't work, but it should still be there; in Windows it just goes away after Gimp 2.8.4 throws the error message(s). For what it's worth, when I relaunch Sample Colorize the gradient options return.


It's seems not a platform specific error.

Looks like they accepted your patch Onkel Hatti. Kudo's to your prowess with the meat of GIMP. They also set the ticket to resolved, but I guess we will have to wait until 2.8.6 (already? lol) before seeing this fix, but I'm sure other quirks will show up by the time the next patch gets released.

Yeah, it is accepted , but unfortunately, with the modification of my patch, there was created an other bug.
I just wrote another comment...

Yes, you are right, the fix will come with the next release. But I am able to compile the fixed libgimpui-2.0-0.dll in 32bit and 64bit, if you know, what I mean...
(but only for windows)

The error is fixed.
For those, who cannot wait...