wine-bugs November 2011

wine-bugs@winehq.org

1 participants
9461 discussions

[Bug 21549] New: Windows PowerShell 1.x installer dies on unimplemented function USERENV.dll.138
by wine-bugs＠winehq.org 19 Mar '21

19 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=21549 Summary: Windows PowerShell 1.x installer dies on unimplemented function USERENV.dll.138 Product: Wine Version: 1.1.37 Platform: x86 URL: http://www.google.de/search?q=WindowsXP-KB926139-v2-x8 6-ENU.exe OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, after working around bug 21542, the installer dies in post-install action: --- snip --- 0030:Starting process L"C:\\3f9c459343b0ee6273e24b88b0d982f2\\update\\update.exe" (entryproc=0x1065e2c) ... 0030:Call shlwapi.PathFileExistsW(0033ad50 L"C:\\users\\Public\\Start Menu\\Programs") ret=68ad8ae7 0030:Call KERNEL32.SetErrorMode(00000001) ret=68c4a703 0030:Ret KERNEL32.SetErrorMode() retval=00008005 ret=68c4a703 0030:Call KERNEL32.GetFileAttributesW(0033ad50 L"C:\\users\\Public\\Start Menu\\Programs") ret=68c4a714 0030:Ret KERNEL32.GetFileAttributesW() retval=00000010 ret=68c4a714 0030:Call KERNEL32.SetErrorMode(00008005) ret=68c4a725 0030:Ret KERNEL32.SetErrorMode() retval=00000001 ret=68c4a725 0030:Ret shlwapi.PathFileExistsW() retval=00000001 ret=68ad8ae7 0030:Call KERNEL32.WideCharToMultiByte(00000000,00000000,0033b00c L"C:\\users\\Public\\Start Menu\\Programs",ffffffff,0033b33c,00000104,00000000,00000000) ret=68ad8d7d 0030:Ret KERNEL32.WideCharToMultiByte() retval=00000024 ret=68ad8d7d 0030:Ret shell32.SHGetSpecialFolderPathA() retval=00000001 ret=01072df8 0030:Call KERNEL32.FindFirstFileA(0033b544 "C:\\users\\Public\\Start Menu\\Programs\\Windows PowerShell 1.0\\@.lnk",0033b18c) ret=0106da6d 0030:Ret KERNEL32.FindFirstFileA() retval=ffffffff ret=0106da6d 0030:trace:seh:raise_exception code=80000100 flags=1 addr=0x7bc4af8a ip=7bc4af8a tid=0030 0030:trace:seh:raise_exception info[0]=0108d004 0030:trace:seh:raise_exception info[1]=0000008a wine: Call from 0x7bc4af8a to unimplemented function USERENV.dll.138, aborting 0030:trace:seh:call_vectored_handlers calling handler at 0x68ec9e52 code=80000100 flags=1 0030:trace:seh:call_vectored_handlers handler at 0x68ec9e52 returned 0 0030:trace:seh:call_vectored_handlers calling handler at 0x6879bdc6 code=80000100 flags=1 0030:trace:seh:call_vectored_handlers handler at 0x6879bdc6 returned 0 0030:trace:seh:call_stack_handlers calling handler at 0x1066099 code=80000100 flags=1 0030:Call msvcrt._except_handler3(0033b25c,0033f37c,0033aeec,0033add0) ret=7bc77ab5 ... --- snip --- Dumping userenv imports for the installer: --- snip --- $ winedump -j import update.exe ... offset 0008c2f4 USERENV.dll Hint/Name Table: 0008D824 TimeDateStamp: 00000000 (Thu Jan 1 01:00:00 1970) ForwarderChain: 00000000 First thunk RVA: 000017F8 Ordn Name 138 <by ordinal> 121 <by ordinal> 119 <by ordinal> ... --- snip --- Actually only ordinal 138 seems to get used (Wine 'Windows XP' config). Unfortunately I didn't find anything useful about this one (MSDN, blogs, Bing ..) :-( By analyzing the caller stack setup we can deduce the necessary information to create a simple stub. The installer calls the ordinal like this: --- snip --- $ winedbg disas ... 0x01072e9b: pushl 0xffffff88(%ebp) 0x01072e9e: leal 0xbc(%ebp),%eax 0x01072ea4: pushl %eax 0x01072ea5: leal 0x5d0(%ebp),%eax 0x01072eab: pushl %eax 0x01072eac: pushl 0xffffff9c(%ebp) 0x01072eaf: leal 0x2c4(%ebp),%eax 0x01072eb5: pushl 0xffffffa0(%ebp) 0x01072eb8: pushl %eax 0x01072eb9: pushl 0xffffffa4(%ebp) 0x01072ebc: leal 0x4cc(%ebp),%eax 0x01072ec2: pushl %eax 0x01072ec3: leal 0x3c8(%ebp),%eax 0x01072ec9: pushl %eax 0x01072eca: leal 0x7d8(%ebp),%eax 0x01072ed0: pushl %eax 0x01072ed1: leal 0x6d4(%ebp),%eax 0x01072ed7: pushl %eax 0x01072ed8: pushl 0xffffffb4(%ebp) 0x01072edb: call *0x10017f8 -> 0x00450000 0x01072ee1: cmpl %ebx,%eax 0x01072ee3: movl %eax,0xffffffa8(%ebp) 0x01072ee6: jnz 0x01072f0c ... --- snip --- number of arguments: 12 calling conv: stdcall return type: most likely boolean (like the other known userenv API). Armed with this information one can add a simple stub, export with ordinal 138, -noname and 12 ptr params, name it whatever you like. If you find any documented name, feel free to use it. If we fake the stub to return FALSE, following messages will be logged to: "c:\windows\KB926139-v2.log" --- snip --- 22.312: Failed To Create Link -3 Windows PowerShell 22.314: Failed To Create Link -3 Release Notes 22.316: Failed To Create Link -3 Getting Started 22.319: Failed To Create Link -3 User Guide 22.321: Failed To Create Link -3 Quick Reference --- snip --- So this API is most likely some Lnk creation stuff. Anyway, that simple stub is sufficient to let the installer proceed with its post-install steps. In the end, the installer runs into bug 16876 (bug in property sheet control). 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 8

[Bug 26936] New: Advanced SystemCare: Error message at start-up
by wine-bugs＠winehq.org 19 Mar '21

19 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=26936 Summary: Advanced SystemCare: Error message at start-up Product: Wine Version: 1.3.18 Platform: x86 URL: http://download.iobit.com/asc-setup.exe OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: lukasz.wojnilowicz(a)gmail.com Created an attachment (id=34357) --> (http://bugs.winehq.org/attachment.cgi?id=34357) Terminal output on wine-1.3.18-171-g1ffb069 Steps to reproduce: 1) remove ~/.wine 2) winetricks gecko 3) install Advanced SystemCare (default installation) 4) wine ASC.exe Behaviour: Error message. Expected behaviour: There should be no error message. Workaround: winetricks ie7 msxml3 Additional information: winetricks msxml3 doesn't solve the problem winetricks ie7 doesn't solve the problem Is this msxml bug then? -- 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 16

[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 15437] New: Company of Heroes Opposing Fronts: Installer fails
by wine-bugs＠winehq.org 19 Mar '21

19 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=15437 Summary: Company of Heroes Opposing Fronts: Installer fails Product: Wine Version: 1.1.5 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: xvachon(a)gmail.com Created an attachment (id=16303) --> (http://bugs.winehq.org/attachment.cgi?id=16303) log Installation of the game is not possible. Exception EAccessViolation error in module GameInst.exe happens. According to test data the game had to be installed from a Windows installation in order to be played. A log is attached. -- 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 66

[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 20291] New: File Maker 10 Advanced installs fine but does not start in Debian 5 wine version 1.01
by wine-bugs＠winehq.org 18 Mar '21

18 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=20291 Summary: File Maker 10 Advanced installs fine but does not start in Debian 5 wine version 1.01 Product: WineHQ Bugzilla Version: unspecified Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: bugzilla-unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ialsahili(a)gmail.com Here is the message that appears when I try to run the program in terminal: -- 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 4

[Bug 20289] New: File Maker 10 Advanced installs fine but does not start in Debian 5 wine version 1.01
by wine-bugs＠winehq.org 18 Mar '21

18 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=20289 Summary: File Maker 10 Advanced installs fine but does not start in Debian 5 wine version 1.01 Product: WineHQ Bugzilla Version: unspecified Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: bugzilla-unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ialsahili(a)gmail.com Here is the message that appears when I try to run the program in terminal: fixme:heap:HeapSetInformation (nil) 1 (nil) 0 fixme:advapi:RegisterEventSourceW ((null),L"Bonjour Service"): stub fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013 fixme:winsock:WSAIoctl SIO_GET_EXTENSION_FUNCTION_POINTER {f689d7c8-6f1f-436b-8a53-e54fe351c322}: stub fixme:winsock:WS_setsockopt Unknown level: 0x00000029 fixme:winsock:WS_setsockopt Unknown level: 0x00000029 fixme:winsock:WS_setsockopt Unknown level: 0x00000029 fixme:winsock:WS_setsockopt Unknown level: 0x00000029 fixme:winsock:WSAIoctl SIO_GET_EXTENSION_FUNCTION_POINTER {f689d7c8-6f1f-436b-8a53-e54fe351c322}: stub fixme:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request: stub err:module:attach_process_dlls "odbc32.dll" failed to initialize, aborting err:module:LdrInitializeThunk Main exe initialization for L"C:\\Program Files\\FileMaker\\FileMaker Pro 10 Advanced\\FileMaker Pro Advanced.exe" failed, status c0000005 -- 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 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

[Bug 26600] New: Filemaker Pro2 under Wine
by wine-bugs＠winehq.org 18 Mar '21

18 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=26600 Summary: Filemaker Pro2 under Wine Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gilles.l.auger(a)gmail.com The program winevdm.exe has encountered a serious problem and must be closed. We are sorry for this situation. This may be caused by an error in the program or a default in Wine. This problem does not occur under Windows. Le programme winevdm.exe a rencontré un problème sérieux et doit être fermé. Nous sommes désolés pour le désagrément subi. Cela peut être causé par une erreur dans le programme ou un défaut dans Wine. Se problème ne se produit pas sous Windows. -- 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 13463] New: 000
by wine-bugs＠winehq.org 18 Mar '21

18 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=13463 Summary: 000 Product: WineHQ Bugzilla Version: unspecified Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P5 Component: bugzilla-unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: maty1206(a)maryanlinux.com Wine can't uninstall the trial of Filemaker Pro. Please, improve this feature. -- 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

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 November 2011