Bug#519221: libpixman -- bug recently submitted related to your patch
Thank you for your response.
I have compiled the latest git of pixman with the --disable-sse2 flag
and it works perfectly. The problems are gone when I disable that
Here is some more information about my system in case any of it is helpful:
- AMD Opteron dual-core CPU, 2.4 GHz, supporting with flags: fpu vme
de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36
clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext
3dnow pni lahf_lm cmp_legacy.
- I am running a 32-bit OS, although the CPU supports 64.
- ATI X300SE PCI-E video card, using the free and open-source radeon
driver for 3D acceleration. I believe this driver only supports some
of openGL 1.2.
- Kernel 2.6.26
- 1GB ram
- Terminal emulator is konsole from KDE 3.5; pseudo-transparency is
turned on (that is, it paints the desktop background as the terminal
background to make it "appear" transparent)
I hope we can find the source of this problem. :) Is it possible to
take out only some of the sse2 modifications so we can determine which
optimization is causing problems?
Thanks for your time,
2009/3/11 André Tupinambá <firstname.lastname@example.org>:
> Hi Arren,
> This is a old patch, about add SSE2 implementation for many compose
> operations. This code was first released in pixman 0.12.0. I really
> don't know what is going on, I need to investigate this.
> Just in case, a good test is run the pixman configure with
> --disable-sse2, to disable this code, keeping all other pixman
> implementation and modifications.
> BTW, I care about :)
> André Tupinambá
> PS: Sorry about any English mistakes, I'm Brazillian and English isn't
> my first language.
> On Wed, Mar 11, 2009 at 12:11 AM, Arren Lex <email@example.com> wrote:
>> I have recently submitted a libpixman bug introduced by a regression
>> caused by one of your patches. The bug report is available here --
>> I don't know if you care about this; I was just hoping you may have
>> had some insight as to what causes it, or ideas how to fix it. :) I
>> want my terminal back!
>> If you want, you can comment on the bug report by emailing responses
>> to firstname.lastname@example.org
>> Thanks a lot for your time,
>> Arren Lex