September 2017 - Wine-Bugs - list.winehq.org

[Bug 35539] New: Proteus 8 demo fails to install
by wine-bugs＠winehq.org Oct. 26, 2021

Oct. 26, 2021

https://bugs.winehq.org/show_bug.cgi?id=35539 Bug ID: 35539 Summary: Proteus 8 demo fails to install Product: Wine Version: 1.7.11 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Classification: Unclassified Hello folks, split off from bug 34457 --- snip --- $ WINEDEBUG=+tid,+seh,+relay,+msi wine ./prodemo.exe >>log.txt 2>&1 ... 0037:trace:msi:ACTION_PerformUIAction Performing action (L"WriteEnvironmentStrings") ... 0037:trace:msi:MSI_ProcessMessage (nil) (nil) (nil) 0 100 L"Action 13:24:18: WriteEnvironmentStrings. Updating environment strings" ... 0037:trace:msi:MSI_DatabaseOpenViewW L"SELECT * FROM `Environment`" 0x33f7e8 ... 0037:trace:msi:ITERATE_WriteEnvironmentString name L"!-*LXKSERVER" value (null) ... 0037:trace:msi:MSI_ProcessMessage (nil) (nil) (nil) 0 200 L"Name: LXKSERVER, Value: , Action 0" ... 0037:trace:msi:ITERATE_WriteEnvironmentString name L"=-*LXKSERVER" value L"[KEY_SERVER]" ... 0037:trace:msi:MSI_FormatRecordW L"[KEY_SERVER]" ... 0037:trace:msi:msi_get_property property L"KEY_SERVER" not found ... 0037:trace:msi:MSI_ProcessMessage (nil) (nil) (nil) 0 200 L"Name: LXKSERVER, Value: , Action 0" ... 0037:trace:msi:MSI_ProcessMessage (nil) (nil) (nil) 0 10 L"Action ended 13:24:18: WriteEnvironmentStrings. Return value 14." ... 0037:err:msi:ITERATE_Actions Execution halted, action L"WriteEnvironmentStrings" returned 14 --- snip --- "Environment" msi table dump with ORCA: --- snip --- Environment Name Value Component_ s72 l255 L255 s72 LXKSERVER !-*LXKSERVER APPFRAME.DLL LXKSERVER_1 =-*LXKSERVER [KEY_SERVER] APPFRAME.DLL --- snip --- The first one has no value -> skipped (ok). The second one has a value and is getting deformatted ... unfortunately 'KEY_SERVER' property is not set at this point, resulting in failure. I found only one occurrence of this property 'KEY_SERVER' in msi tables: "Control" msi table: --- snip --- KeyServerDlg Edit_1 Edit 101 112 125 18 3 KEY_SERVER {260} Bitmap --- snip --- The unattended install using explicit command line property works, see: http://www.softnual.com/html/pds/network-installation.htm --- quote --- Where a server license and dongle are installed the KEY_SERVER property can be set on the command line to point to the licence key server. If set this will set the environment variable, if not set the variable will be cleared. --- quote --- If I pass the property via command line it finishes successfully: --- snip --- $ wine msiexec -i setup_demo8.1.17358.0.msi KEY_SERVER=test ... $ fixme:wshom:WshShell3_RegWrite (L"HKLM\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Environment\\LXKSERVER" {VT_BSTR: L"test"} {vt 10}): stub --- snip --- For UI install, the 'KeyServerDlg' is referenced from 'LicenseKeyTypeDlg' which is referenced from 'LicenseAgreementDlg': --- snip --- LicenseAgreementDlg Back NewDialog WelcomeDlg AI_INSTALL AND LicenseAgreementDlg_Cond 1 LicenseAgreementDlg Next NewDialog SetupTypeDlg AI_INSTALL AND LicenseAgreementDlg_Cond 3 LicenseAgreementDlg Next NewDialog LicenseKeyTypeDlgAI_INSTALL AND LicenseAgreementDlg_Cond AND LicenseKeyTypeDlg_Cond 4 LicenseAgreementDlg Next [LicenseKeyTypeDlg_Cond] 1 Family <> "Demonstration" 2 LicenseAgreementDlg Next [LicenseKeyTypeDlg_Cond] {} 1 1 LicenseAgreementDlg Cancel SpawnDialog CancelDlg 1 100 LicenseAgreementDlg PrintButton DoAction AI_PrintRtf 1 2 LicenseAgreementDlg PrintButton [AI_PRINT_RTF] LicenseAgreementDlg#AgreementText 1 1 --- snip --- 'SetupTypeDlg' is selected for 'next' button instead of 'LicenseKeyTypeDlg': --- snip --- 0037:trace:msi:msi_set_property 0x1437c0 L"LicenseAgreementDlg_Cond" L"1" -1 ... 0037:trace:msi:MSI_EvaluateConditionW 1 <- L"AI_INSTALL AND LicenseAgreementDlg_Cond" ... 0037:trace:msi:msi_dialog_send_event Sending control event L"NewDialog" L"LicenseAgreementDlg" ... 0037:trace:msi:MSI_EvaluateConditionW L"AI_INSTALL AND LicenseAgreementDlg_Cond AND LicenseKeyTypeDlg_Cond" ... 0037:trace:msi:msi_get_property returning L"1" for property L"AI_INSTALL" ... 0037:trace:msi:msi_get_property returning L"1" for property L"LicenseAgreementDlg_Cond" ... 0037:trace:msi:msi_get_property property L"LicenseKeyTypeDlg_Cond" not found ... 0037:trace:msi:MSI_EvaluateConditionW 0 <- L"AI_INSTALL AND LicenseAgreementDlg_Cond AND LicenseKeyTypeDlg_Cond" ... 0037:trace:msi:MSI_EvaluateConditionW 1 <- L"AI_INSTALL AND LicenseAgreementDlg_Cond" 0037:trace:msi:msi_dialog_send_event Sending control event L"NewDialog" L"SetupTypeDlg" --- snip --- 'LicenseKeyTypeDlg_Cond' is tied to control 'Event': --- snip --- LicenseAgreementDlg Next [LicenseKeyTypeDlg_Cond] 1 Family <> "Demonstration" 2 LicenseAgreementDlg Next [LicenseKeyTypeDlg_Cond] {} 1 1 --- snip --- The event condition: --- snip --- 0037:trace:msi:MSI_DatabaseOpenViewW L"SELECT * FROM ControlEvent WHERE `Dialog_` = 'LicenseAgreementDlg' AND `Control_` = 'Next' ORDER BY `Ordering`" 0x33f240 ... 0037:trace:msi:MSI_EvaluateConditionW L"1" ... 0037:trace:msi:COND_GetString Got identifier L"1" ... 0037:trace:msi:MSI_EvaluateConditionW 1 <- L"1" ... 0037:trace:msi:msi_set_property 0x1437c0 L"LicenseKeyTypeDlg_Cond" (null) -1 ... 0037:trace:msi:msi_get_property property L"LicenseKeyTypeDlg_Cond" not found 0037:trace:msi:MSI_DatabaseOpenViewW L"DELETE FROM `_Property` WHERE `_Property` = 'LicenseKeyTypeDlg_Cond'" 0x33f11c ... 0037:trace:msi:MSI_EvaluateConditionW L"Family <> \"Demonstration\"" ... 0037:trace:msi:COND_GetString Got identifier L"Family" ... 0037:trace:msi:msi_get_property returning (null) for property L"Family" ... 0037:trace:msi:msi_get_property returning L"Demonstration" for property L"Family" ... 0037:trace:msi:COND_GetLiteral Got literal L"Demonstration" ... 0037:trace:msi:MSI_EvaluateConditionW 0 <- L"Family <> \"Demonstration\"" ... --- snip --- 'Family' property is hard coded by default to 'Demonstration' value. Makes sense for demo app/installer. Summing it up: at first glance everything looks ok. Maybe it's another MSI client vs. server issue. $ sha1sum prodemo.exe e3409adbc80bd73a36f82890da2b7d16be2fbf51 prodemo.exe $ du -sh prodemo.exe 166M prodemo.exe $ wine --version wine-1.7.11-306-g8f289c8 Regards -- 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 36010] New: Changing font resolution on winecfg changes default main font to Tahoma
by wine-bugs＠winehq.org Oct. 26, 2021

Oct. 26, 2021

http://bugs.winehq.org/show_bug.cgi?id=36010 Bug ID: 36010 Summary: Changing font resolution on winecfg changes default main font to Tahoma Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jbopen(a)gmail.com Changing the value of font resolution under "Desktop" (winecfg) the system.reg changes the value "MS Shell Dlg" to the original "Tahoma". -- 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 32749] New: Implement atl100.dll.AtlAxDialogBoxW to show error dialogs (Visual Studio 2010 (10.0) Express Edition)
by wine-bugs＠winehq.org Oct. 26, 2021

Oct. 26, 2021

http://bugs.winehq.org/show_bug.cgi?id=32749 Bug #: 32749 Summary: Implement atl100.dll.AtlAxDialogBoxW to show error dialogs (Visual Studio 2010 (10.0) Express Edition) Product: Wine Version: 1.5.21 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: atl AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Classification: Unclassified Hello folks, continuation of bug 32564 (Visual Studio 2010 (10.0) Express Edition needs atl100.dll.AtlAxDialogBoxW). Although it's stubbed for now it might be useful to load and show the dialog resource. --- snip --- 0009:fixme:atl:AtlAxDialogBoxW (0x401f0000 #00cc 0x2008a 0x401b589f 0) --- snip --- The user doesn't know what happened in this case. 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 15

[Bug 33118] New: Adding bin.base64 attribute causes duplicate datatype attribute
by wine-bugs＠winehq.org Oct. 26, 2021

Oct. 26, 2021

http://bugs.winehq.org/show_bug.cgi?id=33118 Bug #: 33118 Summary: Adding bin.base64 attribute causes duplicate datatype attribute Product: Wine Version: 1.5.22 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: msxml3 AssignedTo: wine-bugs(a)winehq.org ReportedBy: leslie_alistair(a)hotmail.com Classification: Unclassified The following psedocode is causing duplicate xmlns to appear on a node. node->Create Attribute (_T("xmlns:dt"), _T("urn:schemas-microsoft-com:datatypes")); node->Put Data Type(_T("bin.base64")); node->Put Node TypedValue("DATA"); Do you get a node that looks like the following. <UML:TaggedValue xmlns:dt="urn:schemas-microsoft-com:datatypes" xmlns:dt="urn:schemas-microsoft-com:datatypes" dt:dt="bin.base64" >... -- 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 16666] New: wine segfaults on launch
by wine-bugs＠winehq.org Oct. 24, 2021

Oct. 24, 2021

http://bugs.winehq.org/show_bug.cgi?id=16666 Summary: wine segfaults on launch Product: Wine Version: 1.1.11 Platform: PC OS/Version: OpenBSD Status: NEW Keywords: patch, source Severity: critical Priority: P2 Component: build-env AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Created an attachment (id=18290) --> (http://bugs.winehq.org/attachment.cgi?id=18290) core dump Now for the biggest bug :-) Wine segfaults on launch of any program. Even 'wine --version' crashes. I've got this patch in place (from openbsd's port): diff --git a/loader/pthread.c b/loader/pthread.c index 4c0c892..e7f6479 100644 --- a/loader/pthread.c +++ b/loader/pthread.c @@ -96,6 +96,12 @@ static void init_thread( struct wine_pthread_thread_info *info ) /* if base is too large assume it's the top of the stack instead */ if ((char *)info->stack_base > &dummy) info->stack_base = (char *)info->stack_base - info->stack_size; +#elif defined(__OpenBSD__) + stack_t stack; + if (pthread_stackseg_np(pthread_self(), &stack) != 0) + abort (); + info->stack_base = (char *)stack.ss_sp - stack.ss_size; + info->stack_size = stack.ss_size; #else /* assume that the stack allocation is page aligned */ char dummy; @@ -163,6 +169,8 @@ static void init_current_teb( struct wine_pthread_thread_info *info ) info->pid = getpid(); #ifdef __sun info->tid = pthread_self(); /* this should return the lwp id on solaris */ +#elif defined(__OpenBSD__) + info->tid = pthread_self(); #elif defined(__APPLE__) info->tid = mach_thread_self(); #elif defined(__FreeBSD__) Though, it still segfaults without it. wine-pthread.core 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 20

[Bug 42269] New: There is no fonts in the menu S.T.A.L.K.E.R.: Shadow of Chernobyl
by wine-bugs＠winehq.org Oct. 23, 2021

Oct. 23, 2021

https://bugs.winehq.org/show_bug.cgi?id=42269 Bug ID: 42269 Summary: There is no fonts in the menu S.T.A.L.K.E.R.: Shadow of Chernobyl Product: Wine Version: 2.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: negry.mischa(a)yandex.ru Distribution: --- Created attachment 56970 --> https://bugs.winehq.org/attachment.cgi?id=56970 A screenshot of the problem When you start the game there is no fonts in the menu, same problem in Tropico 5, but in STALKER are the wine versions 1.9.17-1.9.23. And the workspace of STALKER, as seen in the screenshot is limited -- 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 30600] New: Emergency 3 crash with page fault on read access to 0x00000000 in 32-bit code (0x100ac010)
by wine-bugs＠winehq.org Oct. 22, 2021

Oct. 22, 2021

http://bugs.winehq.org/show_bug.cgi?id=30600 Bug #: 30600 Summary: Emergency 3 crash with page fault on read access to 0x00000000 in 32-bit code (0x100ac010) Product: Wine Version: 1.5.3 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: linuxcobra(a)gmx.de Classification: Unclassified Created attachment 40041 --> http://bugs.winehq.org/attachment.cgi?id=40041 Backtrace-output when i install this Game under wine, the install works, but when i will start the game, will not work. via original Windows XP / ME ( both tested) : no problems -- 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 42137] New: DirectInput needs to join both Xbox shoulder triggers into a single axis (aka half-axis problem)
by wine-bugs＠winehq.org Oct. 22, 2021

Oct. 22, 2021

https://bugs.winehq.org/show_bug.cgi?id=42137 Bug ID: 42137 Summary: DirectInput needs to join both Xbox shoulder triggers into a single axis (aka half-axis problem) Product: Wine Version: 1.6.1 Hardware: x86 OS: Linux Status: NEW Keywords: hardware Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: 00cpxxx(a)gmail.com CC: aric(a)codeweavers.com Distribution: --- When MS introduced the Xbox controller into dinput it had the idea of joining both Xbox controller shoulder triggers into a single axis. So the left trigger ranges to the negative side while the right trigger to the positive side of the same axis. Wine currently exposes the triggers are separate axes Z and rZ, this affects some games negatively because the not-pressed default values for the triggers is the lowest possible, for example if the axis ranges from -100 to +100 Wine exposes -100 to the application. The effect is that the application thinks the axis is always pressed and weird things happen, eg auto selecting Z/rZ as every button when configuring a joystick or wrongly selecting Z/rZ as rX/rY making FPS players always look up or down. I don't know if this happens only for Xbox controllers but I believe so. I'll have the chance to test with a real PS3 controller soon. If that is MS only, we need to find a way to distinguish the joysticks (VID/PID?) and merge the axes to mimic MS behavior. At the same time and in opposite direction the XInput API does not employ this hack, since XInput was made for Xbox only controllers it will properly report the values for the axes separately. -- 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 41700] New: "Install Now" and "Customize installation" buttons are invisible in Python 3.5 installer
by wine-bugs＠winehq.org Oct. 22, 2021

Oct. 22, 2021

https://bugs.winehq.org/show_bug.cgi?id=41700 Bug ID: 41700 Summary: "Install Now" and "Customize installation" buttons are invisible in Python 3.5 installer Product: Wine Version: 1.9.23 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- The "Install Now" and "Customize installation" buttons do not appear on either the regular Python 3.5 installer or the Python 3.5 web installer, not even if you hover the mouse over the buttons or press the tab key repeatedly. However, the installation continues if you click where the button should be, and the tab key appears to move focus onto and off of the buttons even though there is no visual feedback. Note that you must set the Windows version to Windows Vista or later in winecfg or the installer will only show you an error message. $ sha1sum python-3.5.2.exe 3873deb137833a724be8932e3ce659f93741c20b python-3.5.2.exe -- 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 11

[Bug 36796] New: Mozilla Firefox 13.0 crashes on startup if run in Windows Vista+ mode (D3D10CreateEffectFromMemory needs more complete Direct3D 10 DXBC parser)
by wine-bugs＠winehq.org Oct. 22, 2021

Oct. 22, 2021

https://bugs.winehq.org/show_bug.cgi?id=36796 Bug ID: 36796 Summary: Mozilla Firefox 13.0 crashes on startup if run in Windows Vista+ mode (D3D10CreateEffectFromMemory needs more complete Direct3D 10 DXBC parser) Product: Wine Version: 1.7.20 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3dx10 Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Hello folks, Henri suggested that Mozilla Firefox in Vista+ mode might be a good candidate to help implementing missing/incomplete DX10/D2D API (https://bugs.winehq.org/show_bug.cgi?id=30966#c5) Running the browser results in crash: --- snip --- $ pwd /home/focht/.wine/drive_c/Program Files/Mozilla Firefox $ wine ./firefox.exe ... fixme:win:EnumDisplayDevicesW ((null),0,0x33c030,0x00000000), stub! fixme:d3d10:D3D10CreateDevice1 Ignoring feature level D3D10_FEATURE_LEVEL_10_0. fixme:dxgi:dxgi_device_init Ignoring adapter type. fixme:win:EnumDisplayDevicesW ((null),0,0x33c030,0x00000000), stub! fixme:d3d10:D3D10CreateDevice1 Ignoring feature level D3D10_FEATURE_LEVEL_10_1. fixme:dxgi:dxgi_device_init Ignoring adapter type. fixme:d2d:d2d_factory_init Ignoring factory type and options. fixme:d3d10:D3D10CreateEffectFromMemory data 0x15d07b0, data_size 4833, flags 0, device 0x143cb0, effect_pool (nil), effect 0x428b710 stub! fixme:d3d10:skip_dword_unknown Skipping 4 unknown DWORDs (DXBC header): fixme:d3d10:skip_dword_unknown 0x5af68935 fixme:d3d10:skip_dword_unknown 0x3e88ff30 fixme:d3d10:skip_dword_unknown 0x96a39662 fixme:d3d10:skip_dword_unknown 0x35cbba93 fixme:d3d10:skip_dword_unknown Skipping 1 unknown DWORDs (DXBC header): fixme:d3d10:skip_dword_unknown 0x00000001 fixme:d3d10:parse_fx10 Unknown 0: 0 fixme:d3d10:parse_fx10 Unknown 1: 0 fixme:d3d10:skip_dword_unknown Skipping 1 unknown DWORDs (local buffer): fixme:d3d10:skip_dword_unknown 0xffffffff fixme:d3d10:skip_dword_unknown Skipping 1 unknown DWORDs (variable): fixme:d3d10:skip_dword_unknown 0x00000000 fixme:d3d10:skip_dword_unknown Skipping 1 unknown DWORDs (variable): fixme:d3d10:skip_dword_unknown 0x00000000 fixme:d3d10:skip_dword_unknown Skipping 1 unknown DWORDs (variable): fixme:d3d10:skip_dword_unknown 0x00000000 fixme:d3d10:skip_dword_unknown Skipping 1 unknown DWORDs (local variable): fixme:d3d10:skip_dword_unknown 0xffffffff fixme:d3d10:skip_dword_unknown Skipping 1 unknown DWORDs (local variable): fixme:d3d10:skip_dword_unknown 0xffffffff ... fixme:d3d10:parse_fx10_state_group Failed to find property info for property 0x37. err:d3d10:parse_fx10_local_variable Failed to read property list. err:d3d10:D3D10CreateEffectFromMemory Failed to parse effect fixme:dbghelp:elf_search_auxv can't find symbol in module err:seh:raise_exception Exception frame is not in stack limits => unable to dispatch exception. --- snip --- $ sha1sum Firefox\ Setup\ 13.0.exe 9002a5ae41ef54edf378506ae80c934b7e8df7dc Firefox Setup 13.0.exe $ du -sh Firefox\ Setup\ 13.0.exe 16M Firefox Setup 13.0.exe $ wine --version wine-1.7.20-122-gd2d62cf Regards -- 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