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: 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.
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, 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.
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
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.
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-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.
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)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.
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
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.
https://bugs.winehq.org/show_bug.cgi?id=42815
Bug ID: 42815
Summary: Autodetection of drives in winecfg crashes Wine in
Wine (Staging)
Product: Wine-staging
Version: 2.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: frail.knight(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 57876
--> https://bugs.winehq.org/attachment.cgi?id=57876
Backtrace
Autodetection of drives in winecfg crashes Wine in Wine (Staging)
I did a clean system install.
I did a clean install of Wine 2.5 (Staging).
$ wine --version
wine-2.5 (Staging)
I was going through the basic setup in Wine.
I started winecfg.
I clicked the Drives tab.
I clicked the Autodetect button on the Drives tab.
Wine Crashes.
This has not happened to me in previous versions such as Wine 2.4 Staging.
Uploading the backtrace and console output...
--
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.
https://bugs.winehq.org/show_bug.cgi?id=43435
Bug ID: 43435
Summary: x32dbg hangs when starting program
Product: Wine-staging
Version: 2.13
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
CC: dmitry(a)baikal.ru, erich.e.hoover(a)wine-staging.com,
michael(a)fds-team.de, sebastian(a)fds-team.de
Distribution: ---
When starting a program to debug, it displays a message like "Breakpoint at
1000154C7 set" and then freezes.
Bisected to
commit 9c509cbf8879a4283cb134321764c1024bcaf855
Author: Dmitry Timoshkov <dmitry(a)baikal.ru>
Date: Wed Mar 16 20:23:28 2016 +0800
kernel32: Implement K32GetMappedFileName. (v2)
Reverting fixes the 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.
https://bugs.winehq.org/show_bug.cgi?id=41544
Bug ID: 41544
Summary: Pressing L-ALT key loses focus from game
Product: Wine-staging
Version: 1.9.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: xkendy(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Uppon started game, after I press button L-ALT, the game lose mouse focus.
Focus mouse pointer is in system (above the game window). After another
pressing L-ALT, or mouse click focus is returned to game.
Affected (tested) games: World Of Tanks (patch 0.9.16), World Of Warplanes
(patch 1.9.6).
How to reproduce:
Fresh instalation WOT and WOWP using this guide for WOT:
https://www.youtube.com/watch?v=CTU0vICF9O4
WOT:
1.9.20-staging L-ALT problem present
1.9.19-staging (or lower): wot not work
WOWP:
1.9.20-staging L-ALT problem present
1.9.19-staging (or lower): L-ALT work correctly
Tested on:
- old installed game WOT
- fresh installed WOT (using guid on youtube)
- fresh installed WOWP (using guid on youtube for WOT)
System: UBUNTU 14.04 LTS x86_64, Graphics: GeForce GT640 (driver 340, tested
also version 372), 8GB RAM, CPU: i5
--
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.
https://bugs.winehq.org/show_bug.cgi?id=43511
Bug ID: 43511
Summary: Crash when launching Assassins Creed 4
Product: Wine-staging
Version: 2.14
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jgarciaalo(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 58896
--> https://bugs.winehq.org/attachment.cgi?id=58896
Crash log
An error occurs when starting Assassins Creed 4.
The game arrives to the first screen but throws a fatal error (seems a
nullpointer).
Note that this game worked on 2.7-Staging, 2.8-Staging and 2.9-Staging.
The next version I checked was the 2.13-staging that had another crash already
solved.
Now in 2.14-staging it crash here.
Submited files:
Error screenshot: ac4_error.png
Crash log: ac4_error.txt
--
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.