http://bugs.winehq.org/show_bug.cgi?id=23098
Summary: Strong lines in some parts of Shareaza and SQLYog Product: Wine Version: 1.2-rc2 Platform: x86 URL: http://shareaza.sourceforge.net/?id=download OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv AssignedTo: wine-bugs@winehq.org ReportedBy: jaimerave@gmail.com
Created an attachment (id=28694) --> (http://bugs.winehq.org/attachment.cgi?id=28694) Screenshot showing the problem in SQLYog
Some line in SQLYog and Shareaza looks more intense than they have to be. I have made a regression test and found this commit as the guilty:
c29cf0591976f96c3adb30c3c3b6db59f4983251 is the first bad commit commit c29cf0591976f96c3adb30c3c3b6db59f4983251 Author: Roderick Colenbrander thunderbird2k@gmail.com Date: Tue Apr 6 19:07:25 2010 +0200
winex11: Add support for 32-bit DDBs.
:040000 040000 73b8486e86ccd609ea2f0c8cf0c920b6ec3783dd 04bcf74196ee257fa4b8391041c627b89e6cbffe M dlls
I'm attaching some screenshots to show the issue.
http://bugs.winehq.org/show_bug.cgi?id=23098
Jaime Rave jaimerave@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, regression, | |source
http://bugs.winehq.org/show_bug.cgi?id=23098
--- Comment #1 from Jaime Rave jaimerave@gmail.com 2010-06-09 08:28:52 --- Created an attachment (id=28695) --> (http://bugs.winehq.org/attachment.cgi?id=28695) Screenshot showing how SQLYog should look
Download link for SQLYog http://code.google.com/p/sqlyog/downloads/list
http://bugs.winehq.org/show_bug.cgi?id=23098
--- Comment #2 from Jaime Rave jaimerave@gmail.com 2010-06-09 08:30:55 --- Created an attachment (id=28696) --> (http://bugs.winehq.org/attachment.cgi?id=28696) Screenshot showing how Shareaza should look
http://bugs.winehq.org/show_bug.cgi?id=23098
--- Comment #3 from Jaime Rave jaimerave@gmail.com 2010-06-09 08:43:29 --- Created an attachment (id=28697) --> (http://bugs.winehq.org/attachment.cgi?id=28697) Screenshot showing the problem in Shareaza
The programs looks fine in Wine 1.1.42
http://bugs.winehq.org/show_bug.cgi?id=23098
Jaime Rave jaimerave@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |thunderbird2k@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=23098
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |trivial
--- Comment #4 from Vitaliy Margolen vitaliy@kievinfo.com 2010-06-09 19:12:16 --- http://bugs.winehq.org/page.cgi?id=fields.html#bug_severity
http://bugs.winehq.org/show_bug.cgi?id=23098
--- Comment #5 from Roderick Colenbrander thunderbird2k@gmail.com 2010-06-14 15:34:01 --- Today I had some time to fix the bug but I don't see the issue anymore in Shareaza. Can you confirm that the bug has been fixed?
http://bugs.winehq.org/show_bug.cgi?id=23098
--- Comment #6 from Jaime Rave jaimerave@gmail.com 2010-06-14 15:59:55 --- Yes, I just test with todays git and the issue is still there.
http://bugs.winehq.org/show_bug.cgi?id=23098
--- Comment #7 from Roderick Colenbrander thunderbird2k@gmail.com 2010-06-14 16:19:48 --- Created an attachment (id=28837) --> (http://bugs.winehq.org/attachment.cgi?id=28837) Screenshot on Wine 1.2 git june 14th 2010 on Ubuntu 10.04 32-bit NV
This is a screenshot on my 32-bit Nvidia based Ubuntu system with current Wine. The issue isn't there. What operating system + videocard + drivers are you using? For instance on OSX the XRender implementation has some bugs and the same for some display drivers. (Note I don't count out a Wine bug)
http://bugs.winehq.org/show_bug.cgi?id=23098
--- Comment #8 from Jaime Rave jaimerave@gmail.com 2010-06-14 16:33:45 --- I'm using 32 bits Ubuntu 10.04 + Intel GM45 + Mesa 7.9 + Intel drivers 2.11.0
http://bugs.winehq.org/show_bug.cgi?id=23098
--- Comment #9 from Roderick Colenbrander thunderbird2k@gmail.com 2010-06-14 16:47:52 --- Hopefully some more people can check this bug. If I'm at home I plan to try it on FGLRX.
http://bugs.winehq.org/show_bug.cgi?id=23098
--- Comment #10 from Roderick Colenbrander thunderbird2k@gmail.com 2010-06-14 22:44:40 --- I have just tested this on a Radeon HD3450 running FGLRX and it doesn't have the rendering bug.
The 32-bit DDB patch caused a lot of bugs like this and most have been fixed now. It exposes an area of XRender which can be buggy in drivers. Since neither Nvidia nor FGLRX have the rendering issue I'm leaning towards a driver bug.
http://bugs.winehq.org/show_bug.cgi?id=23098
Michael Stefaniuc mstefani@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mstefani@redhat.com
--- Comment #11 from Michael Stefaniuc mstefani@redhat.com 2010-06-16 15:43:55 --- I have tested this with a Radeon HD 4670 and the open source driver (xorg-x11-drv-ati-6.13.0-1.fc13.x86_64 and Mesa 7.8.1). I do not have the rendering issue either.
http://bugs.winehq.org/show_bug.cgi?id=23098
Jaime Rave jaimerave@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #12 from Jaime Rave jaimerave@gmail.com 2010-06-23 21:05:48 --- I have downgrade the video drivers and that solved the problem.
http://bugs.winehq.org/show_bug.cgi?id=23098
Jaime Rave jaimerave@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #13 from Jaime Rave jaimerave@gmail.com 2010-06-23 21:06:02 --- Closing invalid.
http://bugs.winehq.org/show_bug.cgi?id=23098
Vitaliy Margolen vitaliy-bugzilla@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sb56637@gmail.com
--- Comment #14 from Vitaliy Margolen vitaliy-bugzilla@kievinfo.com 2010-10-11 19:16:50 CDT --- *** Bug 24710 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=23098
--- Comment #15 from Jaime Rave jaimerave@gmail.com 2010-12-08 21:07:05 CST --- I know the bug is closed, but just as reference i have opened a bug against freedesktop: https://bugs.freedesktop.org/show_bug.cgi?id=30157
They suggested a workaround: (https://bugs.freedesktop.org/show_bug.cgi?id=30157#c4) "When I set up wine registry by importing this registry file
[HKEY_CURRENT_USER\Software\Wine\X11 Driver] "ClientSideWithRender"="N"
then everything works fine."
The bug is in the ddx's core rendering routines. The workaround is for wine to do it's rendering locally and then push the image as a whole to the xserver (hopefully only updating the damage regions!). This may in fact be quicker than hitting the X core rendering paths...
http://bugs.winehq.org/show_bug.cgi?id=23098
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |quentin.denis@gmail.com
--- Comment #16 from Alexandre Julliard julliard@winehq.org 2011-04-07 08:59:44 CDT --- *** Bug 26682 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=23098
fiendishx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fiendishx@gmail.com
--- Comment #17 from fiendishx@gmail.com 2011-05-20 13:17:48 CDT --- (In reply to comment #15)
I know the bug is closed, but just as reference i have opened a bug against freedesktop: https://bugs.freedesktop.org/show_bug.cgi?id=30157
They suggested a workaround: (https://bugs.freedesktop.org/show_bug.cgi?id=30157#c4) "When I set up wine registry by importing this registry file
[HKEY_CURRENT_USER\Software\Wine\X11 Driver] "ClientSideWithRender"="N"
then everything works fine."
The bug is in the ddx's core rendering routines. The workaround is for wine to do it's rendering locally and then push the image as a whole to the xserver (hopefully only updating the damage regions!). This may in fact be quicker than hitting the X core rendering paths...
Using this workaround completely kills performance for me. My only viable solution right now until the Intel driver gets fixed is to downgrade Wine to 1.0.1.
http://bugs.winehq.org/show_bug.cgi?id=23098
--- Comment #18 from Alexandre Julliard julliard@winehq.org 2011-06-21 10:33:35 CDT --- *** Bug 24717 has been marked as a duplicate of this bug. ***