https://bugs.winehq.org/show_bug.cgi?id=42061
Bug ID: 42061
Summary: DOOM(2016) has issues with multiple monitors - crashes
too
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: spleefer90(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
pacman -Q wine-staging-git
wine-staging-git atest.release.r0.ge05b5bf8+wine.2.0.rc2.r0.g56040acaa3-1
I have 2 monitors, both 1920x1080, one 144Hz(left,primary) and second one
60Hz(right,secondary).
Upon launching the game, my left monitor turns off and the game is launched on
the wrong monitor(right).
After messing around with the monitors(turning them back on and going into game
settings), trying to make DOOM run on the other monitor, the game crashes.
Crash error: http://pastebin.com/efU7w1An
I guess the crashing wouldn't be an issue if the game launched on the correct
monitor without turning anything off.
I'll attach full output soon.
--
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=45766
Bug ID: 45766
Summary: Doom 3: BFG hangs during launch
Product: Wine
Version: 3.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sa(a)whiz.se
Distribution: ---
Created attachment 62220
--> https://bugs.winehq.org/attachment.cgi?id=62220
backtrace from gdb
I'm getting a reproducible hang each time I start Doom 3: BFG, GOG version.
(Yes, I know there's a native port!)
The hang happens after the intro videos are played, during the id/Bethesda
logos.
This title seems to require a compatibility context which Mesa just recently
started to support. Still, the game uses some none-spec OpenGL and requires
force_glsl_extensions_warn=true and
allow_glsl_builtin_variable_redeclaration=true to start.
An uneducated guess is something to do with audio? Those are the files the
process keeps open, but might just be a coincidence. (Audio is played during
the intro videos).
Native xact doesn't make a difference, disabling audio in Wine casues the game
to refuse to run.
Doesn't seem to be a regression, it is there as far back as 1.9.10 (the last
version with Platinum rating in AppDB)
Full backtrace from gdb is 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=43984
Bug ID: 43984
Summary: Doom (2016) sometimes hangs upon exit
Product: Wine
Version: 2.19
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: laci(a)monda.hu
Distribution: ---
Generally speaking, Doom (2016) runs flawlessly, but sometimes when I quit it
hangs.
I can see the following in the console:
fixme:bcrypt:BCryptGenRandom ignoring selected algorithm
fixme:bcrypt:BCryptCreateHash ignoring object buffer
fixme:bcrypt:BCryptCreateHash ignoring object buffer
fixme:bcrypt:BCryptGenRandom ignoring selected algorithm
fixme:bcrypt:BCryptCreateHash ignoring object buffer
fixme:bcrypt:BCryptCreateHash ignoring object buffer
fixme:bcrypt:BCryptGenerateSymmetricKey ignoring object buffer
fixme:bcrypt:BCryptGenRandom ignoring selected algorithm
err:hid_report:process_hid_report Device reports coming in too fast, last
report not read yet!
err:hid_report:process_hid_report Device reports coming in too fast, last
report not read yet!
AL lib: (WW) ReleaseThreadCtx: 0x7f46405e8e10 current for thread being
destroyed
--
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=45375
Bug ID: 45375
Summary: Halo Online: Weird black display problems.
Product: Wine
Version: 3.10
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: conmanx360(a)gmail.com
Distribution: ---
This issue happens on certain maps in Halo Online depending on what your
current Z position is. Not all maps suffer from it, only certain ones do. If
you're above the Z position that it begins happening at, everything below
renders normally, but once you go below it, a portion of the frame becomes
black. It seems to be in a pattern. Not all objects are blacked out, either. So
there must be some sort of "priority".
Image examples here: https://imgur.com/a/176i4xr
--
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=44246
Bug ID: 44246
Summary: Call of Duty 4: GL_INVALID_OPERATION &
GL_OUT_OF_MEMORY
Product: Wine
Version: 2.21
Hardware: x86
OS: FreeBSD
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: hardy.schumacher(a)gmx.de
Created attachment 60041
--> https://bugs.winehq.org/attachment.cgi?id=60041
Call of Duty 4: console log
When starting "Call of Duty 4" several warn messages can be seen on console.
Shortly after game mode has been entered, warnings from shader can be seen,
followed by message:
err:d3d:wined3d_debug_callback 0xf8ff878: "GL_INVALID_OPERATION error
generated. <program> object is not successfully linked, or is not a program
object.".
After several seconds, this message is printed to console:
err:d3d:wined3d_debug_callback 0xf8ff878: "GL_OUT_OF_MEMORY error generated.
Failed to allocate memory for texture.".
And finally the game and wine instance are crashing.
I'm using FreeBSD-11.1-p3 on AMD64.
Wine is from port emulators/i386-wine-devel v2.21.
PC is running with NVIDIA driver 340.104.
Port graphics/mesa-dri is on v17.3.1.
--
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=34798
Bug #: 34798
Summary: Silent Hill Homecoming is incredibly SLOW.
Product: Wine
Version: 1.7.4
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: sov.info(a)mail.ru
Classification: Unclassified
It works fine on my comp under Windows 7 or 8, so it's characteristics (2,13
GGh x 2 core, 8 Gb RAM) are all ok.
The game menu and first videoscene fine too, but after that (when we should
start to control personage) it's slow as hell.
I see that game is fully playable, so is it a some kind of regression?
Also - i don't install any components via winetricks. Maybe all that happens
because of it?
I created a *really* gigantic log.
--
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=45762
Bug ID: 45762
Summary: Metal Gear Solid 2 Movies No Longer Play.
Product: Wine
Version: 3.14
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: SolisX007(a)yahoo.com
Distribution: ---
Hello Everyone,
Metal Gear Solid 2 the movies don't play any more. In wine-1.9.10 the
movies play. I have not tested to see exactly to see where the bug
was introduced. I will try and go that later on.
--
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=18391
Summary: Postal 2 - Brightness settings apply themselves to the
Desktop.
Product: Wine
Version: 1.1.20
Platform: PC
URL: http://www.gopostal.com/freestp.php
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: pvtpuddin(a)gmail.com
I have the Gog.com version of Postal 2, so I don't have the native Linux
version. But when I run Postal 2 in either a virtual desktop, or fullscreen,
the game's brightness settings apply themselves to the rest of the desktop.
The default brightness settings washed everything out. And changing the
brightness in game, you could see the desktop getting brighter or darker.
If you don't have Postal 2, you could test this with the free demo of the
Multiplayer part. You don't have to play the game to see this bug, it'll
happen at the menu.
--
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=41749
Bug ID: 41749
Summary: Cannot change volume in Ether One Redux
Product: Wine
Version: 1.9.23
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: plata(a)mailbox.org
Distribution: ---
It is possible to move the sliders, however this does not seem to have any
effect on the actual volume. Especially the environment sounds do not seem to
be affected at all. Therefore it is quite hard (sometimes even impossible) to
understand the dialogs.
I tried pulse and alsa.
--
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=41798
Bug ID: 41798
Summary: The Solus Project crashes while loading with a "Fatal
Error" message
Product: Wine
Version: 1.9.23
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fjfrackiewicz(a)gmail.com
Distribution: ---
Created attachment 56226
--> https://bugs.winehq.org/attachment.cgi?id=56226
Wine 1.9.23-141-g1e78138 terminal output
Wine version:
1.9.23-141-g1e78138
Windows 7 prefix.
When I attempt to run The Solus Project, it crashes with an error message
"Fatal Error".
--
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.