July 2011 - Wine-bugs - list.winehq.org

[Bug 27916] New: Ferro CCTV: Fails to start
by wine-bugs＠winehq.org 15 Dec '23

15 Dec '23

http://bugs.winehq.org/show_bug.cgi?id=27916 Summary: Ferro CCTV: Fails to start Product: Wine Version: 1.3.25 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: lukasz.wojnilowicz(a)gmail.com Created an attachment (id=35713) --> (http://bugs.winehq.org/attachment.cgi?id=35713) Error message Steps to reproduce: 1) remove ~/.wine 2) winetricks wmp9 3) install Ferro CCTV 4) wine FerroCCTV.exe Behaviour: Error message (see attachment). Expected behaviour: No error message. -- 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 12

[Bug 21550] New: Winedbg's disassembler doesn't support SSE2 instructions
by wine-bugs＠winehq.org 15 Dec '23

15 Dec '23

http://bugs.winehq.org/show_bug.cgi?id=21550 Summary: Winedbg's disassembler doesn't support SSE2 instructions Product: Wine Version: 1.1.37 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winedbg AssignedTo: wine-bugs(a)winehq.org ReportedBy: b7.10110111(a)gmail.com Winedbg doesn't support SSE2 instructions while gdb does. -- 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 21790] New: 3D Rad demo "BeltBall" can't use its bundled mfc80u.dll?
by wine-bugs＠winehq.org 14 Dec '23

14 Dec '23

http://bugs.winehq.org/show_bug.cgi?id=21790 Summary: 3D Rad demo "BeltBall" can't use its bundled mfc80u.dll? Product: Wine Version: 1.1.38 Platform: x86 URL: http://www.3drad.com/games/BeltBall%20v102.exe OS/Version: Linux Status: UNCONFIRMED Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com The smallest demo from http://www.3drad.com/free-pc-games.php is the 8MB http://www.3drad.com/games/BeltBall%20v102.exe, sha1sum d8827274480b0391ad200478b2ebe26a2658166d BeltBall v102.exe It installs fine, but when you start it, it complains fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT" (8.0.50727.762) and puts up a dialog saying "The dynamic link library 'MFC80U.DLL' could not be found" even though it's installed in ./3D Rad Games/BeltBall v102/Microsoft.VC80.MFC/mfc80u.dll Perhaps the installer forgot to set an app path or a manifest or something? winetricks vc2005 works around the problem. The game installs and runs fine on Vista; I guess we need to try it on an old XP box that doesn't have vc2005 runtimes already and see if it works there to confirm this bug. (I checked on Vista, and there's no entry for the app in HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths, for what it's worth. And there doesn't seem to be a manifest file next to the .exe.) -- 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 18

[Bug 16957] New: CreateProcess handles are inherited even when bInheritHandles=FALSE
by wine-bugs＠winehq.org 12 Dec '23

12 Dec '23

http://bugs.winehq.org/show_bug.cgi?id=16957 Summary: CreateProcess handles are inherited even when bInheritHandles=FALSE Product: Wine Version: 1.1.2 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: ben(a)salilab.org Created an attachment (id=18729) --> (http://bugs.winehq.org/attachment.cgi?id=18729) test.c The attached file uses CreateProcess to create a subprocess (gzip in this case) with redirected standard output. In order for this to work properly, the output handle created in this code must be inherited by the subprocess - thus the bInheritHandles argument to CreateProcess must be TRUE. And indeed if this program is compiled to test-true.exe, a simple text file 'test.in' and the gzip binary are placed in the same directory, and then test-true.exe is run, it successfully produces the output test.gz. If the TRUE argument is switched to FALSE and the file is compiled again to test-false.exe, when the program is run in the same way on a 'real' Windows sytem (32 bit Vista Business in this case) the following is output: gzip: stdout: Bad file descriptor This is also fine and expected, since the output file handle was not passed to gzip. *However* if the same test-false.exe program is run with Wine (the Fedora 10 wine-core-1.1.12-1.fc10.i386 package in this case) it runs in just the same way as test-true.exe, generating the test.gz output. This suggests to me that the bInheritHandles argument is ignored by Wine. As stated, this is a minor bug but it would be nice if Wine behaved the same way as Windows here. (In our case we discovered this problem after we tested our program successfully under Wine, but then had it fail on a real Windows system.) I am not familiar with the code, but hopefully it should be straightforward enough to provide the subprocess with invalid handles if bInheritHandles=FALSE? -- 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 13778] New: Date and Time display
by wine-bugs＠winehq.org 11 Dec '23

11 Dec '23

http://bugs.winehq.org/show_bug.cgi?id=13778 Summary: Date and Time display Product: Wine Version: unspecified Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: rx9tx(a)qrz.ru Created an attachment (id=13813) --> (http://bugs.winehq.org/attachment.cgi?id=13813) wine window The problem is that in a Windows application running in Wine the date and time displayed as digit like 39591.6425810185 instead of May-23-2008, 15:25, see pictures http://rx9tx.qrz.ru/wine.jpg and http://rx9tx.qrz.ru/windows.jpg . Same about the frequency value 0000000000028.012100 in mHz (28.0121 mhz) is shown like 298112000.0. I dont know what kind of database is used, but it has the .isd extension, also .isf, .ism, .isl files are present. Here's the excerption from the database with the data shown on the pics: http://rx9tx.qrz.ru/log.txt -- 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 25

[Bug 23676] New: Arcanum essentially unusable due to graphics errors
by wine-bugs＠winehq.org 10 Dec '23

10 Dec '23

http://bugs.winehq.org/show_bug.cgi?id=23676 Summary: Arcanum essentially unusable due to graphics errors Product: Wine Version: 1.2 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: alex.richardson(a)gmx.de When playing Arcanum, the issue shown by the screenshot happens as soon as you attempt to scroll the view. It seems that it only happens when scrolling to the top, left right and down seem to be fine. I know this did not happen with older versions of Wine ~1 year ago. For testing purposes there is a demo of the game available here: http://www.terra-arcanum.com/downloads/ If you need any other information please tell me, I'm quite new to reporting bugs in Wine. -- 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 32

[Bug 15399] New: Colin Mcrae Rally 1.0 shows Graphical Glitches within menus and crashes before loading any track.
by wine-bugs＠winehq.org 09 Dec '23

09 Dec '23

http://bugs.winehq.org/show_bug.cgi?id=15399 Summary: Colin Mcrae Rally 1.0 shows Graphical Glitches within menus and crashes before loading any track. Product: Wine Version: 1.1.5 Platform: PC URL: http://appdb.winehq.org/objectManager.php?sClass=version &iId=4216 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: Salz85(a)gmail.com Created an attachment (id=16253) --> (http://bugs.winehq.org/attachment.cgi?id=16253) game run without any argument. After Setting the compatibility to windows 95/98, installing direct media end the indeo codec, Colin Mcrae rally start but deos not show any menu correctly, except for fixed bitmap like the Copyright screen (see the screenshot ). Even if I try to navigate the menu and get to load the track, wine crashes. See the crash.log for the output when the game crashes wine, and menu.log for a debug with "relay,+d3d7,+ddraw" active (reaching the menu, navigating it and then exiting the application). -- 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 49

[Bug 13340] New: dicom image viewer aborts because IMultiLanguage2_GetCharsetInfo doesn' t like "ISO8859-1"
by wine-bugs＠winehq.org 08 Dec '23

08 Dec '23

http://bugs.winehq.org/show_bug.cgi?id=13340 Summary: dicom image viewer aborts because IMultiLanguage2_GetCharsetInfo doesn't like "ISO8859-1" Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com I had an MRI recently, and got a copy on cd-rom. The viewer app crashed quickly on Wine. trace:mlang:fnIMultiLanguage2_GetCharsetInfo 0x19dce8 L"ISO8859-1" 0x32f5b4 ... 0009:Call KERNEL32.lstrcmpiW(01031d58 L"ISO8859-1",0032f524 L"iso-8859-1") ret=7d52ed97 ... 0009:Call oleaut32.SysAllocString(01577b00 L"System does not support the specified encoding.\r\n") ret=69bf1378 ... wine: Unhandled exception 0x80000003 at address 0x7b83d7c1 (thread 0009), starting debugger... Backtrace: =>1 0x7b83d7c1 DebugBreak+0x3() [wine-git/include/winternl.h:1828] in kernel32 2 0x7bc54140 call_entry_point+0x20() in ntdll 3 0x7bc55118 relay_call_from_32+0x1a1(descr=0x7b8b416c, idx=?, stack=0x32f8fc) [wine-git/dlls/ntdll/relay.c:372] in ntdll 4 0x7b8273c1 in kernel32 (+0x73c1) 5 0x69b20265 in msxml4 (+0x10265) 6 0x004b8a53 in efilmlt (+0xb8a53) Looks like Windows is more forgiving about how callers identify charsets. We were only accepting names like "iso-8859-1", but Windows accepts "ISO8859-1". I have test that passes on WinXP, and a patch that fixes both the test and the real app. Will send to wine-patches. -- 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 27

[Bug 25740] New: setupapi: registry values missing %token% replacement (dynamic strings, updspapi) (Windows PowerShell 2.0)
by wine-bugs＠winehq.org 25 Nov '23

25 Nov '23

http://bugs.winehq.org/show_bug.cgi?id=25740 Summary: setupapi: registry values missing %token% replacement (dynamic strings, updspapi) (Windows PowerShell 2.0) Product: Wine Version: 1.3.11 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: setupapi AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, trying to start the Windows PowerShell Integrated Scripting Environment (ISE) after installing Windows PowerShell 2.0 fails. --- snip --- $ wine powershell_ise.exe ... Unhandled Exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ArgumentNullException: Value cannot be null. Parameter name: window at System.Windows.MessageBox.Show(Window owner, String messageBoxText, String caption, MessageBoxButton button, MessageBoxImage icon, MessageBoxResult defaultResult) at Microsoft.Windows.PowerShell.Gui.Internal.Program.Initialize() --- End of inner exception stack trace --- at Microsoft.Windows.PowerShell.GuiExe.Internal.GPowerShell.Main(String[] args) wine: Unhandled exception 0xe0434f4d at address 0x7b838ce2 (thread 0009), starting debugger... --- snip --- The real cause is the inability to locate/load the assembly "CompiledComposition.Microsoft.PowerShell.GPowerShell.dll" leading to later crash. The path to assembly is resolved using registry: --- snip --- 0026:Call advapi32.RegOpenKeyExW(80000002,009bf828 L"Software\\Microsoft\\PowerShell\\1\\PowerShellEngine",00000000,00020019,0032ece8) ret=0036a6a7 0026:Ret advapi32.RegOpenKeyExW() retval=00000000 ret=0036a6a7 ... 0026:Call advapi32.RegQueryValueExW(00000180,009bf770 L"ApplicationBase",00000000,0032ed18,00000000,0032ed1c) ret=0036a7aa 0026:Ret advapi32.RegQueryValueExW() retval=00000000 ret=0036a7aa ... 0026:Call KERNEL32.GetFullPathNameW(0032ea1c L"%SystemRoot%\\system32\\WindowsPowerShell\\v1.0\\CompiledComposition.Microsoft.PowerShell.GPowerShell.dll",00000105,0032e810,00000000) ret=0036a1c3 0026:Ret KERNEL32.GetFullPathNameW() retval=00000073 ret=0036a1c3 --- snip --- Registry export: --- snip --- REGEDIT4 [HKEY_LOCAL_MACHINE\Software\Microsoft\PowerShell\1\PowerShellEngine] "ApplicationBase"="%SystemRoot%\\system32\\WindowsPowerShell\\v1.0" "ConsoleHostAssemblyName"="Microsoft.PowerShell.ConsoleHost,Version=1.0.0.0,Culture=neutral,PublicKeyToken=31bf3856ad364e35,ProcessorArchitecture=msil" "ConsoleHostModuleName"="\"%SystemRoot%\\system32\\WindowsPowerShell\\v1.0\\Microsoft.PowerShell.ConsoleHost.dll\"" "PowerShellVersion"="2.0" "PSCompatibleVersion"="1.0,2.0" "RuntimeVersion"="v2.0.50727" --- snip --- The path contains "%SystemRoot%" token which should have been deformated at _install_ time (.NET app code directly takes the path string). >From the setupapi/updspapi based installer's update.inf: --- snip --- ... [ProductInstall.GlobalRegistryChanges.Install] AddReg=PowerShell.Add.Reg DelReg=PowerShell.Del.Reg ... [PowerShell.Add.Reg] HKLM,SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine,"ApplicationBase",0x00000000,%SystemRoot%\system32\WindowsPowerShell\v1.0 HKLM,SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine,"ConsoleHostAssemblyName",0x00000000,"Microsoft.PowerShell.ConsoleHost,Version=1.0.0.0,Culture=neutral,PublicKeyToken=31bf3856ad364e35,ProcessorArchitecture=msil" HKLM,SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine,"ConsoleHostModuleName",0x00000000,"""%SystemRoot%\system32\WindowsPowerShell\v1.0\Microsoft.PowerShell.ConsoleHost.dll""" HKLM,SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine,"PowerShellVersion",0x00000000,"2.0" HKLM,SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine,"PSCompatibleVersion",0x00000000,"1.0,2.0" HKLM,SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine,"RuntimeVersion",0x00000000,"v2.0.50727" HKLM,SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell,"Path",0x00000000,%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe --- snip --- There are also %token% strings which are _not_ to be replaced, hence the double % quoting: --- snip --- HKLM, SYSTEM\CurrentControlSet\Services\WinRM\Parameters, ServiceDll, 0x00020000, "%%SystemRoot%%\system32\WsmSvc.dll" --- snip --- MSDN says about the "INF AddReg Directive": http://msdn.microsoft.com/en-us/library/ff546320.aspx --- snip --- [add-registry-section] reg-root, [subkey],[value-entry-name],[flags],[value] ... value ... The expression of such a value depends on the registry type specified for the flag, as follows: * A registry string-type value can be expressed either as a "quoted string" or as a %strkey% token defined in a Strings section of the INF file. Such an INF-specified value does not have to include a NULL terminator at the end of each string. ... --- snip --- There is a "dynamic strings" directive present in .inf file: --- snip --- [DynamicStrings] SystemRoot=InstallPathEnvVar,SystemRoot --- snip --- This part is processed by installer, updspapi.UpdSpSetDynamicStringA gets called: --- snip --- 0023:Call setupapi.SetupFindFirstLineA(00144c68,01025d10 "DynamicStrings",00000000,0033bb94) ret=010758be 0023:Call ntdll.RtlCreateUnicodeStringFromAsciiz(0033baa8,01025d10 "DynamicStrings") ret=688f6bbf 0023:Ret ntdll.RtlCreateUnicodeStringFromAsciiz() retval=00000001 ret=688f6bbf 0023:trace:setupapi:SetupFindFirstLineW (0x144c68,L"DynamicStrings",(null)): returning 63/0 .. 0023:Call msvcrt._vsnprintf(0033b34b,000007f7,01025830 "ProcessDynamicStrings: InstallPathEnvVar for %s returned %s",0033bb80) ret=010706ea ... 0023:Call updspapi.UpdSpSetDynamicStringA(00144c68,010f4940 "SystemRoot",001b7108 "C:\\windows") ret=01075d51 0023:fixme:updspapi:UpdSpSetDynamicStringA 0x144c68 "SystemRoot" "C:\\windows" 0023:Ret updspapi.UpdSpSetDynamicStringA() retval=00000001 ret=01075d51 ... 0023:Call msvcrt._vsnprintf(0033b34b,000007f7,01025754 "ProcessDynamicStrings: all %%%s%% replaced with %s.",0033bb80) ret=010706ea --- snip --- Setupapi installer log: --- snip --- 2.734: ProcessDynamicStrings: InstallPathEnvVar for SystemRoot returned C:\windows 2.734: ProcessDynamicStrings: all %SystemRoot% replaced with C:\windows. --- snip --- At later stage, when the registry section is processed: --- snip --- 0023:trace:setupapi:SetupFindNextMatchLineW (0x144c68,L"ProductInstall.GlobalRegistryChanges.Install",L"AddReg"): returning 2 0023:trace:setupapi:SetupGetStringFieldW context 0x144c68/0x144c68/10/2 index 1 returning L"PowerShell.Add.Reg" 0023:trace:setupapi:SetupFindFirstLineW (0x144c68,L"PowerShell.Add.Reg",(null)): returning 48/0 0023:trace:setupapi:SetupGetStringFieldW context 0x144c68/0x144c68/48/0 index 1 returning L"HKLM" 0023:trace:setupapi:SetupGetStringFieldW context 0x144c68/0x144c68/48/0 index 2 returning L"SOFTWARE\\Microsoft\\PowerShell\\1\\PowerShellEngine" ... 0023:trace:setupapi:SetupGetStringFieldA context 0x144c68/0x144c68/48/0 index 4 returning "0x00000000" 0023:Call advapi32.RegCreateKeyExW(80000002,0033935c L"SOFTWARE\\Microsoft\\PowerShell\\1\\PowerShellEngine",00000000,00000000,00000000,02000000,00000000,0033b37c,00000000) ret=688ec641 0023:Ret advapi32.RegCreateKeyExW() retval=00000000 ret=688ec641 0023:trace:setupapi:registry_callback key 0x80000002 L"SOFTWARE\\Microsoft\\PowerShell\\1\\PowerShellEngine" 0023:trace:setupapi:SetupGetStringFieldW context 0x144c68/0x144c68/48/0 index 3 returning L"ApplicationBase" ... 0023:trace:setupapi:SetupGetStringFieldW context 0x144c68/0x144c68/48/0 index 5 returning L"%SystemRoot%\\system32\\WindowsPowerShell\\v1.0" 0023:trace:setupapi:do_reg_operation setting value L"ApplicationBase" to L"%SystemRoot%\\system32\\WindowsPowerShell\\v1.0" 0023:Call advapi32.RegSetValueExW(0000006c,0033935c L"ApplicationBase",00000000,00000001,0075d100,0000005a) ret=688ec5be 0023:Ret advapi32.RegSetValueExW() retval=00000000 ret=688ec5be ... 0023:Call advapi32.RegCloseKey(0000006c) ret=688ec6ce 0023:Ret advapi32.RegCloseKey() retval=00000000 ret=688ec6ce --- snip --- The string field containing %SystemRoot% token never got the replacement value. Updspapi.dll UpdSpSetDynamicStringA() is a stub and does not have any connection to setupapi, maybe this is the problem. Updspapi seems like an internal/private version of Microsofts setupapi library, distributed with installers/SP installers - not to be installed into OS. Unfortunately setting updspapi to "native", skipping Wine's builtin stub crashes the installer. BTW ... the PowerShell console/command line stuff really integrates nicely now that Wine has proper console support (wineconsole no longer needed). 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

[Bug 22596] New: PhotoScape unable to change/save files under Wine 1.1.43
by wine-bugs＠winehq.org 24 Nov '23

24 Nov '23

http://bugs.winehq.org/show_bug.cgi?id=22596 Summary: PhotoScape unable to change/save files under Wine 1.1.43 Product: Wine Version: 1.1.43 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P1 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: daquirm(a)seznam.cz CC: daquirm(a)seznam.cz Created an attachment (id=27721) --> (http://bugs.winehq.org/attachment.cgi?id=27721) LOG from the terminal OS: Ubuntu 10.04 64bit Wine 1.1.42 and 1.1.43 (tried Windows XP and Windows 7 compatibility mode) trying to run PhotoScape v3.40 Problem: PhotoScape is unable to save or edit any files/images. It looks like it's running just with read only permission. Solution: Downgrade to Wine 1.1.31 -- 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