wine-devel

wine-devel@winehq.org

2 participants
84469 discussions

wined3d surface handle buffer overflow
by Fabian Maurer 11 Oct '24

11 Oct '24

Hello, I'm currently investigating a wined3d regression that leads to an assert - bug 57300. In short, there is memorys corruption in "d3d_device2_SwapTextureHandles" when copying a "global handle table" handle into the "device handle table". The "device handle table" is only 64 entries long, but the handle is bigger than that - writing out of bounds. As I see, it all surfaces get allocated into the global handle table. Then in d3d_device2_SwapTextureHandles they get copied into the device handle table. Once in "CreateStateBlock" and once in "EndStateBlock". The device handle table only contains the wined3d state block handle. If those assumptions are correct, I have a few questions: 1) Isn't there a risk of overriding the state block handle when swapping the texture with handle 1? 2) Why are the handles only copied, completely bypassing the ddraw_allocate_handle function? Doesn't this mess up the next call to "ddraw_allocate_handle"? A potential solution to the buffer overflow would be the increase the size of the table if the handle doesn't fit. But I don't know if that's the correct course of action, and I don't know what to do with the table size / count values. Or maybe there' something else wrong here that I'm not seeing, insights would be appreciated. Regards, Fabian Maurer

2 1

Upcoming vkd3d 1.14 release
by Henri Verbeet 10 Oct '24

10 Oct '24

Hi all, As previously announced, the planned release date for vkd3d 1.14 is November 21. That means the public API will become frozen two weeks from now on October 24, and features will be frozen after November 7. As usual, if you're an upstream vkd3d developer, please do the following: - Keep an eye on Bugzilla for any reported regressions. - Review any API changes since the previous release. - Verify all vkd3d tests pass on your hardware/setup, and please send fixes if they don't. - Review and improve the documentation. - Apply your best judgment about which patches are appropriate for the current stage of the release process. If you're a downstream user of vkd3d, please test your applications for any regressions, and file bug reports if you find any. The planned release date for vkd3d 1.15 is February 19. Regards, Henri

1 0

Wine staging 9.19 release
by Alistair Leslie-Hughes 05 Oct '24

05 Oct '24

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 9.19 (354 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * d3dx9_36: Add format description for X8L8V8U8 for format conversions. Removed (No longer required). * None Added: * None Updated: * vkd3d-latest 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.

1 0

ntdll WRITECOPY dropped from staging
by Fabian Maurer 29 Sep '24

29 Sep '24

Hello, I noticed that the ntdll WRITECOPY changes got mostly dropped from staging in commit https://github.com/wine-staging/wine-staging/commit/ 16dce521242b3f4a52cd2c8799ce6fe464fac83c > The current state even after multiple iterations, the whole > WRITECOPY implemenet needs differently. Upstream will need to > do this. As I understand it, the implementation marks WRITECOPY pages as read-only on the unix side, handling the access violation and marking it as read-write afterwards. (Correct me if I'm wrong) What is wrong with the underlying concept, how should it be implemented properly? Regards, Fabian Maurer

2 1

Carry flag state after a system function call
by robert.ayrapetyan＠gmail.com 25 Sep '24

25 Sep '24

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?

5 5

Gitlab forks limit issue
by robert.ayrapetyan＠gmail.com 24 Sep '24

24 Sep '24

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.

2 3

Wine staging 9.18 release
by Alistair Leslie-Hughes 21 Sep '24

21 Sep '24

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.

1 0

Staging WRITECOPY fixes
by DodoGTA GT 20 Sep '24

20 Sep '24

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

1 0

[PATCH] Correction for Bug 52627 - Wishlist: add ohm symbol (greek capital Omega) to wine tahoma font
by MATHEUS VENTURINI BORTOLUZZI 20 Sep '24

20 Sep '24

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

2 1

Gitlab News
by Alexandre Julliard 17 Sep '24

17 Sep '24

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

3 3

Wine staging 9.17 release
by Alistair Leslie-Hughes 06 Sep '24

06 Sep '24

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 9.17 (354 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * cmd: Support for launching programs based on file association. * cmd: Changed errorlevel type to DWORD. * winemapi: Directly use xdg-email if available, enabling file attachments. Removed (No longer required). * None Added: * None Updated: * vkd3d-latest * odbc32-fixes 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.

1 0

Wine staging 9.16 release
by Alistair Leslie-Hughes 24 Aug '24

24 Aug '24

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 9.16 (355 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * odbc32: Support freeing SQL handles for ODBC v2 drivers. * odbc32: Support Allocating SQL handles for ODBC v2 drivers. * odbc32: Support Driver in connection string. * odbc32: SQLSetDescFieldW pass correct handle onto driver. * odbc32: Use SQLAllocHandle to allocate a STMT handle. * odbc32: Call drivers SQLBindCol function. * printdlg: Allow button id psh1 for "Properties" button. * odbc32: Store handles when requesting information of Columns. * odbc32: Pass statment when creating a descriptor. * odbccp32: Support System wide ODBC DSN keys. * odbccp32: SQLWritePrivateProfileStringW check for existing DSN first. * odbc32: SQLSetEnvAttr isnt supported in ODBC v2.0. * odbc32: set_con_attr return success by default. * odbc32: SQLColAttributeW support fallback function. * odbc32: SQLGetDiagRec/W handle fallback function. * setupapi: Add stub for DriverStoreFindDriverPackageW. * winex11.drv: Update a candidate window's position with over-the-spot style. Removed (No longer required). * None Added: * None Updated: * vkd3d-latest * eventfd_synchronization * 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.

1 0

Staging dinput-scancode fix
by DodoGTA GT 23 Aug '24

23 Aug '24

Hello Here's a better regression fix for the dinput-scancode patchset (the 0001 patch of that patchset caused NFS Underground to segfault since Wine 9.15 with the addition of a keycode loop in keyboard_create_device() because of DIPROP_SCANCODE stuff); I modified the existing 0001 patch to solve this by copying the duplicate object checks to that new loop (maybe I should create a separate 0003 patch to show the changes better?) Hopefully the patch can be merged before 9.16 to not re-introduce that regression after it has been worked around in wine-staging 9.15 Thanks

3 2

stack size change
by Mahin Pandya 16 Aug '24

16 Aug '24

Hello everyone, I am looking to change stack size of Wine executable. Apart from specifying .def (which contains STACKSIZE value) file during compilation, is there any other option which is supported by Wine? Some kind configurable runtime option without modifying binary? Sample code: $ cat hello.c #include <stdio.h> #include <windows.h> int PASCAL WinMain (HINSTANCE hInstance, HINSTANCE hPrevInstance, PSTR szCmdLine, int iCmdShow) { char buffer [1024*1024*3]; printf( "Hello world\n"); return 0; } $ winegcc hello.c $ ./a.out Segmentation fault (core dumped) Note: I am able to change/patch stack size via modifying a.out.so file. Any pointers/suggestion are welcome. Thanks in advance. regards, Mahin

1 1

[PATCH v5 00/28] NT synchronization primitive driver
by Elizabeth Figura 12 Aug '24

12 Aug '24

This patch series implements a new char misc driver, /dev/ntsync, which is used to implement Windows NT synchronization primitives. NT synchronization primitives are unique in that the wait functions both are vectored, operate on multiple types of object with different behaviour (mutex, semaphore, event), and affect the state of the objects they wait on. This model is not compatible with existing kernel synchronization objects or interfaces, and therefore the ntsync driver implements its own wait queues and locking. This patch series is rebased against the "char-misc-next" branch of gregkh/char-misc.git. == Background == The Wine project emulates the Windows API in user space. One particular part of that API, namely the NT synchronization primitives, have historically been implemented via RPC to a dedicated "kernel" process. However, more recent applications use these APIs more strenuously, and the overhead of RPC has become a bottleneck. The NT synchronization APIs are too complex to implement on top of existing primitives without sacrificing correctness. Certain operations, such as NtPulseEvent() or the "wait-for-all" mode of NtWaitForMultipleObjects(), require direct control over the underlying wait queue, and implementing a wait queue sufficiently robust for Wine in user space is not possible. This proposed driver, therefore, implements the problematic interfaces directly in the Linux kernel. This driver was presented at Linux Plumbers Conference 2023. For those further interested in the history of synchronization in Wine and past attempts to solve this problem in user space, a recording of the presentation can be viewed here: https://www.youtube.com/watch?v=NjU4nyWyhU8 == Performance == The performance measurements described below are copied from earlier versions of the patch set. While some of the code has changed, I do not currently anticipate that it has changed drastically enough to affect those measurements. The gain in performance varies wildly depending on the application in question and the user's hardware. For some games NT synchronization is not a bottleneck and no change can be observed, but for others frame rate improvements of 50 to 150 percent are not atypical. The following table lists frame rate measurements from a variety of games on a variety of hardware, taken by users Dmitry Skvortsov, FuzzyQuils, OnMars, and myself: Game Upstream ntsync improvement =========================================================================== Anger Foot 69 99 43% Call of Juarez 99.8 224.1 125% Dirt 3 110.6 860.7 678% Forza Horizon 5 108 160 48% Lara Croft: Temple of Osiris 141 326 131% Metro 2033 164.4 199.2 21% Resident Evil 2 26 77 196% The Crew 26 51 96% Tiny Tina's Wonderlands 130 360 177% Total War Saga: Troy 109 146 34% =========================================================================== == Patches == The intended semantics of the patches are broadly intended to match those of the corresponding Windows functions. For those not already familiar with the Windows functions (or their undocumented behaviour), patch 27/28 provides a detailed specification, and individual patches also include a brief description of the API they are implementing. The patches making use of this driver in Wine can be retrieved or browsed here: https://repo.or.cz/wine/zf.git/shortlog/refs/heads/ntsync5 == Previous versions == Changes from v4: * Rework wait-all locking code to avoid taking more than one spinlock at a time, and also to fix a race where the wait-all lock would not be not correctly taken. The new locking mechanism involves taking a simple spinlock for normal "any" waits, and taking a device-wide mutex for "all" waits or when locking any object that is involved in an "all" wait. The mechanism was written by Peter Zijlstra. * Try to reword or clarify various parts of the documentation (patch 27), per Peter Zijlstra. * I did not rename NTSYNC_IOC_SEM_POST to RELEASE (like NT) although this was suggested by Peter Zijlstra, mostly because it's not clear to me that renaming an already committed ioctl would be fine. The API committed isn't actually usable yet, though, so if altering it would be fine on those grounds, I can revise this series to rename the function accordingly. * Similarly, I did not change the create ioctls to return the fd directly, although this was suggested and would be a bit simpler and cleaner, because NTSYNC_IOC_CREATE_SEM already exists upstream and returns the fd through a struct. I can make this change in the next revision if that'd be preferable. I also still would appreciate a clarification on the advice in [1]. [1] https://docs.kernel.org/driver-api/ioctl.html#return-code * Link to v4: https://lore.kernel.org/lkml/20240416010837.333694-1-zfigura@codeweavers.co… * Link to v3: https://lore.kernel.org/lkml/20240329000621.148791-1-zfigura@codeweavers.co… * Link to v2: https://lore.kernel.org/lkml/20240219223833.95710-1-zfigura@codeweavers.com/ * Link to v1: https://lore.kernel.org/lkml/20240214233645.9273-1-zfigura@codeweavers.com/ * Link to RFC v2: https://lore.kernel.org/lkml/20240131021356.10322-1-zfigura@codeweavers.com/ * Link to RFC v1: https://lore.kernel.org/lkml/20240124004028.16826-1-zfigura@codeweavers.com/ Elizabeth Figura (28): ntsync: Introduce NTSYNC_IOC_WAIT_ANY. ntsync: Introduce NTSYNC_IOC_WAIT_ALL. ntsync: Introduce NTSYNC_IOC_CREATE_MUTEX. ntsync: Introduce NTSYNC_IOC_MUTEX_UNLOCK. ntsync: Introduce NTSYNC_IOC_MUTEX_KILL. ntsync: Introduce NTSYNC_IOC_CREATE_EVENT. ntsync: Introduce NTSYNC_IOC_EVENT_SET. ntsync: Introduce NTSYNC_IOC_EVENT_RESET. ntsync: Introduce NTSYNC_IOC_EVENT_PULSE. ntsync: Introduce NTSYNC_IOC_SEM_READ. ntsync: Introduce NTSYNC_IOC_MUTEX_READ. ntsync: Introduce NTSYNC_IOC_EVENT_READ. ntsync: Introduce alertable waits. selftests: ntsync: Add some tests for semaphore state. selftests: ntsync: Add some tests for mutex state. selftests: ntsync: Add some tests for NTSYNC_IOC_WAIT_ANY. selftests: ntsync: Add some tests for NTSYNC_IOC_WAIT_ALL. selftests: ntsync: Add some tests for wakeup signaling with WINESYNC_IOC_WAIT_ANY. selftests: ntsync: Add some tests for wakeup signaling with WINESYNC_IOC_WAIT_ALL. selftests: ntsync: Add some tests for manual-reset event state. selftests: ntsync: Add some tests for auto-reset event state. selftests: ntsync: Add some tests for wakeup signaling with events. selftests: ntsync: Add tests for alertable waits. selftests: ntsync: Add some tests for wakeup signaling via alerts. selftests: ntsync: Add a stress test for contended waits. maintainers: Add an entry for ntsync. docs: ntsync: Add documentation for the ntsync uAPI. ntsync: No longer depend on BROKEN. Documentation/userspace-api/index.rst | 1 + Documentation/userspace-api/ntsync.rst | 398 +++++ MAINTAINERS | 9 + drivers/misc/Kconfig | 1 - drivers/misc/ntsync.c | 989 +++++++++++- include/uapi/linux/ntsync.h | 39 + tools/testing/selftests/Makefile | 1 + .../selftests/drivers/ntsync/.gitignore | 1 + .../testing/selftests/drivers/ntsync/Makefile | 7 + tools/testing/selftests/drivers/ntsync/config | 1 + .../testing/selftests/drivers/ntsync/ntsync.c | 1407 +++++++++++++++++ 11 files changed, 2850 insertions(+), 4 deletions(-) create mode 100644 Documentation/userspace-api/ntsync.rst create mode 100644 tools/testing/selftests/drivers/ntsync/.gitignore create mode 100644 tools/testing/selftests/drivers/ntsync/Makefile create mode 100644 tools/testing/selftests/drivers/ntsync/config create mode 100644 tools/testing/selftests/drivers/ntsync/ntsync.c base-commit: f5b335dc025cfee90957efa90dc72fada0d5abb4 -- 2.43.0

1 30

Wine staging 9.15 release
by Alistair Leslie-Hughes 11 Aug '24

11 Aug '24

Binary packages for various distributions will be available from: https://www.winehq.org/download We have included a few PR to fix regressions with the current wine release. If you want to play NFS Underground or connect to a database via ODBC, take wine-staging for a spin. Summary since last release * Rebased to current wine 9.15 (376 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * None Removed (No longer required). * None Added: * dinput-regression-fix - Fix crash in NFS Underground. * printdlg-properties_btn - [55841] Lotus Approach: print "Properties" button ignored. Updated: * vkd3d-latest * odbc32-fixes * eventfd_synchronization * winemapi-user-xdg-mail 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.

1 0

Wine staging 9.14 release
by Alistair Leslie-Hughes 28 Jul '24

28 Jul '24

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 9.14 (371 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * odbc32: SQLError/W handle NULL handles * odbc32: SQLSetEnvAttr fake success for SQL_ATTR_CONNECTION_POOLING * odbc32: SQLSetConnectAttrW correct default return value * odbc32: SQLTransact handle NULL EnvironmentHandle Removed (No longer required). * None Added: * [53696] d3d11: Semi-stub IDXGISwapChain::GetFrameStatistics. Updated: * vkd3d-latest * odbc32-fixes * 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.

1 0

Staging WRITECOPY fix
by DodoGTA GT 26 Jul '24

26 Jul '24

Hello, I finally managed to submit a regression fix for the ntdll-WRITECOPY patchset (it's a normal Wine patch so there should be no diff confusion this time) Hopefully this can be merged soon because it fixes annoying segfaults in 3 apps (2 of these have a bug report) Thanks

1 0

Upcoming vkd3d 1.13 release
by Henri Verbeet 25 Jul '24

25 Jul '24

Hi all, As previously announced, the planned release date for vkd3d 1.13 is August 29. That means the public API will become frozen one week from now on August 1, and features will be frozen after August 15. As usual, if you're an upstream vkd3d developer, please do the following: - Keep an eye on Bugzilla for any reported regressions. - Review any API changes since the previous release. - Verify all vkd3d tests pass on your hardware/setup, and please send fixes if they don't. - Review and improve the documentation. - Apply your best judgment about which patches are appropriate for the current stage of the release process. If you're a downstream user of vkd3d, please test your applications for any regressions, and file bug reports if you find any. The planned release date for vkd3d 1.14 is November 21. Regards, Henri

1 0

Porting Wine to the other programming languages
by alegorium＠gmail.com 20 Jul '24

20 Jul '24

Hello, everyone! I'm porting parts of WineHQ into other programming languages. Simply came here to make developers aware of the code reuse. Hope everyone here is okay with that. Example: https://github.com/GreenteaOS/Caramel/blob/kawaii/dlls/user32/dialogs.hexa dialog.c reports "2.1 of the License, or (at your option) any later version" Had to apply heuristics to restore some "high-levelness" of the code. Thanks

1 0

Broken GitWeb
by M. GOUJON 18 Jul '24

18 Jul '24

Hi everyone, It appears Wine GitWeb <https://source.winehq.org/git/wine.git/?a=shortlog> page is broken since Monday, returning a 403 Forbidden error. I know there is also the GitLab version <https://gitlab.winehq.org/wine/wine/-/commits/master> but I prefer the old one. Can someone have a look and fix the (permission) issue? Thanks in advance, Regards

7 6

Wine-Staging 9.13 release
by Elizabeth Figura 18 Jul '24

18 Jul '24

The Wine-Staging development release 9.13 is now available. Summary since last release: * Rebased to upstream Wine 9.13. 355 patches are applied to upstream Wine. Patches removed from Wine-Staging since the last release: * ntdll: Implement virtual_map_shared_memory. * server: Implement support for global and local shared memory blocks based on memfd. * user32: Get rid of wineserver call for GetInputState. * ntdll: Only enable wineserver shared memory communication when a special environment variable is set. * server: Store a list of associated queues for each thread input. * user32: Get rid of wineserver call for GetActiveWindow, GetFocus, GetCapture. * user32: Avoid unnecessary wineserver calls in PeekMessage/GetMessage. * user32: Get rid of wineserver call for GetLastInputInfo. Patches added: * odbc32-fixes (replaces odbc-remove-unixodbc) Patches otherwise updated: * vkd3d-latest Binary packages for various distributions will be available from: https://www.winehq.org/download As always, if you find a bug, please report it via https://bugs.winehq.org ἔρρωσθε, Zeb Figura

1 0

Wine staging 9.12 release
by Alistair Leslie-Hughes 30 Jun '24

30 Jun '24

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 9.12 (XXXX patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * oledb32: Support Multiple values when parsing the property Mode. * wined3d: Implement WINED3DFMT_B8G8R8X8_UNORM to WINED3DFMT_L8_UNORM conversion. Removed (No longer required). * Compiler_Warnings Added: * [7955] oledb32: Mode can have multiple values as a string * [56786] odbccp32: Correct lookup of DSN before writing to registry. Updated: * vkd3d-latest * md-launch-association * odbc-remove-unixodbc 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.

1 0

wine-staging wineodbc fix
by DodoGTA GT 28 Jun '24

28 Jun '24

Hello, I've noticed that the wine-staging wineodbc library fails to compile ever since it got introduced in commit 14f63f40e7c87dc87ca1dc64aaa66f344bada4da (but only for 32-bit) This is because the unixlib part of wineodbc requires linking to libodbc (which is rarely present on 32-bit) and because libodbc isn't present, there's a lot of missing symbols The Wine configure.ac does have some checks to prevent building of the whole odbc component if libodbc is missing (but that only works for odbc32, not wineodbc) To fix this issue, enable_odbc32 can be edited to enable_wineodbc in the configure.ac file (make sure to run autoreconf to actually include the fix in the configure script too) Thanks

1 0

Support for loongarch64 architecture
by 李鹏飞 18 Jun '24

18 Jun '24

Hello Everyone: May I ask if there is any official support for the loongarch64 architecture in the future. I added the loongarch64 architecture code based on the wine-9.9, and currently, built-in programs such as regedit and notepad can be launched. I would like to confirm if these codes can be merged by the master branch. 本邮件及其附件含有龙芯中科的商业秘密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制或散发）本邮件及其附件中的信息。如果您错收本邮件，请您立即电话或邮件通知发件人并删除本邮件。 This email and its attachments contain confidential information from Loongson Technology , which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this email in error, please notify the sender by phone or email immediately and delete it.

2 1

← Newer
1
2
3
4
5
6
7
8
...
3379
Older →

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-devel