March 2020 - Wine-bugs - list.winehq.org

[Bug 48703] New: Chummer5a no longer works as of Wine 5.2
by WineHQ Bugzilla 16 Mar '20

16 Mar '20

https://bugs.winehq.org/show_bug.cgi?id=48703 Bug ID: 48703 Summary: Chummer5a no longer works as of Wine 5.2 Product: Wine Version: 5.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: newbie13xd(a)gmail.com Distribution: --- Created attachment 66577 --> https://bugs.winehq.org/attachment.cgi?id=66577 Log from stdout/stderr Even after installing native .NET 4.5.2 (if I recall correctly), Chummer5a does not work as of Wine 5.2. In Wine 5.1 it still does work (checked by first compiling Wine 5.1 — Chummer5a works, checked out 5.2 and compiled — Chummer5a no longer works. Same Wineprefix). The issue that occurs is that after opening Chummer5a with a recent Wine version (5.2 or later) Chummer appears to open, then goes black and a Wine Debugger window appears which promptly disappears (before I'm able to catch what it says) and both windows close. Chummer5a can be downloaded here: https://github.com/Chummer5a/Chummer5a The version of Chummer I used to reproduce this was 5.209, binary release from GitHub. -- 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 3

[Bug 48728] New: Kleos by Wolters Kluwer: crashes on launch
by WineHQ Bugzilla 16 Mar '20

16 Mar '20

https://bugs.winehq.org/show_bug.cgi?id=48728 Bug ID: 48728 Summary: Kleos by Wolters Kluwer: crashes on launch Product: Wine Version: 5.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pavone.lawyer(a)gmail.com Distribution: --- Created attachment 66605 --> https://bugs.winehq.org/attachment.cgi?id=66605 kleos start log Hi, I'm trying to run Kleos under wine. Kleos is an application to manage the work flow in a law firm: https://kleos.wolterskluwer.com. This application is cloud based and it needs a client on the user pc. The software dependecies, as advertised by the developer, are: Windows 7 Service Pack 1 Microsoft .NET Framework 4.6.1 (x86 and x64) Messaging API and Collaboration Data Objects 1.2.1 Visual C++ Redistributable for Visual Studio 2013 (x86 and x64). I use a 64 bit linux distribution (manjaro with 5.5 kernel) and wine 5.3. I created a new 64 bit prefix, setted the windows version to 8.1 and after some experiments and a huge help from the wine forum, I used 2 winetricks: d3dcompiler_47 and dotnet472. With this enviroment I was able to install the application. During the installation process it prompted to install Messaging API and Collaboration Data Objects and I said yes. When I launche the installed app it showed the splash screen , but it crashed after a while. The log is attached. Thanks -- 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 48759] New: Apple clang 11.0.0 incorrectly compiles get_devmode in without-mingw build
by WineHQ Bugzilla 16 Mar '20

16 Mar '20

https://bugs.winehq.org/show_bug.cgi?id=48759 Bug ID: 48759 Summary: Apple clang 11.0.0 incorrectly compiles get_devmode in without-mingw build Product: Wine Version: 5.4 Hardware: x86-64 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: wineps.drv Assignee: wine-bugs(a)winehq.org Reporter: piotr.caban(a)gmail.com Regression SHA1: 6887af4f2bf8a863889f7110e9be78bbfc4fa3f3 Apple clang 11.0.0 produces invalid 64-bit wineps.drv build. In dlls/wineps.drv/init.c: *dm = DefaultDevmode; assignment ends using memcpy. Since it links to msvcrt the parameters are passed incorrectly causing a crash during prefix creation. -- 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 48297] New: Wineboot crashes on 64bit prefix creation (macOS wine built without mingw)
by WineHQ Bugzilla 16 Mar '20

16 Mar '20

https://bugs.winehq.org/show_bug.cgi?id=48297 Bug ID: 48297 Summary: Wineboot crashes on 64bit prefix creation (macOS wine built without mingw) Product: Wine Version: 5.0-rc1 Hardware: x86-64 OS: Mac OS X Status: NEW Keywords: regression, source Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gijsvrm(a)gmail.com Created attachment 66004 --> https://bugs.winehq.org/attachment.cgi?id=66004 backtrace Only happens when creating a 64bit prefix. Attached is the backtrace, there was no other output aside from the regular output when creating a prefix. I'll try to do a regression test ASAP. -- 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 48699] New: d3dformat error : not able to run Skyrim
by WineHQ Bugzilla 16 Mar '20

16 Mar '20

https://bugs.winehq.org/show_bug.cgi?id=48699 Bug ID: 48699 Summary: d3dformat error : not able to run Skyrim Product: Wine Version: 5.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: siddarthn151(a)gmail.com Distribution: --- Created attachment 66573 --> https://bugs.winehq.org/attachment.cgi?id=66573 Wine error log Hi, I'm trying to run The Elder scrolls V : Skyrim game in my Ubuntu 19.10 using wine 5.0 stable version. The installation was fine with no errors and when I try to run TESV.exe, the game loads up and i'm able to select for a new game and then the title rolls and after some 10 sec, the game instructs me to use mouse to look around. I do that and after 5 sec, the game crashes with no error messages. Tried both SkyrimLauncher.exe and TESV.exe. The results are same. I tried switching to very low res and graphics but still the same. I was able to grab the error log(attached). Tried searching the google but unable to find a solution. My System information --> H/W path Device Class Description ======================================================= system HP Pavilion Notebook (M2W75PA#ACJ) /0 bus 8096 /0/0 memory 128KiB BIOS /0/4 processor Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz /0/4/6 memory 32KiB L1 cache /0/4/7 memory 256KiB L2 cache /0/4/8 memory 3MiB L3 cache /0/5 memory 32KiB L1 cache /0/16 memory 8GiB System Memory /0/16/0 memory 8GiB SODIMM DDR3 Synchronous 1600 MHz (0.6 ns) /0/16/1 memory Synchronous [empty] /0/100 bridge Broadwell-U Host Bridge -OPI /0/100/2 display HD Graphics 5500 /0/100/3 multimedia Broadwell-U Audio Controller /0/100/4 generic Broadwell-U Processor Thermal Subsystem /0/100/14 bus Wildcat Point-LP USB xHCI Controller /0/100/14/0 usb1 bus xHCI Host Controller /0/100/14/0/1 input USB Optical Mouse /0/100/14/0/3 multimedia HP Truevision HD /0/100/14/0/7 communication Bluetooth Radio /0/100/14/1 usb2 bus xHCI Host Controller /0/100/16 communication Wildcat Point-LP MEI Controller #1 /0/100/1b multimedia Wildcat Point-LP High Definition Audio Controller /0/100/1c bridge Wildcat Point-LP PCI Express Root Port #1 /0/100/1c.1 bridge Wildcat Point-LP PCI Express Root Port #2 /0/100/1c.2 bridge Wildcat Point-LP PCI Express Root Port #3 /0/100/1c.2/0 wlo1 network RTL8723BE PCIe Wireless Network Adapter /0/100/1c.3 bridge Wildcat Point-LP PCI Express Root Port #4 /0/100/1c.3/0 eno1 network RTL810xE PCI Express Fast Ethernet controller /0/100/1c.4 bridge Wildcat Point-LP PCI Express Root Port #5 /0/100/1c.4/0 display GM108M [GeForce 940M] /0/100/1f bridge Wildcat Point-LP LPC Controller /0/100/1f.2 scsi0 storage Wildcat Point-LP SATA Controller [AHCI Mode] /0/100/1f.2/0 /dev/sda disk 1TB WDC WD10JPVX-60J /0/100/1f.2/0/1 /dev/sda1 volume 498MiB Windows NTFS volume /0/100/1f.2/0/2 /dev/sda2 volume 99MiB Windows FAT volume /0/100/1f.2/0/3 /dev/sda3 volume 15MiB reserved partition /0/100/1f.2/0/4 /dev/sda4 volume 44GiB Windows NTFS volume /0/100/1f.2/0/5 /dev/sda5 volume 885GiB EXT4 volume /0/100/1f.2/1 /dev/cdrom disk DVDRW UJ8G2A /0/100/1f.3 bus Wildcat Point-LP SMBus Controller /0/1 system PnP device PNP0c02 /0/2 system PnP device PNP0b00 /0/3 generic PnP device HPQ8001 /0/6 generic PnP device SYN1ef2 /0/7 system PnP device PNP0c02 /1 power KI04041 /2 power OEM Define 5 /3 anbox0 network Ethernet interface My graphics information --> *-display description: VGA compatible controller product: HD Graphics 5500 vendor: Intel Corporation physical id: 2 bus info: pci(a)0000:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:53 memory:c3000000-c3ffffff memory:d0000000-dfffffff ioport:7000(size=64) memory:c0000-dffff *-display description: 3D controller product: GM108M [GeForce 940M] vendor: NVIDIA Corporation physical id: 0 bus info: pci(a)0000:0a:00.0 version: a2 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=nouveau latency=0 resources: irq:52 memory:c4000000-c4ffffff memory:b0000000-bfffffff memory:c0000000-c1ffffff ioport:3000(size=128) Your help is much appreciated. Thank You. -- 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 6

[Bug 48756] New: Just Cause 3: Not starting at all
by WineHQ Bugzilla 15 Mar '20

15 Mar '20

https://bugs.winehq.org/show_bug.cgi?id=48756 Bug ID: 48756 Summary: Just Cause 3: Not starting at all Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: enp66025(a)eoopy.com Distribution: --- Created attachment 66661 --> https://bugs.winehq.org/attachment.cgi?id=66661 Log 5.0 stable When trying to start Just Cause 3, it doesn't start or show anything. Tested with wine 5.0 stable and wine 5.3 (staging) and installed DXVK 1.5.5. Running on Fedora 31 (64-bit). -- 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 48755] New: History table doesn't break long line
by WineHQ Bugzilla 15 Mar '20

15 Mar '20

https://bugs.winehq.org/show_bug.cgi?id=48755 Bug ID: 48755 Summary: History table doesn't break long line Product: WineHQ Bugzilla Version: unspecified Hardware: x86 URL: https://bugs.winehq.org/show_activity.cgi?id=28282 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: bugzilla-unknown Assignee: wine-bugs(a)winehq.org Reporter: huupoke12(a)gmail.com CC: austinenglish(a)gmail.com Distribution: --- Created attachment 66660 --> https://bugs.winehq.org/attachment.cgi?id=66660 Screenshot The history/activity table doesn't break long line, so the table will continue to expand to outside of the white area, which makes the text unreadable. An example of this can be seen at: https://bugs.winehq.org/show_activity.cgi?id=28282 -- 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 23249] New: Fallout 3: Most sound effects missing.
by wine-bugs＠winehq.org 15 Mar '20

15 Mar '20

http://bugs.winehq.org/show_bug.cgi?id=23249 Summary: Fallout 3: Most sound effects missing. Product: Wine Version: 1.2-rc4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: erik.weatherwax(a)gmail.com CC: eric.pouech(a)orange.fr See bug #21609. A purported fix for this bug was committed to the source tree as commit 258d42982cf526b3d9c59ccb522b27db3f519541, and included in release 1.2-rc4. However, I am experiencing the same issue (no sound effects with the exception of dialogue) as named in that bug report with a clean build of 1.2-rc4. Not surprisingly, regression testing leads back to the same bad commit: c62cf2e049ad37d9561957c47d23fc7ba13adc90 is first bad commit commit c62cf2e049ad37d9561957c47d23fc7ba13adc90 Author: Eric Pouech <eric.pouech(a)orange.fr> Date: Sat Jan 23 18:56:45 2010 +0100 winmm: In mmio manipulation, always ensure that we use a HFILE for mmio internal handlers (and not a HANDLE). :040000 040000 34f94674da252fbcf201217dddb31973ead906ca 59d18475ffc5e5e76df8b5277fb3250ef091721e M dlls named in 21609. -- 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 21

[Bug 47560] New: ws2_32: WS_getpeername behavior for on non-blocking tcp sockets during handshake
by wine-bugs＠winehq.org 15 Mar '20

15 Mar '20

https://bugs.winehq.org/show_bug.cgi?id=47560 Bug ID: 47560 Summary: ws2_32:WS_getpeername behavior for on non-blocking tcp sockets during handshake Product: Wine Version: 4.12.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: oysstu(a)gmail.com Distribution: --- Created attachment 64948 --> https://bugs.winehq.org/attachment.cgi?id=64948 Winedebug output This bug report deals with a difference in behavior of ws2_32:getpeername. It was discovered in the game Titan Quest Anniversary Edition when connection to a multiplayer lobby, but can be reproduced quite easily elsewhere. Once a non-blocking socket is connected to using ws2_32:WS_connect, and ws2_32:getpeername is called before the TCP handshake is completed, the resulting behavior is different on Windows and Linux. On Linux; before the TCP handshake is completed WSAENOTCONN is returned by ws2_32:getpeername. I.e. a socket is not connected before the handshake succeeds, hence one cannot get the peer name On Windows; from msdn the documentation clearly states that "The getpeername function can be used only on a connected socket.". Apparently, once the ws2_32:connect call has been made, it's defined as "connected" until the handshake times out because Windows returns successfully without an error and gives the peer info of the remote address it's trying to connect to. The error can be reproduced by using connect to an IP/port that does not reply followed by the call to getpeername Now, what happens in Titan Quest is that the developers has handled the WSAENOTCONN error by recreating the socket and doing the exact thing again instead of waiting for the socket to connect. Obviously, that's an error on their part, but it does work consistently on Windows. During the handshake, the tcpi_state field of TCP_INFO will show as TCP_SYN_SENT/TCP_SYN_RECV, which can be used to detect when this happens. I don't know the best way to get the peer name without calling getpeername though. I suppose it can be retrieved by re-implementing af_inet:inetgetname() without the check for TCP_SYN_SENT, but this probably affects portability (?). Another more portable way is to cache the address/port in wine, which obviously only works for outgoing connections (don't see why the behavior has to change for incoming connections anyway). af_inet:inetgetname(): https://github.com/torvalds/linux/blob/master/net/ipv4/af_inet.c#L760 I've attached a wine debug log, which shows the connect() call followed by a getpeername() that fails and raises an exception. -- 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 2

[Bug 48751] New: Claybook renders black starting screen.
by WineHQ Bugzilla 15 Mar '20

15 Mar '20

https://bugs.winehq.org/show_bug.cgi?id=48751 Bug ID: 48751 Summary: Claybook renders black starting screen. Product: Wine Version: 5.4 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: leslie_alistair(a)hotmail.com Distribution: --- Created attachment 66655 --> https://bugs.winehq.org/attachment.cgi?id=66655 loaddll,d3d9,d3d,d3d11,-dxgi,-dwrite When starting Claybook via stream, stops at a black starting screen. 015d:err:d3d:wined3d_debug_callback 0x8944540: "GL_INVALID_ENUM error generated. Invalid buffer format.". -- 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 0