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
…
[View More]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.
[View Less]
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.…
[View More]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.
[View Less]
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, …
[View More]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.
[View Less]
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)…
[View More]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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=51062
Bug ID: 51062
Summary: Warframe through Lutris no longer has dx12 option in
Launcher with wine staging 6.7
Product: Wine-staging
Version: 6.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jhu543369(a)gmail.…
[View More]com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Running Warframe through Lutris with a custom runner pointing to
wine-6.6-staging/bin/wine64 and in the launcher options, dx12 experimental is
available. Switch runner to wine-6.7-staging/bin/wine64 and the launcher no
longer has a dx12 experimental option, just dx11. World of Warcraft through
Lutris with the 6.7 runner works fine with dx12.
--
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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=51069
Bug ID: 51069
Summary: 5 builds of winehq-staging are broken in Debian
Stretch
Product: Wine-staging
Version: 5.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lucmove(a)gmail.com
CC: …
[View More]leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 69930
--> https://bugs.winehq.org/attachment.cgi?id=69930
Output of first attempt to run right after the upgrade or downgrade
As of today, April 26 2021, all the 5 latest builds of winehq-staging are
broken on Debian Stretch.
5.12 is the newest build I can use. Versions 5.13, 5.14, 5.15, 5.16 and 5.17.2
all refuse to run on Debian Stretch.
There aren't any newer versions than 5.17.2 in the repository.
I have this line in my apt/sources.list file so I guess I'm downloading all
these broken versions from you:
deb https://dl.winehq.org/wine-builds/debian/ stretch main
The output says, among other things, "run_wineboot failed to start wineboot
c00000e5"
Although I've found reports with that line on Google, I've been unablle to find
a solution and I'm not sure the developers know that so many of the latest
versions are broken. I assume not, based on the number of latest versions that
are broken.
--
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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=51026
Bug ID: 51026
Summary: Winbox don't start
Product: Wine-staging
Version: 6.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: letarch(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
…
[View More]Distribution: ---
Winbox don't start. Tracelog say what not have required libs.
But version wine 6.5 works normal.
--
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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=51003
Bug ID: 51003
Summary: Regression: Multiple games have broken input in
wine-staging 6.6
Product: Wine-staging
Version: 6.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: linards.liepins(a)gmail.com
…
[View More] CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
See bugreports in RHBZ for detailed explanation:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-9ab0461da6
--
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.
[View Less]
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
…
[View More] 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.
[View Less]
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)…
[View More]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.
[View Less]