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 341018 - "Lighten only" mode of Layer produces strange maps in image
"Lighten only" mode of Layer produces strange maps in image
Status: RESOLVED DUPLICATE of bug 164061
Product: GIMP
Classification: Other
Component: General
2.2.x
Other Linux
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2006-05-08 12:38 UTC by Jan Tomasek
Modified: 2008-01-15 13:07 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jan Tomasek 2006-05-08 12:38:03 UTC
Motivation: I've several images of waterfall. I want to merge them down using "Lighten only" mode on 2nd and another layers to enhance efect of white motion blured water.

Bug: Gimp produces strange residua maps on resulting image around areas where effect apply. Check out:

http://www.tomasek.cz/stuff/20060501_7560.jpeg

Original XCF file is:

http://www.tomasek.cz/stuff/20060501_7560.xcf

Bug is somehow hooked to "Merge visible layers" because if I save example image without "Merged" layer resulting jpeg is OK. Check out:

http://www.tomasek.cz/stuff/20060501_7560a.jpeg

Feel free to ask me for any other information that might help you fix bug.

Thanks
Comment 1 Simon Budig 2006-05-08 13:56:02 UTC
This seems to be a bug in the assembly acceleration routines. Try starting the GIMP on the commandline with the "--no-cpu-accel" flag and the errors disappear for me.

I can confirm this with 2.2.10 on a Pentium mobile, the problem seems to be fixed in CVS HEAD.
Comment 2 Michael Schumacher 2006-05-08 15:32:34 UTC
This also happens with 2.2.11 on a P4.
Comment 3 Jan Tomasek 2006-05-08 16:11:30 UTC
(In reply to comment #1)
> This seems to be a bug in the assembly acceleration routines. Try starting the
> GIMP on the commandline with the "--no-cpu-accel" flag and the errors
> disappear for me.

Yes, error disappear if I run Gimp with "--no-cpu-accel".

My CPU:

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 15
model           : 4
model name      : Intel(R) Pentium(R) D CPU 3.20GHz
stepping        : 4
cpu MHz         : 3192.481
cache size      : 1024 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 5
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm pni monitor ds_c
pl est cid cx16 xtpr
bogomips        : 6388.70

processor       : 1
... same as 0.
Comment 4 Sven Neumann 2006-05-10 07:49:49 UTC
Please run gimp with the --verbose command-line and paste the result of the tests for processor instruction sets to this bug-report.
Comment 5 Jan Tomasek 2006-05-10 07:56:59 UTC
Processor instruction sets: +mmx +sse +sse2 -3dnow -altivec -vis
Comment 6 Sean M. 2006-05-12 20:18:55 UTC
one question, i am having this same problem and i am wondering how you run The GIMP with these different things such as "--no-cpu-accel" thanks for your help.
Comment 7 weskaggs 2006-05-23 21:57:45 UTC

*** This bug has been marked as a duplicate of 164061 ***