https://bugs.winehq.org/show_bug.cgi?id=41054
Bug ID: 41054
Summary: Battle.net.exe deadlocks in CriticalSection
Product: Wine-staging
Version: 1.9.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: rankincj(a)yahoo.com
CC: erich.e.hoover(a)wine-staging.com, …
[View More]michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Trying to launch Blizzard's Battle.net.exe using Wine Staging 1.9.15 RPMs from
Fedora 24. However, the process deadlocks and prints messages like:
err:ntdll:RtlpWaitForCriticalSection section 0x10321d8 "?" wait timed out in
thread 0063, blocked by 0000, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x10321d8 "?" wait timed out in
thread 0063, blocked by 0000, retrying (60 sec)
This happens with both 32 bit and 64 bit prefixes. Disabling all "staging"
options via winecfg does not help.
--
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=40225
Bug ID: 40225
Summary: NtQuerySection returns wrong size
Product: Wine
Version: 1.9.3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: mail(a)georg.so
Distribution: ---
Created attachment 53743
--> https://bugs.winehq.org/…
[View More]attachment.cgi?id=53743
NtQuerySection test case via boost interprocess
When using NtQuerySection to get the file size of a file mapping the wine
result deviates from the native one.
With wine, it seems that the size is rounded up to the next page. On native
windows, the real file size is returned.
How to reproduce (e.g. with a mingw cross compile environment):
mkdir build
cd build
mingw64-cmake ..
mingw64-make
wine64 main
Actual behavior:
fixme:winediag:start_process Wine Staging 1.9.3 is a testing version containing
experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug
reports on winehq.org.
region.get_size() == 4096
sizeof(inp)-1 == 5
Assertion failed!
Program: Z:\home\gms\program\libixxxutil\build-case-win-rel\main.exe
File: /home/gms/program/libixxxutil/test/mapped_size_case/main.cc, Line 28
Expression: region.get_size() == sizeof(inp)-1
abnormal program termination
Expected behavior (as e.g. on Windows 7):
No output and success exit code.
How reproducible:
always
The test program uses Boost Interprocess functions for creating that mapping
and getting the size.
See also:
cf.
http://www.boost.org/doc/libs/1_60_0/doc/html/boost/interprocess/mapped_reg…
> The OS could allocate more pages than size/page_size(), but get_address() will always return the address passed in this function (if not null) and get_size() will return the specified size.
http://stackoverflow.com/a/26983182/427158
-> NtQuerySection
--
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=42288
Bug ID: 42288
Summary: Shantae and the Pirate's Curse - gameplay area resized
to a tiny rectangle
Product: Wine-staging
Version: 2.0-rc6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ikk_pl(a)yahoo.co.uk
…
[View More] CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 56999
--> https://bugs.winehq.org/attachment.cgi?id=56999
Screenshot showing the problem
Normally the game uses pixelized graphics during gameplay. In wine the play
area does not get resized to the entire screen, but instead stays at the same
size in a tiny rectangle in the middle of the screen.
(Note that the game doesn't run on vanilla wine, it needs staging patches for
the CreateDeferredContext call.)
--
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=42127
Bug ID: 42127
Summary: DOOM (2016): Crash on the main menu.
Product: Wine-staging
Version: 2.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: b.adam.martin(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, …
[View More]michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 56667
--> https://bugs.winehq.org/attachment.cgi?id=56667
terminal output and backtrace
Since only one attachment is allowed, I have pasted the terminal output at the
head of the backtrace.txt. Search for "backtrace" to skip.
4.8.13-1-ARCH
GTX 770
nvidia 375.26-1
i5 4670k
wine-2.0-rc2 (Staging) --- The Arch repos haven't yet updated to rc3; it's
flagged.
$ wine DOOMx64vk.exe
The game launches fine, goes through the splash screen, and then when presented
with the main menu, abruptly crashes.
I have tried setting different Windows versions winecfg, same result with each.
I have also run $ wine DOOMx64.exe, same result.
--
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=39368
Bug ID: 39368
Summary: Some games (F.E.A.R. 1, Hitman: Contracts) crash on
start when EAX(Environmental Audio Extensions) enabled
Product: Wine-staging
Version: 1.7.40
Hardware: x86
URL: http://www.gamershell.com/download_10167.shtml
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: …
[View More]P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 52478
--> https://bugs.winehq.org/attachment.cgi?id=52478
F.E.A.R. demo backtrace
When EAX is enabled in staging, some games crash on start.
Two examples are F.E.A.R. or Hitman: Contracts.
Both games have demos to reproduce the problem.
Hitman: Contracts demo:
http://www.gamershell.com/download_5663.shtml
wine-1.7.51-268-g781b88b (Staging)
Fedora 22 32-bit
Alsa 1.0.29, stereo speaker setup (PA is not running)
Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
--
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=43543
Bug ID: 43543
Summary: Wrong sounds in Within a Deep Forest
Product: Wine-staging
Version: 2.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: wine(a)thecybershadow.net
CC: erich.e.hoover(a)wine-staging.com, …
[View More]michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
The sound effects in Within a Deep Forest seem to be broken. Specifically, the
wrong samples seem to be used.
For example, selecting a ball material produces a metallic sound (instead of
the loud "twirp"), and bouncing around with the initial ball material plays
various hums and occasionally splashing noises.
Reproducible with WaDF version 1.1.4 and wine-staging 2.14 on a clean
WINEPREFIX. Not reproducible with wine 2.14.
--
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=42318
Bug ID: 42318
Summary: Sleeping Dogs - CSMT prevents getting past
introductory videos, without CSMT the videos are all
purple and continue looping without starting the
actual game.
Product: Wine
Version: 2.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
…
[View More] Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: casparcedro96(a)gmail.com
Distribution: ---
Created attachment 57063
--> https://bugs.winehq.org/attachment.cgi?id=57063
Crash with CSMT enabled
So it seems Sleeping Dogs does not like CSMT for some reason and even without
it I cannot seem to get past the intro videos which show up pink but the audio
is perceptible - it continues to loop playing the videos but never gets into
the game.
--
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=40458
Bug ID: 40458
Summary: Photoshop CC 2015 Amtlib issues
Product: Wine-staging
Version: 1.9.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: msnduy(a)hotmail.de
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-…
[View More]team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 54210
--> https://bugs.winehq.org/attachment.cgi?id=54210
logs
I have issues with running Photoshop CC 2015 (64bit) in Wine-Staging.
It installs fine with both staging and stable (PDApp only works with Staging).
But I can't start it in staging without an error although in wine stable it
works normally but the user interface of photoshop is somehow not correctly
rendered.
Wine-Staging (Compiled from git upstream):
Photoshop shows an error with the error code 16. By luck I also came across the
amtlib.log file which also contained error message with the same error code,
saying:
04/12/16 22:38:32:097 | [ERROR] | | | | AMT | | | 57 | Error: Failed to
update RW check key !
04/12/16 22:38:32:097 | [ERROR] | | | | AMT | | | 57 | ERROR: SLCache is
not writable, hence exiting. (Errno = 16)
I am sure it's the amtlib what is causing the issue as I didn't get these lines
with wine-stable.
The tricky part is that I don't know what patch from wine-staging is causing
this issue.
I attached the log files which are interesting.
I am not sure now how to debug this further as the wine debug output isn't
helpful either (basically the same output as wine stable).
What might by broken can be Registry/memory/file access, the problem is that I
don't know what api calls amtlib is doing.
Well, if someone can give me further instructions how to debug the issue I
would be glad. Also if you have enough time or whatsoever you could try install
Photoshop CC 2015 :).
--
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=43761
Bug ID: 43761
Summary: World of Warcraft d3d11 textures rendering regression
and other... Wine Staging 2.17
Product: Wine-staging
Version: 2.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: zefkerrigan(a)…
[View More]gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 59257
--> https://bugs.winehq.org/attachment.cgi?id=59257
World of Warcraft d3d11 textures rendering regression. Wine Staging 2.17
Sorry, but I really do not have the opportunity to find out if this bug is in
the development Wine branch, because World of Warcraft can only be launched in
Wine Staging, but it can not be launched in a "vanilla" development Wine
branch.
So, I using only Wine Staging.
I could not get the output of the console, because, unfortunately, when I tried
to run the game through the console, I did not manage to run the game until the
stage of character management/movement. That is, the game hangs up every time
the progress bar ends after clicking on the "Enter the World" button. But, I
was surprised that the game is normally run through a shortcut on the dock bar,
which also contains the same command in the line
Exec=wine64 'c:/Program Files (x86)/World of Warcraft/Wow-64.exe'
which I entered into the console (but, without "Exec=", of course).
When I used Wine Staging 2.16 I did not have any noticeable rendering bugs with
the World of Warcraft in DirectX11 mode, or DirectX9.
But, with Wine Staging 2.17 I began to see what's on the attached screenshot if
WoW is running in DirectX11 mode. But, in DirectX9 mode this bug does not
appear, and there are no any distortions in the graphics.
My specs:
Arch Linux x86_64 with latest updates, GNOME.
GPU Radeon HD7770 with latest Mesa.
Wine Staging 2.17 with CSMT is on, x64 Wine prefix, 64bit WoW build.
--
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=43793
Bug ID: 43793
Summary: d3d11-Deferred_Context patchset is missing dependency
on wined3d-1DTextures
Product: Wine-staging
Version: 2.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: shtetldik(a)gmail.com
…
[View More] CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
When d3d11-Deferred_Context is applied, compilation fails like this:
gcc -m64 -c -o wspool.o
/home/user/build/wine-git/wine-source/dlls/winspool.drv/wspool.c -I. \
-I/home/user/build/wine-git/wine-source/dlls/winspool.drv -I../../include \
-I/home/user/build/wine-git/wine-source/include -D__WINESRC__ -D_SPOOL32_
-D_REENTRANT -fPIC \
-Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body
-Wignored-qualifiers \
-Wshift-overflow=2 -Wstrict-prototypes -Wtype-limits
-Wunused-but-set-parameter -Wvla \
-Wwrite-strings -Wpointer-arith -Wlogical-op -O3
../../tools/winegcc/winegcc -o winscard.dll.so -B../../tools/winebuild -m64
-fasynchronous-unwind-tables -shared
/home/user/build/wine-git/wine-source/dlls/winscard/winscard.spec \
winscard.o rsrc.res ../../libs/port/libwine_port.a
/home/user/build/wine-git/wine-source/dlls/wined3d/resource.c: In function
‘wined3d_resource_update_info’:
/home/user/build/wine-git/wine-source/dlls/wined3d/resource.c:403:32: error:
‘WINED3D_RTYPE_TEXTURE_1D’ undeclared (first use in this function); did you
mean ‘WINED3D_RTYPE_TEXTURE_3D’?
else if (resource->type == WINED3D_RTYPE_TEXTURE_1D ||
^~~~~~~~~~~~~~~~~~~~~~~~
WINED3D_RTYPE_TEXTURE_3D
Explicitly adding wined3d-1DTextures helps.
--
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]