January 2023 - Wine-Devel - list.winehq.org

dmloader:dmloader crash on gitlab-debian-64

by Francois Gouget

On test.winehq.org I see that dmloader:dmloader crashed on gitlab-debian-64 due to an assertion (2023-01-12): 060c:loader: 104 tests executed (0 marked as todo, 0 as flaky, 0 failures), 0 skipped. dmloader:loader:060c done (-2147483391) in 0s 88B Test failed: crash (80000101) https://test.winehq.org/data/patterns.html#dmloader:loader I'd like to know if this is caused by the one assert() in stream_get_chunk(). A backtrace could help in that regard but: * The test report on test.winehq.org only has the test output, not Wine's stderr traces which is where a backtrace would be. http://winetest.dolphin/data/047118247ce489a7138428c8b2cd5692ed04337e/linux… * And the GitLab log has neither the test output nor the Wine traces. https://gitlab.winehq.org/wine/wine/-/jobs/8996 So are the Wine traces available somewhere for GitLab's nightly WineTest runs? -- Francois Gouget <fgouget(a)codeweavers.com>

Jan. 26, 2023

Re: [WINE-CE] Wine-CE Can Run Cross Instruction Architecture Windows App

by Stefan Dösinger

Hi, I'm a co-author of https://github.com/andrerh/hangover , which had similar goals. I haven't tried to build your code yet. Sadly gitee doesn't let me look at anything without creating an account, although I could do an actual checkout of your Wine modifications. qemu is still making its way through my slow internet conenction. >From your description it sounds like you are using Wine's under-development windows-style multilib support to run parts of Wine as arm-native code and the rest as x86. You might be interested to know that we have similar plans. The idea is to handle this the same way windows on arm handles this by having an xtajit.dll instead of wow64cpu.dll that does the emulation entry/exit at the wine fake syscall level. André started looking into this and had some success. I don't know if he published his code yet. Upstreaming something for that goal will likely happen after Wine 8.0 is released. The big challenge is emulation speed. Games are a somewhat special case because a lot of CPU time is spent in drivers, which remain ARM native in Wine's hybrid approach or hangover (but not if you use qemu-linux-user). qemu is terribly slow, too slow to run most applications at acceptable speed. Other than d3d and maybe sound mixing, the windows DLLs do relatively little work and all CPU time is spent in the application's code, which remains x86 code and needs to be emulated. Stefan > Am 18.01.2023 um 16:57 schrieb fanwj(a)mail.ustc.edu.cn: > > Wine-CE (Chimera Edition) is a compatibility layer capable of running Windows applications on Cross-architecture paltform of Linux. It is base on Wine Project and Qemu Project. > > Project Address: https://gitee.com/fanwenjie/wine-ce > > TEST App: Sword and Fairy 3 > > Demonstration: https://www.bilibili.com/video/BV1Kd4y157Lm > >

Jan. 26, 2023

[WINE-CE] Wine-CE Can Run Cross Instruction Architecture Windows App

by fanwj＠mail.ustc.edu.cn

Wine-CE (Chimera Edition) is a compatibility layer capable of running Windows applications on Cross-architecture paltform of Linux. It is base on Wine Project and Qemu Project. Project Address: https://gitee.com/fanwenjie/wine-ce TEST App: Sword and Fairy 3 Demonstration: https://www.bilibili.com/video/BV1Kd4y157Lm

Jan. 26, 2023

How should one report GitLab CI bugs?

by Francois Gouget

How should one report GitLab CI bugs? I'm thinking of two types of bugs. 1. Wine test bugs that specifically happen on the GitLab CI infrastructure. See for instance bug 54334 which describes a set of qasf:asfreader failures that has, so far, only been seen in the Linux GitLab CI. I'm thinking some Wine developers may be particularly interested in getting such bugs fixed and thus would want to have a way to find them. Would a 'gitlabci' or just 'ci' keyword be appropriate? 2. Bugs and missing features in the GitLab CI infrastructure itself. For instance the failures that gitlab-win10-21h2 gets in the ole32:clipboard, riched20:richole and user32:msg tests strongly suggest that the AMD driver was installed with its Adrenalin GUI. Since it is known to interfere with the clipboard this could be considered a bug in that Windows 10 VM configuration. (Alternatively one could argue the tests should be modified to be resistant to such interference which would move this issue to the first category.) Which product should one pick in Bugzilla for reporting such bugs? They would not fit in 'Wine' product or any of the other existing products except 'Wine-Testbot' if one considers the GitLab CI to be the new TestBot (though I think that would be quite confusing). -- Francois Gouget <fgouget(a)codeweavers.com>

Jan. 26, 2023

Wine staging 8.0 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 8.0 (478 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * None Added: * None Updated: * None 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.

Jan. 25, 2023

Wine staging 8.0-rc4 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 8.0-rc4 (478 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * none Added: * None Updated: * msxml3-FreeThreadedXMLHTTP60 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.

Jan. 15, 2023

Re: TestBot News: Missing dlls and VM updates

by Francois Gouget

On Thu, 12 Jan 2023, Francois Gouget wrote: [...] > > And does it happen on a specific wine test? > > It's enough to run the amstream:amstream test. More precisely it crashes in the gst_init_check() call! That is, the test works till line 464: 464 check_interface(filter, &IID_IMediaSeeking, FALSE); And the crash happens in dlls/winegstreamer/wg_parser.c in init_gstreamer_once(): 1673 if (!gst_init_check(&argc, &argv, &err)) I guess the good news is that I can crash the X server with: gst-play-1.0 no-such-file.avi And it turns out to be caused by the Xv support so a workaround is to uninstall the gstreamer1.0-vaapi package. Given that it's pretty basic functionality that's broken (though maybe it's a bad interaction with QXL) there's hope that it will be fixed in time. -- Francois Gouget <fgouget(a)codeweavers.com>

Jan. 12, 2023

Re: TestBot News: Missing dlls and VM updates

by Francois Gouget

On Tue, 10 Jan 2023, Bernhard Übelacker wrote: [...] > I tried to run a Xephyr server and run the tests of 8.0rc3 inside of it, > on top of a current Debian testing. > > Could you share more details if Xephyr is started with some parameters, > does it give a backtrace or core, and do you have a window manager running > inside Xephyr? The TestBot does not use Xephyr. It uses a regular X server with the QXL driver. ii xserver-common 2:21.1.6-1 all common files used by various X servers ii xserver-xorg 1:7.7+23 amd64 X.Org X server ii xserver-xorg-core 2:21.1.6-1 amd64 Xorg X server - core server ii xserver-xorg-video-qxl 0.1.5+git20200331-3 amd64 X.Org X server -- QXL display driver It also runs the fvwm window manager as described on the page below: https://wiki.winehq.org/Wine_TestBot_VMs#Unix_configuration ii fvwm 1:2.7.0-1 amd64 F(?) Virtual Window Manager Normally the tests run in a multi-monitor configuration but the crash also happens with a single monitor. There is a backtrace in /var/log/Xorg.0.log: [ 71.406] (EE) [ 71.406] (EE) Backtrace: [ 71.406] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x5648efd6bcc9] [ 71.406] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x40) [0x7f807185af90] [ 71.406] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (pthread_key_delete+0x14c) [0x7f80718a9ccc] [ 71.406] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x12) [0x7f807185aef2] [ 71.407] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0xd3) [0x7f8071845472] [ 71.407] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 71.407] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7f8071845395] [ 71.407] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (__assert_fail+0x42) [0x7f8071853df2] [ 71.407] (EE) 7: /usr/lib/xorg/Xorg (DRIMoveBuffersHelper+0xc33) [0x5648efd241e3] [ 71.407] (EE) 8: /usr/lib/xorg/Xorg (DRI2Authenticate+0xad) [0x5648efd2647d] [ 71.407] (EE) 9: /usr/lib/xorg/Xorg (DRI2GetParam+0x6cb) [0x5648efd271fb] [ 71.407] (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x3d4) [0x5648efbf8734] [ 71.407] (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3bc) [0x5648efbfc6cc] [ 71.407] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x8a) [0x7f807184618a] [ 71.407] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x85) [0x7f8071846245] [ 71.407] (EE) 14: /usr/lib/xorg/Xorg (_start+0x21) [0x5648efbe5b71] [ 71.407] (EE) [ 71.407] (EE) Fatal server error: [ 71.407] (EE) Caught signal 6 (Aborted). Server aborting > And does it happen on a specific wine test? It's enough to run the amstream:amstream test. -- Francois Gouget <fgouget(a)codeweavers.com>

Jan. 12, 2023

Re: TestBot News: Missing dlls and VM updates

by Bernhard Übelacker

Am 09.01.23 um 11:32 schrieb Francois Gouget: > On Fri, 6 Jan 2023, Bernhard Übelacker wrote: >> Does the X server still crash? > > It does. I also upgraded to unstable and it still crashed :-( > > [...] > 0454:fixme:d3d:wined3d_guess_card No card selector available for card vendor 0000 (using GL_RENDERER "llvmpipe (LLVM 15.0.6, 256 bits)"). > 0454:err:winediag:MIDIMAP_drvOpen No software synthesizer midi port found, Midi sound output probably won't work. > X connection to :0.0 broken (explicit kill or server shutdown). > X connection to :0.0 broken (explicit kill or server shutdown). > X connection to :0.0 broken (explicit kill or server shutdown). > X connection to :0.0 broken (explicit kill or server shutdown). > X connection to :0.0 broken (explicit kill or server shutdown). > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027026 The Debian bug given seems not directly connected to a crashing X server, is there another report known? I tried to run a Xephyr server and run the tests of 8.0rc3 inside of it, on top of a current Debian testing. Could you share more details if Xephyr is started with some parameters, does it give a backtrace or core, and do you have a window manager running inside Xephyr? And does it happen on a specific wine test? I am currently running the test suite with "make test -k", but received no crash, but am currently just in dlls/k* tests. Kind regards, Bernhard

Jan. 10, 2023

Re: FOSDEM 2023

by Gijs Vermeulen

Op ma 9 jan. 2023 om 11:44 schreef Henri Verbeet <hverbeet(a)gmail.com>: > Is anyone else already planning to attend this year? > I will definitely be attending. Kind regards, Gijs

Jan. 9, 2023