https://bugs.winehq.org/show_bug.cgi?id=53713
Bug ID: 53713
Summary: Persona 4 Golden crashes on video playback in
decodebin_parser_create+0x3f
Product: Wine
Version: 7.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winegstreamer
Assignee: wine-bugs(a)winehq.org
Reporter: hibbsncc1701(a)gmail.com
Distribution: ---
Created attachment 73142
--> https://bugs.winehq.org/attachment.cgi?id=73142
Backtrace of crash.
Persona 4 Golden now crashes on startup attempting to play the opening FMV,
whereas it worked fine in wine-7.13.
Backtrace 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=49465
Bug ID: 49465
Summary: I cannot install Windows Media Player
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winnipuh00(a)gmail.com
Distribution: ---
Created attachment 67571
--> https://bugs.winehq.org/attachment.cgi?id=67571
error log
FOr some reason i cannot install windows media player. pls 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.
https://bugs.winehq.org/show_bug.cgi?id=50390
Bug ID: 50390
Summary: Resident Evil 5 Gradually fades to black if csmt is
disabled.
Product: Wine
Version: 6.0-rc3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: BOBBLOG(a)protonmail.com
Distribution: ---
Created attachment 69002
--> https://bugs.winehq.org/attachment.cgi?id=69002
RE5-Gradual-Blackout.jpg
Resident Evil 5 Gradually fades to black if csmt is disabled in chapter 4-1
just after open door to the ancient city. This was tested in a wine prefix with
only wmp11 install by winetricks because the game will not boot without wmp11.
--
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=53072
Bug ID: 53072
Summary: After installing WMP11, mfplat is suddenly unavailable
Product: Wine
Version: 7.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gab.pulcio(a)gmail.com
Distribution: ---
Steps to reproduce:
-winetricks wmp11
-open something that requires mfplat
-the program fails to load the dlls "dll not found"
-winetricks mf
-still "dll not found"
Steps to fix:
-winecfg
-library -> delete all WMP and MF custom rules
-wineboot -u
-WMP is still installed and everything now will work
This is a paradox in my opinion
--
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=51794
Bug ID: 51794
Summary: Implement wineclang - a wrapper around clang to build
software with winelib
Product: Wine
Version: 6.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winelib
Assignee: wine-bugs(a)winehq.org
Reporter: kolan_n(a)mail.ru
Distribution: ---
A user should be able to configure which stock clang (i.e. one default in the
distro, or the latest one from the official repos) and which MinGW target and
which sysroot to use. I.e. if I have a CMake toolchain file for
cross-compilation for Windows 64-bit with clang-14 using MinGW-w64 stdlib
installed from Ubuntu packages, then I should be able to just slightly modify
it in order to get native compilation via wine-gcc the following way:
1. replace clang compilers with wineclang
2. provide wineclang with arguments pointing to real clang binaries I want to
use.
Probably it should be unified with winegcc/wineg++ and renamed into
winecompiler, which should be symlinked to
winegcc/wineg++/wineclang/wineclang++.
--
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=48285
Bug ID: 48285
Summary: wine fails to build on OpenBSD 6.6
Product: Wine
Version: 5.0-rc1
Hardware: x86
OS: OpenBSD
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
I recently got some OpenBSD hardware. I'm running amd64 without 32-bit libs,
but tried ./configure --enable-win64 && make. That quickly fails:
../../tools/winegcc/winegcc -o acledit.dll.so --wine-objdir ../.. -m64 -fPIC
-fasynchronous-unwind-tables -shared acledit.spec -mno-cygwin main.o
ld: error: undefined symbol: __wine$func$msvcrt$889$exit
>>> referenced by msvcrt.dl7cmN.o:(exit) in archive ../../dlls/msvcrt/libmsvcrt.a
ld: error: undefined symbol: __wine$func$msvcrt$918$free
>>> referenced by msvcrt.xGOgzp.o:(free) in archive ../../dlls/msvcrt/libmsvcrt.a
ld: error: undefined symbol: __wine$func$msvcrt$930$fwrite
>>> referenced by msvcrt.nznoyJ.o:(fwrite) in archive ../../dlls/msvcrt/libmsvcrt.a
ld: error: undefined symbol: __wine$func$msvcrt$935$getenv
>>> referenced by msvcrt.jGd3C7.o:(getenv) in archive ../../dlls/msvcrt/libmsvcrt.a
ld: error: undefined symbol: __wine$func$msvcrt$977$malloc
>>> referenced by msvcrt.5agt8W.o:(malloc) in archive ../../dlls/msvcrt/libmsvcrt.a
ld: error: undefined symbol: __wine$func$msvcrt$988$memcpy
>>> referenced by msvcrt.poMIg2.o:(memcpy) in archive ../../dlls/msvcrt/libmsvcrt.a
ld: error: undefined symbol: __wine$func$msvcrt$996$perror
>>> referenced by msvcrt.ir9vqr.o:(perror) in archive ../../dlls/msvcrt/libmsvcrt.a
ld: error: undefined symbol: __wine$func$msvcrt$1026$sprintf
>>> referenced by msvcrt.t1nwtD.o:(sprintf) in archive ../../dlls/msvcrt/libmsvcrt.a
ld: error: undefined symbol: __wine$func$msvcrt$1033$strcat
>>> referenced by msvcrt.Au1ZuZ.o:(strcat) in archive ../../dlls/msvcrt/libmsvcrt.a
ld: error: undefined symbol: __wine$func$msvcrt$1035$strchr
>>> referenced by msvcrt.21W0bH.o:(strchr) in archive ../../dlls/msvcrt/libmsvcrt.a
ld: error: undefined symbol: __wine$func$msvcrt$1038$strcpy
>>> referenced by msvcrt.RvKwjV.o:(strcpy) in archive ../../dlls/msvcrt/libmsvcrt.a
ld: error: undefined symbol: __wine$func$msvcrt$1044$strlen
>>> referenced by msvcrt.7i6Hbr.o:(strlen) in archive ../../dlls/msvcrt/libmsvcrt.a
ld: error: undefined symbol: __wine$func$msvcrt$1052$strrchr
>>> referenced by msvcrt.VGJjKk.o:(strrchr) in archive ../../dlls/msvcrt/libmsvcrt.a
ld: error: undefined symbol: __wine$func$msvcrt$1081$vfprintf
>>> referenced by msvcrt.KLRNXW.o:(vfprintf) in archive ../../dlls/msvcrt/libmsvcrt.a
ld: error: undefined symbol: __wine$func$msvcrt$873$bsearch
>>> referenced by msvcrt.vi1qrR.o:(bsearch) in archive ../../dlls/msvcrt/libmsvcrt.a
ld: error: undefined symbol: __wine$func$msvcrt$990$memmove
>>> referenced by msvcrt.qg9ile.o:(memmove) in archive ../../dlls/msvcrt/libmsvcrt.a
ld: error: undefined symbol: __wine$func$msvcrt$1011$realloc
>>> referenced by msvcrt.h4HqQf.o:(realloc) in archive ../../dlls/msvcrt/libmsvcrt.a
ld: error: undefined symbol: __wine$func$msvcrt$1036$strcmp
>>> referenced by msvcrt.tKMem6.o:(strcmp) in archive ../../dlls/msvcrt/libmsvcrt.a
ld: error: undefined symbol: __wine$func$msvcrt$1040$strcspn
>>> referenced by msvcrt.BcWz1G.o:(strcspn) in archive ../../dlls/msvcrt/libmsvcrt.a
ld: error: undefined symbol: __wine$func$msvcrt$1087$vsnprintf
>>> referenced by msvcrt.sbsmdH.o:(vsnprintf) in archive ../../dlls/msvcrt/libmsvcrt.a
ld: error: too many errors emitted, stopping now (use -error-limit=0 to see all
errors)
clang: error: linker command failed with exit code 1 (use -v to see invocation)
winegcc: clang failed
*** Error 2 in dlls/acledit (Makefile:194 'acledit.dll.so')
*** Error 1 in /home/austin/wine-git (Makefile:8546 'dlls/acledit')
LD:
LLD 8.0.1 (compatible with GNU linkers)
compiler:
OpenBSD clang version 8.0.1 (tags/RELEASE_801/final) (based on LLVM 8.0.1)
Target: amd64-unknown-openbsd6.6
Thread model: posix
InstalledDir: /usr/bin
--
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=51051
Bug ID: 51051
Summary: wine-staging 6.7 64 bit build fails in Ubuntu 21.04
Product: Wine-staging
Version: 6.7
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dimesio(a)earthlink.net
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 69913
--> https://bugs.winehq.org/attachment.cgi?id=69913
Ubuntu 21.04 build failure log
All other builds succeeded, but the Ubuntu 21.04 x86_64 staging build fails in
wine64-preloader. Attaching log from the OBS.
--
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=47792
Bug ID: 47792
Summary: master wine doenst detect my clang on configure
Product: Wine
Version: 4.16
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: salva.liebana(a)gmail.com
Distribution: ---
[pi@pi wine]$ ./configure
checking build system type... aarch64-unknown-linux-gnu
checking host system type... aarch64-unknown-linux-gnu
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for cpp... cpp
checking for ld... ld
checking whether gcc supports __builtin_ms_va_list... no
configure: error: You need clang >= 5.0 to build Wine for arm64.
[pi@pi wine]$ clang --version
clang version 8.0.1 (tags/RELEASE_801/final)
Target: aarch64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
--
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=53600
Bug ID: 53600
Summary: Cannot run any program (wine: could not exec the wine
loader)
Product: Wine
Version: 7.16
Hardware: aarch64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gerdya04(a)gmail.com
Distribution: ---
I did compile latest sources according to https://wiki.winehq.org/Building_Wine
configure --enable-win64 (all dependencies ok except vulkan)
make -j8
when trying to run any program i am getting the following error:
gerdya@Surfi:~/projects/wine/buildwin64$ ./wine64 notepad
wine: could not exec the wine loader
OS: Ubuntu 22.04 LTS (aarch64)
Kernel: 5.15.57.1-microsoft-standard-WSL2
Let me know if you need more details.
--
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=53822
Bug ID: 53822
Summary: Mouse sensivity is too high in multiple games
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: VladimirVSC(a)yandex.ru
Distribution: ---
As it said in the headline, some games (F.E.A.R, Morrowind, Call of Juarez -
Bound in Blood and many others, i guess) have much more increased mouse
sensivity comparing to windows (with the same in-game settings installed).
Sometimes even the sensivity set to minimum doesn't help, it is too high
anyway.
--
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=51964
Bug ID: 51964
Summary: Morrowind sometimes crashes on exit
Product: Wine
Version: 6.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: idarktemplar(a)mail.ru
Distribution: Gentoo
Created attachment 70946
--> https://bugs.winehq.org/attachment.cgi?id=70946
backtrace.txt
Morrowind sometimes crashes on exit. Doesn't reproduce reliably. I play game
for some time, including saving and loading, fighting, interacting with NPCs
and local fauna, etc, and when I'm exiting game sometimes it crashes. Not sure
if it's a bug in wine. Attaching crash log.
OS: Gentoo Linux amd64 (x86_64)
Kernel: 5.10.74-gentoo
wine and wine-staging: 6.20
Desktop: KDE Plasma 5 (X11)
Videocard: NVIDIA GeForce GTX 750 (Nvidia drivers 470.82.00)
Wine prefix: 32bit only (WINEARCH=32bit)
Morrowind: GOG version
--
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=16692
Summary: Morrowind Construction Set Crashes on Saving New Plugin
Product: Wine
Version: 1.1.11
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: aestrivex(a)gmail.com
Created an attachment (id=18347)
--> (http://bugs.winehq.org/attachment.cgi?id=18347)
ASCII text file of error output
TES III: Morrowind's Construction Set does not allow the creation of new plugin
files (mods) and causes a crash to desktop upon saving a new plugin file.
Changes to old plugin files suffer no such 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.
https://bugs.winehq.org/show_bug.cgi?id=43943
Bug ID: 43943
Summary: Morrowind randomly crashes
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ggldkm(a)gmail.com
Distribution: ---
Morrowind randomly crashes in 3-120 seconds after the start
I tried wine 2.0.3 and 2.19
--
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=35858
Bug ID: 35858
Summary: Morrowind Overhaul 3.0 installer doesn't work
Product: Wine
Version: 1.7.15
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winebugs140(a)gmail.com
Created attachment 47876
--> http://bugs.winehq.org/attachment.cgi?id=47876
MO3 error message
I've attached a screenshot of the error message that shows up.
--
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=39199
Bug ID: 39199
Summary: Morrowind Graphics Extender (MGE): distant land
generator does not see any files
Product: Wine
Version: 1.7.50
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tuupic(a)gmail.com
Distribution: ---
Created attachment 52255
--> https://bugs.winehq.org/attachment.cgi?id=52255
MGE wizard window
Distant land wizard does not see any files to generate textures.
In windows virtualbox VM with shared dir all works
Same problem with another morrowind graphic extender: MGE XE
I can produce more information if needed.
--
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=39196
Bug ID: 39196
Summary: Morrowind and Morrowind Graphics Extender (MGE):
shader problem
Product: Wine
Version: 1.7.50
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: tuupic(a)gmail.com
Distribution: ---
When I use third person view in game(and sometimes in first person too) if "HDR
shader" or "distand land" is enable picture will corrupted (see attached
screenshots)
Same problem with another graphic extender for morrowind: MGE XE
--
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=43970
Bug ID: 43970
Summary: Mouse is constrained to the borders of the screen when
looking around ingame.
Product: Wine-staging
Version: 2.19
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: libcg(a)protonmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
I've been using wine-staging 2.19 with DOOM 2016 and GTA 5. In both of those
games, looking around using the mouse will sometimes get stuck until I move the
mouse faster out. When going to the game menu, I can see that the cursor is
positioned at one end of the screen. When I place the cursor in the middle of
the screen and go back ingame, the mouse will move freely until I hit one
border of the screen with the cursor again.
It happens with both of these games. I tried DOOM with wine-staging 2.3 and hit
the same issue. Switching between GNOME and Xfce doesn't 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.
https://bugs.winehq.org/show_bug.cgi?id=42765
Bug ID: 42765
Summary: Doom (2016) Sound suddenly shut down
Product: Wine-staging
Version: 2.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mathieu.nivoliez(a)laposte.net
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Sounds does not appear in game or in the menu but it does at the start of
loading screens before being quickly shut down.
Could be link to this issue:
https://steamcommunity.com/app/353380/discussions/0/357287304417743078/
Pulseaudio already set on 48000 Mhz
--
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=38748
Bug ID: 38748
Summary: (dogfood) Chocolate Doom full screen does not always
work properly
Product: Wine
Version: 1.7.43
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mikeonthecomputer(a)gmail.com
Distribution: ---
Created attachment 51661
--> https://bugs.winehq.org/attachment.cgi?id=51661
Screenshot of broken full screen
The full screen setting of Chocolate Doom (which is default) will sometimes
display the screen offset, showing a part of my GNOME desktop and making the
game rather unusable for play. It seems to work correctly the most frequently
if the game is launched from the setup program, but that still doesn't always
work.
I've tested this with the 2.2.0 release, both with the official binaries
(http://www.chocolate-doom.org/downloads/2.2.0/) and my own 64-bit build with
x86_64-w64-mingw32; no difference between the two.
To Wine maintainers, for testing this bug, you can use the FreeDM IWAD so that
Chocolate Doom has a game to run: https://freedoom.github.io/download.html
--
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=13460
Summary: ZDoom: distorted graphics rendering
Product: Wine
Version: 1.0-rc2
Platform: PC-x86-64
URL: http://www.zdoom.org
OS/Version: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P5
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: aeichhorst(a)gmail.com
Created an attachment (id=13376)
--> (http://bugs.winehq.org/attachment.cgi?id=13376)
Hall of Mirrors effect on textures
When running ZDoom, the graphics rendering produces a "hall of mirrors" effect
on textures. This has no effect on gameplay, but is a big eyesore. Another
graphical problem that occurs is a "pixel coloration-distortion" that imposes
colors from one texture onto another. An example of this is when firing the
BFG9000 in Doom the walls will retain pixels of the BFG's green energy ball
color. This can be seen when pulling up the menu (hitting the Esc key) during
gameplay. The menu's yellowish background-shade produces the effect quite well.
I managed to get a screenshot of the "hall of mirrors" effect and is attached
to this report.
--
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=38415
Bug ID: 38415
Summary: Switching weapons does not work after dying
Product: Wine
Version: 1.7.39
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: christopher(a)thielen.co
Distribution: ---
Here's a strange one:
Deus Ex works beautifully in Wine but I noticed after I die, beginning a new
game and pressing one of the keyboard buttons to switch weapons no longer works
as it did.
Wine/Deus Ex registers the key press because the Doom-style weapon switcher at
the bottom of the screen registers the new weapon but the game does not
actually switch weapons.
Using the same 1.112fm Deus Ex "Game of the Year" edition installer on Windows
XP and Windows 8, this bug does not occur, implying there's something fishy
with Wine instead.
--
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=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=50861
Bug ID: 50861
Summary: The Ultimate Doom (GOG Version): Crashes Immediately
on Launch
Product: Wine
Version: 6.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gregory(a)opera.id.au
Distribution: ---
Created attachment 69675
--> https://bugs.winehq.org/attachment.cgi?id=69675
Error details for The Ultimate Doom (GOG version) crashing.
As soon as one tries to launch the GOG version of "The Ultimate Doom", the game
crashes immediately, prior to any part of the game being shown.
The error message is as follows (refer to attachment for further details):
Program Error
The program DOSBox.exe has encountered a serious problem and needs to close. We
are sorry for the inconvenience.
This can be caused by a problem in the program or a deficiency in Wine. You may
want to check the Application Database for tips about running this application.
--
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.