wine-bugs December 2023

wine-bugs@winehq.org

1 participants
2116 discussions

[Bug 53905] New: widl: support MIDL 3.0 and WinMD output
by WineHQ Bugzilla 06 Dec '23

06 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=53905 Bug ID: 53905 Summary: widl: support MIDL 3.0 and WinMD output Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: alvin(a)alvinhc.com C++/WinRT (cppwinrt): https://github.com/microsoft/cppwinrt It is currently impossible to build the custom components in the cppwinrt test suite with mingw-w64. For this to work, widl needs to: - understand MIDL 3.0 syntax, - generate the ABI header (not required if only using C++/WinRT projection), - produce .winmd metadata of the component, - read existing system .winmd metadata (not sure if actually needed). The MIDL command line for this: midl.exe /metadata_dir C:\Windows\System32\WinMetadata /winrt /winmd "D:\a\cppwinrt\cppwinrt\_build\x64\Debug\test_component.winmd" /h "D:\a\cppwinrt\cppwinrt\_build\x64\Debug\test_component.h" /ns_prefix /nomidl test_component.idl ## MIDL 3.0 https://learn.microsoft.com/en-us/uwp/midl-3/intro What I can tell is missing widl so far: - MIDL 3.0 uses different basic type names (e.g. Int32, String) - Attribute types, and using custom attributes Example file: https://github.com/microsoft/cppwinrt/blob/5ca626adae21be363399b44d2b6a9ab3… > widl --winrt -h -H out/test_component.h --ns_prefix test_component.idl test_component.idl:5: error: syntax error, unexpected aIDENTIFIER, expecting ',' or ']' (widl version 7.7 from mingw-w64) ## WinMD metadata https://learn.microsoft.com/en-us/uwp/winrt-cref/winmd-files These are CLR (think .NET and ECMA 335) assemblies used as a replacement for the old typelib files. -- 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 55928] New: NtQuerySystemInformation SystemProcessInformation result misaligned
by WineHQ Bugzilla 06 Dec '23

06 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=55928 Bug ID: 55928 Summary: NtQuerySystemInformation SystemProcessInformation result misaligned Product: Wine Version: 8.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: novae.harpist06(a)icloud.com Distribution: --- Created attachment 75493 --> https://bugs.winehq.org/attachment.cgi?id=75493 Reproducer NtQuerySystemInformation with SystemProcessInformation returns misaligned entries. Reproducer attached. Windows output: Process name: (null) Process name: System Process name: Secure System Process name: Registry ... (trimmed) Wine output: Process name: Z Misaligned at entry 1 -- 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 4

[Bug 55988] New: When trying to log into the EVE:Online Launcher, error shows up
by WineHQ Bugzilla 06 Dec '23

06 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=55988 Bug ID: 55988 Summary: When trying to log into the EVE:Online Launcher, error shows up Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: u78s7gqnd(a)mozmail.com Distribution: --- Created attachment 75595 --> https://bugs.winehq.org/attachment.cgi?id=75595 backtrace Started the EVE:Online- Launcher, while the Update was running tried to log into my account credentials. The launcher didn't crash but an error window showed up. When I later launched the launcher from steam with compatibility mode (GE-Proton-8-23) it worked fine. -- 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 55978] New: Fallout 3: Unimplemented COM object
by WineHQ Bugzilla 05 Dec '23

05 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=55978 Bug ID: 55978 Summary: Fallout 3: Unimplemented COM object Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: m1m1k4tz(a)protonmail.com Distribution: --- Created attachment 75568 --> https://bugs.winehq.org/attachment.cgi?id=75568 log Minor bug that doesn't seem to effect gameplay. I don't have a Windows partition so I can't check and see the original -- 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 15

[Bug 55987] New: Gunner3 doesn't show "save dialog" properly
by WineHQ Bugzilla 04 Dec '23

04 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=55987 Bug ID: 55987 Summary: Gunner3 doesn't show "save dialog" properly Product: Wine Version: 8.21 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 75592 --> https://bugs.winehq.org/attachment.cgi?id=75592 Screenshot how it should look like First, enable virtual desktop in winecfg for easier testing. Then run the game, click Start, then Start again to enter the Level Select screen. Here you can press save. But when clicking that button the game seems to freeze without the save dialog showing. If you click where a button should be now, the save dialog gets shown. When you click a save slot button, the same thing happens. You need to click again where a button should be to make it visible. See attached screenshot. -- 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 41977] New: Gunner3 always crashes due to wine having a different allocation scheme than windows
by wine-bugs＠winehq.org 04 Dec '23

04 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=41977 Bug ID: 41977 Summary: Gunner3 always crashes due to wine having a different allocation scheme than windows Product: Wine Version: 1.9.24 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: ArchLinux Created attachment 56382 --> https://bugs.winehq.org/attachment.cgi?id=56382 Hack to get the game working, patch for the exe Gunner 3 always crashes when selecting a level. According to my debugging, it's because the game allocates memory with RtlAllocateHeap and then accesses the area before that, aka undefined behavior. But note that it works just fine on all windows versions and ReactOS. It's probably WONTFIX, but since it works on windows I'll provide a hack (and maybe a patch) for usage on linux. Attached an patch for the gunner3.exe, make sure it has the MD5 4481bc4382bb00353edf0635516d904d. -- 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 6

[Bug 55975] New: crash if any application during file-open dialog when $WINEPREFIX/drive_c/users/$(whoami) is renamed or does not exist
by WineHQ Bugzilla 04 Dec '23

04 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=55975 Bug ID: 55975 Summary: crash if any application during file-open dialog when $WINEPREFIX/drive_c/users/$(whoami) is renamed or does not exist Product: Wine Version: 8.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alois.schloegl(a)gmail.com Distribution: --- Created attachment 75563 --> https://bugs.winehq.org/attachment.cgi?id=75563 WINEDEBUG log during winefile crash due to missing or non-matching c:/users/username directory I prepared a WINEPREFIX for a difficult to install application, and wanted to share this with other users. I made sure the other user has read permessions to all files, and the other users then copied that WINEPREFIX, so that the fileownership is change to the other user. For the other user, that application was always crashing as soon as she started the file-open dialog. The same application was working just fine for me. After changing c:\drive_c\users\YOURNAME to the other users name, and fixing all the symlinks to her $HOME directory, the application was working fine. The main issue here is the crash - without showning any meaningful error message. In order to reproduce this, start a new wineprefix, and run winefile export WINEPREFIX=$HOME/.wine.test wineboot -i winefile This was working, now rename c:\drive_c\users\YOURNAME mv $WINEPREFIX/drive_c/users/$(whoami){,-changed} winefile winefile will crash, and so will any other application as soon as you start an file selection dialog (typically "File Open"-dialog). Even saveing the backtrace was not possible. I would expect a more graceful handling of this case, either by generating the missing directory and files, or by some error dialog indicating what the problem is. -- 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 5

[Bug 55925] New: StarOffice 4.0 crashes on start
by WineHQ Bugzilla 04 Dec '23

04 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=55925 Bug ID: 55925 Summary: StarOffice 4.0 crashes on start Product: Wine Version: 8.20 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 75485 --> https://bugs.winehq.org/attachment.cgi?id=75485 WINEDEBUG=+ole Steps to reproduce: 1. Run `SETUP.EXE` (straightforward even if you don't know German) 2. Run `wine 'C:\office40\soffice.exe'` This looked suspicious: 0114:trace:ole:StgOpenStorage16 (c:\office40\config\soffice.cfg,00000000,0x00000040,00000000,0,02D7F530) 0114:warn:ole:StgOpenStorage16 Couldn't open file for storage $ sha256sum SETUP.EXE 68f4fa4f1b2cc18056190c8082dacf4d8e296b4aec97527bb5b52eafabf6c699 -- 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 2

[Bug 29255] New: Microsoft Office 2003, 2007 & 2010 applications do not print OTF
by wine-bugs＠winehq.org 04 Dec '23

04 Dec '23

http://bugs.winehq.org/show_bug.cgi?id=29255 Bug #: 29255 Summary: Microsoft Office 2003, 2007 & 2010 applications do not print OTF Product: Wine Version: 1.3.34 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gunwald(a)gmx.de Classification: Unclassified Created attachment 37835 --> http://bugs.winehq.org/attachment.cgi?id=37835 Document showing that OTF printing does not work All Microsoft Office applications form 2003 to 2010 are not able to print documents using any OTF (Open Type Font). Printing a Document using any OTF leads in a completely blank page. I think, this is an important bug, because printing is a main function of any office application. This bug may be related to bug 25515 (http://bugs.winehq.org/show_bug.cgi?id=25515). I did attach an document to demonstrate the bug. -- 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 11

[Bug 43418] New: gOddysey Pacemaker crashes with "User lib not found"
by wine-bugs＠winehq.org 03 Dec '23

03 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=43418 Bug ID: 43418 Summary: gOddysey Pacemaker crashes with "User lib not found" Product: Wine Version: 2.12 Hardware: x86 URL: http://web.archive.org/web/20110624013029if_/http://we bzoom.webs.com/smiff/PaceMakerR.zip OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Split of from Bug 43414. For me the program doesn't work at all, while the OP from Bug 43414 reported it working. Snipped from the log that looks suspicous to me: ------ 009:Ret PE DLL (proc=0x63cc6560,module=0x63c60000 L"msvcrt.dll",reason=PROCESS_ATTACH,res=(nil)) retval=1 0009:Call PE DLL (proc=0x2251000,module=0x2250000 L"JV-ODE.dll",reason=PROCESS_ATTACH,res=(nil)) trace:seh:raise_exception code=c0000005 flags=0 addr=0x22c6010 ip=022c6010 tid=0009 trace:seh:raise_exception info[0]=00000000 trace:seh:raise_exception info[1]=9eeef1ec trace:seh:raise_exception eax=02251000 ebx=7bd06000 ecx=b68a9cb0 edx=0033f95c esi=0033f5d8 edi=00000001 trace:seh:raise_exception ebp=0033f5b8 esp=0033f59c cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010246 trace:seh:call_stack_handlers calling handler at 0x7bcc7010 code=c0000005 flags=0 trace:seh:__regs_RtlUnwind code=c0000005 flags=2 trace:seh:__regs_RtlUnwind calling handler at 0x7bca52f0 code=c0000005 flags=2 trace:seh:__regs_RtlUnwind handler at 0x7bca52f0 returned 1 0009:exception in PE entry point (proc=0x2251000,module=0x2250000,reason=PROCESS_ATTACH,res=(nil)) 0009:Ret PE DLL (proc=0x2251000,module=0x2250000 L"JV-ODE.dll",reason=PROCESS_ATTACH,res=(nil)) retval=0 0009:Call PE DLL (proc=0x2251000,module=0x2250000 L"JV-ODE.dll",reason=PROCESS_DETACH,res=(nil)) trace:seh:raise_exception code=c0000005 flags=0 addr=0x22510a0 ip=022510a0 tid=0009 trace:seh:raise_exception info[0]=00000000 trace:seh:raise_exception info[1]=9eedf000 trace:seh:raise_exception eax=00000000 ebx=00000000 ecx=02250000 edx=0033f900 esi=00000001 edi=00000000 trace:seh:raise_exception ebp=0033f5b8 esp=0033f5a0 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010246 trace:seh:call_stack_handlers calling handler at 0x7bcc7010 code=c0000005 flags=0 trace:seh:__regs_RtlUnwind code=c0000005 flags=2 trace:seh:__regs_RtlUnwind calling handler at 0x7bca52f0 code=c0000005 flags=2 trace:seh:__regs_RtlUnwind handler at 0x7bca52f0 returned 1 0009:exception in PE entry point (proc=0x2251000,module=0x2250000,reason=PROCESS_DETACH,res=(nil)) 0009:Ret PE DLL (proc=0x2251000,module=0x2250000 L"JV-ODE.dll",reason=PROCESS_DETACH,res=(nil)) retval=0 0009:Ret KERNEL32.LoadLibraryA() retval=00000000 ret=100092fe 0009:Call KERNEL32.LoadLibraryA(0067fb94 "blitzclose.dll") ret=100092fe 0009:Call PE DLL (proc=0x2251199,module=0x2250000 L"blitzclose.dll",reason=PROCESS_ATTACH,res=(nil)) ------ It seems like it can't load the DLLs, and thus crashes. But I might be wrong. -- 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs December 2023