wine-bugs March 2007

wine-bugs@winehq.org

13 participants
2688 discussions

[Bug 7657] Fonts rendered differently in Win98 vs WinXP
by Wine Bugs 08 Mar '07

08 Mar '07

http://bugs.winehq.org/show_bug.cgi?id=7657 ------- Additional Comments From wine(a)enzerink.net 2007-07-03 18:34 ------- Created an attachment (id=5269) --> (http://bugs.winehq.org/attachment.cgi?id=5269&action=view) Screendump in Windows 98 mode showing no artefacts Font issue that is the subject of this bug can be seen in the headings. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 7657] New: Fonts rendered differently in Win98 vs WinXP
by Wine Bugs 08 Mar '07

08 Mar '07

http://bugs.winehq.org/show_bug.cgi?id=7657 Summary: Fonts rendered differently in Win98 vs WinXP Product: Wine Version: 0.9.32. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: wine-comctl32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: wine(a)enzerink.net In Galactic Civilizations there is a slight difference in the way one of the fonts is rendered resulting in minor artefacts when the app is set to Windows 2000 or Windows XP mode, but not when set to Windows 98 mode. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 7594] Wine window scrolling is broken
by Wine Bugs 07 Mar '07

07 Mar '07

http://bugs.winehq.org/show_bug.cgi?id=7594 ------- Additional Comments From Hubmasterflex(a)hotmail.com 2007-07-03 17:45 ------- PokerStars has this problem too, but from 0.9.32, it seems as if progress is being made. I can scroll up or down, drag the scroll box up or down, or click within the scroll bar to move quickly up or down. The only problem seems to be that the scroll bar box (the box that shows progress within the scroll bar itself) stays put or resets itself at the very top at all costs when it is vertical, don't know about a horizontal bar. Before 0.9.32, doing any of these would reset the contents of available poker tables to the very top. Hopefully, this will be fixed a.s.a.p. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 7653] GDI deadlock on startup of any program
by Wine Bugs 07 Mar '07

07 Mar '07

http://bugs.winehq.org/show_bug.cgi?id=7653 ------- Additional Comments From zarquon(a)t-online.de 2007-07-03 17:45 ------- Leftover stuff is unlikely because I always clean the tree _before_ patching it up (so I couldn't find any *.o *.a *.so files after a regular clean). OK, I tried distclean anyway, deleted all leftover Makefiles and configured the tree. Anything in particular you're interested in? Because the verbose output doesn't look any different, apart from some messages about specials that won't be built at the end (like CUPS support or XRandr). Then I tried running it, but it failed exactly as before. So I renamed ~/.wine and ran tools/wineprefixcreate -- which built and populated ~/.wine and then bombed: wine: Unhandled page fault on read access to 0x00000037 at address 0x6028bdc0 (thread 0009), starting debugger... warn:gdi:GDI_GetObjPtr Invalid handle 0xe88 warn:gdi:GDI_GetObjPtr Invalid handle (nil) [...] wine client error:0: init_thread failed with status c000011f err:seh:start_debugger Couldn't start debugger ("winedbg --auto 406 820") (1359) Read the Wine Developers Guide on how to set up winedbg or another debugger err:seh:raise_exception Unhandled exception code c000013a flags 0 addr 0x601f53c2 I then tried running 0.9.32 with this new ~/.wine and first had to fiddle around with drive_c and dosdevices/c: a bit because my windows stuff is located elsewhere (symbolic links), but got that sorted out (including the updated C:\windows directory). So I tried 0.9.32 on DeusEx and it bombed too. Noteworthy stuff: warn:module:load_builtin_dll failed to load .so lib for builtin L"C:\\Programs\\DeusEx\\System\\Core.dll": /cryptohome/andreas/.wine/dosdevices/c:/Programs/DeusEx/System/Core.dll: invalid ELF header This seems a bit odd. Even if it's OK it's highly irritating. warn:module:load_builtin_dll cannot open .so lib for builtin L"Core.dll": /opt/wine/lib/wine/core.dll.so: cannot open shared object file: No such file or directory This is odd because /opt/wine is my regular install directory (currently 0.9.8) and since I'm running 0.9.32 from the source directory, Wine shouldn't look there at all! warn:module:load_builtin_dll failed to load .so lib for builtin L"C:\\windows\\system32\\advapi32.dll": /cryptohome/andreas/.wine/dosdevices/c:/windows/system32/advapi32.dll: invalid ELF header wine: Unhandled page fault on read access to 0x00000000 at address 0x602892dd (thread 0009), starting debugger... err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0xb579c The end. I'll probably try the full 0.9.32 tarball tomorrow (I used the patches so far), but highly doubt it'll fix this problem. Any further ideas? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 7485] Crash in primitiveDeclarationConvertToStridedData
by Wine Bugs 07 Mar '07

07 Mar '07

http://bugs.winehq.org/show_bug.cgi?id=7485 wine(a)enzerink.net changed: What |Removed |Added ---------------------------------------------------------------------------- Version|0.9.31. |0.9.32. ------- Additional Comments From wine(a)enzerink.net 2007-07-03 17:35 ------- Interestingly textures/facets are drawn apparently normally (although much slower) using Mesa rather than my normal fglrx driver. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 4790] wotr: FPE during SSE division
by Wine Bugs 07 Mar '07

07 Mar '07

http://bugs.winehq.org/show_bug.cgi?id=4790 ------- Additional Comments From p.beutner(a)gmx.net 2007-07-03 17:21 ------- > err:seh:fpe_handler Got unexpected trap 19 that is not a "cache flush cpu exception" but a SIMD/SSE exception. And looking at the asm code it seems this divide-by-zero fault is generated on purpose. Google says that this is probably part of a runtime SSE detection routine to detect if the OS supports SIMD exceptions. The problem is wine doesn't properly recognizes and responds to this exception. Needs some testing first what exactly windows does here. I'll try to look into this if no one beats me to it. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 4790] wotr: FPE during SSE division
by Wine Bugs 07 Mar '07

07 Mar '07

http://bugs.winehq.org/show_bug.cgi?id=4790 ------- Additional Comments From rmh(a)aybabtu.com 2007-07-03 16:56 ------- Urgh. +relay seems to indicate that CPUID was used just before the exception happened. Earlier I verified that the code is testing for SSE and SSE2 flags (although disabling these checks didn't avoid the FPE). This makes sense, but contradicts my former supposition. I'm not sure about anything now (maybe this FPE is just the wrong thing to look at?) :-( 0009:Call kernel32.MultiByteToWideChar(00000000,00000000,008c99a0 "AuthenticAMD",ffffffff,010a1150,0000000c) ret=00798320 0009:Ret kernel32.MultiByteToWideChar() retval=00000000 ret=00798320 0009:Call ntdll.RtlAllocateHeap(010a0000,00000000,00000010) ret=0082a2a9 0009:Ret ntdll.RtlAllocateHeap() retval=010a1178 ret=0082a2a9 0009:Call kernel32.WideCharToMultiByte(00000000,00000000,010a1150 L"AuthenticAMD",ffffffff,010a1178,0000000c,00000000,00000000) ret=0079796e 0009:Ret kernel32.WideCharToMultiByte() retval=00000000 ret=0079796e err:seh:fpe_handler Got unexpected trap 19 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 7652] Transcendence: text and numbers either missing or displayed wrong
by Wine Bugs 07 Mar '07

07 Mar '07

http://bugs.winehq.org/show_bug.cgi?id=7652 ------- Additional Comments From thestig(a)google.com 2007-07-03 16:56 ------- Ok, great, the game runs now. (I had to enable emulate virtual desktop for it to work on my machine) Now I get a little ship that flies around and gets shot up. How do I get to the menu that has the problem like the one in your screenshots? Also, is the mouse suppose to be usable in the game? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 7530] Wine fails to compile on Intel-Macs, 'x86_DEBUG_STATE32' undeclared
by Wine Bugs 07 Mar '07

07 Mar '07

http://bugs.winehq.org/show_bug.cgi?id=7530 truiken(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID ------- Additional Comments From truiken(a)gmail.com 2007-07-03 16:49 ------- Invalid. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 4790] wotr: FPE during SSE division
by Wine Bugs 07 Mar '07

07 Mar '07

http://bugs.winehq.org/show_bug.cgi?id=4790 ------- Additional Comments From rmh(a)aybabtu.com 2007-07-03 16:22 ------- Created an attachment (id=5268) --> (http://bugs.winehq.org/attachment.cgi?id=5268&action=view) FPE in Windows XP I've run the game through a debugger under Windows XP, and it catches the same FPE (screenshot attached). After that, the process terminates. The only explanation I can think of is that this program includes an anti-tracing mechanism and aborts when a debugger is found. In this case, it could either be that: - The FPE is just a red herring. - The FPE is purposely caused by the program as a "weird" manner of telling us not to mess with it. Please can someone with a clue about this confirm or deny my supposition ? And if it is to be confirmed, any idea on what can wine do to work around this mess ? Thanks -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs March 2007