https://bugs.winehq.org/show_bug.cgi?id=40838
Bug ID: 40838
Summary: I am able to install the Launcher. however as soon as
installation/updates are complete, the window crashes
into a small box at the upper right corner of my
screen, then crashes comepletely after that
Product: Wine
Version: 1.9.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ak11(a)cox.net
Distribution: ---
Created attachment 54811
--> https://bugs.winehq.org/attachment.cgi?id=54811
NO THIS IS NOT THE SAME CASE AS bug 40628....the logs are different
I am able to install the Launcher. however as soon as installation/updates are
complete, the window crashes into a small box at the upper right corner of my
screen, then crashes comepletely after that.
Any ideas? I hope its an easy fix, i almost have it working!
--
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=44211
Bug ID: 44211
Summary: Wine (2.21) doesn't work anymore on any game on
FreeBSD
Product: Wine
Version: 2.21
Hardware: x86-64
OS: FreeBSD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: adrien_fernandes2(a)hotmail.com
Created attachment 59990
--> https://bugs.winehq.org/attachment.cgi?id=59990
Output of AC with csmt
FreeBSD/amd64 11.1 (the release version in december 2017)
Wine staging 2.21 32 bits (built from a 32 bits chroot)
nVidia 765m (nvidia-driver-384.59)
12 GB RAM (even if 32 bits applications take less, you have the information)
from my 32 bits chroot, I installed the nVidia driver
libGL.so -> libGL-NVIDIA.so.1
libGL.so.1 -> libGL-NVIDIA.so.1
libGLESv2.so -> libGLESv2-NVIDIA.so.2
libGLESv2.so.2 -> libGLESv2-NVIDIA.so.2
It always worked that way four months ago (last time I was on my computer)
So actually I tried Streets of Rogue and Assassin's Creed. I copy the output of
AC so you can see what the terminal says me. I set CSMT on one try and disabled
it on the second. (Assassin's Creed always worked in the past, that's why I
give you its 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.
http://bugs.winehq.org/show_bug.cgi?id=35234
Bug ID: 35234
Summary: Fallout: New Vegas launcher crashes when selecting a
DLC by double click
Product: Wine
Version: 1.7.9
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
Classification: Unclassified
Created attachment 46995
--> http://bugs.winehq.org/attachment.cgi?id=46995
terminal output
I browsed Bugzilla's already closed and currently opened bug reports related to
Fallout: New Vegas/Fallout 3, but haven't find anything similar to this. It's
not a new bug because I can reproduce it with Wine 1.4.1, 1.6.1, 1.7.9 as well.
The problem: when you start Fallout:New Vegas, the launcher offers an option
named <Data Files> where you can enable/disable the installed DLCs. If I
double-click on the name of the DLC, Wine produces a crash as can be seen in
the attached log.
Single clicking on the name of the DLC doesn't produce the crash.
This was tested with a clean wineprefix, without any dll overrides, dwrite and
gameoverlayrenderer already disabled.
Fedora 19 x86
X.Org X Server 1.14.4
Nvidia binary drivers 325.15
--
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=45575
Bug ID: 45575
Summary: Skyrim: No controller input when multiple controllers
are connected
Product: Wine
Version: 3.13
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ahyattdev(a)icloud.com
Skyrim works fine when I have one wired Xbox 360 controller plugged in but when
I have another one also plugged into my machine that I am not using neither
controller works with the game.
I have tested what the behavior is on Windows and Skyrim works fine when
multiple Xbox controllers are connected. When running through Wine none of the
controllers give any input.
--
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=48582
Bug ID: 48582
Summary: PlayStation Now: Controllers aren't detected with
Microsoft's native xinput1_3.dll
Product: Wine
Version: 5.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: xinput
Assignee: wine-bugs(a)winehq.org
Reporter: devilj(a)outlook.pt
Distribution: ---
Xbox One controllers (at least) aren't detected when using Microsoft's native
xinput1_3.dll, but they are working fine when using Wine's built-in version.
I captured a log using Wine's BUILT-IN implementation, but it doesn't say much.
The program polls "XInputGetStateEx" to get the state of indices 0 and 1:
004d:trace:xinput:XInputGetStateEx (index 0, state 0842FEB0)!
004d:trace:xinput:XInputGetStateEx (index 1, state 0842FEB0)!
And the respective +relay (using only the built-in module):
0040:Call xinput1_3.XInputGetStateEx(00000000,07edfeb0) ret=0048d99d
0040:Ret xinput1_3.XInputGetStateEx() retval=00000000 ret=0048d99d
0040:Call xinput1_3.XInputGetStateEx(00000001,07edfeb0) ret=0048d99d
0040:Ret xinput1_3.XInputGetStateEx() retval=0000048f ret=0048d99d
--
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=46151
Bug ID: 46151
Summary: XInput support doesn't support rumble on the DS4 (at
least)
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: xinput
Assignee: wine-bugs(a)winehq.org
Reporter: epigramx(a)yahoo.com
Distribution: ---
That would be a neat feature and it's lacking right now. All Xbox Controllers
support two motors on the device. It appears that currently Wine doesn't
provide that data to applications. I was interested in the DS4 specifically out
of the box but I support the feature may be missing on the actual Xbox
controllers as well.
--
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=45688
Bug ID: 45688
Summary: Gamepad appears both as dinput and xinput (eg.
Valkyria Chronicles)
Product: Wine
Version: 3.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dinput
Assignee: wine-bugs(a)winehq.org
Reporter: gabriel.corona(a)enst-bretagne.fr
Distribution: ---
AFAIU, on Windows a gamepad appears either on DirectInput or on XInput.
Some games are helpful and automatically work with both. For example, Valkyria
Chronicles apparently automatically switches between DirectInput and Xinput
based on the latests input.
On Wine >= 3.3, every gamepad appears both on DirecrInput and XInput. This is
useful because the gamepad can work both on DirectInput and XInput gamed.
However, on Valkyria Chronicles (for example) the effect is that the game
switches randomly between the two modes because it apparently sees the same
gamepad from both APIs. This can be seen because the buttons displayes on
screen change from numbered key labels ("1", "2", "3", etc.) and XInput based
key labels ("A", "B", "C", "D").
In order to sucessfully run the game, I has to disable the gamepad from
DirectInput (using "wine control"). This works, but prevents running
DirectInput only games without reconfiguration.
A possible workaround would be to have an option to disable DirectInput
gamepads if both libraries are mapped in the same process.
--
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=44086
Bug ID: 44086
Summary: HiDPI: Consider evaluating `GDK_SCALE` for default DPI
size
Product: Wine
Version: 2.0.3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: pmenzel+bugs.winehq.org(a)molgen.mpg.de
Distribution: ---
Opening the Wine configuration on a HiDPI monitor, the fonts are very small.
Despite having the user to increase the DPI size under the tab *Graphics*,
environment variables like `GDK_SCALE` [1] should be evaluated, and the default
DPI number be adjusted accordingly.
[1] https://wiki.archlinux.org/index.php/HiDPI
--
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=38749
Bug ID: 38749
Summary: Left 4 Dead: text in terminal is unreadable
Product: Wine
Version: 1.7.44
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ilya-valeev(a)yandex.ru
Distribution: ---
Created attachment 51666
--> https://bugs.winehq.org/attachment.cgi?id=51666
Log
When I call terminal (`), I cant read some text (see screenshot). Font tips
from here:
https://appdb.winehq.org/objectManager.php?sClass=version&iId=19444
doesnt help.
Tried wine 1.6.2, 1.7.42 and 1.7.44. Debian 8. 1920x1080
--
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=48666
Bug ID: 48666
Summary: Left 4 Dead 2: freezes during loading when shader
detail set to higher than medium
Product: Wine
Version: 5.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jhopper(a)safe-mail.net
Distribution: ---
Created attachment 66522
--> https://bugs.winehq.org/attachment.cgi?id=66522
wine console output
only freezes when vulkan renderer used (DXVK) GL working fine, there used to be
a problem with this when GL was used in previous versions of wine but I
couldn't find that specific bug in the list
--
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=43040
Bug ID: 43040
Summary: steam version of Left 4 Dead 2 v2.1.4.7 prevents
connection to server with a 'client timed out' error
Product: Wine
Version: 2.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: manoa(a)manoa.flnet.org
Distribution: ---
the bug occurs usually on the second attempt to connect to a server
in addition, once the error occurs it will persist, even after steam is
restarted
if not trying to connect to a server for a couple of minutes it may allow
connection, but if that connection fails, the next connection will have the
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.
https://bugs.winehq.org/show_bug.cgi?id=37158
Bug ID: 37158
Summary: Left 4 Dead pressing tab crashes the game
Product: Wine
Version: 1.6.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: nothingmuchheretosay(a)gmail.com
Pressing tab in a game, whether in Single or Multiplayer mode, the game will
crash.
--
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=23832
Summary: Mass Effect 2 stutter on initial rotation after
awakening
Product: Wine
Version: 1.2
Platform: x86
URL: http://masseffect.bioware.com/cdn/A/ME2_DEMO/MassEffec
t2DemoEN.exe
OS/Version: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: directx-d3dx9
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
CC: wine-bugs(a)winehq.org
Using the saved game from bug 23684, restart the mission;
when you start waking up, press escape twice to skip the
movies. Now sweep the mouse to rotate yourself to look around.
On Windows, this is very smooth.
On Wine, there is a noticeable amount of stuttering.
The problem stops as soon as you've looked at enough of the room
to have it in cache, or something like that.
--
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=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=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.
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.