July 2014 - 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 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 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

[Bug 34297] New: Allow reconnecting to disconnected joysticks
by wine-bugs＠winehq.org Oct. 22, 2021

Oct. 22, 2021

http://bugs.winehq.org/show_bug.cgi?id=34297 Bug #: 34297 Summary: Allow reconnecting to disconnected joysticks Product: Wine Version: 1.7.0 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: directx-dinput AssignedTo: wine-bugs(a)winehq.org ReportedBy: achurch+wine(a)achurch.org Classification: Unclassified Created attachment 45660 --> http://bugs.winehq.org/attachment.cgi?id=45660 Proof-of-concept patch Currently, if a joystick is disconnected and then reconnected (because the cable is pulled out, for example), Wine acts as though the joystick is present but stuck at the last state it reported, and it fails to report any subsequent changes in device state, which is an arguably suboptimal user experience. The attached patch (against 1.7.0) changes the Linux evdev driver to attempt to reopen a joystick device after a read fails. This patch uses the simple heuristic of "if it's on the same device file and has the same name, it's the same joystick", which means (1) it won't reconnect if the device file changes and (2) it could falsely reconnect if there are multiple input devices with the same name, but it works for simple circumstances. Naturally, one could iterate over all possible input devices to try and find the device, but that could be fairly expensive to do on every poll operation, and it would probably involve concurrency issues relating to checking whether the device is already known as a different joystick. In the long run, it might be better to monitor the /dev/input directory for added and removed devices (perhaps using inotify) and use those events to handle reconnection. -- 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 21564] New: warning forever ignores keyboard input after losing/regaining focus
by wine-bugs＠winehq.org Oct. 21, 2021

Oct. 21, 2021

http://bugs.winehq.org/show_bug.cgi?id=21564 Summary: warning forever ignores keyboard input after losing/regaining focus Product: Wine Version: 1.1.37 Platform: x86 URL: http://www18.big.or.jp/~hikoza/Prod/index_e.html OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: madewokherd(a)gmail.com Steps to reproduce: * Install Warning Forever from the linked website. * Start the program by running c:\wf\wf.exe. (The installer does not create a shortcut. This is the same on Windows.) * Select "Window mode". * Verify that the 'z' key can be used to make selections in the menu. * Switch to another window. * Switch back to Warning Forever window. * Verify that keyboard input no longer works. -- 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 22369] New: A child window without WS_EX_MDICHILD style should not be tiled by the WM_MDITILE message.
by wine-bugs＠winehq.org Oct. 21, 2021

Oct. 21, 2021

http://bugs.winehq.org/show_bug.cgi?id=22369 Summary: A child window without WS_EX_MDICHILD style should not be tiled by the WM_MDITILE message. Product: Wine Version: unspecified Platform: All OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: a.m.winehq(a)gmail.com In user32/mdi.c -> MDITile -> #L763(wine-1.1.42) for-loop "remove all the windows we don't want", the windows without WS_EX_MDICHILD window style should be also removed from win_array. MDICascade is also. -- 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 37