January 2025 - Wine-bugs - list.winehq.org

[Bug 56521] New: ChessBase 17 3D board hangs when opened and isn't drawn
by WineHQ Bugzilla 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=56521 Bug ID: 56521 Summary: ChessBase 17 3D board hangs when opened and isn't drawn Product: Wine Version: 9.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dav75uk(a)yahoo.co.uk Distribution: --- Created attachment 76274 --> https://bugs.winehq.org/attachment.cgi?id=76274 The output from clicking open board When trying to use the 3D board (not the raytraced board), a dialog saying Initializing 3D board pops up. It just hangs after a reasonable wait and the dialog stays showing. No board is drawn. No interesting output occurs if switching to a 2D board and back again (something hanging or a lock in the initialisation maybe). Workaround is to use the 2D board (untick use new 2D board). See attached log which contains everything from opening the board (with its other panes) to the dialog popping up (no further output). -- 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 51603] New: All applications were run with a crash dialog, and can not run any application after re-create the .wine prefix.
by WineHQ Bugzilla 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=51603 Bug ID: 51603 Summary: All applications were run with a crash dialog, and can not run any application after re-create the .wine prefix. Product: Wine-staging Version: 6.14 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: avenjames(a)live.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Created attachment 70452 --> https://bugs.winehq.org/attachment.cgi?id=70452 Backtrace from the crash dialog. Machine: MacBook Pro Retina-2015mid with OSX 10.14.6 Mojave I remember that last time I was using OSX 10.13, I got the same problem. With the Wine-staging from Gcenx's build. But after deleted the .wine and run the Wine-staging again, it was back to work normally, But after playing two games: Red Alert 2 and Diablo II, I don't know if I was playing too long, games was crashed finally and then I run "wineserver -k" to kill all the wine-preloader processes, Then after awhile I wanna to play the game again but it was crashed on the halfway, then I start the Terminal to input: winecfg it was showing: ----------------------------------------------------------------------------- Last login: Sat Aug 14 16:36:30 on ttys000 192:~ avenue$ winecfg 0024:fixme:esync:do_esync eventfd not supported on this platform. 002c:fixme:esync:do_esync eventfd not supported on this platform. 002c:fixme:winediag:LdrInitializeThunk wine-staging 6.14 is a testing version containing experimental patches. 002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org. wine: Unhandled page fault on read access to 0000000000000000 at address 00000003AF6DF950 (thread 002c), starting debugger... 0034:fixme:esync:do_esync eventfd not supported on this platform. 0040:fixme:esync:do_esync eventfd not supported on this platform. 0040:err:display:prepare_devices Failed to remove monitor 0040:err:display:macdrv_init_monitor Failed to initialize monitor 0040:err:display:cleanup_devices Failed to remove GPU 0040:err:ole:start_rpcss Failed to open service manager 0034:err:display:cleanup_devices Failed to remove GPU 0034:err:display:prepare_devices Failed to remove monitor 0034:err:display:macdrv_init_monitor Failed to initialize monitor 0034:err:display:cleanup_devices Failed to remove GPU 0034:fixme:thread:get_thread_times not implemented on this platform 0058:fixme:esync:do_esync eventfd not supported on this platform. 0060:fixme:esync:do_esync eventfd not supported on this platform. 0040:err:ole:start_rpcss Failed to open service manager 0060:err:display:cleanup_devices Failed to remove GPU 0060:err:ole:start_rpcss Failed to open service manager /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Common/ChunkCompression.cpp:49: Error: unsupported compressor 8 /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Libraries/CompressData/CompressData.c:353: Error: Unknown compression scheme encountered for file '/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exceptions.plist' /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Common/ChunkCompression.cpp:49: Error: unsupported compressor 8 /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Libraries/CompressData/CompressData.c:353: Error: Unknown compression scheme encountered for file '/System/Library/CoreServices/CoreTypes.bundle/Contents/Library/AppExceptions.bundle/Exceptions.plist' 0024:err:display:cleanup_devices Failed to remove GPU 0070:fixme:esync:do_esync eventfd not supported on this platform. /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Common/ChunkCompression.cpp:49: Error: unsupported compressor 8 /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Libraries/CompressData/CompressData.c:353: Error: Unknown compression scheme encountered for file '/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exceptions.plist' /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Common/ChunkCompression.cpp:49: Error: unsupported compressor 8 /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Libraries/CompressData/CompressData.c:353: Error: Unknown compression scheme encountered for file '/System/Library/CoreServices/CoreTypes.bundle/Contents/Library/AppExceptions.bundle/Exceptions.plist' 0070:err:display:cleanup_devices Failed to remove GPU 0078:fixme:esync:do_esync eventfd not supported on this platform. 0078:err:display:cleanup_devices Failed to remove GPU 0078:err:display:prepare_devices Failed to remove monitor 0078:err:display:macdrv_init_monitor Failed to initialize monitor 0078:err:display:cleanup_devices Failed to remove GPU 0060:err:display:prepare_devices Failed to remove monitor 0060:err:display:macdrv_init_monitor Failed to initialize monitor 0060:err:display:cleanup_devices Failed to remove GPU 0078:err:winecfg:open_mountmgr failed to open mount manager err 2 192:~ avenue$ 0060:err:ole:start_rpcss Failed to open service manager --------------------------------------------------------------------------------- Then I tried to input: rm -rf .wine and run again the winecfg to recreate the files, it said: ---------------------------------------------------------------------------------- 192:~ avenue$ winecfg wine: created the configuration directory '/Users/avenjames/.wine' 0024:fixme:esync:do_esync eventfd not supported on this platform. 002c:fixme:esync:do_esync eventfd not supported on this platform. 002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 002c:fixme:winediag:LdrInitializeThunk wine-staging 6.14 is a testing version containing experimental patches. 002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org. wine: Unhandled page fault on read access to 0000000000000000 at address 00000003AF6DF950 (thread 002c), starting debugger... 002c:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 40 48" (2) Read the Wine Developers Guide on how to set up winedbg or another debugger wine: could not load kernel32.dll, status c0000135 192:~ avenue$ ---------------------------------------------------------------------------------- Then WINE CAN NOT RUN ANY APPLICATION AGAIN, even tried brew re-install the wine but it was still couldn't make it. attached backtrace.txt for checking. -- 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 57688] New: secur32:GetUserNameExW NameFormat [8,12] not implemented
by WineHQ Bugzilla 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57688 Bug ID: 57688 Summary: secur32:GetUserNameExW NameFormat [8,12] not implemented Product: Wine Version: 10.0-rc5 Hardware: x86-64 URL: https://learn.microsoft.com/en-us/windows/win32/api/se cext/ne-secext-extended_name_format OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: secur32 Assignee: wine-bugs(a)winehq.org Reporter: winehq.tabloid372(a)passmail.net Distribution: Fedora In ``` 0148:fixme:secur32:GetUserNameExW NameFormat 8 not implemented 0158:fixme:secur32:GetUserNameExW NameFormat 12 not implemented ``` enum values not handled in the switch https://github.com/wine-mirror/wine/blob/master/dlls/secur32/secur32.c#L1166 ``` NameUserPrincipal = 8, [..] NameDnsDomain = 12, ``` Since `NameSamCompatible` is already implemented in the upper part of the switch and we have a domain then `NameDnsDomain` should be composable in a fairly trivial way. Additionally, `NameUserPrincipal` seems to be a simpler version of that logic with a calls to: ``` GetUserNameW(usrname, &len)) GetComputerNameW(samname, &len)) -> usrname+'@'+samname. ``` If I am not mistaken? -- 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 56843] New: wineandroid: fixing output on recent android versions.
by WineHQ Bugzilla 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=56843 Bug ID: 56843 Summary: wineandroid: fixing output on recent android versions. Product: Wine Version: unspecified Hardware: aarch64 OS: Android Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: twaikyont(a)gmail.com Currently wineandroid relies on Gralloc V1 which is not an option on recent android versions. There is other acceptable solution. You can pass Surface through Binder API so you will get ANativeWindow (or at least Surface which can be converted to ANativeWindow) directly from Activity instead of creating it with broken `alloc_win_data`. Binder API is not available in regular processes, but you can use it in Java. You can start java code from your Wine apk installed to system like ``` export CLASSPATH=<path to apk> export LD_PRELOAD=<path to apk>!/lib/<ABI>/libwine.so # wher ABI is something you can get with `Build.SUPPORTED_ABIS[0]` /system/bin/app_process / your.class.name :0 ``` And JVM will start the `static void main(String[] args);` from `your.class.name`. Getting path to apk will be like ``` /** * Get the apk path of this application. * @param context any context (e.g. an Activity or a Service) * @return full apk file path, or null if an exception happened (it should not happen) */ public static String getApkName(Context context) { String packageName = context.getPackageName(); PackageManager pm = context.getPackageManager(); try { return pm.getApplicationInfo(packageName, 0).publicSourceDir; } catch (Throwable x) { } return null; } ``` `main` function can be fully native so you can simply pass control to native code right after starting process. Of course wine's main executable should be built as a library to let JVM load it via `System.loadLibrary` C version of `main` can not use Java's `args` so it should be converted like ``` JNIEXPORT jboolean JNICALL Java_wine_CmdEntryPoint_start(JNIEnv *env, __unused jclass cls, jobjectArray args) { pthread_t t; // execv's argv array is a bit incompatible with Java's String[], so we do some converting here... int argc = (*env)->GetArrayLength(env, args) + 1; // Leading executable path char** argv = (char**) calloc(argc, sizeof(char*)); argv[0] = (char*) "wine"; for(int i=1; i<argc; i++) { jstring js = (jstring)((*env)->GetObjectArrayElement(env, args, i - 1)); const char *pjc = (*env)->GetStringUTFChars(env, js, JNI_FALSE); argv[i] = (char *) calloc(strlen(pjc) + 1, sizeof(char)); //Extra char for the terminating NULL strcpy((char *) argv[i], pjc); (*env)->ReleaseStringUTFChars(env, js, pjc); } return main(argc, argv); } ``` After this point you will be able to use java code and java Android APIs. Next step is obtaining Binder connection to your activity. It is not very straightforward but it is possible. Full code will be pretty much long so I will simply put links to my project which works on Android 8+. Pay attention to functions sendBroadcast and createContext (createContext is used in static block in the end of file). It requires exposing some private Android APIs, but it is not restricted if you are using app_process this way. https://github.com/termux/termux-x11/blob/master/app/src/main/java/com/term… Make sure you are creating thread with performing `Looper.prepareMainLooper();` and `Looper.loop()` to make sure Binder background requests will work fine in static block (to make sure it will work before JVM invokes `main` function, just for case it is `native`). Next step will be acquiring Surface from Wine's activity. Of course you can create AIDL with single function like `Surface getSurface(int hwnd);` and obtain Surface directly from `alloc_win_data` or simillar function via JNI. But in my cases it did not work. I mean sending request from my process to Activity which should respond with Surface object did not work. But I succeeded passing Surface by sending requst from Activity to my process containing Surface in arguments like `void pushSurface(in Surface surface, int hwnd);`. Binder request from Activity to your process will work in different thread asyncronously so `alloc_win_data` should send surface request to activity and wait for Binder response or timeout. I hope I explained everything with enough details. Thank you for your hard work. -- 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 47345] New: When clicking on the Drivers tab, winecfg crashes
by wine-bugs＠winehq.org 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=47345 Bug ID: 47345 Summary: When clicking on the Drivers tab, winecfg crashes Product: Wine Version: 4.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: soulsofblack12(a)hotmail.com Distribution: --- Created attachment 64676 --> https://bugs.winehq.org/attachment.cgi?id=64676 The error I am running wine-staging, when i launch winecfg from the console and try to click on the Drivers tab, winecfg crashes and closes itself. -- 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 4

[Bug 57122] New: When clicking on the image in the WeChat group chat and attempting to enlarge it, a program error is reported
by WineHQ Bugzilla 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57122 Bug ID: 57122 Summary: When clicking on the image in the WeChat group chat and attempting to enlarge it, a program error is reported Product: Wine Version: 9.0-rc5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rayklaus(a)163.com Distribution: --- Created attachment 77012 --> https://bugs.winehq.org/attachment.cgi?id=77012 file saved according to prompts when the program crashes linux info: PRETTY_NAME="Ubuntu 24.04.1 LTS" NAME="Ubuntu" VERSION_ID="24.04" VERSION="24.04.1 LTS (Noble Numbat)" VERSION_CODENAME=noble ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" UBUNTU_CODENAME=noble LOGO=ubuntu-logo wineinfo: ii wine 9.0~repack-4build3 all Windows API implementation - standard suite ii wine32:i386 9.0~repack-4build3 i386 Windows API implementation - 32-bit binary loader ii wine64 9.0~repack-4build3 amd64 Windows API implementation - 64-bit binary loader ii winetricks 20240105-2 all simple tool to work around common problems in Wine -- 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 57201] New: EA client cannot launch game after wine 8.17+
by WineHQ Bugzilla 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57201 Bug ID: 57201 Summary: EA client cannot launch game after wine 8.17+ Product: Wine Version: 8.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: steampunque8(a)gmail.com Distribution: --- Created attachment 77096 --> https://bugs.winehq.org/attachment.cgi?id=77096 last steps of bisect wine 8.16 was able to launch old origin games with the new EA client. with wine 8.17 and above, some kind of an arcane error message is given and the launch fails. I bisected the problem to 917d6afa695ba8d5124a11b02b18c6777cc9e56c, wbemprox: Implement Win32OperatingSystem.Installdate. The last stages of the bisect are attached. OS is Slackware 15.0, x86_64, RTX 4070. Windows version is set to 10 in winecfg. I don't know if this affects other than old origin games as I only have one origin game that I ever launch (and that very rarely), PvZ GoTY. -- 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 57328] New: little garden spectrometer V0.2.exe crashes when trying to select the USB camera
by WineHQ Bugzilla 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57328 Bug ID: 57328 Summary: little garden spectrometer V0.2.exe crashes when trying to select the USB camera Product: Wine Version: 9.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jonstew1983+wine(a)gmail.com Distribution: --- Created attachment 77278 --> https://bugs.winehq.org/attachment.cgi?id=77278 Console output from Wine including crash message little garden spectrometer V0.2.exe can be downloaded from https://drive.google.com/drive/folders/1i7VcQxSc1r_lNGZZ3H5pEf1PhfrYwtP5 The hardware is from https://www.aliexpress.us/item/1005007241834839.html but it also crashes trying to access my laptop USB camera. Wine was installed with the command `sudo dnf install wine --allowerasing` on Linux fedora 6.10.12-200.fc40.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Sep 30 21:38:25 UTC 2024 x86_64 GNU/Linux -- 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 57728] New: Sensitivity of relative mouse movement is scaled by coefficient of desktop scaling
by WineHQ Bugzilla 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57728 Bug ID: 57728 Summary: Sensitivity of relative mouse movement is scaled by coefficient of desktop scaling Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: lassebq.mine(a)gmail.com Distribution: --- I am using GNOME Wayland session with main monitor (1440p) running at 125% desktop scale. Currently there's a bug with application scaling being done separately based on DPI value, so I set DPI to 120 https://bugs.winehq.org/show_bug.cgi?id=56285 In all first person games the same mouse travel distance leads to a higher camera rotation angle in game. So if a game has a sensitivity slider, to get the same mouse sensitivity as you had at 100% scale, you need to divide this value by your desktop scale (in this case, 1.25) and apply changes to these settings on per-game basis. Obviously, not an ideal workaround and requires to do a lot of tweaking. -- 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 57774] New: "Application must be updated" with Wine 10, MacOS Sequoia 15.3 MacBook Pro M4 pro
by WineHQ Bugzilla 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57774 Bug ID: 57774 Summary: "Application must be updated" with Wine 10, MacOS Sequoia 15.3 MacBook Pro M4 pro Product: Wine Version: 10.0 Hardware: arm OS: MacOS Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jean.pierre.cointre(a)gmail.com Created attachment 77975 --> https://bugs.winehq.org/attachment.cgi?id=77975 MacBook Pro System Report I bought my MacBook Pro with M4 pro processor yesterday. MacOS is up to date with MacOS Sequoia 15.3 I followed the WineHQ installation doc (authorization in Gatekeeper and install XQuartz-2.8.5.pkg) and installation was fine. Unfortunately, "Wine Stable" in the LaunchPad is gray and when I open it, I have the message "Application must be updated". If I browse to the MacOS sub folder and run the executable, I can read "zsh: bad CPU type in executable: /Applications/Wine Stable.app/Contents/MacOS/wine". I attach the MacBook Pro System 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.

1 1