December 2020 - Wine-Bugs - list.winehq.org

[Bug 48037] New: In World of Tanks in battle, mouse stuck in the middle
by WineHQ Bugzilla May 8, 2021

May 8, 2021

https://bugs.winehq.org/show_bug.cgi?id=48037 Bug ID: 48037 Summary: In World of Tanks in battle, mouse stuck in the middle Product: Wine Version: 4.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: HASH.DuOrden(a)gmail.com Distribution: --- Starting with wine 4.17, in battle mouse is stuck to the center of the screen, it's just wiggles in middle and do not move the targeting reticle. This feels very similar to what happens when "MouseWarpOverride"="force" with only difference that with "MouseWarpOverride"="force" mouse acts like this all the time but here mouse are stuck to center only when game requests the lock, I'm not sure that I get the technical part correctly. PS:This feels like a continuation of a bug #47771. -- 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 18

[Bug 47932] New: Mouse-clicks no longer recognized `World of Warships`
by WineHQ Bugzilla May 8, 2021

May 8, 2021

https://bugs.winehq.org/show_bug.cgi?id=47932 Bug ID: 47932 Summary: Mouse-clicks no longer recognized `World of Warships` Product: Wine-staging Version: 4.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lukas.lueg(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- `World of Warships 0.8.8` used to work more or less flawlessly in wine-4.16; since the update to 4.17 left/right mouse clicks are no longer recognized at all in the main menu (including login), rendering the application unusable. The problem appeared since `wine-4.17-2" on x86_64, using Fedora 30. Downgrading to 4.16 fixed the problem. -- 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 50237] New: The Sims 3 - cannot interact with objects and floor.
by WineHQ Bugzilla May 8, 2021

May 8, 2021

https://bugs.winehq.org/show_bug.cgi?id=50237 Bug ID: 50237 Summary: The Sims 3 - cannot interact with objects and floor. 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: germanapps(a)gmail.com Distribution: --- Created attachment 68743 --> https://bugs.winehq.org/attachment.cgi?id=68743 Wine logs After upgrading from Wine Staging 5.21 to Staging 5.22 a serious bug appeared: When you interact with floor or an object in "Life" mode, action menu is broken and moved to the far right side of the screen and game cursor is moved to the far left side. Video footage of the bug here: http://www.mediafire.com/file/v7wmvjcghtl28pz/sims3-wine5.22-mousebug.mp4/f… I have done some tests beginning from 5.9 (which was the last reported version and doesn't even allow to initialize a new prefix and throws errors instead) to 5.22 and only 5.22 has this bug. It is consistent, so there should be no problem for others to reproduce it. Tested on Debian 10.6 Stable with KDE, Linux Mint 19.3 Xfce and Linux Mint 20 Xfce. -- 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 50395] New: Star Wars: Galactic Battlegrounds needs dpmodemx.dll.SPInit
by WineHQ Bugzilla May 8, 2021

May 8, 2021

https://bugs.winehq.org/show_bug.cgi?id=50395 Bug ID: 50395 Summary: Star Wars: Galactic Battlegrounds needs dpmodemx.dll.SPInit Product: Wine-staging Version: 6.0-rc3 Hardware: x86-64 URL: https://www.fileplanet.com/archive/p-2037/Star-Wars-Ga lactic-Battlegrounds-Demo OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 69013 --> https://bugs.winehq.org/attachment.cgi?id=69013 terminal output After the dxdiag-new-dlls patchset has been added to Staging, such games as Age of Empires 2, Star Wars: Galactic Battlegrounds crash immediately after starting. -- 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 50162] New: msvcrt-Math_Precision patchset breaks audio in Diablo III
by WineHQ Bugzilla May 8, 2021

May 8, 2021

https://bugs.winehq.org/show_bug.cgi?id=50162 Bug ID: 50162 Summary: msvcrt-Math_Precision patchset breaks audio in Diablo III Product: Wine-staging Version: 5.22 Hardware: x86-64 URL: https://www.blizzard.com/download/confirmation?platfor m=windows&product=d3 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maciej.stanczew+b(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Regression SHA1: 7734f7a8087291ec15c4d1adfe1a6db055972266 Distribution: ArchLinux Created attachment 68678 --> https://bugs.winehq.org/attachment.cgi?id=68678 Use precise_cosh in unix_cosh instead of unix_cos Steps to reproduce: 1. Lower your audio volume to not break ears; 2. Launch Diablo III ("wine Diablo\ III64.exe -launch"). Expected result: Menu music starts playing, UI sounds work. Actual result: There is about 2 seconds of loud, garbled audio, then silence. I've bisected this to msvcrt-Math_Precision patchset and its latest rebase. Wine 2fb08bed46f + Staging 0192a7b3 don't have the issue. Wine c72e1b096d1 + Staging 7734f7a8 is where the problem is introduced. Building Staging 5.22 with "-W msvcrt-Math_Precision" also produces a working version. Looking at the patchset's rebase (7734f7a8), we see that precise_cosh was used in unix_cos instead of unix_cosh. Reverting unix_cos to use cos, and using precise_cosh instead in unix_cosh, solves the issue for me. I've attached a patch with these changes. -- 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 16

[Bug 49374] New: skyrim is unable to run under staging 5.10
by WineHQ Bugzilla May 8, 2021

May 8, 2021

https://bugs.winehq.org/show_bug.cgi?id=49374 Bug ID: 49374 Summary: skyrim is unable to run under staging 5.10 Product: Wine-staging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: l12436(a)yahoo.com.tw CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 67434 --> https://bugs.winehq.org/attachment.cgi?id=67434 last log with error skyrim is unable to run in recently wine. error is in the attachment. This is happened for a period of time. I have tested on vanilla wine, it is able to run without any issue. -- 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 10

[Bug 50255] New: server/fd.c:1986:18: error: 'O_SYMLINK' undeclared
by WineHQ Bugzilla May 8, 2021

May 8, 2021

https://bugs.winehq.org/show_bug.cgi?id=50255 Bug ID: 50255 Summary: server/fd.c:1986:18: error: 'O_SYMLINK' undeclared Product: Wine-staging Version: 6.0-rc1 Hardware: x86-64 OS: FreeBSD Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gerald(a)pfeifer.com CC: leslie_alistair(a)hotmail.com, marcus(a)jet.franken.de, z.figura12(a)gmail.com Created attachment 68780 --> https://bugs.winehq.org/attachment.cgi?id=68780 Proposed patch to unbreak the build 6.0-rc1 features a new build failure versus 5.22: server/fd.c: In function 'open_fd': server/fd.c:1986:18: error: 'O_SYMLINK' undeclared (first use in this function) 1986 | flags |= O_SYMLINK; | ^~~~~~~~~ Indeed O_SYMLINK appears nowhere under /usr/include on FreeBSD 11.x nor on my openSUSE system with glibc 2.32. The latter does have O_PATH, so the following snippet from server/fd.c comes to the rescue: #if !defined(O_SYMLINK) && defined(O_PATH) # define O_SYMLINK (O_NOFOLLOW | O_PATH) #endif The attached patch fixes (or works around) this issue. Successfully tested on FreeBSD 11/i386. -- 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 44207] New: Wine fails to run Unigine Heaven 4.0
by wine-bugs＠winehq.org May 8, 2021

May 8, 2021

https://bugs.winehq.org/show_bug.cgi?id=44207 Bug ID: 44207 Summary: Wine fails to run Unigine Heaven 4.0 Product: Wine-staging Version: 2.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: b1779506(a)trbvn.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 59977 --> https://bugs.winehq.org/attachment.cgi?id=59977 Crash log Download URL: https://benchmark.unigine.com/heaven Download link: http://assets.unigine.com/d/Unigine_Heaven-4.0.exe File: Unigine_Heaven-4.0.exe See log. -- 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 9

[Bug 50106] New: ESync broke mountmgr
by WineHQ Bugzilla May 8, 2021

May 8, 2021

https://bugs.winehq.org/show_bug.cgi?id=50106 Bug ID: 50106 Summary: ESync broke mountmgr Product: Wine-staging Version: 5.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: javirrdar(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- After wine update 5.19 (gb49e8743) to 5.21 (ge2d9f97b) mountmgr just stop working on my setup. Symptoms are constant spamming: > fixme:service:scmdatabase_autostart_services Auto-start service L"MountMgr" failed to start: 50 > fixme:service:scmdatabase_autostart_services Auto-start service L"winebus" failed to start: 50 And winecfg can't connect to Mount Manager, installers (e.g. GoG installer) doesn't display anything on directory select. If you disable esync\fsync using env variables, it works. It seems like this bug appears on 5.19 (gbe9c9681) and newest wine-staging versions. Oddly, with WINEDEBUG=+all it works (slowly, but works). Some race condition in ESync? How to reproduce: - Create new wine prefix - Launch winecfg (issue not occurs) - Close winecfg - Launch winecfg again (issue occurs) After that issue will occurs every 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 14

[Bug 46021] New: Mass Effect 3 | Mouse uncontrollably / jumps around. Keyboard button "locks in" sometimes
by wine-bugs＠winehq.org May 8, 2021

May 8, 2021

https://bugs.winehq.org/show_bug.cgi?id=46021 Bug ID: 46021 Summary: Mass Effect 3 | Mouse uncontrollably / jumps around. Keyboard button "locks in" sometimes Product: Wine-staging Version: 3.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: roquene(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Moving mouse let it jump uncontrollably around. very slow minimal movement seem to work, but faster let the player character make a 180°. moving the mouse upwards sometimes "locks" the camera facing upwards and only possible to turn it in circle. Moving the character per keyboard sometimes locks in. So moving forward and releasing the button and the character keeps moving until key pressed again. in game menu comparable behaviour. moving over menupoint only highlight it if moved very slow. problem does not occur in normal 3.18 and not with old versions like staging-2.8 could not test later version. staging-2.21 for example shows only black screen. -- 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 7