September 2024 - Wine-Devel

Carry flag state after a system function call

by robert.ayrapetyan＠gmail.com

Hello, some legacy applications depend on the carry flag state after calling system functions. I've noticed that certain apps work correctly when using Wine installed from packages, but fail when Wine is built from sources. After investigating, I found that Wine from Debian packages is compiled with certain flags that stabilize ESP at the end of system function calls (e.g., sub ESP, 0x10), which, as a side effect, clears the carry flag, making the application happy. I tried using fno-omit-frame-pointer, but it generates lea instructions, which don't impact the carry flag. Has anyone else encountered same behavior? How frequently do older applications rely on the carry flag after system function calls? Also, which specific flags are used to compile the Wine version available in Debian packages?

Sept. 24, 2024

Gitlab forks limit issue

by robert.ayrapetyan＠gmail.com

Hello, could you please let me know who I should contact to increase the quotas for my account (rayrapetyan) on https://gitlab.winehq.org/wine? I'm currently unable to fork Wine from https://gitlab.winehq.org/wine/wine/-/forks/new due to the following error: "Limit reached. You cannot create projects in your personal namespace. Contact your GitLab administrator." Also, would you consider accepting a merge request that modifies the GetDriveTypeA\W function to prioritize the mount manager? Let me know if this was discussed somewhere already.

Sept. 24, 2024

Wine staging 9.18 release

by Alistair Leslie-Hughes

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 9.18 (361 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * None Removed (No longer required). * None Added: * None Updated: * vkd3d-latest * ntdll-WRITECOPY Where can you help * Run Steam/Battle.net/GOG/UPlay/Epic * Test your favorite game. * Test your favorite applications. * Improve staging patches and get them accepted upstream. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

Sept. 21, 2024

Staging WRITECOPY fixes

by DodoGTA GT

Hello, I found a few issues with the WRITECOPY patch after wine-staging commit ae46f56f2cf20585387ff61cb7b36fd5f3d84837 which I managed to pretty much fix Patch 0003 is a replacement for the previous 0003 patch (apparently very early signal handling is still needed for some Unix-side ntdll functions); the added early argument checks could be replaced with NtCurrentTeb() instead (this would lead to 2 identical signal_init_process() calls though which may look weird) Patch 0004 updates the previous 0004 patch by removing a forgotten i386 compile-time check (which didn't make sense after that wine-staging commit) Patch 0005 is updated to fix conflicts because of the patch 0004 update (so it can be ignored for a manual rebase) Patch 0010 enables the WRITECOPY stuff by default (this is effectively a replacement for patches 0010 and 0011 without their hacky logic which really only works for Chromium-based applications); if this patch addition is too radical, then at least patches 0010 and 0011 should definitely be removed (hopefully there won't be another patch race anytime soon) Please note that patch 0003 also adds an extra ntdll-Syscall_Emulation dependency to fix a bad interaction with that patchset (also I should've sent this email at least a day earlier but hopefully some of these patches can get pushed) Thanks

Sept. 20, 2024

Re: [PATCH] Correction for Bug 52627 - Wishlist: add ohm symbol (greek capital Omega) to wine tahoma font

by Nikolay Sivov

On Fri, Sep 20, 2024 at 5:34 PM MATHEUS VENTURINI BORTOLUZZI < matheus.venturini(a)acad.ufsm.br> wrote: > Good afternoon, I've made a patch to fix the Ohm sign not appearing in > LTSpice. I followed what was written in the discussion of Bug 52627 > <https://bugs.winehq.org/show_bug.cgi?id=52627> - I copied the glyph for > "OHM SIGN" and pasted it for "GREEK CAPITAL LETTER OMEGA" using FontForge. > Since this is my first contribution to anything ever, I would greatly > appreciate if someone could test this patch... > Hi, This looks reasonable to me, as a solution. Changes should be submitted in a form of merge requests at https://gitlab.winehq.org/wine/wine. Note that you'll need to modify .sfd sources for both regular and bold Tahoma, and regenerate ttf files using fontforge built from https://gitlab.winehq.org/wine/fontforge. > > Thank you in advance > > Matheus > > >

Sept. 20, 2024

[PATCH] Correction for Bug 52627 - Wishlist: add ohm symbol (greek capital Omega) to wine tahoma font

by MATHEUS VENTURINI BORTOLUZZI

Good afternoon, I've made a patch to fix the Ohm sign not appearing in LTSpice. I followed what was written in the discussion of Bug 52627 <https://bugs.winehq.org/show_bug.cgi?id=52627> - I copied the glyph for "OHM SIGN" and pasted it for "GREEK CAPITAL LETTER OMEGA" using FontForge. Since this is my first contribution to anything ever, I would greatly appreciate if someone could test this patch... Thank you in advance Matheus

Sept. 20, 2024

Re: Gitlab News

by Alexandre Julliard

Eric Pouech <eric.pouech(a)orange.fr> writes: > Le 11/09/2024 à 21:12, Alexandre Julliard a écrit : >> Folks, >> >> As you may have noticed, now that the ARM64 support is done (just >> kidding), I've picked up the work on the Gitlab migration: >> >> 1. The Wiki has been moved to Gitlab, it's now at [1]. Existing URLs >> to the previous Wiki are redirected to the appropriate page. There >> are also separate Wikis for appdb, vkd3d and wine-staging, under >> their respective project pages. > > thanks! it'll make updating much easier now > > 1) > > some updates (eg [1] done from web interface) have a diff that appears > with all lines touched (which is not the case) > > the modified files have now CRLF line termination (while untouched haven't) > > is that something we want to change to have better history view? Indeed that's annoying. I've converted all the files to CRLF, so from now on the diffs should be more readable. -- Alexandre Julliard julliard(a)winehq.org

Sept. 17, 2024

Re: Gitlab News

by Alex Henrie

On Thu, Sep 12, 2024 at 5:23 AM Eric Pouech <eric.pouech(a)orange.fr> wrote: > some updates (eg [1] done from web interface) have a diff that appears > with all lines touched (which is not the case) > > the modified files have now CRLF line termination (while untouched haven't) > > is that something we want to change to have better history view? > > > [1] > https://gitlab.winehq.org/wine/wine/-/wikis/Wine-Developer's-Guide/Debugging-Wine/diff?version_id=adbf744d1d2ae02da245be29bdbfd2bf366793d5 As a workaround, you can click the "Hide whitespace changes" button. But it's a little insane that GitLab saves wiki pages with CRLF line endings, as can be seen when downloading the Markdown source file for the page.[1] I see that the wiki is actually a Git repository located at <ssh://git(a)gitlab.winehq.org/wine/wine.wiki.git>. Could we push a .gitattributes file to that repository with the line "* text=auto" to make it use Unix line endings? [2] At the same time, it will be necessary to run dos2unix over any files that have been accidentally converted to CRLF and recommit them. -Alex [1] https://gitlab.winehq.org/wine/wine/-/wikis/Wine-Developer's-Guide/Debugging-Wine.md [2] https://git-scm.com/docs/gitattributes#_checking_out_and_checking_in

Sept. 12, 2024

Re: Gitlab News

by Eric Pouech

Le 11/09/2024 à 21:12, Alexandre Julliard a écrit : > Folks, > > As you may have noticed, now that the ARM64 support is done (just > kidding), I've picked up the work on the Gitlab migration: > > 1. The Wiki has been moved to Gitlab, it's now at [1]. Existing URLs > to the previous Wiki are redirected to the appropriate page. There > are also separate Wikis for appdb, vkd3d and wine-staging, under > their respective project pages. thanks! it'll make updating much easier now 1) some updates (eg [1] done from web interface) have a diff that appears with all lines touched (which is not the case) the modified files have now CRLF line termination (while untouched haven't) is that something we want to change to have better history view? [1] https://gitlab.winehq.org/wine/wine/-/wikis/Wine-Developer's-Guide/Debugging-Wine/diff?version_id=adbf744d1d2ae02da245be29bdbfd2bf366793d5

Sept. 12, 2024

Gitlab News

by Alexandre Julliard

Folks, As you may have noticed, now that the ARM64 support is done (just kidding), I've picked up the work on the Gitlab migration: 1. The Wiki has been moved to Gitlab, it's now at [1]. Existing URLs to the previous Wiki are redirected to the appropriate page. There are also separate Wikis for appdb, vkd3d and wine-staging, under their respective project pages. As part of the migration I've done some minor edits, but most of the Wiki is badly out-of-date, and could use some love. Help is welcome! Check the Writers page [2] for details on how to contribute. 2. We are now hosting the Mono project on the WineHQ Gitlab [3]. Please join me in welcoming the Mono developers to our community! 3. We have new hardware for the Gitlab server, which is now noticeably faster. Thanks to Jeremy Newman for setting this up! This also made it possible to enable robots.txt again so that our content is indexed. The next step will be to install new hardware for the Gitlab runners to offer more CI bandwidth. 4. The Gitlab issue tracker is currently disabled because it was attracting too much spam. I'm going to re-enable it, first for use by Mono, and then ultimately also for Wine itself. To fight the spam I'm planning to add an explicit user verification step, modelled along the procedure used by Freedesktop.org [4]. 5. As part of the new sign-up process, I think it would be a good idea to have an explicit Code of Conduct to spell out our expectations. Instead of reinventing the wheel, I propose that we adopt the Contributor Covenant [5] that many other projects (including Mono) are already using. Thoughts? Questions? Comments? [1]: https://gitlab.winehq.org/wine/wine/-/wikis [2]: https://gitlab.winehq.org/wine/wine/-/wikis/Writers [3]: https://gitlab.winehq.org/mono [4]: https://gitlab.freedesktop.org/freedesktop/freedesktop/-/wikis/home [5]: https://www.contributor-covenant.org/ -- Alexandre Julliard julliard(a)winehq.org

Sept. 11, 2024