April 2020 - Wine-Bugs - list.winehq.org

[Bug 48885] New: Having problems with TodoList Abstractspoon
by WineHQ Bugzilla April 4, 2020

April 4, 2020

https://bugs.winehq.org/show_bug.cgi?id=48885 Bug ID: 48885 Summary: Having problems with TodoList Abstractspoon Product: Wine Version: unspecified Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cotfas(a)gmail.com Created attachment 66830 --> https://bugs.winehq.org/attachment.cgi?id=66830 logs+video Hello All, I`m writing about the issue that I have with the Todolist Abstractspoon application that no longer works as a daily use from the Catalina update. Currently I have: Mac OS X Catalina 10.15.4 Crossover 19.0.1 Todolist Abstractspoon 7.2 The problem arise with the Catalina update, when I tried to open and work with bigger TDL files it crashes and the app can not be used. Also resizing the screen takes more time to process (it has a big flickering). I have attached: - A video on how the crash is reproduced on my end; - Logs from the Todolist app from Crossover/wine and VirtualBox/WinXP (running it with ToDoList.exe -g generates that logs); - Logs from the Crossover run command (without extra logging channel); - The TDL file that I use, the one that the crash can be reproduced (the actual text is randomised); The Todolist app version 7.2 can be downloaded from: https://www.abstractspoon.com http://abstractspoon.pbwiki.com/f/todolist_exe.zip I`ve tested with Todolist version 6 and 8(beta) and the same issue. The Todolist app worked great on Mojave with: http://winebottler.kronenberg.org WineBottlerCombo_1.8.6.dmg (not 100% sure which wine version were). I think I tested it with WineBottlerCombo_4.0.1.1.dmg as well back then when I had Mojave and it was not worked (but for this I`m not 100% sure). Tried with Windows 8 (32bit), and WinXP 64bit bottle under Crossover, the same issue. The Todolist app worked great also on the linux machine (ubuntu18) with wine version ~3 I think (but I no longer have the linux machine). I have used also the Crossover archive from Linux, and the actual windows xp/virtualbox files as crossover bottle, but does not work. I might think that it is a problem in wine version rather than crossover, but when I tested it with Crossover 19 on ubuntu it worked, and I guess the Crossover 19 uses wine version 4. Maybe is there a way I can switch between wine versions for a particular bottle or for the Crossover app? Also look at the crash from the Crossover logs: wine: Unhandled page fault on read access to 0x03ecb970 at address 0x1007:0x6e971c33 (thread 0025), starting debugger... 0025:err:seh:start_debugger Couldn't start debugger ("winedbg --auto 36 188") (2) Read the Wine Developers Guide on how to set up winedbg or another debugger How can I setup the debugger to see what it is happening? Thank you, Best 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.

1 1

[Bug 13788] New: Logitech Harmony Remote Software Fails USB Update
by wine-bugs＠winehq.org April 4, 2020

April 4, 2020

http://bugs.winehq.org/show_bug.cgi?id=13788 Summary: Logitech Harmony Remote Software Fails USB Update Product: Wine Version: 1.0-rc3 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jimrorie(a)logisys.biz Technically this is version 7.4.3 which can only be installed by installing 7.4.1 and going though the update process. Selecting "Update Remote" in the main screen results in a timeout waiting for communication with the remote via USB. -- 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 40869] New: Software (made in Matlab) installer crashes and closes immediately
by wine-bugs＠winehq.org April 4, 2020

April 4, 2020

https://bugs.winehq.org/show_bug.cgi?id=40869 Bug ID: 40869 Summary: Software (made in Matlab) installer crashes and closes immediately Product: Wine Version: 1.9.13 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vulturekoke1(a)hotmail.com Distribution: --- Created attachment 54931 --> https://bugs.winehq.org/attachment.cgi?id=54931 Program Error Details The installer of a specialized program that was made using Matlab crashes immediately upon running. Program Link: https://drive.google.com/open?id=0BwSh3pslkCJhdWRFYzFvcUMtQmc MD5SUM: cc08c913d4ab5564e54b5d34eef82347 -- 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 48886] New: LogiRegistryService (part of Logitech Gaming Software 8.x) hogs CPU, relying on blocking behaviour of 'wtsapi32.WTSWaitSystemEvent'
by WineHQ Bugzilla April 4, 2020

April 4, 2020

https://bugs.winehq.org/show_bug.cgi?id=48886 Bug ID: 48886 Summary: LogiRegistryService (part of Logitech Gaming Software 8.x) hogs CPU, relying on blocking behaviour of 'wtsapi32.WTSWaitSystemEvent' Product: Wine Version: 5.5 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: wtsapi32 Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, as it says. https://support.logi.com/hc/en-us/articles/360025298053 Download: https://download01.logi.com/web/ftp/pub/techsupport/gaming/LGS_8.82.151_x64… Snapshot: https://web.archive.org/web/20200404175412/https://download01.logi.com/web/… Installer log 'LGS8_setup.log': --- snip --- ... installing "C:\Program Files\Logitech Gaming Software\Drivers\APOService\LogiRegistryService.exe" -install returned 0 starting "C:\Program Files\Logitech Gaming Software\Drivers\APOService\LogiRegistryService.exe" -start returned 0 ... --- snip --- Relevant part of trace log: --- snip --- $ WINEDEBUG=+seh,+relay,+msi,+wtsapi wine ./LGS_8.82.151_x64_Logitech.exe >>log.txt 2>&1 ... 011b:Call KERNEL32.CreateProcessW(00000000,0011eda0 L"\"C:\\Program Files\\Logitech Gaming Software\\Drivers\\APOService\\LogiRegistryService.exe\"",00000000,00000000,100000000,00000400,00889760,00000000,0022f5a0,0022f580) ret=140006757 ... 011b:Ret KERNEL32.CreateProcessW() retval=00000001 ret=140006757 ... 0125:Starting thread proc 0x7bccded0 (arg=0x11b760) 0125:Call wtsapi32.WTSWaitSystemEvent(00000000,00000028,00eefb00) ret=140004086 ... 0125:Ret wtsapi32.WTSWaitSystemEvent() retval=00000000 ret=140004086 0125:Call wtsapi32.WTSWaitSystemEvent(00000000,00000028,00eefb00) ret=140004086 0125:fixme:wtsapi:WTSWaitSystemEvent Stub 0000000000000000 0x00000028 0000000000EEFB00 0125:Ret wtsapi32.WTSWaitSystemEvent() retval=00000000 ret=140004086 0125:Call wtsapi32.WTSWaitSystemEvent(00000000,00000028,00eefb00) ret=140004086 0125:fixme:wtsapi:WTSWaitSystemEvent Stub 0000000000000000 0x00000028 0000000000EEFB00 0125:Ret wtsapi32.WTSWaitSystemEvent() retval=00000000 ret=140004086 0125:Call wtsapi32.WTSWaitSystemEvent(00000000,00000028,00eefb00) ret=140004086 0125:fixme:wtsapi:WTSWaitSystemEvent Stub 0000000000000000 0x00000028 0000000000EEFB00 0125:Ret wtsapi32.WTSWaitSystemEvent() retval=00000000 ret=140004086 ... 011b:Call KERNEL32.ExitProcess(00000000) ret=7fc308ecdbdc --- snip --- --- snip --- $ grep "Call wtsapi32.WTSWaitSystemEvent(" log.txt | wc -l 1934913 --- snip --- Basically it uses 'WTSWaitSystemEvent' to monitor session changes. 0x28 = WTS_EVENT_CONNECT | WTS_EVENT_LOGON * WTS_EVENT_CONNECT - A client connected to a WinStation. * WTS_EVENT_LOGON - A user logged on to the system from either the Remote Desktop Services console or from a client WinStation. It only stops at one point because the installer schedules "reboot" which stops the service. On WINEPREFIX restart, the autostart service hogs one core because it endlessly calls this API in quick succession, spamming console as well. Silencing the stub using FIXME-once is obviously not a proper solution. Faking event data won't help either because the code runs in a thread that expects "long time" blocking behaviour: App code: --- snip --- ... 0000000140004070 | lea r8,qword ptr ss:[rsp+60] ; pEventFlags 0000000140004075 | mov edx,28 ; EventMask 000000014000407A | xor ecx,ecx ; hServer 000000014000407C | mov dword ptr ss:[rsp+60],ebp 0000000140004080 | call qword ptr ds:[<&WTSWaitSystemEvent>]; should block 0000000140004086 | mov ecx,dword ptr ss:[rsp+60] ; pEventFlags 000000014000408A | mov dword ptr ss:[rsp+40],ecx 000000014000408E | mov ebx,eax ; retval 0000000140004090 | lea rax,qword ptr ss:[rsp+60] 0000000140004095 | mov qword ptr ss:[rsp+38],rax 000000014000409A | mov dword ptr ss:[rsp+30],28 00000001400040A2 | lea r9,qword ptr ds:[140024CA8] 00000001400040A9 | mov r8d,C0 00000001400040AF | mov rdx,rsi 00000001400040B2 | mov ecx,5 00000001400040B7 | mov qword ptr ss:[rsp+28],rbp 00000001400040BC | mov dword ptr ss:[rsp+20],ebx 00000001400040C0 | call logiregistryservice.140004450 ; debug_message 00000001400040C5 | test ebx,ebx ; retval 00000001400040C7 | je logiregistryservice.1400040DA 00000001400040C9 | mov rcx,qword ptr ds:[rdi+38] 00000001400040CD | mov rcx,qword ptr ds:[rcx+218] 00000001400040D4 | call qword ptr ds:[<&JMP.&SetEvent>] ; signal oth thread 00000001400040DA | cmp byte ptr ds:[rdi+60],bpl ; pEventFlags 00000001400040DE | jne logiregistryservice.140004070 ; loop again 00000001400040E0 | mov rcx,qword ptr ds:[rdi+58] 00000001400040E4 | call qword ptr ds:[<&JMP.&SetEvent>] 00000001400040EA | lea r9,qword ptr ds:[140024C70] ... --- snip -- Wine source: https://source.winehq.org/git/wine.git/blob/7096ab45444d7b7cbb926b5a51af0cb… --- snip --- 567 /************************************************************ 568 * WTSWaitSystemEvent (WTSAPI32.@) 569 */ 570 BOOL WINAPI WTSWaitSystemEvent(HANDLE hServer, DWORD Mask, DWORD* Flags) 571 { 572 /* FIXME: Forward request to winsta.dll::WinStationWaitSystemEvent */ 573 FIXME("Stub %p 0x%08x %p\n", hServer, Mask, Flags); 574 return FALSE; 575 } --- snip --- Microsoft docs: https://docs.microsoft.com/en-us/windows/win32/api/wtsapi32/nf-wtsapi32-wts… $ sha1sum LGS_8.82.151_x64_Logitech.exe f21ae9214f8608ac192cd474c5f15734a75ca115 LGS_8.82.151_x64_Logitech.exe $ du -sh LGS_8.82.151_x64_Logitech.exe 117M LGS_8.82.151_x64_Logitech.exe $ wine --version wine-5.5-242-g7096ab4544 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.

1 1

[Bug 47464] New: wineboot keep crash after build with msvcrt.
by wine-bugs＠winehq.org April 4, 2020

April 4, 2020

https://bugs.winehq.org/show_bug.cgi?id=47464 Bug ID: 47464 Summary: wineboot keep crash after build with msvcrt. Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: l12436(a)yahoo.com.tw Distribution: --- Created attachment 64838 --> https://bugs.winehq.org/attachment.cgi?id=64838 crash stack I have update to wine 4.12, and build with myself I found one thing. wineboot keep crashing after build with msvcrt with crash stack trace. I have try to remove it from build with msvcrt, and it back normal again. the attachment is crash stacktrace. -- 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 23

[Bug 33668] New: Physx 9.12.1031 : Installation fails in 64-bit WINEPREFIX
by wine-bugs＠winehq.org April 4, 2020

April 4, 2020

http://bugs.winehq.org/show_bug.cgi?id=33668 Bug #: 33668 Summary: Physx 9.12.1031 : Installation fails in 64-bit WINEPREFIX Product: Wine Version: 1.5.31 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vbscript AssignedTo: wine-bugs(a)winehq.org ReportedBy: berillions(a)gmail.com Classification: Unclassified Hi, It's impossible to install this version of Physx into a 64bits wineprefix. The installer can be launch, can accept the licence agreement but has an error during the installation. The installation of this version is possible into a 32Bits wineprefix. It's the message that i have when i try to install it into 64Bits wineprefix : fixme:vbscript:parse_script parser failed around L"\\default\", \"\", \"\", , , , oCtx).Get(\"StdRegProv\") \r\n \r\n Set oInParams = oReg.Methods_(\"GetStringValue\").InParameters \r\n oInParams.hDefKey = RootKey \r\n oInParams.sSubKeyName = Key \r\n oInParams.sValueName = Value \r\n \r\n Set oOutParams = oReg.ExecMethod_(\"GetStringV"... Thanks, Max -- 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 735] The WM_INPUTLANGCHANGE message is not send when switching layouts
by WineHQ Bugzilla April 4, 2020

April 4, 2020

https://bugs.winehq.org/show_bug.cgi?id=735 Tal Cohen <tal(a)forum2.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tal(a)forum2.org --- Comment #30 from Tal Cohen <tal(a)forum2.org> --- The bug is still there in Wine 5.0. This bug makes Wine almost useless for anyone using bidirectional language combinations (e.g., English and Hebrew, or French and Arabic, etc.). Any Windows control that accepts text input uses WM_INPUTLANGUAGECHANGE to adjust from RTL to LTR text processing. Applications that do their own text processing (e.g., browsers, Microsoft Office, graphic design programs, CAD software) also rely on this message and are broken without it. Switching the keyboard language on the Linux level allows me to send (e.g.) Hebrew characters to the Windows application, but since that Windows application does not realize it's now in RTL mode, it will completely botch the text; it lives in an impossible situation where the input direction is LTR but the characters provided are from an RTL language. As Shachar noted in #11, a complete mapping to all possible (current and future) keyboard layouts is not as critical as indicating a switch to a layout that has a different directionality. [Reproduced by creating my own test program, cross-compiling compiling it on Ubuntu 18.04/Cinnamon 4.2.4 (not that it matters), and running it using wine-5.0; running the exact same binary on Windows 10 shows that the program itself works as expected. I then searched and found this is a known bug... for almost 18 years.] -- 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.

1 0

[Bug 48513] New: The following packages have unmet dependencies: winehq-stable : Depends: wine-stable (= 5.0.0~bionic)
by WineHQ Bugzilla April 4, 2020

April 4, 2020

https://bugs.winehq.org/show_bug.cgi?id=48513 Bug ID: 48513 Summary: The following packages have unmet dependencies: winehq-stable : Depends: wine-stable (= 5.0.0~bionic) Product: Packaging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: nrbrtx(a)gmail.com CC: dimesio(a)earthlink.net, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Currently users can't install packages for Ubuntu 18.04 LTS while following your official guide (https://wiki.winehq.org/Ubuntu) So the below steps: ``` sudo dpkg --add-architecture i386 wget -nc https://dl.winehq.org/wine-builds/winehq.key sudo apt-key add winehq.key sudo apt-add-repository 'deb https://dl.winehq.org/wine-builds/ubuntu/ bionic main' sudo apt update sudo apt install --install-recommends winehq-stable ``` end with ``` Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: winehq-stable : Depends: wine-stable (= 5.0.0~bionic) E: Unable to correct problems, you have held broken packages. ``` Problem was seen on AskUbuntu several times - the last was https://askubuntu.com/q/1205550/66509 . -- 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.

1 10

[Bug 48876] New: Origin: Crashes on start
by WineHQ Bugzilla April 4, 2020

April 4, 2020

https://bugs.winehq.org/show_bug.cgi?id=48876 Bug ID: 48876 Summary: Origin: Crashes on start Product: Wine Version: 5.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wolfy1339(a)gmail.com Distribution: --- Created attachment 66813 --> https://bugs.winehq.org/attachment.cgi?id=66813 Output of running Origin from the terminal I had Origin installed before in my wine prefix, then it started crashing when it used to work. So, I nuked my wine prefix and reinstalled it. The install process failed, which has happened before, so I used a workaround script provided by Lutris (https://github.com/DrDoctor13/wine-origin-updater) and this extracts the files from the installer into the proper directory. When I tried to start Origin (from the terminal) it immediately crashed. It seems to have been caused by a missing WLDAP32.dll -- 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.

1 7

[Bug 38128] New: FF3usME: Crashes upon reading data from ROM file.
by wine-bugs＠winehq.org April 3, 2020

April 3, 2020

https://bugs.winehq.org/show_bug.cgi?id=38128 Bug ID: 38128 Summary: FF3usME: Crashes upon reading data from ROM file. Product: Wine Version: 1.6 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: terffinatorz(a)gmail.com Created attachment 50821 --> https://bugs.winehq.org/attachment.cgi?id=50821 Detail report that comes with the error FF3usME (a rom editing tool) crashes upon selecting objects to change. Program starts up fine, you can load the ROM file and you can select an operation but once in the menu if you select something in one of the drop down boxes the program crashes with the attached detail report. -- 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