'critical error' running luminosity mask script
This discussion is connected to the gimp-user-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.
This is a read-only list on gimpusers.com so this discussion thread is read-only, too.
'critical error' running luminosity mask script
Hi -- I just filed a bug (here
) for a 'critical
error' that happens for me with 2.10 RC1 (AppImage from here
).
I thought I'd write here in case anyone had any ideas for workarounds that I might try until the bug gets fixed. E.g. maybe there is something obviously deprecated that the script is doing? (I didn't write the script, but I modified it slightly.) It worked fine with 2.9.5. The script is attached at the bug report.
Thanks for any ideas!
-Casey
'critical error' running luminosity mask script
On Fri, Apr 20, 2018 at 01:35:40PM -0700, Casey Connor wrote:
Hi -- I just filed a bug (here
) for a 'critical error'
that happens for me with 2.10 RC1 (AppImage from here ).I thought I'd write here in case anyone had any ideas for workarounds that I might try until the bug gets fixed. E.g. maybe there is something obviously deprecated that the script is doing? (I didn't write the script, but I modified it slightly.) It worked fine with 2.9.5. The script is attached at the bug report.
Thanks for any ideas!
-Casey
On 2.10.0-RC2 (with latest babl and gegl), running that script after starting the gimp from a term gives a series of failed assertions:
gimp: Gimp-Core-CRITICAL: gimp_channel_push_undo: assertion 'gimp_item_is_attached (GIMP_ITEM (channel))' failed gimp: Gimp-Core-CRITICAL: gimp_channel_push_undo: assertion 'gimp_item_is_attached (GIMP_ITEM (channel))' failed gimp: Gimp-Core-CRITICAL: gimp_channel_push_undo: assertion 'gimp_item_is_attached (GIMP_ITEM (channel))' failed gimp: Gimp-Core-CRITICAL: gimp_channel_push_undo: assertion 'gimp_item_is_attached (GIMP_ITEM (channel))' failed gimp: Gimp-Core-CRITICAL: gimp_channel_push_undo: assertion 'gimp_item_is_attached (GIMP_ITEM (channel))' failed gimp: Gimp-Core-CRITICAL: gimp_channel_push_undo: assertion 'gimp_item_is_attached (GIMP_ITEM (channel))' failed gimp: Gimp-Core-CRITICAL: gimp_channel_push_undo: assertion 'gimp_item_is_attached (GIMP_ITEM (channel))' failed gimp: Gimp-Core-CRITICAL: gimp_channel_push_undo: assertion 'gimp_item_is_attached (GIMP_ITEM (channel))' failed
This does not crash, but obviously the script no-longer works.
Welcome to the script-fu console! And yes, things which worked in even 2.9.6 no-longer work. Happy lisping (if such a concept is possible), or else just "good luck with debugging it".
ĸen
This email was written using 100% recycled letters.
'critical error' running luminosity mask script
Thanks --
starting the gimp from a term gives a series of failed assertions
Hmmm, all I got in stdout was
*WARNING* missing babl fast path(s): "R'G'B'A u8" to "B' u8" *WARNING* missing babl fast path(s): "R'G'B'A u8" to "A u8"
...but anyway yeah I saw those failed assertions in the debug dialog, too.
I don't find any quick ref guides to updating scripts to work with 2.10... any pointers to docs online re: what to look out for?
-c
gimp: Gimp-Core-CRITICAL: gimp_channel_push_undo: assertion 'gimp_item_is_attached (GIMP_ITEM (channel))' failed gimp: Gimp-Core-CRITICAL: gimp_channel_push_undo: assertion 'gimp_item_is_attached (GIMP_ITEM (channel))' failed gimp: Gimp-Core-CRITICAL: gimp_channel_push_undo: assertion 'gimp_item_is_attached (GIMP_ITEM (channel))' failed gimp: Gimp-Core-CRITICAL: gimp_channel_push_undo: assertion 'gimp_item_is_attached (GIMP_ITEM (channel))' failed gimp: Gimp-Core-CRITICAL: gimp_channel_push_undo: assertion 'gimp_item_is_attached (GIMP_ITEM (channel))' failed gimp: Gimp-Core-CRITICAL: gimp_channel_push_undo: assertion 'gimp_item_is_attached (GIMP_ITEM (channel))' failed gimp: Gimp-Core-CRITICAL: gimp_channel_push_undo: assertion 'gimp_item_is_attached (GIMP_ITEM (channel))' failed gimp: Gimp-Core-CRITICAL: gimp_channel_push_undo: assertion 'gimp_item_is_attached (GIMP_ITEM (channel))' failed
This does not crash, but obviously the script no-longer works.
Welcome to the script-fu console! And yes, things which worked in even 2.9.6 no-longer work. Happy lisping (if such a concept is possible), or else just "good luck with debugging it".
ĸen
'critical error' running luminosity mask script
On Fri, Apr 20, 2018 at 02:35:22PM -0700, Casey Connor wrote:
Thanks --
starting the gimp from a term gives a series of failed assertions
Hmmm, all I got in stdout was
*WARNING* missing babl fast path(s): "R'G'B'A u8" to "B' u8" *WARNING* missing babl fast path(s): "R'G'B'A u8" to "A u8"
...but anyway yeah I saw those failed assertions in the debug dialog, too.
I'll guess they are on stderr.
I don't find any quick ref guides to updating scripts to work with 2.10... any pointers to docs online re: what to look out for?
-c
You said you had edited the script - did you not use the script-fu console and its included help for that ? It's some months since I last had to do that, I'm rusty on the details.
And I doubt there will be any quick guides before 2.10 is released. Things change during development. For example, one script I used in 2.9.6 gave a lot of warnings - but in RC1 it appeared to work ok without producing any warnings.
More generally: everyone who uses external scripts will need to test them to see if they still work.
ĸen
This email was written using 100% recycled letters.
'critical error' running luminosity mask script
You said you had edited the script - did you not use the script-fu console and its included help for that ? It's some months since I last had to do that, I'm rusty on the details.
Yeah it was a couple years ago, so it's lost to the fog of memory. :-) I think I was updating an old script to be compatible with the more recent versions of gimp. I think I just edited the text file directly. Anyway, guess I'll dive back in again.
I reported it as a bug instead of just debugging the script because gimp popped up a 'critical error' with the stack trace and requested in the dialog that I file a bug about it... didn't seem like it was just a script error, in other words. Sound appropriate?
Thanks, -c
'critical error' running luminosity mask script
I’ll have a look at it when I get a moment. Might just need to update
something simple.
On Fri, Apr 20, 2018 at 5:45 PM Casey Connor
wrote:
You said you had edited the script - did you not use the script-fu console and its included help for that ? It's some months since I last had to do that, I'm rusty on the details.
Yeah it was a couple years ago, so it's lost to the fog of memory. :-) I think I was updating an old script to be compatible with the more recent versions of gimp. I think I just edited the text file directly. Anyway, guess I'll dive back in again.
I reported it as a bug instead of just debugging the script because gimp popped up a 'critical error' with the stack trace and requested in the dialog that I file a bug about it... didn't seem like it was just a script error, in other words. Sound appropriate?
Thanks, -c
_______________________________________________ gimp-user-list mailing list
List address: gimp-user-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list List archives: https://mail.gnome.org/archives/gimp-user-list
https://patdavid.net GPG: 66D1 7CA6 8088 4874 946D 18BD 67C7 6219 89E9 57AC
'critical error' running luminosity mask script
Yeah it was a couple years ago, so it's lost to the fog of memory. :-) I
think I was updating an old script to be compatible with the more recent
versions of gimp. I think I just edited the text file directly. Anyway,
guess I'll dive back in again.I reported it as a bug instead of just debugging the script because gimp
popped up a 'critical error' with the stack trace and requested in the dialog that I file a bug about it... didn't seem like it was just a script error, in other words. Sound appropriate?Thanks, -c
I do not suppose any of you mailing list guys ever even think of looking at the gimpusers forum, after all why should you.
but similar question came up a few days ago
http://www.gimpusers.com/mailmsg.php?89758%40forums.gimpusers.com
The Gimp 2.10 appimage is not the best when it come to adding scripts and plugins, however for once it works.
Just pop the script sg-luminosity-masks29.scm in ~/.config/GIMP-AppImage/2.10/scripts/
looks like this: https://i.imgur.com/5EXnsrb.jpg
'critical error' running luminosity mask script
Just to follow up -- Michael Natterer has fixed this... turns out the script was working fine but the error dialog was unnecessary. Thanks all!
https://bugzilla.gnome.org/show_bug.cgi?id=795418
-c
On 04/20/2018 04:14 PM, Pat David wrote:
I’ll have a look at it when I get a moment. Might just need to update something simple.
On Fri, Apr 20, 2018 at 5:45 PM Casey Connor > wrote:> You said you had edited the script - did you not use the script-fu > console and its included help for that ? It's some months since I > last had to do that, I'm rusty on the details.
Yeah it was a couple years ago, so it's lost to the fog of memory. :-) I
think I was updating an old script to be compatible with the more recent
versions of gimp. I think I just edited the text file directly. Anyway,
guess I'll dive back in again.I reported it as a bug instead of just debugging the script because gimp
popped up a 'critical error' with the stack trace and requested in the
dialog that I file a bug about it... didn't seem like it was just a script error, in other words. Sound appropriate?Thanks, -c
_______________________________________________ gimp-user-list mailing list
List address: gimp-user-list@gnome.org
List membership:
https://mail.gnome.org/mailman/listinfo/gimp-user-list List archives: https://mail.gnome.org/archives/gimp-user-list-- https://patdavid.net
GPG: 66D1 7CA6 8088 4874 946D 18BD 67C7 6219 89E9 57AC
'critical error' running luminosity mask script
Thanks a bunch, Rich -- that script works without error and much faster, too, and the masks are in the proper order when done.
But it seems a lot less aggressive; meaning, the "LLL" mask still includes much of the image, not just the brightest parts. It's working, just doesn't generate as strong a separation as I would need to make it useful.
If I have time to poke around at it, I will. And if there are any other luminosity mask scripts out there I haven't heard of, I'm all ears! (In my secret dreams I hope that a scripter somewhere will make a fancy exposure-blending mask-making tool...)
Much obliged,
-c
I do not suppose any of you mailing list guys ever even think of looking at the gimpusers forum, after all why should you.
but similar question came up a few days ago
http://www.gimpusers.com/mailmsg.php?89758%40forums.gimpusers.com
The Gimp 2.10 appimage is not the best when it come to adding scripts and plugins, however for once it works.
Just pop the script sg-luminosity-masks29.scm in ~/.config/GIMP-AppImage/2.10/scripts/
looks like this: https://i.imgur.com/5EXnsrb.jpg
'critical error' running luminosity mask script
On Sat, Apr 21, 2018 at 05:12:45PM +0200, rich404 wrote:
I do not suppose any of you mailing list guys ever even think of looking at the gimpusers forum, after all why should you.
but similar question came up a few days ago
http://www.gimpusers.com/mailmsg.php?89758%40forums.gimpusers.com
I expect we'll receive that in a few days or weeks, whenever someone has time to approve the 'unsubscribed' posts, but -
The Gimp 2.10 appimage is not the best when it come to adding scripts and plugins, however for once it works.
Just pop the script sg-luminosity-masks29.scm in ~/.config/GIMP-AppImage/2.10/scripts/
looks like this: https://i.imgur.com/5EXnsrb.jpg
You might have that directory, but in my from-source RC2 install my local scripts are read from
~/.config/GIMP/2.10/scripts/
i.e. GIMP not GIMP-AppImage : something different in how your version was built ? I only ask because there will be enough pain from updating old documentation without multiple variants of the directory name.
ĸen
This email was written using 100% recycled letters.
'critical error' running luminosity mask script
I'm not the qualified person to respond to this, but: my understanding was that App-Image versions use that directory so as not to mess with normal installs, which is exactly how I would hope it would work... e.g. they're supposed to be 'portable' etc. but need to store their user settings somewhere, so... seems reasonable? The CCE uses yet a different directory: GIMP-CCE-AppImage...
Or did you mean something else?
You might have that directory, but in my from-source RC2 install my local scripts are read from
~/.config/GIMP/2.10/scripts/
i.e. GIMP not GIMP-AppImage : something different in how your version was built ? I only ask because there will be enough pain from updating old documentation without multiple variants of the directory name.
ĸen
'critical error' running luminosity mask script
On Sat, Apr 21, 2018 at 09:51:08PM -0700, Casey Connor wrote:
I'm not the qualified person to respond to this, but: my understanding was that App-Image versions use that directory so as not to mess with normal installs, which is exactly how I would hope it would work... e.g. they're supposed to be 'portable' etc. but need to store their user settings somewhere, so... seems reasonable? The CCE uses yet a different directory: GIMP-CCE-AppImage...
Or did you mean something else?
No, that is what I meant. When I was fixing my own script yesterday I had to remind myself where non-system scripts lived. The online tutorial mentioned ~/.gimp-2.8/scripts which is clearly out of date.
So, it seems there can be any number of possible directories in ~/.config for 2.10 - hopefully they all start 'GIMP' even if they have a suffix.
ĸen
This email was written using 100% recycled letters.
