July 2024 - Wine-Bugs - list.winehq.org

[Bug 45416] New: mousepointer of runes of magic disapears if the window gets blurred and refocused
by wine-bugs＠winehq.org Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=45416 Bug ID: 45416 Summary: mousepointer of runes of magic disapears if the window gets blurred and refocused Product: Wine Version: 3.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winebugs(a)evolution-hosting.eu Distribution: Fedora Version: wine-3.11-1.fc27.x86_64 / wine-staging-common-3.11-1.i686 mousepointer of runes of magic disapears if the window gets blurred and refocused aka.. mouse out of the window and back in. After selecting an item in the back, it gets back to normal, but if you can't hit one, the mousepointer gets only updated when left or right mb is pressed. the button click just updates the position, but it does not stop the problem, only a item drop (in the bag ) does. it was no problem with this version: # cat /root/wine.works.rpm.liste mingw32-wine-gecko-2.47-2.fc26.noarch mingw64-wine-gecko-2.47-2.fc26.noarch wine-2.10-1.fc25.i686 wine-2.10-1.fc25.x86_64 wine-alsa-2.10-1.fc25.i686 wine-alsa-2.10-1.fc25.x86_64 wine-arial-fonts-2.10-1.fc25.noarch wine-capi-2.10-1.fc25.i686 wine-capi-2.10-1.fc25.x86_64 wine-cms-2.10-1.fc25.i686 wine-cms-2.10-1.fc25.x86_64 wine-common-2.10-1.fc25.noarch wine-core-2.10-1.fc25.i686 wine-core-2.10-1.fc25.x86_64 wine-courier-fonts-2.10-1.fc25.noarch wine-debuginfo-1.9.3-1.fc23.x86_64 wine-desktop-2.10-1.fc25.noarch wine-filesystem-2.10-1.fc25.noarch wine-fixedsys-fonts-2.10-1.fc25.noarch wine-fonts-2.10-1.fc25.noarch wine-ldap-2.10-1.fc25.i686 wine-ldap-2.10-1.fc25.x86_64 wine-marlett-fonts-2.10-1.fc25.noarch wine-mono-4.7.0-1.fc25.noarch wine-ms-sans-serif-fonts-2.10-1.fc25.noarch wine-openal-2.10-1.fc25.i686 wine-openal-2.10-1.fc25.x86_64 wine-opencl-2.10-1.fc25.i686 wine-opencl-2.10-1.fc25.x86_64 wine-pulseaudio-2.10-1.fc25.i686 wine-pulseaudio-2.10-1.fc25.x86_64 wine-small-fonts-2.10-1.fc25.noarch wine-staging-2.10-1.i686 wine-staging-common-2.10-1.i686 wine-symbol-fonts-2.10-1.fc25.noarch wine-systemd-2.10-1.fc25.noarch wine-system-fonts-2.10-1.fc25.noarch wine-tahoma-fonts-2.10-1.fc25.noarch wine-tahoma-fonts-system-2.10-1.fc25.noarch wine-times-new-roman-fonts-2.10-1.fc25.noarch winetricks-20170517-1.fc25.noarch wine-twain-2.10-1.fc25.i686 wine-twain-2.10-1.fc25.x86_64 wine-wingdings-fonts-2.10-1.fc25.noarch -- 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 3

[Bug 35179] New: Quake Live standalone login window crashes when TAB pressed
by wine-bugs＠winehq.org Feb. 7, 2025

Feb. 7, 2025

http://bugs.winehq.org/show_bug.cgi?id=35179 Bug ID: 35179 Summary: Quake Live standalone login window crashes when TAB pressed Product: Wine Version: 1.7.8 Hardware: x86-64 URL: http://quakelive.com OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: alexandru.balut(a)gmail.com Classification: Unclassified Steps to reproduce: 1. Open QuakeLive's Launcher.exe 2. Wait a few seconds for the round Play button to become red. At this point the username field should be focused. 3. Press TAB three times, notice the app crashes $ sha1sum .wine-ql/drive_c/Program\ Files\ $x86$/Quake\ Live/Launcher.exe b4d565634bdac72047790d64dbc870b8b8bb5f48 .wine-ql/drive_c/Program Files (x86)/Quake Live/Launcher.exe $ sha1sum QuakeLiveSetup_840.exe 843d1542bccaaf1bd46bee0acec95d4bfdfc898b QuakeLiveSetup_840.exe $ wine --version wine-1.7.8 -- 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 16

[Bug 53953] New: Recent Wine 7.21 commit makes the build environment unable to detect 32-bit FreeType 2 libraries on Fedora
by WineHQ Bugzilla Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=53953 Bug ID: 53953 Summary: Recent Wine 7.21 commit makes the build environment unable to detect 32-bit FreeType 2 libraries on Fedora Product: Wine Version: 7.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: build-env Assignee: wine-bugs(a)winehq.org Reporter: nanotwerp(a)gmail.com Distribution: --- The commit in question is the one linked here: https://gitlab.winehq.org/wine/wine/-/commit/c7a97b5d5d56ef00a0061b75412c6e… -- 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 33

[Bug 46740] New: Photoshop CS5 crashes upon opening in Wine-4.0
by wine-bugs＠winehq.org Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=46740 Bug ID: 46740 Summary: Photoshop CS5 crashes upon opening in Wine-4.0 Product: Wine Version: 4.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Syogren.Asherushi(a)gmail.com Distribution: --- Created attachment 63744 --> https://bugs.winehq.org/attachment.cgi?id=63744 The backtrace See attachment. -- 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 3

[Bug 54510] New: d3d11:d3d11 - test_tgsm() fails in 32-bit tests on the debian11 VM
by WineHQ Bugzilla Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=54510 Bug ID: 54510 Summary: d3d11:d3d11 - test_tgsm() fails in 32-bit tests on the debian11 VM Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d3d11:d3d11 - test_tgsm() fails in 32-bit tests on the debian11 VM: d3d11.c:25778: Test failed: Got 0, expected 33 (index 1). d3d11.c:25778: Test failed: Got 0, expected 66 (index 2). ... d3d11.c:25810: Test failed: Got 0, expected 32 (index 0). d3d11.c:25810: Test failed: Got 0, expected 96 (index 1). ... d3d11.c:25852: Test failed: Got 0.00000000e+000, expected 1 (index 32). d3d11.c:25854: Test failed: Got 0, expected 1 (index 32). d3d11.c:25852: Test failed: Got 0.00000000e+000, expected 2 (index 33). d3d11.c:25854: Test failed: Got 0, expected 2 (index 33). ... See https://test.winehq.org/data/patterns.html#d3d11:d3d11 These failures are close to 100% reproducible (but not quite) and started on 2023-02-14. But note that the test also has a preexisting crash which masks these failures in the test pattern. Interestingly these failures do not happen: * In the wow32 and wow64 tests (note: debian11b is a clone of debian11). * On my fgtb-debian11 VM. * On the debiant VM. -- 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 56521] New: ChessBase 17 3D board hangs when opened and isn't drawn
by WineHQ Bugzilla Feb. 7, 2025

Feb. 7, 2025

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 Feb. 7, 2025

Feb. 7, 2025

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 56843] New: wineandroid: fixing output on recent android versions.
by WineHQ Bugzilla Feb. 7, 2025

Feb. 7, 2025

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 Feb. 7, 2025

Feb. 7, 2025

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 51092] New: reMarkable desktop app - Software Updater indefinetly runs
by WineHQ Bugzilla Feb. 6, 2025

Feb. 6, 2025

https://bugs.winehq.org/show_bug.cgi?id=51092 Bug ID: 51092 Summary: reMarkable desktop app - Software Updater indefinetly runs Product: Wine Version: 5.0.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: graeme.wiebe(a)gmail.com Distribution: --- Quite simple: the software updater runs indefinitely, which can be easily solved by closing the popup. -- 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