https://bugs.winehq.org/show_bug.cgi?id=43686
Bug ID: 43686
Summary: Fallout New Vegas not starting on Fedora
Product: Wine-staging
Version: 2.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: delentef(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 59138
--> https://bugs.winehq.org/attachment.cgi?id=59138
Trace of Fallout NV (fdelente)
Hello,
I'm on Fedora 26 64 bits, with wine staging 2.15 in a 32-bit prefix, I
installed Fallout New Vegas through Steam but it doesn't start: the launcher
shows up, I click play, I have the splash screen (the game is in windowed mode)
showing the copyrights text but it closes and Fallout NV stops here. I have
installed d3dx9 and quartz with winetricks though, as suggested on d3dx9, and
have plenty of other games working correctly (Dark Souls I, II and II Scholar,
Bioshock 2, Dishonored, Borderlands...)
A trace with WINEDEBUG=+d3d doesn't show any error, I only have fixmes for
gstreamer:
fixme:gstreamer:unknown_type Could not find a filter for caps:
application/x-id3
I installed all i686 versions of the gstreamer plugins, I tried disabling the
gstreamer library in winecfg, but no luck, the game won't start.
I attach the log I have obtained in the console.
--
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=44696
Bug ID: 44696
Summary: Dark Souls: Prepare to Die Edition 2.0 - Crash When
Returning to the Title Screen
Product: Wine
Version: 3.3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: escomk3(a)hotmail.com
Distribution: ---
Created attachment 60703
--> https://bugs.winehq.org/attachment.cgi?id=60703
Terminal Output with Backtrace
Sometimes, not always, the game crashes when returning to the title screen
(either via the in-game quit option, or by backing out after selecting 'New
Game', which sometimes seems to trigger the crash more often-like).
The game has been also seen to crash every time when entering the title screen,
after it had crashed once before, but this was 'fixed' by making sure the Wine
processes were terminated ('wineserver -k' for example), although that may have
been experienced in a not-so-clean Wine prefix.
Both bug 38490 and bug 43398 seem different enough (and somewhat abandoned) for
this to be a separate issue (though they are very similar; perhaps the root
cause is not very different).
--
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=38765
Bug ID: 38765
Summary: VMR9 steals focus from within Wine
Product: Wine
Version: 1.7.38
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: quartz
Assignee: wine-bugs(a)winehq.org
Reporter: jasonwinter(a)hotmail.com
Distribution: ---
When a graph transitions from pause to run with a VMR9 video window present
(which has been owned by another window with put_Owner) the Wine window
implementing VMR9 is incorrectly given focus. This will steal focus from an
active window in a different process, and because the actual owner wasn't
active, all focus is lost within the Wine subsystem.
I.E. Task bar says original app is focused, but that window title has gone
grey, the VRM9 window title goes blue but nothing actually has focus.
Note, if the graph is run when the app owning the VMR9 is focused, everything
works as normal including the Message-Drain API in VMR9, although focus is
still lost from the app owner window. This possibly obscures this bug.
Note also, I think "other things" like altering mouse pointer visibility with
mouse-move messages also cause the Wine window implementing VMR9 to gain focus,
so simply moving the mouse over video output can steal focus from a different
active application within Wine.
--
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=43110
Bug ID: 43110
Summary: Unhandled exception: assertion failed in 32-bit code
(0xf76fec79) when running Indycar Series
Product: Wine
Version: 2.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: opnoack(a)icloud.com
Distribution: ---
Created attachment 58307
--> https://bugs.winehq.org/attachment.cgi?id=58307
Screenshot
OS: Antergos/Arch Linux
Kernel: Linux version 4.11.2-1-ARCH (builduser@tobias) (gcc version 7.1.1
20170516 (GCC) ) #1 SMP PREEMPT Mon May 22 06:53:49 CEST 2017
I followed the guide on
https://appdb.winehq.org/objectManager.php?sClass=version&iId=28433:
- Copied files from Program Files to home folder
- Installed dinput8 with winetricks
- Started game and received a backtrace
I attached a screenshot, the stdout and stderr logs and the backtrace itself.
Stdout and stderr: https://pastebin.com/tVJsqsXF
Backtrace: https://pastebin.com/6ETbyyQz
--
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=38668
Bug ID: 38668
Summary: wolfestein the new blood
Product: Wine
Version: 1.7.43
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: inkobj
Assignee: wine-bugs(a)winehq.org
Reporter: pinturiano(a)gmail.com
Distribution: ---
Created attachment 51595
--> https://bugs.winehq.org/attachment.cgi?id=51595
wolfestein the new blood issue
Installed Wolfestein, the old blood via Steam and all works fine.
Played the game, also worked fine.
I got crash after restarting the game, after loading the saved games.
The bug issue is on xaudio2_7 i think.
--
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=19496
Summary: Irfanview in Wine: Invalid MCI Device ID
Product: Wine
Version: unspecified
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ray_woodcock(a)hotmail.com
I'm using Ubuntu 9.04 (Jaunty). I have installed Wine 1.1.26 and IrfanView
4.25. The installation is partially successful. I can open Irfanview, for
example, and change its Preferences.
I have set IrfanView to be the default program for .wav files by right-clicking
on a .wav file and selecting Properties > Open With > IrfanView. When I
double-click on a .wav, I get this error message:
"Error: Windows can't play this file! Windows error text: Invalid MCI device
ID. Use the ID returned when opening the MCI device.. You can try to install
additional video/audio codecs from this site: www.fourcc.org/indexcod.htm or
try the DirectShow option in Properties->Video."
The DirectShow option does not fix the problem. After I click OK on this error
message, it repeats. I click OK again. This happens a total of four times. Then
IrfanView plays the audio file, with a little window that says "No Device." If
I click the arrow in IrfanView, to move on to the next audio file, the same
routine repeats.
--
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=44122
Bug ID: 44122
Summary: Tomb Raider VI can not play video or crash if quarkz
is enabled
Product: Wine
Version: 2.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: legluondunet(a)free.fr
Distribution: ---
Created attachment 59852
--> https://bugs.winehq.org/attachment.cgi?id=59852
TRAOD wine 2.21 terminal log
Hello,
I installed Tomb Raider VI from Steam and when I launched the game, only a
black screen instead of video.
It's a known problem (see winehq tests).
I installed quartz with winetricks, the first video played correctly (EIDOS
logo) and then the game crashed.
Terminal log joined.
error message from TRAOD launcher:
Build Sep 17 2003 15:53:15
The Following Error has occured
GAME_ERROR_STRUCTURED_EXCEPTION_HANDLE
TRAOD_P4.exe caused a EXCEPTION_ACCESS_VIOLATION in module <UNKNOWN> at
0023:7D652705
0023:7D652705 <UNKNOWN>
0023:35542138 quartz.dll
0023:3553C1C2 quartz.dll
0023:3553C9FA quartz.dll
0023:3553862A quartz.dll
0023:3553840B quartz.dll
0023:35538358 quartz.dll
0023:3557170F quartz.dll
0023:3556BB66 quartz.dll
0023:00418F0A TRAOD_P4.exe
0023:00418061 TRAOD_P4.exe
0023:0041A520 TRAOD_P4.exe
0023:005344D8 TRAOD_P4.exe
0023:00000000 <UNKNOWN>
The game ran well months ago.
I reinstalled it on a new wineprefix, same result.
workaround: disable quartz override and type enter or esc to bypass the 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.
https://bugs.winehq.org/show_bug.cgi?id=43210
Bug ID: 43210
Summary: GTA San Andreas takes off
Product: Wine-staging
Version: 2.10
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tall89(a)mail.ru
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
GTA San Andreas first starts, but then collapses, after which an error occurs
(a serious error was found, we apologize for the inconvenience), while the
screen resolution is reduced to 800x600
--
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=38087
Bug ID: 38087
Summary: Settlers III: mouse not working on start screen and
menu (after fixing raw input bug 33479)
Product: Wine
Version: 1.7.32
Hardware: x86
URL: http://www.fileplanet.com/27965/20000/fileinfo/The-Set
tlers-III:-Quest-of-the-Amazons-Demo
OS: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: sebastian(a)fds-team.de
CC: gyebro69(a)gmail.com, stefan(a)codeweavers.com
Depends on: 33479
Regression SHA1: f6dde7062413a1dfdd71acc92c5178ac66f3ade0
Distribution: ArchLinux
Originally reported here:
https://bugs.wine-staging.com/show_bug.cgi?id=95
The problem doesn't occur with plain Wine, because the incorrect commit from
bug 33479 somehow magically "works around" this regression. I am opening this
bug anyway because sooner or later a proper fix will get upstream.
To reproduce this issue, you have to revert
76bbf106a28c4caa82873e8450bde7d4adc765bf, or alternatively apply the staging
fix for bug 33479. See here for more details
https://bugs.winehq.org/show_bug.cgi?id=33479#c45 .
When starting Settlers 3 as fullscreen, before the bad commit was introduced
the mouse cursor appears and works properly on the start screen and in the
menu. After the bad commit the mouse cursor doesn't show up anymore. This makes
it impossible to enter the game.
Patch http://source.winehq.org/patches/data/108577 does not help in this case,
and the issue is still present in latest upstream Wine
(wine-1.7.36-83-gf75d1b0).
Desktop environment: XFCE 4.1
md5sum(S3_A_Demo.exe): f8f8214bed453cde3c7b2a1fe80f947a
The regression test was performed by reverting
76bbf106a28c4caa82873e8450bde7d4adc765bf at each step.
$ git bisect good
f6dde7062413a1dfdd71acc92c5178ac66f3ade0 is the first bad commit
commit f6dde7062413a1dfdd71acc92c5178ac66f3ade0
Author: Stefan Dösinger <stefan(a)codeweavers.com>
Date: Tue Nov 18 21:26:57 2014 +0100
wined3d: Restore the display mode on focus change.
:040000 040000 aa87fc202d416bf38b92925b0040cbdbcc9e3a84
23850dec1d6e575a9050437206d54d48db834005 M dlls
:040000 040000 0e90d026408ce1c052257f931536dd23c1e53a6f
5e45b170033d4faab106d4de13292c70ce3cbed4 M include
--
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=29576
Bug #: 29576
Summary: ImgBurn fails to get duration of FLAC files via
DC-Bass Source
Product: Wine
Version: 1.3.36
Platform: x86-64
URL: http://download.imgburn.com/SetupImgBurn_2.5.6.0.exe
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: RandomAccountName(a)mail.com
Classification: Unclassified
Created attachment 38308
--> http://bugs.winehq.org/attachment.cgi?id=38308
Terminal output
ImgBurn supports burning audio CDs from a few types of audio files out of the
box, but additional formats, including FLAC, can be supported by installing
DirectShow filers. DC-Bass Source provides support for various codecs,
including FLAC:
http://www.dsp-worx.de/?n=15
Unfortunately, this doesn't actually work with Wine; trying to add a FLAC file
to the compilation after installing DC-Bass Source produces an error:
GetDuration failed!
File Name: <file path>
Reason: Error: 0x80004001
The file is added to the list of tracks anyway, but attempting to create a CUE
sheet for burning will fail with the same message until the offending file(s)
are removed. Using native qedit.dll makes that error go away, and a CUE sheet
is created successfully.
AAC files fail with the same error initially, but native qedit only changes the
error code for those files...
Steps to reproduce:
1. Install ImgBurn
2. Download and extract DC-Bass Source:
http://download.dsp-worx.de/?f=DCBassSource_v1.30_Binary.zip
3. From the DC-Bass Source directory, run register.bat
4. Start ImgBurn and go to tools -> create CUE file
5. Try to add a FLAC file
--
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.