wine-bugs June 2024

wine-bugs@winehq.org

1 participants
2130 discussions

[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 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 42741] New: StarCraft I: 1.18 PTR fails to initialize ClientSdk.dll
by wine-bugs＠winehq.org 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=42741 Bug ID: 42741 Summary: StarCraft I: 1.18 PTR fails to initialize ClientSdk.dll Product: Wine Version: 2.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: li.davidm96(a)gmail.com Distribution: --- Created attachment 57743 --> https://bugs.winehq.org/attachment.cgi?id=57743 stderr output of Wine when running StarCraft.exe The 1.18 public test release of the upcoming version of StarCraft I does not launch, as ClientSdk.dll fails to initialize. Tested with Wine 2.4 (latest from Arch repositories), in a fresh 64-bit wineprefix. Architecture is AMD64. The download is here: https://us.battle.net/forums/en/starcraft/topic/20753915707 sha1sum: 2d6702a425f13659227814fbc903568d63daeb08 /home/lidavidm/Downloads/Starcraft+1.18+PTR+1202.zip -- 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 133

[Bug 51092] New: reMarkable desktop app - Software Updater indefinetly runs
by WineHQ Bugzilla 06 Feb '25

06 Feb '25

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

[Bug 33199] New: iexplore crash when changing location.href in if stamtement xhtml
by wine-bugs＠winehq.org 06 Feb '25

06 Feb '25

http://bugs.winehq.org/show_bug.cgi?id=33199 Bug #: 33199 Summary: iexplore crash when changing location.href in if stamtement xhtml Product: Wine Version: 1.5.25 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: thepouar(a)gmail.com Classification: Unclassified Created attachment 43914 --> http://bugs.winehq.org/attachment.cgi?id=43914 xhtml file that crashes iexplore iexplore crashes when trying to change the URL in javascript within an if statement, attached a file that causes the crash -- 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 12

[Bug 54350] New: WHERE does not work
by WineHQ Bugzilla 06 Feb '25

06 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=54350 Bug ID: 54350 Summary: WHERE does not work Product: Wine Version: 8.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: giecrilj(a)stegny.2a.pl Distribution: --- > WHERE /? (no 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 11

[Bug 40570] New: Skype 7 - Unhandled exception in thread 9 or Unhandled page fault on read access
by wine-bugs＠winehq.org 05 Feb '25

05 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=40570 Bug ID: 40570 Summary: Skype 7 - Unhandled exception in thread 9 or Unhandled page fault on read access Product: Wine Version: 1.9.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rmoisto(a)gmail.com Distribution: --- The latest Skype desktop client for Windows (currently 7.23.0.105) does not work with wine 1.9.9 but works fine with 1.9.7 and 1.9.8. Starting Skype with 1.9.9 spits out various errors. In some instances Skype.exe will go in an infinite loop and the debugger hangs, other times the debugger exists instantly. Exists cleanly: wine: Unhandled exception 0xc0000409 in thread 9 at address 0x115d6b8 (thread 0009), starting debugger... Hangs forever: wine: Unhandled page fault on write access to 0x65756cf1 at address 0x63656ee6 (thread 0009), starting debugger... I can attach more console output if needed. -- 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

[Bug 52592] New: MilkyTracker does not work: no valid waveout devices.
by WineHQ Bugzilla 05 Feb '25

05 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=52592 Bug ID: 52592 Summary: MilkyTracker does not work: no valid waveout devices. Product: Wine Version: unspecified Hardware: aarch64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: carlo.bramix(a)libero.it Distribution: --- MilkyTracker is an multi-platform music application for creating .MOD and .XM module files. https://github.com/milkytracker/MilkyTracker Unfortunately, it doesn't work on WINE because it cannot open any waveout device. Sources of MilkyTracker do these actions: 1) waveOutOpen(&hwo, WAVE_MAPPER, &format, 0, 0, CALLBACK_NULL); This call is a success and it returns a valid handle. 2) waveOutGetID(hwo,(LPUINT)&waveOutID); This call also returns success and it returns a value of 63 into "waveOutID". BUT THIS IS WRONG. "waveOutID" should be equal to WAVE_MAPPER, which equal to -1, as you can see in point (1). 3) waveOutGetDevCaps((UINT)waveOutID, &waveoutcaps, sizeof(waveoutcaps)); As result, this call to waveOutGetDevCaps() fails with return value of MMSYSERR_BADDEVICEID. Here there is the point where there is the code that I'm talking about: https://github.com/milkytracker/MilkyTracker/blob/4f97b7011b20519890e30368e… The cause of the trouble is the way the function waveOutGetID() is implemented. waveOutGetID() calls WINMM_GetDeviceFromHWAVE(). And WINMM_GetDeviceFromHWAVE() calls WINMM_DecomposeHWAVE() Into WINMM_DecomposeHWAVE(), there are these lines: ULONG32 l = HandleToULong(hwave); *device_index = l & 0xFF; But this is wrong, because *device_index will be never able to return -1 that is the value for WAVE_MAPPER. -- 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 16

[Bug 48605] New: MuseScore 3 shows splash screen, then quits
by WineHQ Bugzilla 05 Feb '25

05 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=48605 Bug ID: 48605 Summary: MuseScore 3 shows splash screen, then quits Product: Wine Version: 5.1 Hardware: x86-64 URL: https://musescore.org/ OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tobbi.bugs(a)googlemail.com $ wine --version wine-5.1 $ openssl sha256 MuseScore-3.4.2-x86_64.msi SHA256(MuseScore-3.4.2-x86_64.msi)= 8d2fc9d79cb0a5b0a8a5ccbb8ec80a972d1ecd264cb416c75ae42ab0b8b6d475 Steps to reproduce: 1. Install MuseScore using msiexec. 2. Start the game after installation of using the explorer. Expected result: MuseScore starts and shows the main window. Current result: MuseScore shows a splash screen and then quits. -- 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

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 2024