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

[Bug 50859] New: X Error of failed request: GLXBadFBConfig
by WineHQ Bugzilla 14 Jun '23

14 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=50859 Bug ID: 50859 Summary: X Error of failed request: GLXBadFBConfig Product: Wine-staging Version: 6.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: linsilstef(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- [stefan(a)yuntani Downloads]$ wine64 Gw2Setup-64.exe 0034:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 005c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1 0064:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1 006c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1 002c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1 0024:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1 00f4:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1 0024:fixme:heap:RtlSetHeapInformation 0000000000020000 0 000000000022FD30 4 0024:fixme:heap:RtlSetHeapInformation 0000000001620000 0 000000000022FD10 4 0024:fixme:heap:RtlSetHeapInformation 0000000001620000 1 0000000000000000 0 0024:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFO X Error of failed request: GLXBadFBConfig Major opcode of failed request: 150 (GLX) Minor opcode of failed request: 0 () Serial number of failed request: 218 Current serial number in output stream: 218 The error also occurs in wine 6.3. and Wine 6.4 System Fedora 34 Mesa version 21.0.0-2 -- 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 27

[Bug 43708] New: Major terrain glitching on SPORE
by wine-bugs＠winehq.org 14 Jun '23

14 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=43708 Bug ID: 43708 Summary: Major terrain glitching on SPORE Product: Wine-staging Version: 2.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: emily.shadowsong(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 59176 --> https://bugs.winehq.org/attachment.cgi?id=59176 Clearly, it's already getting wierd... I've been playing SPORE for a while now, it has worked normally; at one point in playing I pressed ALT+TAB and the whole terrain just glitched. It shows up that way on the map, it's not graphics-related because I can physically touch the messed-up land. There's sometimes jagged spikes, often times lines through the planet, and extremely tall mountains, making the game practically unplayable unless I have wings. Sometimes it'll appear as though my nest spawned inside water, and if I try to walk out of the water and onto what looks like land I'll be eaten by the fish monster. I've reinstalled SPORE about five times now and it hasn't helped. I've tried running SPORE on safe mode as well. I have the core SPORE, galactic adventures, and creepy & cute parts pack. Every time I alt tab, the terrain changes again and gets more and more messed up. -- 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 49588] New: Cannot build wine with GCC 10 and Address Sanitizer
by WineHQ Bugzilla 13 Jun '23

13 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=49588 Bug ID: 49588 Summary: Cannot build wine with GCC 10 and Address Sanitizer Product: Wine Version: 5.13 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mikrutrafal(a)protonmail.com Distribution: --- Created attachment 67745 --> https://bugs.winehq.org/attachment.cgi?id=67745 config.log Hi, When I tried to compile Wine with address sanitizer with GCC 10 with this command ``` ./configure --enable-win64 CFLAGS="-Og -fsanitize=address" LDFLAGS="-fsanitize=address -lasan -lpthread" make -j8 ``` then this errors prints to config.log when configuring build ``` configure:4663: gcc -V >&5 gcc: error: unrecognized command-line option '-V' gcc: fatal error: no input files compilation terminated. configure:4663: gcc -qversion >&5 gcc: error: unrecognized command-line option '-qversion'; did you mean '--version'? gcc: fatal error: no input files compilation terminated. ``` -- 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 6

[Bug 54988] New: Final Fantasy XIV: Japanese IME behavior incorrect
by WineHQ Bugzilla 13 Jun '23

13 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54988 Bug ID: 54988 Summary: Final Fantasy XIV: Japanese IME behavior incorrect Product: Wine Version: 8.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: achurch+wine(a)achurch.org Regression SHA1: d9fc3eab9a4ae39c94fa484d65679de22d02e75a Distribution: --- Final Fantasy XIV: Japanese IME behavior incorrect As of Wine 8.8, when using a Japanese input method editor (IME), the IME is no longer disabled in cases where it should be, such as the following: 1) Log in to Final Fantasy XIV (get in-game). 2) Click on the chat input bar to enter text entry mode. 3) Enable the Japanese IME (so that Japanese text can be typed). 4) With the IME active, press Enter to leave text entry mode. Expected behavior: The IME is disabled, so that keyboard controls (WASD etc.) are properly recognized. Observed behavior: The IME remains enabled, preventing keyboard controls from working until the user disables the IME manually. This is a regression from Wine 8.7; git bisect identifies d9fc3eab9a4ae39c94fa484d65679de22d02e75a as introducing the regression. -- 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 8

[Bug 50760] New: SteuerSparErklärung 2021 (German tax program): crashes on launching main window
by WineHQ Bugzilla 12 Jun '23

12 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=50760 Bug ID: 50760 Summary: SteuerSparErklärung 2021 (German tax program): crashes on launching main window Product: Wine Version: 6.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: debian(a)carbon-project.org Distribution: --- Created attachment 69547 --> https://bugs.winehq.org/attachment.cgi?id=69547 Console output while executing the program Since test version and paid version are the same (the only restriction I know of is: you can't send the tax declarations to the tax authority with the test version), you can reproduce this issue with the test version available at https://download.steuertipps.de/software/SSE26Standard/testversion The report is about version 26.29.77 but prior versions showed this crash as well. Steps to reproduce (after default installation; WARNING: you need to set your profile to *Windows 10*, prior versions are no longer supported by the program): 1. Launch SSE.exe from the main install directory 2. Select the option "Steuererklärung 2020" (any other works too as far as I can tell, but this is the main function for most people) 3. Observe the main window starting to appear and then two instances of the crash reporter of the tax program getting launched, showing you the information the program wants to send to the vendor (Akademische Arbeitsgemeinschaft). I don't see anything of the crash logged to the console, the only error I can see there is > 0024:err:seh:dispatch_exception Fatal EXCEPTION_WINE_CXX_EXCEPTION exception (code=e06d7363) raised Otherwise there are mostly FIXMEs, so this could very well be a missing function somewhere. The program itself logs the following to a file: > 02.03.2021 15:19:38.080: Exception: Access Violation at 00000000 > 02.03.2021 15:19:38.080: PageFile: 397.66 MB WorkingSetSize: 462.65 MB > 02.03.2021 15:19:38.080: Writing Minidump: > 02.03.2021 15:19:38.154: Unhandled Exception (TopLevelFilter) > 02.03.2021 15:19:38.154: Exception: Breakpoint at 02AEB4EA > 02.03.2021 15:19:38.155: PageFile: 395.32 MB WorkingSetSize: 461.28 MB > 02.03.2021 15:19:38.155: Writing Minidump: > 02.03.2021 15:19:38.155: Saved dump file to 'C:\users\kai\Temp\__Akad__Crash_02.dmp' > 02.03.2021 15:19:38.155: Version: 26, 0, 26075, 0 > 02.03.2021 15:19:38.155: Build: Build-26075 > 02.03.2021 15:19:42.588: Saved dump file to 'C:\users\kai\Temp\__Akad__Crash_01.dmp' > 02.03.2021 15:19:42.588: Version: 26, 0, 26075, 0 > 02.03.2021 15:19:42.588: Build: Build-26075 > 02.03.2021 15:19:42.594: Exception: Access Violation at CCCCCC02 > 02.03.2021 15:19:42.594: PageFile: 424.93 MB WorkingSetSize: 526.80 MB > 02.03.2021 15:19:42.594: Writing Minidump: > 02.03.2021 15:19:42.595: Saved dump file to 'C:\users\kai\Temp\__Akad__Crash_03.dmp' > 02.03.2021 15:19:42.595: Version: 26, 0, 26075, 0 > 02.03.2021 15:19:42.595: Build: Build-26075 > 02.03.2021 15:19:42.601: Exception: Access Violation at CCCCCC02 > 02.03.2021 15:19:42.601: PageFile: 424.93 MB WorkingSetSize: 526.80 MB > 02.03.2021 15:19:42.601: Writing Minidump: > 02.03.2021 15:19:42.602: Saved dump file to 'C:\users\kai\Temp\__Akad__Crash_04.dmp' > 02.03.2021 15:19:42.602: Version: 26, 0, 26075, 0 > 02.03.2021 15:19:42.602: Build: Build-26075 > 02.03.2021 15:19:42.608: Exception: Access Violation at CCCCCC02 > 02.03.2021 15:19:42.608: PageFile: 424.93 MB WorkingSetSize: 526.80 MB > 02.03.2021 15:19:42.608: Writing Minidump: > 02.03.2021 15:19:42.609: Saved dump file to 'C:\users\kai\Temp\__Akad__Crash_05.dmp' > 02.03.2021 15:19:42.609: Version: 26, 0, 26075, 0 > 02.03.2021 15:19:42.609: Build: Build-26075 > 02.03.2021 15:19:42.614: Unhandled Exception (TopLevelFilter) > 02.03.2021 15:19:42.614: Exception: Access Violation at CCCCCC02 > 02.03.2021 15:19:42.614: PageFile: 424.93 MB WorkingSetSize: 526.80 MB > 02.03.2021 15:19:42.615: Writing Minidump: > 02.03.2021 15:19:42.616: Saved dump file to 'C:\users\kai\Temp\__Akad__Crash_06.dmp' > 02.03.2021 15:19:42.616: Version: 26, 0, 26075, 0 > 02.03.2021 15:19:42.616: Build: Build-26075 > 02.03.2021 15:19:42.656: MiniDumper::TopLevelFilter failed The non-staging version fails earlier for me and doesn't get even this far (previous editions, up until "SteuerSparErklärung 2020", all worked fine for me, even on non-staging versions of Wine. But those allowed Windows 7 as the OS). Attached you find all the output from the console and the minidump files produced by the program itself (upload follows this initial report). Let me know, if you need anything else. -- 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 40528] New: Cygwin installs (with errors) but doesn't work at all
by wine-bugs＠winehq.org 12 Jun '23

12 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=40528 Bug ID: 40528 Summary: Cygwin installs (with errors) but doesn't work at all Product: Wine Version: 1.9.8 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)lam.pl Distribution: --- Cygwin was installed with "setup.exe version 2.873 (64 bit)". When installing, many packages' post-install scripts returned exit code -1073741819. They also repeatedly said on the console: running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/mintty.sh" error: Unable to redirect output to '/var/log/setup.log.runXa00041'; using console fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:ntdll:NtQueryInformationProcess (process=0xffffffffffffffff) Unimplemented information class: ProcessSessionInformation fixme:advapi:LsaOpenPolicy ((null),0x180309f00,0x00000001,0xffffc2f8) stub fixme:advapi:LsaClose (0xcafe) stub fixme:netapi32:NetUserGetInfo Level 3 is not implemented err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x7bc9b52c error: Unable to remove temporary file '/var/log/setup.log.runXa00041' abnormal exit: exit code=-1073741819 setup.exe says "cygwin" was installed as 2.5.1-1 version. And now, "wine whatever.exe" in $HOME.wine/drive_c/cygwin64/bin (and that includes "wine bash -i --login", but I've tried all others, literally anything like "wine less.exe") says: fixme:winediag:start_process Wine Staging 1.9.8 is a testing version containing experimental patches. fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. err:winedevice:ServiceMain driver L"Null" failed to load fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:ntdll:NtQueryInformationProcess (process=0xffffffffffffffff) Unimplemented information class: ProcessSessionInformation fixme:advapi:LsaOpenPolicy ((null),0x180309f00,0x00000001,0xffffc2f8) stub fixme:advapi:LsaClose (0xcafe) stub fixme:netapi32:NetUserGetInfo Level 3 is not implemented Cygwin WARNING: Couldn't compute FAST_CWD pointer. This typically occurs if you're using an older Cygwin version on a newer Windows. Please update to the latest available Cygwin version from https://cygwin.com/. If the problem persists, please see https://cygwin.com/problems.html err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x7bc9b52c -- 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 32

[Bug 50341] New: MS-MPI 10.x crashes due to use-after-free in RpcAsyncCompleteCall()
by WineHQ Bugzilla 11 Jun '23

11 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=50341 Bug ID: 50341 Summary: MS-MPI 10.x crashes due to use-after-free in RpcAsyncCompleteCall() Product: Wine Version: 5.6 Hardware: x86-64 URL: https://github.com/microsoft/Microsoft-MPI/releases/do wnload/v10.1.1/msmpisetup.exe OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: rpc Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- Continued from bug 45699. RPCRT4_process_packet() frees the stub message which RpcAsyncCompleteCall() subsequently uses. -- 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 3

[Bug 51952] New: World of Warcraft Classic (WOW) has funky graphics with DX12
by WineHQ Bugzilla 11 Jun '23

11 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=51952 Bug ID: 51952 Summary: World of Warcraft Classic (WOW) has funky graphics with DX12 Product: Wine Version: 6.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: blue-t(a)web.de Distribution: --- Created attachment 70933 --> https://bugs.winehq.org/attachment.cgi?id=70933 Console output When i start wow classic with the dx12 render mode, everything in the game world is barely visible due to render issues. The Interface is ok, but i hid it in the example picture. -- 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 8

[Bug 45227] New: Framemaker 8 element window is drawn incorrectly
by wine-bugs＠winehq.org 11 Jun '23

11 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=45227 Bug ID: 45227 Summary: Framemaker 8 element window is drawn incorrectly Product: Wine Version: 3.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- In Framemaker 8.0 (and Framemaker 7.2) the element window is drawn too wide with garbage added. To reproduce: - Download Framemaker 8 from the download link https://supportdownloads.adobe.com/detail.jsp?ftpID=4549 and install it. This installs a demo version which is 30 days functional. - Start Framemaker with "wine start FrameMaker.exe" - Create new document with File->New->Document (select Portrait mode) - In the child window for the new document open the element window (click the triangle in the right scrollbar) The element window should be two columns wide with element symbols. It is drawn too wide with garbage content added on the right side. This is the same bug as #19609 but now there is a download link for a trial version (thanks to Louis). -- 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 32863] New: Mathematica main menu window has extra space under menu
by wine-bugs＠winehq.org 11 Jun '23

11 Jun '23

http://bugs.winehq.org/show_bug.cgi?id=32863 Bug #: 32863 Summary: Mathematica main menu window has extra space under menu Product: Wine Version: 1.5.22 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: b7.10110111(a)gmail.com Classification: Unclassified Created attachment 43397 --> http://bugs.winehq.org/attachment.cgi?id=43397 Screenshot In Windows there's nothing like the black bar under menu seen in the screenshot (denoted by arrow). -- 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 7