wine-bugs January 2023

wine-bugs@winehq.org

1 participants
3730 discussions

[Bug 53659] New: Beyond Good & Evil: missing images in configuration tool
by WineHQ Bugzilla 20 Jan '23

20 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=53659 Bug ID: 53659 Summary: Beyond Good & Evil: missing images in configuration tool Product: Wine Version: 7.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: matheus.venturini(a)acad.ufsm.br Distribution: --- Created attachment 73063 --> https://bugs.winehq.org/attachment.cgi?id=73063 Wine console output Beyond Good & Evil's configuration tool (SettingsApplication.exe) doesn't show some images that are supposed to appear when using it. This doesn't negatively affect the use of the tool, but it ends up looking a little strange. These are the most interesting lines on the output generated by Wine: fixme:wbemprox:wbem_services_CreateInstanceEnum unsupported flags 0x30 fixme:wbemprox:enum_class_object_Next timeout not supported fixme:ddraw:ddraw7_Initialize Ignoring guid {aeb2cdd4-6e41-43ea-941c-8361cc760781}. I'm using the GOG version, sadly the game doesn't have a demo for PC. -- 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 14

[Bug 54344] New: simtower (setup.exe) says could not open the file name "h:\wine64....."
by WineHQ Bugzilla 19 Jan '23

19 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=54344 Bug ID: 54344 Summary: simtower (setup.exe) says could not open the file name "h:\wine64....." Product: Wine Version: 8.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: elias_0000_0000(a)yahoo.com Distribution: --- simtower (setup.exe) says could not open the file name "h:\wine64....." setup.exe tries to expand the files, but it says the above message. What i must do? I downloaded expand.exe to expand files in dosbox by hand but it takes time. -- 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

[Bug 54333] New: Game "10S": crashes when starting new game
by WineHQ Bugzilla 19 Jan '23

19 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=54333 Bug ID: 54333 Summary: Game "10S": crashes when starting new game Product: Wine Version: 8.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: stabilergriller(a)gmail.com Distribution: --- Created attachment 73899 --> https://bugs.winehq.org/attachment.cgi?id=73899 complete output of the "code error" window A free demo of the game is provided on https://owch.itch.io/10s. Wine boots up the main menu successfully, but crashes when actually trying to get ingame (click the "Let's Play!" button). A "Code Error" pops up. My stats: OS: Arch GPU: Intel HD Graphics 610 Driver Mesa 22.3.3 Kernel version: 6.1.5 -- 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 7

[Bug 50306] New: Riptide GP Renegade: not able to connect to online multiplayer server (Error code 403)
by WineHQ Bugzilla 19 Jan '23

19 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=50306 Bug ID: 50306 Summary: Riptide GP Renegade: not able to connect to online multiplayer server (Error code 403) Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ranplayer(a)protonmail.com Distribution: --- Created attachment 68878 --> https://bugs.winehq.org/attachment.cgi?id=68878 Wine output When you try to connect to the Online Multiplayer, the game shows the following message: """ Connection error: Unable to connect to the game server. Please, check you network connection and try again. (Error code 403) """ I created a clean prefix and installed only the Steam client and the game. No additional library was added. This issue happens on previous Wine versions as well. Game link: https://store.steampowered.com/app/443860/Riptide_GP_Renegade Setup: O.S: Manjaro Linux Arch: x86_64 Kernel: 5.4.80 Desktop Environment: KDE Plasma 5.20.4 CPU: Intel Core i5-4690s GPU: Nvidia GTX 970 4GB -- 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 2

[Bug 54310] New: Test on an older distribution
by WineHQ Bugzilla 19 Jan '23

19 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=54310 Bug ID: 54310 Summary: Test on an older distribution Product: Wine-Testbot Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: novae.harpist06(a)icloud.com Distribution: --- There were several recent bugs that affect / affected older distros: https://bugs.winehq.org/show_bug.cgi?id=54060 https://bugs.winehq.org/show_bug.cgi?id=54166 https://bugs.winehq.org/show_bug.cgi?id=54210 https://bugs.winehq.org/show_bug.cgi?id=51268 I think it'd make sense to have an older distro as test VM to avoid these. The current oldest vendor-supported distro is RHEL7 (and rebuilds). I think it'd make sense to use that / a rebuild. I tested on an Oracle Linux 7.9 install, and used the following commands to get a compilation going: yum install -y -q https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm printf '[epel-archive]\nname=EPEL Archive\nbaseurl=https://archives.fedoraproject.org/pub/archive/epel/7.2019…' > /etc/yum.repos.d/epel-archive.repo yum install -y -q gcc-c++ make glibc-devel.i686 mingw32-gcc mingw64-gcc yum-builddep wine the archive repo is necessary as mingw was removed from EPEL around that time. -- 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 2

[Bug 54226] New: widl: implement `cstruct_out` option to generate C bindings compatible with small struct return values
by WineHQ Bugzilla 19 Jan '23

19 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=54226 Bug ID: 54226 Summary: widl: implement `cstruct_out` option to generate C bindings compatible with small struct return values Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: alvin(a)alvinhc.com According to https://devblogs.microsoft.com/oldnewthing/20220113-00/?p=106152, the previous C bindings are incompatible with the C++ COM ABI when the method returns a small struct for MSVC. Their solution is to add the `/cstruct_out` flag to the MIDL compiler (https://learn.microsoft.com/en-us/windows/win32/midl/-cstruct-out, added in the Win11 SDK according to comments) to generate new C bindings compatible with the C++ COM ABI. This is similar to the (long-standing) GCC issue with its mingw-w64 MS ABI (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64384), which has been worked around in widl/mingw-w64 by having special wrapper functions in the C++ bindings, guarded by `WIDL_EXPLICIT_AGGREGATE_RETURNS`. I think widl should follow suit to implement a `--cstruct_out` flag to do the same thing for the C bindings. This does not need to be guarded by `WIDL_EXPLICIT_AGGREGATE_RETURNS` because both GCC and MSVC has the same issue and will require the same fix. (I do not know if we need some kind of guard for the mingw-w64 headers to revert to the old function declarations, but given that the old bindings are practically broken perhaps it doesn't matter.) (I have not checked what `/cstruct_out` on MIDL actually does to the C bindings.) -- 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 2

[Bug 54316] New: wine staging lacks wine-staging package (8.0~rc4~jammy-1)
by WineHQ Bugzilla 18 Jan '23

18 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=54316 Bug ID: 54316 Summary: wine staging lacks wine-staging package (8.0~rc4~jammy-1) Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: monsterovich(a)gmail.com CC: dimesio(a)earthlink.net Distribution: --- ┌(monsterovich@pc)─(pts/0)─(~) └─(>) LANG= sudo apt dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: wine-staging The following NEW packages will be installed: wine-staging:i386 The following packages will be upgraded: wine-staging-amd64 wine-staging-i386:i386 winehq-staging 3 upgraded, 1 newly installed, 1 to remove and 0 not upgraded. Need to get 216 MB of archives. After this operation, 46.1 kB of additional disk space will be used. Do you want to continue? [Y/n] -- 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 51484] New: dmloader:loader fails randomly with a DMUS_E_LOADER_BADPATH error
by WineHQ Bugzilla 18 Jan '23

18 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=51484 Bug ID: 51484 Summary: dmloader:loader fails randomly with a DMUS_E_LOADER_BADPATH error Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-dmusic Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Created attachment 70320 --> https://bugs.winehq.org/attachment.cgi?id=70320 Unsuccessful attempt to more reliably reproduce the failure dmloader:loader fails randomly in test_directory(): https://test.winehq.org/data/patterns.html loader.c:105: Test failed: SetSearchDirectory failed with 0x88781181 loader.c:107: Test failed: SetSearchDirectory failed with 0x88781181 where 0x88781181 == DMUS_E_LOADER_BADPATH. As of writing only w7u and cw-gtx560-1506 had failures but they are quite rare (up to 110 runs between failures), so maybe the other platforms just got lucky. Also once (2021-06-21) there was this set of failures: loader.c:105: Test failed: SetSearchDirectory failed with 0x88781181 loader.c:107: Test failed: SetSearchDirectory failed with 0 So it's as if there was a race condition causing SetSearchDirectory() to fail until some initialization process completed. That or it's some sort of uninitialized memory issue and the failures truly are random; or SetSearchDirectory() checks the presence of some directory corresponding to "", and some other process interferes with that. The attached patch has no success reproducing this issue so maybe the cause is external. -- 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 9

[Bug 40446] New: WinSCP is missing text in the "About" window
by wine-bugs＠winehq.org 18 Jan '23

18 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=40446 Bug ID: 40446 Summary: WinSCP is missing text in the "About" window Product: Wine Version: 1.9.7 Hardware: x86 URL: http://winscp.net/download/winscp577.zip OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mshtml Assignee: wine-bugs(a)winehq.org Reporter: t.artem(a)mailcity.com Distribution: --- Run WinSCP, invoke Tools -> About, see no text. Logged errors in console: fixme:ieframe:PersistStreamInit_InitNew (0x1c1728) fixme:ieframe:OleControl_OnAmbientPropertyChange Unknown dispID -702 fixme:ieframe:OleControl_OnAmbientPropertyChange Unknown dispID -701 fixme:ieframe:OleControl_OnAmbientPropertyChange Unknown dispID -703 fixme:ieframe:OleControl_OnAmbientPropertyChange Unknown dispID -704 fixme:iphlpapi:NotifyIpInterfaceChange (family 0, callback 0x6a0a6836, context 0x215da80, init_notify 0, handle 0x2a6e7f4): stub fixme:imm:ImmGetDescriptionW (0x4090409, (nil), 0): semi stub fixme:imm:ImmGetDescriptionW (0x4090409, 0x503f508, 9): semi stub fixme:imm:ImmReleaseContext (0x40116, 0x1b7458): stub fixme:win:EnumDisplayDevicesW ((null),0,0x32a304,0x00000000), stub! fixme:ntdll:NtLockFile I/O completion on lock not implemented yet fixme:ieframe:BrowserService_GetTravelLog 0x1e00b0 0x32ae98 fixme:mshtml:OleControl_OnAmbientPropertyChange edit mode is not supported fixme:ieframe:ClientSite_GetContainer (0x1c17ec)->(0x32ae7c) fixme:mshtml:nsChannel_GetContentDisposition (0x1fcec0)->(0x3285e8) fixme:mshtml:nsChannel_GetContentDispositionHeader (0x1fcec0)->(0x327d3c) err:mshtml:update_window_doc SetDesignMode failed: 80070057 fixme:ieframe:ClientSite_GetContainer (0x1c17ec)->(0x32dd4c) fixme:ieframe:DocHostUIHandler_GetDropTarget (0x1c17ec) fixme:win:WINNLSEnableIME hwnd 0x40084 enable -1: stub! fixme:ntdll:EtwRegisterTraceGuidsW (0x69ee122c, 0x503c9f8, {509962e0-406b-46f4-99ba-5a009f8d2225}, 3, 0x5e60ab8, (null), (null), 0x503ca28): stub fixme:ntdll:EtwRegisterTraceGuidsW register trace class {a3da04e0-57d7-482a-a1c1-61da5f95bacb} fixme:ntdll:EtwRegisterTraceGuidsW register trace class {917b96b1-ecad-4dab-a760-8d49027748ae} fixme:ntdll:EtwRegisterTraceGuidsW register trace class {26d1e091-0ae7-4f49-a554-4214445c505c} fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) err:mshtml:do_ns_command DoCommand("cmd_fontFace") failed: 80004005 fixme:ieframe:PropertyNotifySink_OnChanged unimplemented dispid 1005 fixme:mshtml:HTMLDocument_put_designMode Unsupported arg L"Off" fixme:ieframe:ClientSite_GetContainer (0x1c17ec)->(0x32f1ec) fixme:mshtml:nsChannel_GetContentDisposition (0x1fce28)->(0x32ec68) fixme:mshtml:nsChannel_GetContentDispositionHeader (0x1fce28)->(0x32e3bc) err:mshtml:update_window_doc SetDesignMode failed: 80070057 fixme:ieframe:ControlSite_OnFocus (0x1c17ec)->(0) fixme:ieframe:InPlaceSite_OnInPlaceDeactivateEx fNoRedraw (1) ignored fixme:mshtml:HlinkTarget_SetBrowseContext (0x1e15c8)->((nil)) -- 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 15

[Bug 52107] New: %ERRORLEVEL% shall not be reset when setting an environment variable in a batch file
by WineHQ Bugzilla 18 Jan '23

18 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=52107 Bug ID: 52107 Summary: %ERRORLEVEL% shall not be reset when setting an environment variable in a batch file Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: jinoh.kang.kr(a)gmail.com CC: others.meder(a)gmail.com Distribution: --- The fix in https://bugs.winehq.org/show_bug.cgi?id=47791 (commit 617d14bc1238b57327a8400eda1c1ab22624beb7) is incomplete; it only applies to interactive case, and the bug is left unchanged for the batch mode case. When a variable is successfully set, %ERRORLEVEL% is left as-is regardless of whether the interpreter is in batch mode or not. See also: https://ss64.com/nt/set.html -- 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

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 January 2023