wine-bugs June 2023

wine-bugs@winehq.org

1 participants
2826 discussions

[Bug 53155] New: msys2 cannot be installed under wine
by WineHQ Bugzilla 13 May '25

13 May '25

https://bugs.winehq.org/show_bug.cgi?id=53155 Bug ID: 53155 Summary: msys2 cannot be installed under wine Product: Wine Version: 7.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hramrach(a)gmail.com Distribution: --- Created attachment 72589 --> https://bugs.winehq.org/attachment.cgi?id=72589 terminal output There is a number of bugs that reference msys2 but all are marked as staging sp presumably they should be addressed in the staging version. nonetheless msys2 installer gets still stuck at 66% sha256sum Downloads/msys2-x86_64-20220603.exe 6e5a76e36a651542e6b907a39776effb7670a139d6a017c3808fdcfaca84ee83 Downloads/msys2-x86_64-20220603.exe -- 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 25

[Bug 53620] New: err:ole:com_get_class_object class {2d3468c1-36a7-43b6-ac24-d3f02fd9607a} not registered
by WineHQ Bugzilla 12 May '25

12 May '25

https://bugs.winehq.org/show_bug.cgi?id=53620 Bug ID: 53620 Summary: err:ole:com_get_class_object class {2d3468c1-36a7-43b6-ac24-d3f02fd9607a} not registered Product: Wine Version: 7.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: wuyudi1109(a)gmail.com Distribution: --- I run a game, and it shows this. ``` 0454:err:ole:com_get_class_object class {2d3468c1-36a7-43b6-ac24-d3f02fd9607a} not registered 0454:err:ole:com_get_class_object no class object {2d3468c1-36a7-43b6-ac24-d3f02fd9607a} could be created for context 0x1 ``` Then crash. According to https://wiki.winehq.org/Wine_Developer%27s_Guide/COM_in_Wine#Writing_COM_Co… I find it's about shell32.dll. And I find that this key is not in wine's reg. So how can I fix it? (I tried to add it by hand, but still not work.) Also, I found this in [wine's code](https://github.com/wine-mirror/wine/blob/master/include/shobjidl.idl) ``` [ uuid(2d3468c1-36a7-43b6-ac24-d3f02fd9607a) ] coclass EnumerableObjectCollection { interface IEnumObjects; } ``` -- 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 48361] New: Honkai Impact 3rd doesn't start
by WineHQ Bugzilla 10 May '25

10 May '25

https://bugs.winehq.org/show_bug.cgi?id=48361 Bug ID: 48361 Summary: Honkai Impact 3rd doesn't start Product: Wine Version: 5.0-rc2 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Without wine-staging the game crashes, with wine-staging the game simply "terminates". The log simply says ###### 000b:fixme:winediag:__wine_start_process Wine Staging 5.0-rc2 is a testing version containing experimental patches. 000b:fixme:winediag:__wine_start_process Please mention your exact version when filing bug reports on winehq.org. Terminated ###### Any logs I should provide? -- 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 18

[Bug 52254] New: Cold Steel Subs: Application is not transparent (relies on DwmExtendFrameIntoClientArea)
by WineHQ Bugzilla 09 May '25

09 May '25

https://bugs.winehq.org/show_bug.cgi?id=52254 Bug ID: 52254 Summary: Cold Steel Subs: Application is not transparent (relies on DwmExtendFrameIntoClientArea) Product: Wine Version: 7.0-rc2 Hardware: x86-64 URL: https://zerofield.net/2020/09/30/hajimari-no-kiseki-sp readsheet-translation/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dwmapi Assignee: wine-bugs(a)winehq.org Reporter: johnny(a)localmomentum.net Distribution: --- Created attachment 71376 --> https://bugs.winehq.org/attachment.cgi?id=71376 ColdSteelSubs transparency code (currently not in the distributed application) This application provides a transparent clickthrough overlay to show English translations on top of the original Japanese source. It relies on layered windows and DwmExtendFrameIntoClientArea to handle the transparent display. Currently, the main UI elements show, but the game (or any other application) does not show through. This seems to be because DwmExtendFrameIntoClientArea is only a stub. I'm not sure if that's the only reason it's not transparent, but it's at least one of the reasons. The program itself uses the unity3d engine along with some native dll calls to the relevant user32 apis to handle the transparency. I was able to get a copy of the relevant code (but not the whole application), of which I will attach. Since I can't get all of the code, I've been using an unity sample application to try to figure out some parts myself (the relevant code is here https://github.com/pheonise/Unity3D-Desktop-Overlay/blob/master/Assets/Scri…). This unity3d application works as expected on windows, but is not transparent via wine (as expected). When i comment the call to DwmExtendFrameIntoClientArea, then it its also no longer transparent on windows as well. It seems that if the sample application works, then I can make sure the dev applies to the same technique to the overlay application. Please let me know If i can provide any more information. -- 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 53574] New: MSYS2 "pacman -Sy" fails key lookup
by WineHQ Bugzilla 06 May '25

06 May '25

https://bugs.winehq.org/show_bug.cgi?id=53574 Bug ID: 53574 Summary: MSYS2 "pacman -Sy" fails key lookup Product: Wine Version: 7.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: joel(a)airwebreathe.org.uk Distribution: --- Created attachment 72951 --> https://bugs.winehq.org/attachment.cgi?id=72951 Log of console interaction With a fresh Msys2 installation, pacman fails to run, because it keeps producing "key lookup failed" errors. The user is prompted to with the following message: error: mingw32: key "5F944B027F7FE2091985AA2EFA11531AA0AA7F57" is unknown :: Import PGP key 5F944B027F7FE2091985AA2EFA11531AA0AA7F57? [Y/n] Y However, if the user selects "yes", pacman simply asks the same question again after a short delay, in an infinite loop. -- 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 55138] New: msys2: bash.exe is not able to fork/start another process.
by WineHQ Bugzilla 06 May '25

06 May '25

https://bugs.winehq.org/show_bug.cgi?id=55138 Bug ID: 55138 Summary: msys2: bash.exe is not able to fork/start another process. Product: Wine Version: 8.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Created attachment 74697 --> https://bugs.winehq.org/attachment.cgi?id=74697 allocation stacks in parent and child bash.exe This is a followup to bug 47808. If I understand it right, bug 47808 was primarily about native libraries getting called at a win32 stack which was not yet committed. Those native libraries then jumped over the guard page, therefore the stack got not grown, instead a crash reported. This aspect was fixed by using the syscall interface and therefore bug 47808 was closed. But there is another issue that causes a msys2-forked process crashing, because after the stack was grown it still misses the PAGE_READWRITE flags. For this Zeb Figura included in the first attachement to bug 47808 "always expand the stack if within the stack reserve" a line adding the flags "VPROT_COMMITTED | VPROT_READ | VPROT_WRITE" to the page that gets the VPROT_GUARD removed in grow_thread_stack. This modification still enables a forked process to run. The issue can be reproduced with an unmodified wine by just - running msys2 bash.exe interactively - then trying to start e.g. notepad from it. Attached file shows the stack when the stack gets allocated - in a working msys2-parent process and - in a failing msys2-forked child process. Therefore it looks like the forked stack get really setup differently, but it is still not clear if or when this memory gets the READ/WRITE added in native 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 8

[Bug 53121] New: IrfanView: In full screen mode the image title is not correctly repainted when switching between images
by WineHQ Bugzilla 05 May '25

05 May '25

https://bugs.winehq.org/show_bug.cgi?id=53121 Bug ID: 53121 Summary: IrfanView: In full screen mode the image title is not correctly repainted when switching between images Product: Wine Version: 7.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- Created attachment 72576 --> https://bugs.winehq.org/attachment.cgi?id=72576 Example Steps to reproduce: 1. Download IrfanView 2. File -> Open an image file (which matches or exceeds your display resolution) 3. Press Enter (goes in full screen mode) 4. Press right arrow or left arrow (alternatively "Space" and "Back Space") to browse through images forward or backward. The area where the image path and name are being rendered starts to look bad (i.e. it's not correctly repainted). It's in the left top corner. The example is attached. -- 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 42284] New: Enable using Wine with Wayland and without X on Linux
by wine-bugs＠winehq.org 05 May '25

05 May '25

https://bugs.winehq.org/show_bug.cgi?id=42284 Bug ID: 42284 Summary: Enable using Wine with Wayland and without X on Linux Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shtetldik(a)gmail.com Distribution: --- Currently, Wine on Linux is strongly dependent on X, and when used with the desktop environment with new Wayland display server, Wine is forced to run through XWayland, which so far remains a poor experience. The whole Linux desktop is now strongly pushing the switch from X to Wayland, and many major applications are now in the process of enabling this switch. Is there some plan for such effort in Wine? Is it even feasible? I couldn't find any bugs opened for it, so I'm opening one here to track this. -- 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 77

[Bug 10941] New: Wine does not print in a newly allocated console window
by wine-bugs＠winehq.org 04 May '25

04 May '25

http://bugs.winehq.org/show_bug.cgi?id=10941 Summary: Wine does not print in a newly allocated console window Product: Wine Version: 0.9.52. Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wine-console AssignedTo: wine-bugs(a)winehq.org ReportedBy: mail2benny(a)gmail.com Created an attachment (id=9867) --> (http://bugs.winehq.org/attachment.cgi?id=9867) The binary which recreates the bug Wine does not print in a newly allocated console window using the function FreeConsole(); and AllocConsole(); I've written a program which recreates the bug. I'll post the binary and the source. (compiled on Dev-C++ 4.9.9.2, in Wine) -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 25

[Bug 54336] New: Wow64 compatibility breaks on newer 64-bit glibc releases
by WineHQ Bugzilla 03 May '25

03 May '25

https://bugs.winehq.org/show_bug.cgi?id=54336 Bug ID: 54336 Summary: Wow64 compatibility breaks on newer 64-bit glibc releases Product: Wine Version: 8.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ruanformigoni(a)gmail.com Distribution: --- Newer versions of 64-bit glibc break current Wow64 compatibility implementation. For a new vm of fedora 36: $ ./wine-ge-7-35-continuous-x86_64.AppImage --version Usage: wine PROGRAM [ARGUMENTS...] Run the specified program wine --help Display this help and exit wine --version Output version information and exit glibc.x86_64 version is 2.35-20.fc36 glibc.i686 is not installed. -- For a new vm of fedora 37: $ /wine-ge-7-35-continuous-x86_64.AppImage --version /tmp/.mount_wine-gEI9DJM/bin/wine: No such file or directory glibc.x86_64 version is 2.36-9.fc37 glibc.i686 is not installed (installing fixes 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.

1 20

← Newer
1
2
3
4
5
6
7
8
...
283
Older →

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