July 2008 - Wine-Bugs - list.winehq.org

[Bug 14276] winehelp: various bugs

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=14276 --- Comment #1 from markk(a)clara.co.uk 2008-07-04 04:28:12 --- Created an attachment (id=14568) --> (http://bugs.winehq.org/attachment.cgi?id=14568) Example help file -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

July 4, 2008

[Bug 14276] New: winehelp: various bugs

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=14276 Summary: winehelp: various bugs Product: Wine Version: 1.1.0 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: markk(a)clara.co.uk Created an attachment (id=14567) --> (http://bugs.winehq.org/attachment.cgi?id=14567) Crash log This is a list of various bugs I have found in Wine's winhelp implementation, as compared to running WINHLP32.EXE from Windows 95 under Wine. Broken "imagemaps": Load whatsnew.help. You should be able to click the text in the image to go to various pages, but Wine winhelp does not allow you to do that. Moving/resizing main window: For some help files, Wine winhelp moves and resizes the main window whenever links or navigation buttons are clicked. Windows 95 winhelp does not do that. Load msdncd.hlp and move or resize the winhelp window. As soon as you click a link or button, the window is moved to its previous size and position. The msdncd.hlp file also shows up other bugs: - At the top of each page there should be a grey bar. This does not appear in Wine winhelp. - On the "Opening Books and Topics" page, the paragraph formatting is incorrect. (The paragraph corresponding to each icon should appear to the right of it.) - On "Searching for Words and Phrases", paragraph formatting is also incorrect. Also, the example text should be rendered in bold. - Clicking the >> button when on the "Searching for Words and Phrases" page causes winhelp to crash, reporting caret.c:449: ME_InsertTableCellFromCursor: Assertion `run->member.run.pCell->next' failed. wine: Assertion failed at address 0xb7f5c410 (thread 0045), starting debugger... (See the log attached for rest of the output) relnotes.hlp also shows the paragraph formatting problem. Hang with 100% CPU use: Load quenzar.hlp. CPU usage goes to 100% for about a minute (on my old slow PC), but the help window does open eventually. Font sizes: Wine winhelp uses much smaller fonts than Windows 95 Winhelp. The Wine "Normal" font is smaller than the Windows 95 "Small" font etc. Window titles: The Wine winhelp title bar always says "WINE Help". Windows 95 Winhelp shows instead the help file title and filename, e.g. "GNU Chess Help - chess.hlp". Missing scroll bar: Sometimes the vertical scroll bar is incorrectly omitted. Start Wine winhlp32, and without resizing its window, open chess.hlp. Click on "Article: What is GNU Chess". The bottom line is not shown but there is no vertical scroll bar. If you resize the window (e.g. make it narrower) the scroll bar may appear, but sometimes it does not, depending on the exact width you resize to. On loading chess.hlp, Wine reports err:winhelp:HLPFILE_DoReadHlpFile buf[0x14] = 0 If you then click "GNU Chess sample match with MACH", Wine reports fixme:winhelp:HLPFILE_BrowseParagraph Unsupported bits 4200, potential trouble ahead (repeated many times) On loading emle.hlp, Wine reports err:winhelp:HLPFILE_DoReadHlpFile buf[0x14] = 0 fixme:winhelp:HLPFILE_BrowseParagraph Unsupported bits 2204, potential trouble ahead (second line repeats if you click any links) On loading pphelp.hlp, Wine reports fixme:winhelp:MACRO_SetHelpOnFile ("PPHELP.HLP") (repeated whenever you click a link) Extraneous flashing cursor/caret: Wine winhelp shows a flashing cursor/caret symbol when you click somewhere in the text. Windows winhelp does not do that. The current behaviour may be desired, e.g. it makes selecting text using the keyboard possible. However... - Click in the page so the cursor is shown, then click on a link to go to another page. A flashing cursor is present at the top left before you click in the page. - On some help pages, the flashing cursor is present at the top left even before the user clicks in the page. Also, if there is a large graphic at the top left, a huge flashing cursor may appear (see cwdeluxe.hlp and click on the picture). Windows 95 Winhelp does not allow images to be selected. Mouse pointer flickering: When moving the mouse pointer over the help window, the pointer flickers between the normal X pointer (white arrow) and an insertion point (and also a black arrow). The pointer does not flicker at all when running Windows 95 Winhelp under Wine. (There it is always an insertion point, changing to a hand when over a clickable link.) Missing << and >> buttons: For many help files, the forward and back buttons (<< and >>) are not shown in Wine winhelp. However they do appear with other help files (e.g. pphelp.hlp). Wrong initial position in page: Load winrisk.hlp into Wine winhelp. Resize the window to be about half its original width and height. Click the Contents button. The view moves about half-way down the page. Click "Revision History". The view is over half-way down the page. (In both cases, Windows 95 winhelp remains at the top of the page.) Search: The search button is not implemented in Wine winhelp, Wine reporting fixme:winhelp:MACRO_Search () when that button is clicked. The Topics button does bring up a list of topics, but: - selecting a topic and clicking OK does not always go to the correct page (see castle1.hlp) - it should be possible to select a topic by double-clicking. Opaque drop shadows: The drop shadows on popup boxes are solid black. Windows winhelp uses a cross-hatch pattern, so drop shadows appear semi-transparent. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

July 4, 2008

[Bug 13101] GLXBadDrawable when antialias ON (Nvidia driver bug?)

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=13101 --- Comment #66 from Norbert Mihály <norbert79(a)freemail.hu> 2008-07-04 04:25:49 --- Roderick, when you sent the error log, did you also include our comments, or just have included a link to this bug? This might help them tracing of the problem. It seems, that ATI is not affected, which would make you right on this question, but what is most confusing, that native linux binaries are (as it seems) not ot be affected by this problem, but Wine. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

July 4, 2008

[Bug 10445] winhelp.exe problem displaying help file, related to LF / CR-LF end-of-line issue?

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=10445 markk(a)clara.co.uk changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED --- Comment #3 from markk(a)clara.co.uk 2008-07-04 04:15:42 --- Yes, the problem appears to be fixed now (testing with Wine 1.1.0). -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

July 4, 2008

[Bug 14275] New: Kontakt 3 fails at startup

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=14275 Summary: Kontakt 3 fails at startup Product: Wine Version: 1.1.0 Platform: PC URL: http://www.native-instruments.com/index.php?id=kontakt3 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: skore(a)skore.de Created an attachment (id=14566) --> (http://bugs.winehq.org/attachment.cgi?id=14566) An error trace from a Kontakt 3 startup I will attach an error trace which should be of most help, but have to add here, that I actually tested the demo version of Kontakt 3 before buying it. Back then, there were some quirks, but it was starting. I think the wine version might have been something like 0.9.59. However, when I try to start the demo version with 1.0 or 1.1, it fails. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

July 4, 2008

[Bug 13101] GLXBadDrawable when antialias ON (Nvidia driver bug?)

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=13101 --- Comment #65 from Norbert Mihály <norbert79(a)freemail.hu> 2008-07-04 03:55:09 --- Sure, I understand this, but this does not solve the antalising problem, nor the multisampling problem. If you are so convinced, that this can be ONLY a driver problem, please answer me the following simple question: Why does this bug appear only with Wine, and does not appear on any Linux binary based OpenGL game? (Undependant of the driver version, forced or not forced, doesn't matter.) -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

July 4, 2008

[Bug 13101] GLXBadDrawable when antialias ON (Nvidia driver bug?)

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=13101 --- Comment #64 from Roderick Colenbrander <thunderbird2k(a)gmx.net> 2008-07-04 03:44:48 --- Let me quickly explain how GLX (opengl for X)/WGL (opengl for windows) work and how you set up multisampling. Then you will see that it is most likely a driver bug. In short GLX/WGL support offer various 'pixel formats' using which OpenGL will be rendered (this is called an XVisual / GLXFBconfig in case of GLX). A pixel format defines the number of red/green/blue/alpha bits but things like double buffering and multisampling are also properties of a pixel format. Each pixel format offers only a single multisampling format. When you set up rendering you create a window using the pixel format you want. In case you want multisampling, you select a format with multisampling and then it is activated. Before you can render to the window you need to attach it to a multisampling capable opengl context using wglMakeCurrent/glXMakeCurrent. The nvidia drivers return GLXBadDrawable. (In case of a pixel format mismatch GLXBadMatch is returned which isn't the case here) -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

July 4, 2008

[Bug 13101] GLXBadDrawable when antialias ON (Nvidia driver bug?)

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=13101 --- Comment #63 from Norbert Mihály <norbert79(a)freemail.hu> 2008-07-04 03:35:58 --- Roderick! I made contact with Robert, who has done a lot of investigation on his side, and wrote me the following: [Quote] I did a lot of experimenting with Nvidia drivers and wine versions back to 0.60. I was never able to obtain a viable bisect, and it does indeed appear that something in the Nvidia drivers changed after 100.14.19 that broke AA with wine. However, as I said before I'm not convinced that it is necessarily a "bug", I would tend to think that it's an API change that the wine developers aren't aware of. So what I'm doing now is using wine 1.0, with the two patches I've attached to this email, and Nvidia drivers 96.43.05. The only reason I'm not using 100.14.19 is because I use Avant Window Manager, and there's a bug with it, the 100.14.19 drivers, and Steam. If you don't use Avant I would go with the 100.14.19 drivers because there is a noticeable improvement in video quality. By the way, I can't use wine 1.10 or the latest git because I can't install Microsoft Office service pack 3. I'm not sure why. [/Quote] I personally made the similar conclusion, tough my investigation was a bit limited. Robert also explained me some problems with your surface rendering, and also included two diffs; I am asking him, if he plans to submit his modifications, because you guys might be interested. I would like to ask you kindly just at least considering the possibility, that the Wine Team might have something missed out, and this might be not really a 'bug', but maybe an API change. Regards: Norbert -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

July 4, 2008

[Bug 14274] Unreadable fonts / dialogues with Wine and ATI cards

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=14274 --- Comment #1 from Aniruddha <mailing_list(a)orange.nl> 2008-07-04 02:47:07 --- Created an attachment (id=14565) --> (http://bugs.winehq.org/attachment.cgi?id=14565) Unreadable properties dialogue in Goalpro -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

July 4, 2008

[Bug 14274] New: Unreadable fonts / dialogues with Wine and ATI cards

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=14274 Summary: Unreadable fonts / dialogues with Wine and ATI cards Product: Wine Version: 1.1.0 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: mailing_list(a)orange.nl Created an attachment (id=14564) --> (http://bugs.winehq.org/attachment.cgi?id=14564) Unreadable dialogue from Grabit Ever since I installed my Radeon HD 3850 in Linux I noticed a strange problem with fonts and dialogues in Wine. Fonts are hard to read because they are covered with a greyish line. I tried searching in the bug database for a dupe, but I didn't know the exact keyword to use, I searched for graphics corruption and ATI but this yielded no results. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

July 4, 2008