June 2009 - Wine-Bugs - list.winehq.org

[Bug 18302] New: Adobe Acrobat Pro 7: Preferences-Window is broken
by wine-bugs＠winehq.org July 24, 2021

July 24, 2021

http://bugs.winehq.org/show_bug.cgi?id=18302 Summary: Adobe Acrobat Pro 7: Preferences-Window is broken Product: Wine Version: 1.1.20 Platform: PC-x86-64 URL: http://ardownload.adobe.com/pub/adobe/acrobat/win/7x/7.0 /misc/AcTR7EFG.exe OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: waltherbans(a)yahoo.de When you clicking on "Edit"->"Preference" in Adobe Acrobat Professional 7 a grey box will pop up, listing the Preference's categories in the left. Clicking on an item gives a message box saying: "The value of the magnification must be "Actual Size", "Fit Page", "Fit Width", "Fit Visible", "Automatic", or a value between 8,33% and 6400%." Noting else happens. -- 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 20

[Bug 17120] New: Synful Orchestra: crash when run
by wine-bugs＠winehq.org July 24, 2021

July 24, 2021

http://bugs.winehq.org/show_bug.cgi?id=17120 Summary: Synful Orchestra: crash when run Product: Wine Version: 1.1.13 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntoskrnl AssignedTo: wine-bugs(a)winehq.org ReportedBy: amranello(a)gmail.com Wine crash when I run Synful Orchestra in dssi-vst. Trial Synful Orchestra download http://www.synful.com/Download.htm -- 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 16671] New: Revit Architecture 2009: Installation fails with call not implemented
by wine-bugs＠winehq.org July 24, 2021

July 24, 2021

http://bugs.winehq.org/show_bug.cgi?id=16671 Summary: Revit Architecture 2009: Installation fails with call not implemented Product: Wine Version: 1.1.11 Platform: PC-x86-64 URL: http://students.autodesk.com OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: netbox(a)pi-xi.net Created an attachment (id=18299) --> (http://bugs.winehq.org/attachment.cgi?id=18299) wine output into console AutoDesk Revit Architecture 2009 installation fails. Everything works up to the part where the installer begins copying files. It manages to install .NET 2.0 and after that reports that installation failed with a "Call not implemented" -error. The produced log by the installer is very vague. This bug is an exact replica of installation failure with Revit Architecture 2008. -- 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

[Bug 17161] New: Provide lodctr.exe tool to prevent misleading process spawn failure console messages (.NET installers)
by wine-bugs＠winehq.org July 24, 2021

July 24, 2021

http://bugs.winehq.org/show_bug.cgi?id=17161 Summary: Provide lodctr.exe tool to prevent misleading process spawn failure console messages (.NET installers) Product: Wine Version: 1.1.13 Platform: Other URL: http://www.microsoft.com/downloads/details.aspx?FamilyID =262d25e3-f589-4842-8157-034d1e7cf3a3 OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, a minor nuisance that can be easily fixed... I had to add notes to .NET Framework appdb entries because people wrote about messages which looked like install errors to them. --- snip --- wine: could not load L"C:\\windows\\system32\\lodctr.exe": Module not found --- snip --- Such failures are in fact harmless, not relevant to overall installer status. "lodctr.exe" is a simple command line executable for loading performance data into registry. It is often called from .NET Framework v1.x, 2.x, 3.x installers. MSDN info: http://technet.microsoft.com/en-us/library/bb490926.aspx http://msdn.microsoft.com/en-us/library/aa934371.aspx --- quote --- The loading function of lodctr, LoadPerfCounterTextStrings, is declared in Loadperf.h and exported from Loadperf.dll. You can call this function directly from your install program. The following example shows the syntax for this function. LONG LoadPerfCounterTextStrings( LPSTR lpCommandLine, BOOL bQuietModeArg ); The lpCommandLine parameter is the name of your .ini file. The bQuietModeArg parameter is a Boolean value that specifies whether to display output during the loading of the text strings for the counter. --- quote --- MSDN note suggests that this command line tool is only a thin wrapper which simply calls LoadPerfCounterTextStrings() as workhorse, passing/forwarding the command line as-is. It should be easy to add this tool - even with LoadPerfCounterTextStringsA/W being stubs - to silence installers which try to spawn it. Typical installer logs: --- snip --- 1: 0 2: C:\windows\system32\lodctr.exe C:\windows\Microsoft.NET\Framework\v2.0.50727\_Networkingperfcounters.ini;18;C:\windows\system32\ 3: 4: 5: 6: 7: 8: 9: 10: Action 21:27:31: RunProcess. Installing Performance Counters for ".NET CLR Networking" ... --- snip --- --- snip --- ... 1: 0 2: C:\windows\system32\lodctr.exe "C:\windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\_TransactionBridgePerfCounters.ini";dummy;C:\windows\system32\ 3: 4: 5: 6: 7: 8: 9: 10: 1: C:\windows\system32\lodctr.exe "C:\windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\_TransactionBridgePerfCounters.ini" 2: 1: 0 2: C:\windows\system32\lodctr.exe "C:\windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\_TransactionBridgePerfCounters.ini";dummy;C:\windows\system32\ 3: 4: 5: 6: 7: 8: 9: 10: 1: 0 2: C:\windows\system32\lodctr.exe "C:\windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\_TransactionBridgePerfCounters.ini";dummy;C:\windows\system32\ 3: 4: 5: 6: 7: 8: 9: 10: ... --- snip --- 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

[Bug 16956] New: Lexware: Installation of .Net 2.0 SP 1 fails
by wine-bugs＠winehq.org July 24, 2021

July 24, 2021

http://bugs.winehq.org/show_bug.cgi?id=16956 Summary: Lexware: Installation of .Net 2.0 SP 1 fails Product: Wine Version: 1.1.11 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: koesterreich(a)gmx.net Created an attachment (id=18728) --> (http://bugs.winehq.org/attachment.cgi?id=18728) The error-message I am trying to install Lexware financial office Pro 2009 [1] I installed some stuff via winetricks-20081223: winetricks msxml3 jet40 mdac28 dotnet20 winxp The installation fails with "An error occured during the installation of the component Microsoft .Net Framework 2.0 - Service Pack 1. Errorcode: 1603 Installation of 'Microsoft .Net Framework 2.0 - Service Pack 1' failed. The setup will be cancelled." (Translated from German,, see appended Screenshot) [1] Lexware in AppDB: http://appdb.winehq.org/objectManager.php?sClass=application&iId=5505 -- 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 69

[Bug 10376] New: recent winsock SO_REUSEADDR patch reveals parameter handling problem in WS_setsockopt
by wine-bugs＠winehq.org July 24, 2021

July 24, 2021

http://bugs.winehq.org/show_bug.cgi?id=10376 Summary: recent winsock SO_REUSEADDR patch reveals parameter handling problem in WS_setsockopt Product: Wine Version: CVS/GIT Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wine-net AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, seems recent winsock SO_REUSEADDR patch --- snip --- URL: http://source.winehq.org/git/wine.git/?a=commit;h=58b030c270e68c4e130a7decb… Author: Kai Blin <kai.blin <at> gmail.com> Date: Sat Nov 3 08:45:12 2007 +0100 ws2_32: Map SO_REUSEADDR. BSD socket SO_REUSEADDR is not a complete match, but features like "allow binding to a port immediately after closing it" seem to be compatible. --- snip --- triggers a code path in WS_setsockopt() which leads to crash. The cause is an application bug. EvenBalance PunkBuster "PnkBstrA" service which creates local communication sockets accidentally passes the value instead of value address to WS_setsockopt(). The services can be installed and tested with their "pbsvc.exe" tool from http://www.evenbalance.com/downloads/pbsvc/pbsvc.exe --- snip --- .. 0015:trace:winsock:WS_setsockopt socket: 005c, level 0xffff, name 0x4, ptr 0x1, len 1 0015:trace:seh:raise_exception code=c0000005 flags=0 addr=0x76587df5 0015:trace:seh:raise_exception info[0]=00000000 0015:trace:seh:raise_exception info[1]=00000001 0015:trace:seh:raise_exception eax=00000001 ebx=7658e11c ecx=00000002 edx=00000004 esi=0000ffff edi=00000001 0015:trace:seh:raise_exception ebp=617c57a4 esp=617c574c cs=0073 ds=007b es=007b fs=0033 gs=003b flags=00210293 0015:trace:seh:call_stack_handlers calling handler at 0x7bc38810 code=c0000005 flags=0 --- snip --- Their source code snippet probably looks like this: --- snip --- if (setsockopt( sock, .., ..., (char*)value, value_len) != SOCKET_ERROR) --- snip --- Instead of this: --- snip --- if (setsockopt( sock, .., ..., (char*)&value, value_len) != SOCKET_ERROR) --- snip --- Micro$oft "fixes" such crappy^H^H^H^H^H^Hbuggy applications by using SEH to catch invalid pointer dereferencing. If you execute a hand-crafted WS_setsockopt() test case with invalid pointer value in Windows you will see something like this: --- snip --- First-chance exception at 0x719b5280 (mswsock.dll) in test.exe: 0xC0000005: Access violation reading location 0x00000001. --- snip --- Returned last error is WSAEFAULT (bad pointer value/address supplied). Solution: either wrap the whole function within structured exception handler (SEH) or use IsBadReadPtr() on passed pointer and return WSAEFAULT if fishy. Regards -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 9

[Bug 12954] New: Autodesk Design Review - Not Installing
by wine-bugs＠winehq.org July 24, 2021

July 24, 2021

http://bugs.winehq.org/show_bug.cgi?id=12954 Summary: Autodesk Design Review - Not Installing Product: Wine Version: 0.9.59. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: chris(a)ncode.com.au Created an attachment (id=12700) --> (http://bugs.winehq.org/attachment.cgi?id=12700) Wine command line output This product is an industry standard for communication of CAD designs. It is also freeware from Adobe and can be downloaded from here if needed for debugging: http://download.autodesk.com/esd/designreview/SetupDesignReview2009.exe It does not install. After starting and all the installation questions have been answered, the installer crashes (see output in attached 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.

2 16

[Bug 12999] New: 3d studio MAX 9 trial installer crash when starting up RaySat service?
by wine-bugs＠winehq.org July 24, 2021

July 24, 2021

http://bugs.winehq.org/show_bug.cgi?id=12999 Summary: 3d studio MAX 9 trial installer crash when starting up RaySat service? Product: Wine Version: CVS/GIT Platform: Other URL: http://www.soft32.com/download_81704.html OS/Version: other Status: NEW Keywords: download, Installer Severity: normal Priority: P2 Component: advapi32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com This seems to be the next problem after bug 12597: rm -rf .wine sh winetricks -q corefonts dotnet20 cc580 vcrun2003 vcrun6 wsh56 wine 3dsmax9Trial.exe cd .wine/drive_c/3dsmax9Trial/ wine Setup.exe aborts for me near the very end, saying err:msi:ITERATE_StartService Failed to start service L"mi-raysat_3dsmax9_32" err:msi:ITERATE_Actions Execution halted, action L"InstallFinalize" returned 1627 (even if you uncheck the "start raysat service" checkbox in the installer). After that, starting wine, even with a bogus command, complains similarly: $ wine-git/wine xyzzy ... fixme:advapi:RegisterEventSourceA ((null),"RaySat_3dsmax9_32 Server"): stub ... err:eventlog:ReportEventW L"(1458) RegisterServiceCtrlHandler: Service does not exist (0x424)" It seems that raysat_3dsmax9_32server.exe starts up, tries to do trace:service:OpenServiceW 0x119d98 L"RaySat_3dsmax9_32Server" 32768 which fails, presumably because the service isn't up yet? (Why isn't it doing CreateService? Perhaps it's probing to make sure it's not already started up once. But if that's so, why does it just exit without creating the service?) -- 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 12597] New: 3d studio MAX 9 trial installer crash
by wine-bugs＠winehq.org July 24, 2021

July 24, 2021

http://bugs.winehq.org/show_bug.cgi?id=12597 Summary: 3d studio MAX 9 trial installer crash Product: Wine Version: CVS/GIT Platform: Other URL: http://3dsmaxtrial.autodesk.com/3dsmax9trial/3dsmax9Tria l.exe OS/Version: other Status: NEW Keywords: download, Installer Severity: normal Priority: P2 Component: msi AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com The trial installer gets further now, but still crashes. With today's wine from git, I did rm -rf .wine sh winetricks corefonts dotnet20 cc580 vcrun2003 wine 3dsmax9Trial.exe cd .wine/drive_c/3dsmax9Trial/ wine Setup.exe After about five minutes, it got to the dialog that asks questions; after entering your name, etc, it crashed like this: Unhandled exception: page fault on read access to 0x00000001 in 32-bit code (0xb7e5f588). Backtrace: =>1 0xb7e5f588 vsnprintfW+0x458(str=0xb43a7a, len=0x64, format=0x7ec7c700, valist=) [libs/wine/string.c:376] in libwine.so.1 (0x0033eb2c) 2 0x7ec4ec63 MSI_QueryGetRecord+0xa3(db=0x12e2f0, fmt=0x7ec7c700) [dlls/msi/msiquery.c:224] in msi (0x0033eb6c) 3 0x7ec2c33e msi_dialog_seltree_handler+0x6e(dialog=0xac8e68, control=0x3a30620, param=) [dlls/msi/dialog.c:2073] in msi (0x0033eb9c) 4 0x7ec2f09b MSIDialog_WndProc+0x1db(hwnd=0xa0042, msg=0x4e, wParam=0x0, lParam=0x33ef2c) [dlls/msi/dialog.c:3362] in msi (0x0033ecbc) ... 376 while (*striter) -- 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

[Bug 11420] New: service control manager API problem: name of named objects might differ (client vs. service process)
by wine-bugs＠winehq.org July 24, 2021

July 24, 2021

http://bugs.winehq.org/show_bug.cgi?id=11420 Summary: service control manager API problem: name of named objects might differ (client vs. service process) Product: Wine Version: 0.9.54. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: advapi32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Created an attachment (id=10552) --> (http://bugs.winehq.org/attachment.cgi?id=10552) patch which fixes client vs. service SCM API when using named objects Hello, there seems to be a misconception in usage of names for named objects in service control manager API. Some people might have experienced such situation: wine hangs for several seconds on startup (when starting services). I usually disabled autostart type services (except for builtin ones) and the problems went away. Lately while fixing Microsoft Visual Studio .NET installers (2002/2003/2005) this problem became more and more annoying because the installers and VS.NET depend on some services, namely "debug manager" (service has to be running). Consider the following snippet with "service_get_event_handle" trace message added by me to highlight the problem: 0x9: client (net.exe) 0x11: service process (mdm.exe) 0x12: dispatcher thread --- snip trace --- .. 0009:trace:advapi:OpenSCManagerW ((null),(null),0x000f003f) 0009:trace:advapi:sc_handle_alloc sc_handle type=0 -> 0x121450 0009:trace:advapi:OpenSCManagerW returning 0x121450 (access : 0x000f003f) 0009:trace:advapi:OpenServiceA 0x121450 "mdm" 983103 0009:trace:advapi:OpenServiceW 0x121450 L"mdm" 983103 0009:trace:advapi:sc_handle_alloc sc_handle type=1 -> 0x121488 0009:trace:advapi:OpenServiceW returning 0x121488 0009:trace:advapi:GetServiceDisplayNameA 0x121450 "mdm" 0x34ee48 0x34fe48 0009:trace:advapi:GetServiceDisplayNameW 0x121450 L"mdm" 0x1214b8 0x34ee08 The Machine Debug Manager service is starting. 0009:trace:advapi:StartServiceA (0x121488,0,(nil)) 0009:trace:advapi:StartServiceW 0x121488 0 (nil) 0009:trace:advapi:LockServiceDatabase 0x121450 0009:trace:advapi:LockServiceDatabase returning 0x3c 0009:trace:advapi:service_start_process service_get_event_handle(L"mdm"): 0x40 0011:trace:advapi:LookupPrivilegeValueW L"",L"SeDebugPrivilege",0x34fc80 0011:trace:advapi:LookupPrivilegeValueW L"" -> 00000000-00000014 0011:trace:advapi:AdjustTokenPrivileges 0011:trace:advapi:StartServiceCtrlDispatcherA 0x34fc9c 0011:trace:advapi:service_run_threads Starting 1 pipe listener threads. Services running as process 16 0012:trace:advapi:service_control_dispatcher 0x121ea8 L"Machine Debug Manager" 0012:trace:advapi:service_control_dispatcher service_get_event_handle(L"Machine Debug Manager"): 0x48 0009:trace:advapi:UnlockServiceDatabase 0x3c 0009:trace:advapi:StartServiceW returning 0 The Machine Debug Manager service failed to start. 0009:trace:advapi:CloseServiceHandle 0x121488 0009:trace:advapi:sc_handle_destroy_service destroying service 0x121488 0009:trace:advapi:CloseServiceHandle 0x121450 0009:trace:advapi:sc_handle_destroy_manager destroying SC Manager 0x121450 000d:trace:advapi:service_run_threads last user process exited, shutting down 0011:trace:advapi:service_run_threads last user process exited, shutting down --- snip trace --- When a service is started, named objects are created to internally communicate data/events from the service process (dispatcher) to client side SCM API and vice versa. Unfortunately there exist service proccesses which pass service names to dispatcher table (StartServiceCtrlDispatcher) not matching the service name on the client side (registry "Services" key). --- snip dlls/advapi32/service.c --- static DWORD WINAPI service_control_dispatcher(LPVOID arg) { service_data *service = arg; LPWSTR name; HANDLE pipe, event; TRACE("%p %s\n", service, debugstr_w(service->name)); /* create a pipe to talk to the rest of the world with */ name = service_get_pipe_name(service->name); <--------- *problem*! pipe = CreateNamedPipeW(name, PIPE_ACCESS_DUPLEX, PIPE_TYPE_BYTE|PIPE_WAIT, 1, 256, 256, 10000, NULL ); if (pipe==INVALID_HANDLE_VALUE) ERR("failed to create pipe for %s, error = %d\n", debugstr_w(service->name), GetLastError()); HeapFree(GetProcessHeap(), 0, name); /* let the process who started us know we've tried to create a pipe */ event = service_get_event_handle(service->name); <--------- *problem*! SetEvent(event); CloseHandle(event); .. --- snip dlls/advapi32/service.c --- As result, different named objects are created and signaled so the client side can't communicate with the service side using named pipe and events. This leads to infamous timeout problem (30 sec) and service startup failing. In case of Microsoft Debug Manager the service is called "mdm" (registry). The service process itself passes "Microsoft Debug Manager" as name to dispatch table (see first trace). Problem: how can both sides communicate a "common" name for named objects? The service dispatcher part on the service side has only dispatch table data available which doesn't help much. I thought about this problem and found a feasible solution ... well call it "hack" whatever. If the client side API passes the service name in one of the process startup parameter members before process creation, the service process' dispatcher routine is able to access this data and create the named objects used for communication. I (ab)used startupinfo "title" member because only wine itself make exclusive use of most service process startup parameters. If not considered safe, use reserved/undoc fields... With that patch applied the services in question start fine and can be controlled using "net" commands. No more hangs ;-) 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 22