wine-bugs June 2024

wine-bugs@winehq.org

1 participants
1269 discussions

[Bug 56650] New: Report on SELinux 'execheap' Issues with wine-preloader
by WineHQ Bugzilla 11 Jun '24

11 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=56650 Bug ID: 56650 Summary: Report on SELinux 'execheap' Issues with wine-preloader Product: Wine Version: 9.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: chplee(a)gmail.com Distribution: --- This report was prepared by ChatGPT. I'm sorry that my own ability is not enough to support such a large amount of code analysis, so I have to turn to ChatGPT. I'm filing this report because a lot of people are suffering from this problem. Please refer to: https://bugzilla.redhat.com/show_bug.cgi?id=2247299 ### Report on SELinux 'execheap' Issues with `wine-preloader` #### Introduction The `wine-preloader` program is a crucial part of the Wine software, which allows Windows applications to run on Unix-like operating systems. An issue has been identified where SELinux prevents `wine-preloader` from executing code in writable memory regions, raising security alerts related to 'execheap' accesses. This report identifies potential sources of the issue in the program and provides recommendations for modifications. #### Potential Issues Identified 1. **Memory Mapping and Protection Setup**: In `wine-preloader`, memory mapping is handled with protections set that could potentially include both write and execute permissions. This is particularly evident in the function calls to `wld_mmap`, where memory protection flags are set based on the segment flags parsed from ELF headers. ```c wld_mmap((void *)(l->l_addr + c->mapstart), c->mapend - c->mapstart, c->prot, MAP_FIXED | MAP_COPY | MAP_FILE, fd, c->mapoff); ``` Here, the `c->prot` can contain combinations of `PROT_READ`, `PROT_WRITE`, and `PROT_EXEC` based on the segment's flags. 2. **Dynamic Code Generation**: Dynamic generation or modification of code could potentially occur, though not explicitly shown in the code snippets provided, it could be inferred from the overall functionality where executable code may be modified or generated on-the-fly. 3. **Modifying Memory Protection Attributes**: The use of `wld_mprotect` to change the protection attributes of memory pages could lead to states where pages are both writable and executable. ```c wld_mprotect((caddr_t) (zero & ~page_mask), page_size, c->prot|PROT_WRITE); ``` Although this snippet aims to make pages writable temporarily, if combined inappropriately with executable flags elsewhere, it could trigger SELinux policies. #### Recommendations - **Restricting Memory Permissions**: Enforce strict separations between writable and executable pages. Modify the logic that sets memory protections to ensure that no memory page is both writable and executable at the same time. This can be achieved by adjusting the ELF segment loading routines to separate code and data segments clearly. - **Use of Memory Protection Changes**: Implement a clear two-step process for handling memory that needs to be executable: - Initially, set memory to writable to modify or generate code. - Once modifications are complete, change the memory protection to executable only (removing write permissions). - **Code Audit and Testing**: Conduct a thorough audit of the places where memory permissions are set. Test under a SELinux-enforced environment to ensure that the adjustments meet security policies without hindering functionality. - **SELinux Policy Adjustments**: If `wine-preloader` inherently requires certain operations that SELinux policies restrict, consider creating custom SELinux policy modules that allow specific actions while maintaining overall security. This should be done cautiously to avoid creating unnecessary security holes. #### Conclusion Adjustments to `wine-preloader` should focus on ensuring that memory regions are either writable or executable but never both. By adhering to security best practices and possibly adjusting SELinux policies, `wine-preloader` can function effectively without triggering security violations in SELinux environments. -- 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 56819] New: Danganronpa V3 demo crashes on start shortly after GStreamer assertion failure
by WineHQ Bugzilla 11 Jun '24

11 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=56819 Bug ID: 56819 Summary: Danganronpa V3 demo crashes on start shortly after GStreamer assertion failure Product: Wine Version: 9.10 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 76628 --> https://bugs.winehq.org/attachment.cgi?id=76628 WINEDEBUG=+console GST_DEBUG=4 The demo is free on Steam. Terminal output is attached. The relevant part seems to be: (wine:543494): GStreamer-Video-CRITICAL **: 18:38:47.343: gst_video_info_from_caps: assertion 'gst_caps_is_fixed (caps)' failed First reported at https://www.reddit.com/r/LinuxCrackSupport/comments/15unp2s/danganronpa_v3_… -- 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 56805] New: DuckStation Does Not Find PlayStation BIOS File
by WineHQ Bugzilla 11 Jun '24

11 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=56805 Bug ID: 56805 Summary: DuckStation Does Not Find PlayStation BIOS File Product: Wine Version: 9.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: crashdance22(a)protonmail.com Distribution: --- When running the DuckStation installer or trying to run the PlayStation BIOS after installation, the installer and emulator itself cannot find SCPH5001.bin. The emulator does list the file as detected and available in the BIOS dropdown box, but proceeds to say it is not found. I have reproduced this issue in Wine Stable and Development versions on multiple machines and Ubuntu-based distros. The problem does not occur on Windows. I am aware DuckStation is natively available on Linux. However, the Windows version must be run in Wine to use the Online Crash Team Racing mod network client. The software cannot be run in a VM due to it needed to load DirectX libraries on startup. I have attached a zipped log file with WINEBUG=+all. I know using the "+all" option can be excessive but I was not able to easily find any errors or fixme statements otherwise. The log begins as soon as I start the DuckStation installer and I terminate Wine as soon as I see the "cannot find BIOS file" error message. -- 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 56793] New: Age of Empires 2 Fails to Run
by WineHQ Bugzilla 10 Jun '24

10 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=56793 Bug ID: 56793 Summary: Age of Empires 2 Fails to Run Product: Wine Version: 9.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dartme18(a)gmail.com Distribution: --- I'm using arch linux. I did ``` export WINEARCH=win32 WINEPREFIX=/home/lmat/.wine32 mkdir aoe2cd1 fuseiso aoe2cd1.iso aoe2cd1 cd aoe2cd1 wine ./aoesetup.exe ``` The setup ran marvelously. I then went to run the game: ``` cd ~/.wine32/drive_c/Program\ Files/Microsoft\ Games/Age\ of\ Empires\ II wine empires2.exe ``` and I see a window saying, "The program empires2.exe has encountered a serious problem and needs to close....". The details show "Unhandled exception: page fault on read access to 0xffffffff in 32-bit code..." Later down, it shows "Platform: i386" which seems correct. Maybe I need to install some directx or something? The game comes with directx 6 on the CD, I think. -- 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 56818] New: Ruby: Whiteout demo doesn't work correctly on OGL4.2-level drivers
by WineHQ Bugzilla 10 Jun '24

10 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=56818 Bug ID: 56818 Summary: Ruby: Whiteout demo doesn't work correctly on OGL4.2-level drivers Product: Wine Version: 9.10 Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: svyatpro(a)gmail.com Created attachment 76622 --> https://bugs.winehq.org/attachment.cgi?id=76622 log file AMD technology demo Ruby: Whiteout download link: https://www.guru3d.com/download/ruby-whiteout-(ati-technology-demo)/ -- 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 19712] New: Template text instead of usual information in VirtualBox installer
by wine-bugs＠winehq.org 10 Jun '24

10 Jun '24

http://bugs.winehq.org/show_bug.cgi?id=19712 Summary: Template text instead of usual information in VirtualBox installer Product: Wine Version: 1.1.27 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi AssignedTo: wine-bugs(a)winehq.org ReportedBy: b0ntrict0r(a)yandex.ru Created an attachment (id=23024) --> (http://bugs.winehq.org/attachment.cgi?id=23024) Screenshot that illustrates the problem Text labels are filled with a template text instead of components description, installation path, size, etc. in VirtualBox 2.2.4 installer. Text in label (1) substitutes with proper content after selecting component in the tree, and text in label (3) substitutes with proper text after selecting installation path in "Browse" dialog. -- 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 18

[Bug 56801] New: Invalid path to UIAutomationCore.dll in the registry
by WineHQ Bugzilla 10 Jun '24

10 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=56801 Bug ID: 56801 Summary: Invalid path to UIAutomationCore.dll in the registry Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: oleaut32 Assignee: wine-bugs(a)winehq.org Reporter: rikul(a)inbox.ru Distribution: --- Created attachment 76604 --> https://bugs.winehq.org/attachment.cgi?id=76604 test app I'm using the pywinauto library to perform some automatic actions in a GUI. pywinauto, in turn, uses comtypes, which requires the location of UIAutomationCore.dll to work. During this process, comtypes reports that it cannot find UIAutomationCore.dll. It turns out that, comtypes uses windll.oleaut32.QueryPathOfRegTypeLib (that is, the QueryPathOfRegTypeLib from oleaut32.dll) to find UIAutomationCore.dll. Wine 9.0 registry [HKEY_CLASSES_ROOT\Typelib\{8A9CA8EB-856B-43D9-ABD7-4A590054064F}\1.0\0\win64] lists its location as "C:\windows\system32\uiautomationcore.dll\1", while the path in Wine 8.0 is C:\windows\system32\uiautomationcore.dll. Windows registry shows path as C:\windows\system32\uiautomationcore.dll Can the correctness of this behavior be verified? Should it be "C:\windows\system32\uiautomationcore.dll\1" (\1 at the end) or is this the wrong value? I have attached a test application that reports the guid and path from the registry. -- 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 44210] New: GNUTLS_CIPHER_CHACHA20_POLY1305 is not work
by wine-bugs＠winehq.org 10 Jun '24

10 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=44210 Bug ID: 44210 Summary: GNUTLS_CIPHER_CHACHA20_POLY1305 is not work Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: secur32 Assignee: wine-bugs(a)winehq.org Reporter: serg.chaplya(a)gmail.com Distribution: --- Hello! I've tried to run this tool (http://cryptopump.info/en/download) on my Ubuntu system. I got some error: fixme:secur32:schannel_get_cipher_algid unknown algorithm 23 fixme:secur32:schannel_get_mac_algid unknown algorithm 200 fixme:secur32:schannel_get_cipher_algid unknown algorithm 23 fixme:secur32:schannel_get_mac_algid unknown algorithm 200 fixme:secur32:schannel_get_cipher_algid unknown algorithm 23 fixme:secur32:schannel_get_mac_algid unknown algorithm 200 fixme:secur32:schannel_get_cipher_algid unknown algorithm 23 fixme:secur32:schannel_get_mac_algid unknown algorithm 200 I've found that this error is here: https://github.com/wine-mirror/wine/blob/master/dlls/secur32/schannel_gnutl… Because GNUTLS_CIPHER_CHACHA20_POLY1305 is not supported. -- 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 44985] New: BIAS FX: Blank window when running the app
by wine-bugs＠winehq.org 10 Jun '24

10 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=44985 Bug ID: 44985 Summary: BIAS FX: Blank window when running the app Product: Wine Version: 3.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: oxez911(a)gmail.com Distribution: --- Created attachment 61119 --> https://bugs.winehq.org/attachment.cgi?id=61119 term output Distribution: Debian sid Wine version: 3.6.0~sid (Using the wine-devel package from winehq.org) Description: Trying the BIAS FX standalone app (both in 32 and 64bit) result in a blank window (black or white, seems random..) Note: the trial can be downloaded free of change at https://www.positivegrid.com/bias-fx/ I attached a trace of what I saw in the terminal, I can provide more info if needed (I'm not sure what WINEDEBUG needed to be set at, I didn't tweak it) -- 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 66

[Bug 56814] New: "Lossless Scaling" program crashes on launch
by WineHQ Bugzilla 10 Jun '24

10 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=56814 Bug ID: 56814 Summary: "Lossless Scaling" program crashes on launch Product: Wine Version: 9.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: perplexedon(a)gmail.com Distribution: --- Created attachment 76616 --> https://bugs.winehq.org/attachment.cgi?id=76616 3 backtraces for attempts to launch the program with wine. Ubuntu 22.04, x86-64bit AMD. Running wine 9.10, the program fails to launch, outputting the first part (attached). With the 9.10 Wine Mono msi installed via "wine uninstaller", it still fails to launch, outputting the second part. The outputs also mention dotnet48, so I installed this with winetricks --force -q dotnet48, however this gave the third output. This was reproduced identically in clean 64 and 32 bit wineprefixes. Background on the program: Lossless scaling is a tool for real-time GPU driven resolution up-scaling and frame interpolation of other programs. As an example, I use it on Windows to bring the game "Celeste", which is locked to 60fps, up to 165fps graphically without the subtle physics alterations that existing fps increase mods result in. No such tools yet exist natively for Linux, and I am not aware of any others on Windows. -- 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

Jump to page:

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 June 2024