http://bugs.winehq.org/show_bug.cgi?id=32237
Bug #: 32237
Summary: A slower speed of light: Game crashes after Intro
Product: Wine
Version: 1.5.14
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fox6x6x6(a)gmail.com
Classification: Unclassified
Created attachment 42525
--> http://bugs.winehq.org/attachment.cgi?id=42525
wine output
The game starts normally and you can watch the Intro, but after that the game
crashes.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=29128
Bug #: 29128
Summary: L.A. Noire fails to launch
Product: Wine
Version: 1.3.33
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: peanuthead_069(a)yahoo.com
Classification: Unclassified
Created attachment 37529
--> http://bugs.winehq.org/attachment.cgi?id=37529
Terminal log of launch attempt.
Well, since no one seems to have tested this game yet, I decided to take
matters into my own hands. The installer now works on 1.3.33, but the game
itself doesn't. All the necessary dependencies are installed already, but still
even the mandatory patch required to activate and launch the game doesn't work.
Even the no-spaces workaround when installing the game showed no signs of the
Noire launching.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=39847
Bug ID: 39847
Summary: Installation ABBYY Aligner2
Product: Wine
Version: 1.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: msrom(a)mail.ru
Distribution: ---
Created attachment 53196
--> https://bugs.winehq.org/attachment.cgi?id=53196
log
Cannot install application ABBYY Aligner2
--
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=44077
Bug ID: 44077
Summary: Overwatch: Within the first minute of game play the
entire OS stops rendering (requires hard reboot)
Product: Wine-staging
Version: 2.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sander.smid(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
wine-2.21 (Staging)
Linux oribi 4.13.12-1-ARCH #1 SMP PREEMPT Wed Nov 8 11:54:06 CET 2017 x86_64
GNU/Linux
Graphics: Card: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX
470/480/570/580]
Display Server: x11 (X.Org 1.19.5 ) drivers: nvidia (unloaded:
modesetting,fbdev,nv,vesa,nouveau)
Resolution: 1920x1200(a)59.95hz
OpenGL: renderer: AMD Radeon RX 480 Graphics (AMD POLARIS10 / DRM
3.18.0 / 4.13.12-1-ARCH, LLVM 5.0.0)
version: 4.5 Mesa 17.2.5
env WINEPREFIX="/games/BattleNet" /usr/bin/wine
/games/BattleNet/drive_c/Program\ Files\ \(x86\)/Overwatch/Overwatch.exe
--
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=45291
Bug ID: 45291
Summary: Dauntless Open Beta : Cant play Intro Video resulting
in not responding black screen
Product: Wine
Version: 3.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winegstreamer
Assignee: wine-bugs(a)winehq.org
Reporter: asembus(a)gmail.com
Distribution: ---
Tried to test the open beta version for dauntless with addtional dotnet
installation. the launcher works fine but when the game start it doesnt show
intro video and ends up with black screen.
i've read the log and it seems the error is caused when the video cannot be
shown
[2018-06-02T11:11:33,434][ 0][LogMediaUtils][Error]Cannot play
file://../../../Archon/Content/MoviesPackaged/MediaExample.mp4, because none of
the enabled media player plug-ins support it:
--
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=44089
Bug ID: 44089
Summary: Strider crashes after loading screen
Product: Wine
Version: 2.21
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx11
Assignee: wine-bugs(a)winehq.org
Reporter: strider(a)strycore.com
Distribution: ---
Created attachment 59805
--> https://bugs.winehq.org/attachment.cgi?id=59805
backtrace of the crash
While the main menu works fine, when starting a game, the game crashes. This is
a regression that started in Wine Staging 2.16, when the deferred context patch
(https://dev.wine-staging.com/patches/181/) was introduced. I had a build of
Wine Staging 2.15 with that patch enabled and I noticed crashes starting with
that build and onward until the latest tested, Staging 2.21.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=18104
Summary: Final Draft: text to speech fails
Product: Wine
Version: 1.1.19
Platform: All
URL: http://www.finaldraft.com/downloads/demo-final-draft.php
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jens(a)porup.com
Final Draft is the screenwriter's standard word processor.
It offers a text to speech feature that does not work in wine. It doesn't break
anything if you try; the buttons just don't do anything at all.
Terminal output coming soon.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=42136
Bug ID: 42136
Summary: switching tab in sapi.cpl crashes control
Product: Wine
Version: 2.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fiendishx(a)gmail.com
Distribution: ---
Created attachment 56693
--> https://bugs.winehq.org/attachment.cgi?id=56693
console log
sapi.cpl is installed by the Microsoft Speech SDK installer from
https://download.microsoft.com/download/B/4/3/B4314928-7B71-4336-9DE7-6FA4C…
(or via winetricks)
$ wine control '.wine/drive_c/Program Files (x86)/Common Files/Microsoft
Shared/Speech/sapi.cpl'
brings up the Speech Properties control panel.
Choosing the tab labeled "Text To Speech" crashes the control. Console log
attached.
--
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=45111
Bug ID: 45111
Summary: Winamp - Milkdrop complains
Product: Wine
Version: 3.7
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: stu.axon(a)gmail.com
Distribution: ---
Clicking the visualisation tab displays a dialog:
MILKDROP ERROR
Error compiling ps_2_0 warp shader
:127:8:error: syntax error, unexpected KW_TEXTURE
Then you click OK and get another dialog
MILKDROP ERROR
Your hardware says that it supports shader model
3.0 [PSVersion==0x300],
but it doesn't seem to do it properly -
maybe your display is just buggy.
You might want to try updating your display driver
to the latest WHQL driver from the chipset
manufacturer
(NVIDIA, ATI, etc)
Googling for
wine winamp "ps_2_0 warp shader"
Shows the issue going back to at least 2010
Tested on AMD Radeon Vega 8 - on wine 3.7-staging
--
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=40502
Bug ID: 40502
Summary: Global objects constructors fail when invoking
standard libs
Product: Wine
Version: 1.8.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: winelib
Assignee: wine-bugs(a)winehq.org
Reporter: mirko.ortensi(a)gmail.com
Distribution: ---
I managed to recompile and link my win32 application but at execution time, it
crashes because of a segmentation fault where memset (or the bare
printf("HELLO")) is invoked in the global object constructor (any call to
standard C library is enough to trigger the crash).
The global object is built in the stack, then it seems that at launch time my
object constructor is called before C Standard Library is ready.
Now, as a workaround I can declare a pointer to global object and instantiate
it in the main (tested, it works)...though...this is something I'd like to
avoid to keep the code as original as possible. Removing the global objects,
everything works like a charm.
As far as I understand, global object constructors are called after Wine
infrastructure is ready to go, though I have doubts now regarding C Standard
Library.
(Please check 8.3.3. Starting a Winelib process
https://www.winehq.org/docs/winedev-guide/x3172)
This code reproduces the error:
#include <stdio.h>
class Printer
{
public:
Printer(){printf("HI\n");}
};
Printer p;
int main(void)
{
return 0;
}
The issue is reproduced by this code linking to msvcrt:
wineg++ -mno-cygwin issue.cpp -o issue
Linking to system libs, this code does not reproduce the issue.
wineg++ issue.cpp -o issue
Now, in my code (pretty big software I am porting to Linux) I still need to
isolate root cause, issue is reproduced even linking against system libraries
(not Wine's msvcrt, then). Anyway, I think there's a bug somewhere when linking
to msvcrt even in this silly piece of code.
--
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.