November 2024 - Wine-bugs - list.winehq.org

[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 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 05 Feb '25

05 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