May 2014 - Wine-bugs - list.winehq.org

[Bug 34998] New: 11 button mouse not detected in Wow
by wine-bugs＠winehq.org 26 Nov '23

26 Nov '23

http://bugs.winehq.org/show_bug.cgi?id=34998 Bug #: 34998 Summary: 11 button mouse not detected in Wow Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: info(a)nuteknik.com Classification: Unclassified I am running wine 1.7.6 on Ubuntu 13.10. I have a Razer Ochori 2013 mouse whose mouse buttons are not all detected while running wow 5.4. The mouse has four side buttons, two on the left, two on the right. Both buttons on the right side are not detected in wow. xev receives Buttonpress events for those two buttons, as 10 and 11. note: xev receives both left side buttons as 8 and 9. And curiously...I have never been able find buttons 6 or 7 on this mouse. The mouse wheel does not tilt right or left... I posted this issue in the forums and was suggested to open a bug. Thanks for your help. -- 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 3

[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 34720] New: Resident Evil 3: in the game launcher fonts not rendered correctly
by wine-bugs＠winehq.org 25 Nov '23

25 Nov '23

http://bugs.winehq.org/show_bug.cgi?id=34720 Bug #: 34720 Summary: Resident Evil 3: in the game launcher fonts not rendered correctly Product: Wine Version: 1.7.4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: winebugs140(a)gmail.com Classification: Unclassified Created attachment 46293 --> http://bugs.winehq.org/attachment.cgi?id=46293 RE3 Trace +font You run the launcher using ResidentEvil3_menu.exe. I don't get anything in the log. I've created a trace +font. The problem can be reproduced in the demo (check out the link). Tested with: Windows Vista (without Wine), GeForce 9600M GS--the program works fine here Ubuntu 13.04, GeForce 9600M GS (NVIDIA driver 313) Mac OS X 10.7.5, ATI HD 2600 Pro, Mac Driver/X11 -- 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 34197] New: Rootmagic 6 Invalid operation GDI+ (Code 1)
by wine-bugs＠winehq.org 24 Nov '23

24 Nov '23

http://bugs.winehq.org/show_bug.cgi?id=34197 Bug #: 34197 Summary: Rootmagic 6 Invalid operation GDI+ (Code 1) Product: Wine Version: unspecified Platform: x86 OS/Version: Windows Status: UNCONFIRMED Severity: major Priority: P2 Component: gdi32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: ivebeeneverywheremate(a)gmail.com Classification: Unclassified I have tried to open Rootsmagic 6 on Linux Mint 13 using Wine 1.4. A message dialog box appears with a message "Invalid operation in GDI+ (Code:1)". There is no issue with Wine opening Rootsmagic 4. -- 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 10

[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

[Bug 35333] New: Text underline problem using GM_ADVANCED graphics mode and dc rotation
by wine-bugs＠winehq.org 22 Nov '23

22 Nov '23

http://bugs.winehq.org/show_bug.cgi?id=35333 Bug ID: 35333 Summary: Text underline problem using GM_ADVANCED graphics mode and dc rotation Product: Wine Version: 1.7.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: ralf.habacker(a)freenet.de Classification: Unclassified Created attachment 47126 --> http://bugs.winehq.org/attachment.cgi?id=47126 wine screenshot with underlined text and TA_BASELINE text align (error) Underlined text painted with TextOut() is not been drawn correctly in GM_ADVANCED graphicsmode. -- 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 33664] New: Can't paste from clipboard in Miranda
by wine-bugs＠winehq.org 22 Nov '23

22 Nov '23

http://bugs.winehq.org/show_bug.cgi?id=33664 Bug #: 33664 Summary: Can't paste from clipboard in Miranda Product: Wine Version: 1.5.31 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: 1and2(a)gmx.at Classification: Unclassified Created attachment 44563 --> http://bugs.winehq.org/attachment.cgi?id=44563 Terminal log I cannot paste text from the clipboard in a chat window in Miranda 0.10.12. OS: openSuse 12.3 KDE Terminal log 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 5

[Bug 28659] New: rpcrt4/server test crashes on 32-bit FreeBSD9
by wine-bugs＠winehq.org 16 Nov '23

16 Nov '23

http://bugs.winehq.org/show_bug.cgi?id=28659 Bug #: 28659 Summary: rpcrt4/server test crashes on 32-bit FreeBSD9 Product: Wine Version: 1.3.30 Platform: x86 OS/Version: FreeBSD Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: rpc AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Classification: Unclassified Created attachment 36831 --> http://bugs.winehq.org/attachment.cgi?id=36831 backtrace The rpcrt4/rpc test fails as well, but that may be related to missing ntlm_auth (which I haven't found how to satisfy on FreeBSD). The server test shows that same error, but also crashes, so something nastier is going on. Backtrace 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 9

[Bug 22904] New: Register URL protocol handlers under Linux
by wine-bugs＠winehq.org 15 Nov '23

15 Nov '23

http://bugs.winehq.org/show_bug.cgi?id=22904 Summary: Register URL protocol handlers under Linux Product: Wine Version: unspecified Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: kempe.marcus(a)gmail.com winemenubuilder is able to automatically register file type associations and build menus under Linux, when triggered by an application under wine. It would be great if the same thing were true for protocol handlers, so that these would become registered in much the same way as when using gconftool in gnome: gconftool -s /desktop/gnome/url-handlers/spotify/command 'wine c:\\spotify\\spotify.exe %s' --type String gconftool-2 -s /desktop/gnome/url-handlers/spotify/enabled --type Boolean true Would this be possible, hard, or maybe not a good idea? -- 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 20474] New: Wine can't be built with GCC in C99 mode
by wine-bugs＠winehq.org 14 Nov '23

14 Nov '23

http://bugs.winehq.org/show_bug.cgi?id=20474 Summary: Wine can't be built with GCC in C99 mode Product: Wine Version: unspecified Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: build-env AssignedTo: wine-bugs(a)winehq.org ReportedBy: yann(a)droneaud.fr For multiple reason, wine can't be built by GCC in C99 mode ( --std=c99 ). In particular, wine rely on GCC behavor regarding to extern inline. It produces errors regarding asm construct conflicting with extern inline symbols. It produces errors with multiple defination of inline function in object files. According to this, it seems that wine is not compatible with C99, but rely a lot on GCC specific behavor. See also bug #20306 -- 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 26