October 2013 - Wine-bugs - list.winehq.org

[Bug 21930] New: Free Ghost installer crashes during project building in console
by wine-bugs＠winehq.org 24 Jul '21

24 Jul '21

http://bugs.winehq.org/show_bug.cgi?id=21930 Summary: Free Ghost installer crashes during project building in console Product: Wine Version: 1.1.39 Platform: x86 URL: http://www.ethalone.com/download/gi/GIFree.exe OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ariafan(a)mail.ru Created an attachment (id=26619) --> (http://bugs.winehq.org/attachment.cgi?id=26619) Test installation project Try in console wineconsole "c:\program files\Ethalone\Ghost Installer\Bin\GIBuild.exe" test.gpr Message is appeared during project building: fixme:msvcrt:MSVCRT__sopen : pmode 0x81b6 ignored and later err:seh:setup_exception_record stack overflow 860 bytes in thread 003f eip 00406df5 esp 00240fd4 stack 0x240000-0x241000-0x340000 testsetup.exe was not created. See test.gpr in attachment. -- 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.

2 15

[Bug 22176] New: Rocket Reader 8.3 fails to install
by wine-bugs＠winehq.org 24 Jul '21

24 Jul '21

http://bugs.winehq.org/show_bug.cgi?id=22176 Summary: Rocket Reader 8.3 fails to install Product: Wine Version: 1.1.16 Platform: x86 URL: ftp://rocketreader.com/rocketreaderv83.exe OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: lukasz.wojnilowicz(a)gmail.com CC: julliard(a)winehq.org Created an attachment (id=27054) --> (http://bugs.winehq.org/attachment.cgi?id=27054) WINEDEBUG=+relay on Wine 1.1.41-72-ge9be1b4 At installation, around 75%, the program displays an error (Error changing registry data), after that it deletes all what it has installed. This error doesn't appear on Wine 1.1.15 so it's regression. Regression test did give 1c91d54503f9b2afa513dc4dd79bf19bc9bad51a is the first bad commit commit 1c91d54503f9b2afa513dc4dd79bf19bc9bad51a Author: Alexandre Julliard <julliard(a)winehq.org> Date: Wed Feb 18 14:44:17 2009 +0100 msvcrt: Don't try to duplicate invalid handles. Don't reset std handles if we didn't set them. :040000 040000 2abf5f9a82de1d29b1fccadc658fc3a956388ac4 86464380dfe4aca4c5c11ea2a539a1fc5def03b8 M dlls Reverting this fault patch enables me to install Rocket Reader. The program doesn't install on wine 1.1.41. In terminal there is fixme:richedit:ME_HandleMessage EM_SETMARGINS: stub fixme:richedit:ME_HandleMessage EM_SETMARGINS: stub fixme:richedit:ME_HandleMessage EM_SETMARGINS: stub fixme:richedit:ME_HandleMessage EM_SETMARGINS: stub fixme:richedit:ME_HandleMessage EM_SETMARGINS: stub fixme:sfc:SfcIsFileProtected ((nil), L"C:\\Program Files\\RocketReaderV83\\french.qmc") stub I'm attaching terminal output with +relay -- 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.

2 7

[Bug 21562] New: Multiple init/deinit of msvcrt (std fd's) causes pluto app installer to hang
by wine-bugs＠winehq.org 24 Jul '21

24 Jul '21

http://bugs.winehq.org/show_bug.cgi?id=21562 Summary: Multiple init/deinit of msvcrt (std fd's) causes pluto app installer to hang Product: Wine Version: 1.1.37 Platform: x86 URL: http://pluto.brain-killer.org/download/pluto_FE_w32_en _0036.exe OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, an interesting one... WINEDEBUG=+tid,+seh,+loaddll,+msvcrt,+server,+relay wine ./pluto_FE_w32_en_0036.exe >>log.txt 2>&1 The app installer creates an additional worker (unpack) thread from its main thread: --- snip --- 0009:Call KERNEL32.CreateThread(00000000,00000000,0042b674,00000000,00000000,00436718) ret=0042c3e8 0009: *fd* 6 <- 22 0009: new_thread( access=001f03ff, attributes=00000000, suspend=1, request_fd=6 ) 0009: new_thread() = 0 { tid=001b, handle=0004 } ... 001b:Starting thread proc 0x42b674 (arg=(nil)) ... 0009:Ret KERNEL32.CreateThread() retval=00000004 ret=0042c3e8 --- snip --- The app installer main thread contains a loop to check if the (unpack) worker thread (handle = 0x4) is still alive. While doing so, it pumps messages and delays the next check, illustrated by following code snippet: --- snip --- 0009:Ret KERNEL32.Sleep() retval=00000000 ret=004167e4 0009:Call KERNEL32.GetExitCodeThread(00000004,0032fd9c) ret=0042c40f 0009: get_thread_info( handle=0004, tid_in=0000 ) 0009: get_thread_info() = 0 { pid=0008, tid=001b, teb=7ffd4000, affinity=ffffffffffffffff, creation_time=1caa28d3911cf76 (-0.0285120), exit_time=0, exit_code=259, priority=0, last=0 } 0009:Ret KERNEL32.GetExitCodeThread() retval=00000001 ret=0042c40f 0009:Call user32.PeekMessageA(0032fd0c,00000000,00000000,00000000,00000001) ret=004167d9 ... 0009:Ret user32.PeekMessageA() retval=00000000 ret=004167d9 0009:Call KERNEL32.Sleep(00000001) ret=004167e4 --- snip --- Unfortunately something goes wrong and the app installer refuses to terminate - because the worker checking loop suddenly became a forever loop: --- snip --- ... 0009:Call KERNEL32.Sleep(00000001) ret=004167e4 0009:Ret KERNEL32.Sleep() retval=00000000 ret=004167e4 0009:Call KERNEL32.GetExitCodeThread(00000004,0032fd9c) ret=0042c40f 0009: get_thread_info( handle=0004, tid_in=0000 ) 0009: get_thread_info() = INVALID_HANDLE { pid=0000, tid=0000, teb=00000000, affinity=00000000, creation_time=0, exit_time=0, exit_code=0, priority=0, last=0 } 0009:Ret KERNEL32.GetExitCodeThread() retval=00000000 ret=0042c40f 0009:Call user32.PeekMessageA(0032fd0c,00000000,00000000,00000000,00000001) ret=004167d9 0009: get_message( flags=00000001, get_win=00000000, get_first=00000000, get_last=ffffffff, hw_id=00000000, wake_mask=00000000, changed_mask=00000000 ) 0009: get_message() = PENDING { win=00000000, msg=00000000, wparam=00000000, lparam=00000000, type=0, time=00000000, active_hooks=80000000, total=0, data={} } ... 0009:Ret user32.PeekMessageA() retval=00000000 ret=004167d9 --- snip --- The installer code doesn't evaluate the return code of GetExitCodeThread() but instead accesses the exit code variable directly, comparing it to 0x103 -> STILL_ACTIVE. Because the thread once lived in this state, this variable is never touched by Wine in case the thread handle becomes invalid. GetExitCodeThread() fails but the variable still contains the last known "good" value -> STILL_ACTIVE (the app doesn't reinit it). The app still thinks the worker is alive and goes into forever loop. Now the culprit: the thread handle, delivered to caller upon returning from CreateThread() is _never_ closed by app explicitly -> CloseHandle() so GetExitCodeThread() should be successful in any case. We have to go back in time to unearth the problem ... lets look what happens to this thread handle (0x4). --- snip --- ... 001b:Call KERNEL32.FreeLibrary(10000000) ret=004242bb 001b:Call PE DLL (proc=0x10001148,module=0x10000000 L"unpack.dll",reason=PROCESS_DETACH,res=(nil)) 001b:Ret PE DLL (proc=0x10001148,module=0x10000000 L"unpack.dll",reason=PROCESS_DETACH,res=(nil)) retval=1 001b:Call PE DLL (proc=0x5de0cc9c,module=0x5de00000 L"crtdll.dll",reason=PROCESS_DETACH,res=(nil)) 001b:Ret PE DLL (proc=0x5de0cc9c,module=0x5de00000 L"crtdll.dll",reason=PROCESS_DETACH,res=(nil)) retval=1 001b:Call PE DLL (proc=0x5c7cd8b4,module=0x5c790000 L"msvcrt.dll",reason=PROCESS_DETACH,res=(nil)) ... 001b:trace:msvcrt:DllMain (0x5c790000, DLL_PROCESS_DETACH, (nil)) pid(8), tid(1b), tls(4) 001b:trace:msvcrt:msvcrt_free_mt_locks : uninitializing all mtlocks ... 001b:trace:msvcrt:MSVCRT__close :fd (3) handle (0xfffffff6) 001b:Call KERNEL32.CloseHandle(fffffff6) ret=5c7ad9fc 001b: close_handle( handle=0004 ) 001b: close_handle() = 0 001b:Ret KERNEL32.CloseHandle() retval=00000001 ret=5c7ad9fc 001b:trace:msvcrt:msvcrt_free_fd :fd (3) freed 001b:trace:msvcrt:MSVCRT__close :ok ... 001b:trace:msvcrt:MSVCRT__close :fd (4) handle (0xfffffff5) 001b:Call KERNEL32.CloseHandle(fffffff5) ret=5c7ad9fc 001b: close_handle( handle=0008 ) 001b: close_handle() = 0 001b:Ret KERNEL32.CloseHandle() retval=00000001 ret=5c7ad9fc 001b:trace:msvcrt:msvcrt_free_fd :fd (4) freed 001b:trace:msvcrt:MSVCRT__close :ok ... 001b:trace:msvcrt:MSVCRT__close :fd (5) handle (0xfffffff4) 001b:Call KERNEL32.CloseHandle(fffffff4) ret=5c7ad9fc 001b: close_handle( handle=000c ) 001b: close_handle() = 0 001b:Ret KERNEL32.CloseHandle() retval=00000001 ret=5c7ad9fc 001b:trace:msvcrt:msvcrt_free_fd :fd (5) freed 001b:trace:msvcrt:MSVCRT__close :ok 001b:trace:msvcrt:MSVCRT__fcloseall :closed (3) handles ... 001b:trace:msvcrt:MSVCRT__close :fd (0) handle (0x8) 001b:Call KERNEL32.CloseHandle(00000008) ret=5c7ad9fc 001b: close_handle( handle=0008 ) 001b: close_handle() = INVALID_HANDLE 001b:Ret KERNEL32.CloseHandle() retval=00000000 ret=5c7ad9fc ... 001b:warn:msvcrt:MSVCRT__close :failed-last error (6) ... 001b:trace:msvcrt:MSVCRT__close :ok ... 001b:trace:msvcrt:MSVCRT__close :fd (1) handle (0xc) 001b:Call KERNEL32.CloseHandle(0000000c) ret=5c7ad9fc 001b: close_handle( handle=000c ) 001b: close_handle() = INVALID_HANDLE 001b:Ret KERNEL32.CloseHandle() retval=00000000 ret=5c7ad9fc ... 001b:warn:msvcrt:MSVCRT__close :failed-last error (6) ... 001b:trace:msvcrt:MSVCRT__close :ok ... 001b:trace:msvcrt:MSVCRT__close :fd (2) handle (0x50) 001b:Call KERNEL32.CloseHandle(00000050) ret=5c7ad9fc 001b: close_handle( handle=0050 ) 001b: close_handle() = 0 001b:Ret KERNEL32.CloseHandle() retval=00000001 ret=5c7ad9fc 001b:trace:msvcrt:msvcrt_free_fd :fd (2) freed 001b:Call KERNEL32.GetStdHandle(fffffff4) ret=5c7ac729 001b:Ret KERNEL32.GetStdHandle() retval=0000000c ret=5c7ac729 001b:trace:msvcrt:MSVCRT__close :ok ... 001b:trace:msvcrt:msvcrt_free_console :Closing console handles --- snip --- *eek* ... the thread handle gets closed as part of msvcrt cleanup! PROCESS_DETACH -> msvcrt_free_io() -> MSVCRT__fcloseall() This will close fd(3), fd(4), fd(5) -> stdin,stdout,stderr Corresponding msvcrt init: --- snip --- ... 001b:Call PE DLL (proc=0x5c7cd8b4,module=0x5c790000 L"msvcrt.dll",reason=PROCESS_ATTACH,res=(nil)) ... 001b:trace:msvcrt:DllMain (0x5c790000, DLL_PROCESS_ATTACH, (nil)) pid(8), tid(1b), tls(0) ... 001b:Call KERNEL32.GetStartupInfoA(0096e4b8) ret=5c7acdd6 001b:Ret KERNEL32.GetStartupInfoA() retval=00000011 ret=5c7acdd6 001b:Call KERNEL32.GetStdHandle(fffffff6) ret=5c7acf77 001b:Ret KERNEL32.GetStdHandle() retval=00000004 ret=5c7acf77 001b:Call KERNEL32.DuplicateHandle(ffffffff,00000004,ffffffff,5c7db2e0,00000000,00000001,00000002) ret=5c7acfc0 001b: dup_handle( src_process=ffffffff, src_handle=0004, dst_process=ffffffff, access=00000000, attributes=00000002, options=00000002 ) 001b: dup_handle() = 0 { handle=0008, self=1, closed=0 } 001b:Ret KERNEL32.DuplicateHandle() retval=00000001 ret=5c7acfc0 001b:Call KERNEL32.GetStdHandle(fffffff5) ret=5c7acff6 001b:Ret KERNEL32.GetStdHandle() retval=00000008 ret=5c7acff6 001b:Call KERNEL32.DuplicateHandle(ffffffff,00000008,ffffffff,5c7db304,00000000,00000001,00000002) ret=5c7ad03f 001b: dup_handle( src_process=ffffffff, src_handle=0008, dst_process=ffffffff, access=00000000, attributes=00000002, options=00000002 ) 001b: dup_handle() = 0 { handle=000c, self=1, closed=0 } 001b:Ret KERNEL32.DuplicateHandle() retval=00000001 ret=5c7ad03f 001b:Call KERNEL32.GetStdHandle(fffffff4) ret=5c7ad075 001b:Ret KERNEL32.GetStdHandle() retval=0000000c ret=5c7ad075 001b:Call KERNEL32.DuplicateHandle(ffffffff,0000000c,ffffffff,5c7db328,00000000,00000001,00000002) ret=5c7ad0be 001b: dup_handle( src_process=ffffffff, src_handle=000c, dst_process=ffffffff, access=00000000, attributes=00000002, options=00000002 ) 001b: dup_handle() = 0 { handle=0050, self=1, closed=0 } 001b:Ret KERNEL32.DuplicateHandle() retval=00000001 ret=5c7ad0be 001b:trace:msvcrt:msvcrt_init_io :handles (0x8)(0xc)(0x50) --- snip --- The culprit: msvcrt is actually loaded and unloaded _two_ times! Upon the first unload sequence all std/fd handles are teared down (including handle 0x4) - this makes the handle values available in server again. When the worker thread is created it gets the unused handle 0x4 assigned from wineserver. This is the handle which is then polled by installers GetExitCodeThread() loop. When msvcrt is loaded a second time, GetStdHandle( STD_XXX) will still deliver its original value from PEB (0x4, 0x8, 0xC). Upon second msvcrt unload, fd(3), fd(4), fd(5) are closed again but this time they close something completely different (indication are also fd close errors following), leaving the app installer in forever loop. Regards -- 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.

2 7

[Bug 27478] New: wordview_zh-cn.exe crash
by wine-bugs＠winehq.org 24 Jul '21

24 Jul '21

http://bugs.winehq.org/show_bug.cgi?id=27478 Summary: wordview_zh-cn.exe crash Product: Wine Version: 1.3.21 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi AssignedTo: wine-bugs(a)winehq.org ReportedBy: fracting(a)gmail.com Created an attachment (id=35133) --> (http://bugs.winehq.org/attachment.cgi?id=35133) Log: start wordview_zh-cn.exe 1. Download wordview_zh-cn.exe from http://www.microsoft.com/downloads/zh-cn/confirmation.aspx?displaylang=zh-c… wget --referer=http://www.microsoft.com http://download.microsoft.com/download/3/a/c/3ac87e64-8099-46d6-8e04-363d2d… 2. start the installer with wine $ wine Wine/wordview_zh-cn.exe &> wordview_zh-cn.log then the installer will crash. See attachment for full log Backtrace: =>0 0x492cccb9 cabinet_seek_stream+0x19(hf=0, dist=0, seektype=0x1) [/build/buildd/wine1.3-1.3.21/dlls/msi/media.c:280] in msi (0x003292a4) 1 0x360ac2b5 FDI_read_entries+0x54(fdi=0x556190, hf=0, pfdici=0x329438, pmii=0x5902f4) [/build/buildd/wine1.3-1.3.21/dlls/cabinet/fdi.c:466] in cabinet (0x003293a4) 2 0x360b01eb FDICopy+0x23a(hfdi=0x556190, pszCabinet="<STREAM>", pszCabPath=0x0(nil), flags=0, pfnfdin=0x492ce170, pfnfdid=(nil), pvUser=0x329688) [/build/buildd/wine1.3-1.3.21/dlls/cabinet/fdi.c:2535] in cabinet (0x003295b4) 3 0x492cebb7 msi_cabextract+0x456(package=0x529480, mi=0x555e10, data=0x329688) [/build/buildd/wine1.3-1.3.21/dlls/msi/media.c:632] in msi (0x00329624) -- 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.

2 6

[Bug 30076] New: .NET Framework 4.x with WinVer setting "Windows 7" spams terminal with "LocaleNameToLCID/LCIDToLocaleName unsupported flags 8000000" (LOCALE_ALLOW_NEUTRAL_NAMES)
by wine-bugs＠winehq.org 24 Jul '21

24 Jul '21

http://bugs.winehq.org/show_bug.cgi?id=30076 Bug #: 30076 Summary: .NET Framework 4.x with WinVer setting "Windows 7" spams terminal with "LocaleNameToLCID/LCIDToLocaleName unsupported flags 8000000" (LOCALE_ALLOW_NEUTRAL_NAMES) Product: Wine Version: 1.4-rc6 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Classification: Unclassified Hello, a minor one ... When using .NET 4.x Framework in "Windows 7" mode (at least installer requires this) the terminal is spammed with: --- snip --- $ wine ./hello.exe ... fixme:nls:LocaleNameToLCID unsupported flags 8000000 fixme:nls:LocaleNameToLCID unsupported flags 8000000 fixme:nls:LocaleNameToLCID unsupported flags 8000000 fixme:nls:LocaleNameToLCID unsupported flags 8000000 fixme:nls:LocaleNameToLCID unsupported flags 8000000 fixme:nls:LocaleNameToLCID unsupported flags 8000000 fixme:nls:LocaleNameToLCID unsupported flags 8000000 fixme:nls:LocaleNameToLCID unsupported flags 8000000 fixme:nls:LCIDToLocaleName unsupported flags 8000000 fixme:nls:LCIDToLocaleName unsupported flags 8000000 fixme:nls:LCIDToLocaleName unsupported flags 8000000 Hello C# World :-) --- snip --- This due to LOCALE_ALLOW_NEUTRAL_NAMES (0x8000000) being passed to allow returning neutral names/lcids for name. MSDN: http://msdn.microsoft.com/en-us/library/windows/desktop/dd318711%28v=vs.85%… --- quote --- Windows 7 and later: Can be set to LOCALE_ALLOW_NEUTRAL_NAMES to allow the return of a neutral LCID. --- quote --- One could set to default "Windows XP" after installation but I'm not sure about the side-effects. Regards -- 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.

2 11

[Bug 33377] New: Dependencies on third-party import dlls are undetected
by wine-bugs＠winehq.org 23 Jul '21

23 Jul '21

http://bugs.winehq.org/show_bug.cgi?id=33377 Bug #: 33377 Summary: Dependencies on third-party import dlls are undetected Product: Wine-Testbot Version: unspecified Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com Classification: Unclassified Created attachment 44167 --> http://bugs.winehq.org/attachment.cgi?id=44167 Patch to reproduce this bug The attached patch reproduces an issue first encountered 'in the wild' with this set of patches: * [1/3] include: Add COM interface definitions needed for PrintDlgEx implementation. http://www.winehq.org/pipermail/wine-patches/2013-April/123420.html * [3/3] comdlg32: Add an interactive PrintDlgEx test. http://www.winehq.org/pipermail/wine-patches/2013-April/123422.html * Re: [3/3] comdlg32: Add an interactive PrintDlgEx test. http://www.winehq.org/pipermail/wine-devel/2013-April/099397.html Here is the core of the issue: * The patch contains a first chunk that modifies include/commdlg.h. * This causes a new symbol to be exported by libuuid.a. * The comdlg32:printdlg test needs that symbol to be relinked. The problem is that the WineTestBot does not do a full recompile (for performance reasons), and thus libuuid.a is not rebuilt. So the comdlg32 relink fails because of the missing symbol. Unfortunately there's really no clear indication in the patch that libuuid.a needs to be rebuilt. We could very well run into the same issue with dxguid or a number of other dlls. Some options: * Systematically do a full rebuild. This would be pretty wasteful. * Do a full rebuild whenever the patch touches 'include/'. * Hardcode a list of uuid-like dlls and rebuild them all whenever a patch touches 'include/'. * Detect which uuid-like dlls the test links with (by parsing the Makefile?), and rebuild those whenever the patch touches 'include/'. It's also possible that any chunk outside of the test directory could get us into trouble if we link with the corresponding dll. -- 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.

2 2

[Bug 33749] New: fix for "called from wrong apartment" bug in ClientRpcChannelBuffer_SendReceive
by wine-bugs＠winehq.org 23 Jul '21

23 Jul '21

http://bugs.winehq.org/show_bug.cgi?id=33749 Bug #: 33749 Summary: fix for "called from wrong apartment" bug in ClientRpcChannelBuffer_SendReceive Product: Wine Version: 1.6-rc1 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: ole32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: rosen.diankov(a)gmail.com Classification: Unclassified There are cases where the "called from wrong apartment" gets called in ole32/rpc.c:ClientRpcChannelBuffer_SendReceive and there is no COM apartment set. Actually the thread should be using the implicit multithreaded apartment created from a previous thread's CoInitializeEx call http://blogs.msdn.com/b/oldnewthing/archive/2013/04/19/10412399.aspx Therefore the fix is really simple, add this check right in the beginning of ClientRpcChannelBuffer_SendReceive if( !COM_CurrentApt() ) { apartment_joinmta(); } Note that in Windows 7 and beyond, there's a new flag that controls the implicit MTA behavior called APTTYPEQUALIFIER. http://msdn.microsoft.com/library/dd542638 Wine should support this for Windows 7 and beyond. -- 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.

2 6

[Bug 24688] New: RTL and encoding problem with Ihulan
by wine-bugs＠winehq.org 21 Jul '21

21 Jul '21

http://bugs.winehq.org/show_bug.cgi?id=24688 Summary: RTL and encoding problem with Ihulan Product: Wine Version: 1.3.4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: sh.yaron(a)gmail.com Ihulan (www.oniton.com) is a Hebrew greetings apps, there's also an English version called U.R.Celeb (http://urceleb.oniton.com/) The Hebrew installation (http://www.oniton.com/uploads/secure/Ihulan453.exe) has several issues: 1. The text is Gibberish. 2. On the terms of service (2nd page) the text is in Hebrew but selectingthe mixes its order, also the header (in read) are split in the middle by LRM for some reason... 3. The window is not RTL although I'm not sure it should be... This also demonstrates some of the typical problems with Hebrew. Kind regards, Yaron Shahrabani -- 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.

2 34

[Bug 28326] New: CDBurnerXP's audio player is missing some visual elements
by wine-bugs＠winehq.org 20 Jul '21

20 Jul '21

http://bugs.winehq.org/show_bug.cgi?id=28326 Summary: CDBurnerXP's audio player is missing some visual elements Product: Wine Version: 1.3.27 Platform: x86-64 URL: http://cdburnerxp.se/download?more-options OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: gdiplus AssignedTo: wine-bugs(a)winehq.org ReportedBy: RandomAccountName(a)mail.com Created an attachment (id=36293) --> (http://bugs.winehq.org/attachment.cgi?id=36293) Builtin/native gdiplus comparison screenshots In CDBurnerXP, the audio player dialog does not display the elapsed playback time, and the outer edges of the pseudo-LED showing the current track are also missing. Both can be seen with native gdiplus. To reproduce the problem: 1. Use winetricks dotnet20 before installing 2. From the main menu, choose "audio disc" 3. Observe the appearance of the audio player above the upper-right corner of the program window -- 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.

2 11

[Bug 28795] New: ExeInfoPE: PE protection schemes that abuse %gs won't run (breaks glibc TLS selector)
by wine-bugs＠winehq.org 20 Jul '21

20 Jul '21

http://bugs.winehq.org/show_bug.cgi?id=28795 Bug #: 28795 Summary: ExeInfoPE: PE protection schemes that abuse %gs won't run (breaks glibc TLS selector) Product: Wine Version: 1.3.30 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Classification: Unclassified Hello, newer versions of "ExeInfoPE" (>0.0.2.3) which coin their own PE protection scheme don't run anymore. There is still bug 26701 though the app crashes now earlier. With tracing enabled: --- snip --- ... 0024:Call KERNEL32.VirtualProtect(00400000,00001000,00000004,0032fe40) ret=05bd0336 0024:Ret KERNEL32.VirtualProtect() retval=00000001 ret=05bd0336 0024:Call KERNEL32.VirtualProtect(00400000,00001000,00000002,0032fe40) ret=05bd034b 0024:Ret KERNEL32.VirtualProtect() retval=00000001 ret=05bd034b 0024:trace:seh:raise_exception code=c0000005 flags=0 addr=0xb74a916a ip=b74a916a tid=0024 0024:trace:seh:raise_exception info[0]=00000000 0024:trace:seh:raise_exception info[1]=ffffffff 0024:trace:seh:raise_exception eax=7bc9d7a7 ebx=b75e0ff4 ecx=0032fdcc edx=7bc9d7a7 esi=0032fc74 edi=ffffffc8 0024:trace:seh:raise_exception ebp=0032fc48 esp=0032f6bc cs=0073 ds=007b es=007b fs=0033 gs=0002 flags=00010246 0024:trace:seh:call_vectored_handlers calling handler at 0x7e16e0bd code=c0000005 flags=0 0024:trace:seh:call_vectored_handlers handler at 0x7e16e0bd returned 0 0024:trace:seh:call_stack_handlers calling handler at 0x7bc90f61 code=c0000005 flags=0 0024:Call KERNEL32.UnhandledExceptionFilter(0032f194) ret=7bc90f9b wine: Unhandled page fault on read access to 0xffffffff at address 0xb74a916a (thread 0024), starting debugger... 0024:trace:seh:start_debugger Starting debugger "winedbg --auto 35 52" 0024:Ret KERNEL32.UnhandledExceptionFilter() retval=00000000 ret=7bc90f9b 0024:trace:seh:call_stack_handlers handler at 0x7bc90f61 returned 1 Unhandled exception: page fault on read access to 0xffffffff in 32-bit code (0xb74a916a). Register dump: CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:0002 EIP:b74a916a ESP:0032f6bc EBP:0032fc48 EFLAGS:00010246( R- -- I Z- -P- ) EAX:7bc9d7a7 EBX:b75e0ff4 ECX:0032fdcc EDX:7bc9d7a7 ESI:0032fc74 EDI:ffffffc8 Stack dump: 0x0032f6bc: 0032fc7c 7bc9d82e 0032fc58 b74a992c 0x0032f6cc: 0032fc7c 7bc9d82d 00000001 00000000 0x0032f6dc: 0032fc8c 7bc9d82d 00000001 00000001 0x0032f6ec: 7bc9d82d 00000000 00000000 00000001 0x0032f6fc: 7bc9d82d 00000000 00000000 00000000 0x0032f70c: 00000000 00000000 00000000 00000000 Backtrace: =>0 0xb74a916a _IO_vfprintf+0x3a() in libc.so.6 (0x0032fc48) 1 0xb74cbdbb vsnprintf+0xca() in libc.so.6 (0x0032fc74) 2 0x7bc350f9 NTDLL_dbg_vprintf+0x56() in ntdll (0x0032fd90) 3 0xb761ab63 wine_dbg_printf+0x2e() in libwine.so.1 (0x0032fdc0) 4 0x7bc640e5 relay_call+0x113() in ntdll (0x0032fe10) 5 0x7b8224ad in kernel32 (+0x124ac) (0x0032fe60) 6 0x004075cd in exeinfope (+0x75cc) (0x0032fe60) 7 0x7b85de44 call_process_entry+0xb() in kernel32 (0x0032fe78) 8 0x7b85df8a start_process+0x143() in kernel32 (0x0032fec8) 9 0x7bc7a244 call_thread_func+0xb() in ntdll (0x0032fed8) 10 0x7bc7a282 call_thread_entry_point+0x33() in ntdll (0x0032ffb8) 11 0x7bc51ebc start_process+0x25() in ntdll (0x0032ffe8) 12 0xb761edb5 wine_call_on_stack+0x1c() in libwine.so.1 (0x00000000) 0xb74a916a _IO_vfprintf+0x3a in libc.so.6: movl %gs:0x00000000,%ecx --- snip --- The protection scheme fiddles with %gs selector value which breaks TLS pointer access through %gs:0 (Wine uses %fs) or the stack protector scheme that Userland libs and Wine are built with (glibc provided __stack_chk_guard at %gs:0x14). My gcc 4.6.1 x86 host toolchain has -fstack-protector enabled by default hence Wine gets the stack canary code in the binaries. The Glibc here (Xubuntu 11.10) has stack smashing protection enabled by default. Even if Wine is built with "-fno-stack-protector" the app would still break glibc %gs TLS code. This is just a "collector" bug for apps that run into this issue. WONTFIX obviously, there is no reliable way to know when to repair/restore %gs value (and restarting faulting instruction). Regards -- 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.

2 9