wine-bugs March 2008

wine-bugs@winehq.org

1 participants
3661 discussions

[Bug 10204] New: Incorrectly raised FD_WRITE socket event
by wine-bugs＠winehq.org 02 Jun '21

02 Jun '21

http://bugs.winehq.org/show_bug.cgi?id=10204 Summary: Incorrectly raised FD_WRITE socket event Product: Wine Version: 0.9.48. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P3 Component: wine-net AssignedTo: wine-bugs(a)winehq.org ReportedBy: rraptorr(a)nails.eu.org Created an attachment (id=8812) --> (http://bugs.winehq.org/attachment.cgi?id=8812) FD_WRITE event on socket test program According to MSDN WSAEventSelect function description (http://msdn2.microsoft.com/en-us/library/ms741576.aspx), FD_WRITE event should be raised only once after: a) successful connection b) WSAEWOULDBLOCK error while in nonblocking mode. MSDN description: "The FD_WRITE network event is handled slightly differently. An FD_WRITE network event is recorded when a socket is first connected with connect/WSAConnect or accepted with accept/WSAAccept, and then after a send fails with WSAEWOULDBLOCK and buffer space becomes available. Therefore, an application can assume that sends are possible starting from the first FD_WRITE network event setting and lasting until a send returns WSAEWOULDBLOCK. After such a failure the application will find out that sends are again possible when an FD_WRITE network event is recorded and the associated event object is set." Unfortunately, it seems that in Wine 0.9.48 (and a few earlier versions too) this event is raised every time it is possible to write to the socket. I've created a simple test program (FD_WRITE-test.c) that shows this problem. When ran on Windows I get: lNetworkEvents: 2 lNetworkEvents: 0 but when ran on Wine: lNetworkEvents: 2 lNetworkEvents: 2 which means that FD_WRITE was raised twice and it shouldn't. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 53

[Bug 9504] New: Cannot close CMonthCalCtrl popup by clicking outside popup
by wine-bugs＠winehq.org 02 Jun '21

02 Jun '21

http://bugs.winehq.org/show_bug.cgi?id=9504 Summary: Cannot close CMonthCalCtrl popup by clicking outside popup Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wine-user AssignedTo: wine-bugs(a)winehq.org ReportedBy: peter(a)cendio.se I have an application that uses a custom control: A wrapper that displays a CMonthCalCtrl in a popup window. In Windows, it's possible to close the popup by clicking outside the popup. With Wine, however, it is necessary to either select a date or press Escape. The popup will also be closed if the user tries to move the popup window (which has X11 WM decorations). When clicking outside the popup with Wine, Wine generates a beep through X11 (I believe this happens since a WM_SETCURSOR with HTERROR is generated). A demo program is available as http://www.cendio.se/~astrand/wine/6-close-popup/. Requires Visual C++ 2005 runtime libraries. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 28

[Bug 10635] New: Tivo Desktop 2.5.1 will not install
by wine-bugs＠winehq.org 28 May '21

28 May '21

http://bugs.winehq.org/show_bug.cgi?id=10635 Summary: Tivo Desktop 2.5.1 will not install Product: Wine Version: 0.9.50. Platform: PC URL: http://www.tivo.com/mytivo/domore/tivotogo/windows.html OS/Version: Windows XP Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-ole AssignedTo: wine-bugs(a)winehq.org ReportedBy: joseph_scott123(a)msn.com When trying to install Tivo Desktop 2.5.1 I get the following messages and it fails to install. fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),0,3,(nil),0,(nil)) - stub! err:ole:CoGetClassObject class {6c736db1-bd94-11d0-8a23-00aa00b58e10} not registered err:ole:CoGetClassObject no class object {6c736db1-bd94-11d0-8a23-00aa00b58e10} could be created for context 0x1 fixme:msi:AutomationObject_GetIDsOfNames Unknown member L"UILevel", clsid {000c1090-0000-0000-c000-000000000046} fixme:seh:_abnormal_termination (void)stub fixme:seh:_abnormal_termination (void)stub fixme:seh:_abnormal_termination (void)stub Usage: Install a product: msiexec {package|productcode} [property] msiexec /i {package|productcode} [property] msiexec /a package [property] Repair an installation: msiexec /f[p|o|e|d|c|a|u|m|s|v] {package|productcode} Uninstall a product: msiexec /x {package|productcode} [property] Advertise a product: msiexec /j[u|m] package [/t transform] [/g languageid] msiexec {u|m} package [/t transform] [/g languageid] Apply a patch: msiexec /p patchpackage [property] msiexec /p patchpackage /a package [property] Modifiers for above operations: msiexec /l[*][i|w|e|a|r|u|c|m|o|p|v|][+|!] logfile msiexec /q{|n|b|r|f|n+|b+|b-} Register a module: msiexec /y module Unregister a module: msiexec /z module Display usage and copyright: msiexec {/h|/?} NOTE: Product code on commandline unimplemented as of yet Copyright 2004 Vincent B�ron -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 17

[Bug 11833] New: GroupMail: Unhandled page fault on read access to 0x00000000 at address 0x164675c
by wine-bugs＠winehq.org 07 May '21

07 May '21

http://bugs.winehq.org/show_bug.cgi?id=11833 Summary: GroupMail: Unhandled page fault on read access to 0x00000000 at address 0x164675c Product: Wine Version: 0.9.56. Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: info(a)netherworld.com.ar When i open File => create new mail. the app crashes and the debug shows an Unhandled page fault. please fix -- 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 21

[Bug 10219] New: Windows Media Player 11 setup fails
by wine-bugs＠winehq.org 03 May '21

03 May '21

http://bugs.winehq.org/show_bug.cgi?id=10219 Summary: Windows Media Player 11 setup fails Product: Wine Version: 0.9.48. Platform: PC URL: http://www.microsoft.com/windows/windowsmedia/download/A llDownloads.aspx?displang=en&qstechnology= OS/Version: Linux Status: NEW Keywords: download, Installer Severity: normal Priority: P2 Component: wine-misc AssignedTo: wine-bugs(a)winehq.org ReportedBy: alex(a)thehandofagony.com The setup program for Windows Media Player 11 tries to validate Windows if the version is set to XP, and this fails. There was talk some time ago about an ntlm_auth patch that would allow the validation, but it fails for me even though I have the correct version of Samba installed. However, the installer does not run the Genuine check if the Windows version is set to Vista. When run thus it does work, however; it tries to create an instance of a wuapi.dll class, which is not registered in Wine. When I use a native dll from XP and register it the console output changes saying no instance could be created. The installer then says no updates could be found. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 19

[Bug 11228] New: .NET Framework 2.0 Registry Bug
by wine-bugs＠winehq.org 24 Mar '21

24 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=11228 Summary: .NET Framework 2.0 Registry Bug Product: Wine Version: 0.9.53. Platform: Other OS/Version: other Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: n.tessore(a)gmail.com When installing the .NET Framework 2.0, the installer creates a registry key HKEY_LOCAL_MACHINE\Software\Microsoft\.NETFramework\Policy\AppPatch\v[RTM_ProductVersion].00000 --- The correct key would be HKEY_LOCAL_MACHINE\Software\Microsoft\.NETFramework\Policy\AppPatch\v2.0.50727.00000 --- This leads to seemingly meaningless errors in a number of unexpected places (ie. normal non-.NET applications), like this one here: fixme:advapi:RegisterEventSourceA ((null),".NET Runtime"): stub fixme:advapi:RegisterEventSourceW (L"",L".NET Runtime"): stub fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x00000000,(nil),0x0001,0x00000000,0x33e64c,(nil)): stub err:eventlog:ReportEventW L"Error enumerating shim databases - 234" fixme:advapi:DeregisterEventSource (0xcafe4242) stub -- 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 13

[Bug 10325] New: Avencast: Rise of the Mage crash on attempt to play startup video
by wine-bugs＠winehq.org 23 Mar '21

23 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=10325 Summary: Avencast: Rise of the Mage crash on attempt to play startup video Product: Wine Version: 0.9.48. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wine-directx AssignedTo: wine-bugs(a)winehq.org ReportedBy: cheetahmorph(a)gmail.com Created an attachment (id=8986) --> (http://bugs.winehq.org/attachment.cgi?id=8986) Logfile auto-generated by the Avencast Demo >From watching the installer, I noticed several .wmv files installed. Game asked for d3dx9_30.dll, which was copied from my other harddrive partition to the game folder. Game launches easily, showing the splash screen, and then this error: DXC Error (DirectX9) DXC_VideoPlayerOverlayBase: CoCreateInstance failed (VideoMixingRenderer) Upon clicking "Ok", the game crashes. Link to demo: http://files.filefront.com/Avencast+Rise+of+the+Mage+Demo/;8771255;/fileinf… Attached: Log that the demo created on its own, might be useful -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 24

[Bug 10467] New: Making Microsoft .NET 2.0 to work in wine, based on example app FastMD5 1.4 for NET 2.0
by wine-bugs＠winehq.org 19 Mar '21

19 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=10467 Summary: Making Microsoft .NET 2.0 to work in wine, based on example app FastMD5 1.4 for NET 2.0 Product: Wine Version: CVS/GIT Platform: PC URL: http://www.paehl.de/english.php OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-dotnet AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, this bug id exists for the sole purpose of showing my little journey of getting .NET 2.0 to work in wine. This topic does *NOT* cover the MONO project in any way. The windows version of MONO is covered by other bug reports. DISCLAIMER: This is just a first step which aims at major show stoppers. There are *many* issues left when it comes to managed (JIT) vs. unmanaged (native) API code bridging. To iron out all the bugs, many different applications are needed which cover the whole range of .NET Framework. I randomly chose a simple .NET 2.0 app which uses plain system.windows.forms stuff (no fancy controls/interop). --- snip --- http://www.paehl.de/fastmd5_net20.zip FASTMD5 create very fast with low CPU use a MD5 hash. Required .NET 1.1 or 2.0 --- snip --- Just as foreword: yes, it plain sucks to debug mixed code in wine (managed + unmanaged) because the tools required don't work reliable (or at all) due to several wine bugs/design problems. Prerequisite: successful installation of .NET 2.0 Framework and wine-0.9.49 (or GIT) ---------- If you start .NET apps they will fail with stack overflows and some exceptions thrown. The exception type tells us what we are dealing with: 0xe0434f4d For the uninitiated: this an exception type exclusively thrown by .NET common language runtime (CLR). Using my specially hacked wine to run tools like windbg one can get a raw estimate by looking at native method callstack: --- snip --- 0:000> sxe clr .. 0:000> .load clr20\sos.dll .. 0:000> g .. 0:000> kb ChildEBP RetAddr Args to Child WARNING: Stack unwind information not available. Following frames may be wrong. 0034efb8 79f97065 e0434f4d 00000001 00000001 KERNEL32!RaiseException+0x78 0034f018 7a0945a4 00a11cb4 00000000 00000000 mscorwks!RaiseTheExceptionInternalOnly+0x226 0034f0dc 02fa364b 00000000 0000007f 0034f138 mscorwks!JIT_Throw+0xd0 0034f1d8 79e88f63 00000000 0012e0f8 0034f22c 0x2fa364b 0034f1f8 79e88f63 00000000 00000000 0016b200 mscorwks!CallDescrWorker+0x33 0034f210 79e88ee4 0034f2e8 00000002 0034f2b0 mscorwks!CallDescrWorker+0x33 .. --- snip --- JIT code is at 0x2fa364b which transfers managed exceptions using mscorwks!JIT_Throw() to native code/OS. Lets look at CLR exception info... --- snip --- 0:000> !PrintException Exception object: 00a11cb4 Exception type: System.TypeInitializationException Message: The type initializer for 'System.Globalization.TextInfo' threw an exception. InnerException: <none> StackTrace (generated): <none> StackTraceString: <none> HResult: 80131534 --- snip --- And the managed code callstack... --- snip --- 0:000> !ClrStack OS Thread Id: 0xf (0) ESP EIP 0034f040 7b8414d8 [HelperMethodFrame: 0034f040] 0034f0e4 02fa364b System.Globalization.TextInfo.GetNativeTextInfo(Int32) 0034f114 02fa3511 System.Globalization.TextInfo.get_InvariantNativeTextInfo() 0034f140 02fa193d System.String.Compare(System.String, Int32, System.String, Int32, Int32, System.StringComparison) 0034f16c 02fa15a1 System.Security.Util.URLString.PreProcessForExtendedPathRemoval(System.String, Boolean) 0034f184 02fa10b0 System.AppDomainSetup.NormalizePath(System.String, Boolean) 0034f1a4 02fa06d6 System.AppDomainSetup.SetupDefaultApplicationBase(System.String) 0034f1bc 02fa02cc System.AppDomain.SetupFusionStore(System.AppDomainSetup) 0034f1d4 02fa01fa System.AppDomain.SetupDomain(Boolean, System.String, System.String) 0034f42c 79e88f63 [GCFrame: 0034f42c] 0034f9e0 79e88f63 [DebuggerClassInitMarkFrame: 0034f9e0] --- snip --- Some native method call in GetNativeTextInfo() seems to be the culprit. For many (string) resource based stuff to work, a unicode OS casing table is required. The table for the invariant version is built from external .NLS file. To make story short: wine does not ship the default case mapping table for unicode characters: "l_intl.nls". This is a "must" requirement and failure results in early TypeInitializationException while setting up default application domain. Short fix: copy the file from your windows system32 directory to wine system32. Long run fix: let wine generate/install this file. Not a big deal. Now simple .NET _console_ based apps (like "Hello World") will work. --------------------------------------- Stay tuned, more goodies to come ... Regards -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 109

[Bug 12099] New: .NET Framework 1.1 installer requires loadperf. dll in case of AeDebug -> Auto=0 (unhandled exception dialog)
by wine-bugs＠winehq.org 18 Mar '21

18 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=12099 Summary: .NET Framework 1.1 installer requires loadperf.dll in case of AeDebug -> Auto=0 (unhandled exception dialog) Product: Wine Version: CVS/GIT Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Created an attachment (id=11486) --> (http://bugs.winehq.org/attachment.cgi?id=11486) example patch to add loadperf.dll and simple UnloadPerfCounterTextStringsW stub preventing .NET 1.1 installer exception Hello, VS.NET 7.x installers modify AeDebug which results in error message box from .NET Framework 1.1 installer due to an unhandled exception. With default AeDebug Auto=1 and standalone .NET 1.1 installation you won't notice it because this exception doesn't affect overall "success" result of installer. You can capture output from console to see winedbg actually spawned. VS.NET 7.x installers add/modify the following JIT debugging keys: --- snip --- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger Auto: 1 -> 0 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger Default: cordbg.exe !a 0x%x8 --- snip --- Extract from .msi file: --- snip --- _FldbVs7eve_RegFile_887_00017.3643236F_FC70_11D3_A536_0090278A1BB8 2 SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug Auto 0 _VS_Debugging___VS7JIT_____X86.3643236F_FC70_11D3_A536_0090278A1BB8) .. --- snip --- You can simulate the behaviour on clean ~/.wine if you manually set AeDebug/Auto=0 (default is 1) and then execute the standalone .NET 1.1 installer. --- snip --- 002d:Call KERNEL32.lstrlenA(0034f55c "2008-03-17 21:20:25\t\tStarting\tUninstalling performance counters\r\n") ret=79e88b92 .. 002d:Call KERNEL32.LoadLibraryA(79e61310 "loadperf.dll") ret=79e907ed 002d:Ret KERNEL32.LoadLibraryA() retval=00000000 ret=79e907ed 002d:Call KERNEL32.GetLastError() ret=79e907f9 002d:Ret KERNEL32.GetLastError() retval=0000007e ret=79e907f9 002d:Call KERNEL32.RaiseException(c06d007e,00000000,00000001,0034f960) ret=79e9082c 002d:trace:seh:raise_exception code=c06d007e flags=0 addr=0x7b8419a0 002d:trace:seh:raise_exception info[0]=0034f910 002d:trace:seh:raise_exception eax=7b82c3e9 ebx=7b8af3e4 ecx=00000000 edx=0034f904 esi=0034f904 edi=0034f880 002d:trace:seh:raise_exception ebp=0034f868 esp=0034f804 cs=0073 ds=007b es=007b fs=0033 gs=003b flags=00200212 002d:trace:seh:call_stack_handlers calling handler at 0x402518 code=c06d007e flags=0 .. 002d:Call KERNEL32.UnhandledExceptionFilter(0034f350) ret=7c34c456 wine: Unhandled exception 0xc06d007e at address 0x7b8419a0 (thread 002d), starting debugger... 002d:Call user32.MessageBoxA(00000000,0034efd8 "Unhandled exception 0xc06d007e at address 0x7b8419a0.\nDo you wish to debug it?",7b8a3e47 "Exception raised",00000014) ret=7b841deb --- snip --- The message box is shown with the option to dismiss the exception or to debug it. This can be pretty confusing to users who have no knowledge how to deal with this. Well, actually this exception should never occur. Wine can prevent this problem by providing a simple loadperf.dll and UnloadPerfCounterTextStringsW stub. Output after patch: --- snip --- 0041:Ret KERNEL32.LoadLibraryA() retval=607d0000 ret=79e907ed 0041:Call KERNEL32.InterlockedExchange(79e96fa8,607d0000) ret=79e9083e 0041:Ret KERNEL32.InterlockedExchange() retval=00000000 ret=79e9083e 0041:Call KERNEL32.GetProcAddress(607d0000,79e919b4 "UnloadPerfCounterTextStringsW") ret=79e908c4 0041:Ret KERNEL32.GetProcAddress() retval=607d8808 ret=79e908c4 0041:Call loadperf.UnloadPerfCounterTextStringsW(0034f9d0 L"u \"ASP.NET_1.1.4322\"",00000001) ret=79e86e64 0041:fixme:loadperf:UnloadPerfCounterTextStringsW (L"u \"ASP.NET_1.1.4322\"", 1): stub! 0041:Ret loadperf.UnloadPerfCounterTextStringsW() retval=00000000 ret=79e86e64 --- snip --- Please add this dll and the UnloadPerfCounterTextStringsW stub. The attached patch is provided as example to quickly validate the problem solution. 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 13

[Bug 11990] New: Script and Field Lists in FileMaker Pro are blank
by wine-bugs＠winehq.org 18 Mar '21

18 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=11990 Summary: Script and Field Lists in FileMaker Pro are blank Product: Wine Version: 0.9.57. Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dempsey(a)weirdfish.net Created an attachment (id=11316) --> (http://bugs.winehq.org/attachment.cgi?id=11316) Manage Databases Comparison I've installed FileMaker Advanced 9 fine using the latest Wine but when trying to view both fields and scripts it shows all the lines, but doesn't show the text which should be showing the name. I guess the problem occurs in all three places as they use the same control for : Field Listing in Manage Database Script Listing in Manage Scripts Script Steps in Edit Script http://magicbadger.com/dump/images/wine/FM_Manage_Database.png http://magicbadger.com/dump/images/wine/FM_Manage_Scripts.png http://magicbadger.com/dump/images/wine/FM_Edit_Script.png -- 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

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 2008