After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 693719 - Flame Filter doesn't show color palettes
Flame Filter doesn't show color palettes
Status: RESOLVED DUPLICATE of bug 693797
Product: GIMP
Classification: Other
Component: libgimp
2.8.4
Other All
: Normal normal
: 2.8
Assigned To: GIMP Bugs
GIMP Bugs
: 696211 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-02-13 15:50 UTC by Robert
Modified: 2013-05-10 11:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Robert 2013-02-13 15:50:46 UTC 
Using GIMP 2.8.4 PORTABLE on Windows XP SP3 32bit. With a black background, go to Filters > Render > Nature > Flame. No "flame" renderings are created in the preview boxes. If I change the background to white, the renderings do show in the preview box, but they will then be rendered white against white. I tried it again with a red background and it works as red and white, but it's a lot more work to have to change BG colors after creating the flames layer.  I still have GIMP 2.8.2 PORTABLE on the same computer. It works fine and doesn't suffer from this problem.
Comment 1 Michael Schumacher 2013-02-13 15:59:52 UTC 
Seems like the color map selector doesn't allow to choose from the palettes anymore.
Comment 2 Michael Schumacher 2013-02-15 09:17:26 UTC 
A bit more:

The flame filter dailog show a color map selection - it allows to choose from the images layers, some predefined palettes and the current gradient, at least.

However, this seems to be broken - most times only the background is present, sometimes (happened to me when reshowing the filter from the filters menu) the other options appear, but can't be selected.
Comment 3 Michael Natterer 2013-02-15 10:02:17 UTC 
Broken on linux too.
Comment 4 Michael Schumacher 2013-02-15 14:32:16 UTC 
Is bug #693797 related?
Comment 5 Michael Natterer 2013-02-15 17:48:59 UTC 
Yes it's indeed the same bug.

*** This bug has been marked as a duplicate of bug 693797 ***
Comment 6 Michael Schumacher 2013-05-10 11:05:23 UTC 
*** Bug 696211 has been marked as a duplicate of this bug. ***