wine-bugs January 2020

wine-bugs@winehq.org

1 participants
7387 discussions

[Bug 48069] New: floating point exception (core dumped) when WINEESYNC=1
by WineHQ Bugzilla 23 Jan '20

23 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=48069 Bug ID: 48069 Summary: floating point exception (core dumped) when WINEESYNC=1 Product: Wine-staging Version: 4.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ZenAnonX(a)protonmail.ch CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Wine-Staging Crashes with "floating point exception (core dumped)" on running any application with esync enabled. Applications run fine with esync disabled on staging or with esync enabled on master Most probably introduced with commit fb40c21c7280d5cb66f0cec8ed2f4e4e25e1fc56 -- 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.

1 3

[Bug 41199] New: SW KoTOR: Unhandled page fault on write access
by wine-bugs＠winehq.org 23 Jan '20

23 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=41199 Bug ID: 41199 Summary: SW KoTOR: Unhandled page fault on write access Product: Wine Version: 1.9.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bystrzak14(a)gmail.com Distribution: --- Created attachment 55439 --> https://bugs.winehq.org/attachment.cgi?id=55439 Log from gameplay I recently installed KoTOR on Fedora 24. Game starts correctly through Steam and works fluently, but it randomly crashes during loading new area or saved game. I tried tweaking "quartz" to "bultin" as in this thread https://bugs.winehq.org/show_bug.cgi?id=22910 although is kinda old. Anyway, this didn't solve my problem. Those crashes are really annoying and I can't really enjoy the game because of that. I run the game with custom prefix using 32bit. I attach complete log generated throughout my gameplay. -- 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.

2 9

[Bug 48497] New: DXVA2 patchset not compatible with GCC 10
by WineHQ Bugzilla 23 Jan '20

23 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=48497 Bug ID: 48497 Summary: DXVA2 patchset not compatible with GCC 10 Product: Wine-staging Version: 5.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mike(a)cchtml.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- GCC 10 defaults have changed. https://gcc.gnu.org/gcc-10/porting_to.html#common Default to -fno-common A common mistake in C is omitting extern when declaring a global variable in a header file. If the header is included by several files it results in multiple definitions of the same variable. In previous GCC versions this error is ignored. GCC 10 defaults to -fno-common, which means a linker error will now be reported. To fix this, use extern in header files when declaring global variables, and ensure each global is defined in exactly one C file. As a workaround, legacy C code can be compiled with -fcommon. int x; // tentative definition - avoid in header files extern int y; // correct declaration in a header file Fedora Rawhide (Fedora 32) now has GCC 10 and Wine-staging fails to build. The fix is simple. Add 'extern' to the two offending lines below: sed -i 's/BOOL config_vaapi_drm DECLSPEC_HIDDEN;/extern BOOL config_vaapi_drm DECLSPEC_HIDDEN;/' dlls/dxva2/dxva2_private.h sed -i 's/char config_vaapi_drm_path\[MAX_PATH\] DECLSPEC_HIDDEN;/extern char config_vaapi_drm_path\[MAX_PATH\] DECLSPEC_HIDDEN;/' dlls/dxva2/dxva2_private.h -- 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.

1 2

[Bug 47417] New: Overwatch doesn't capture mouse movement to croshairs
by wine-bugs＠winehq.org 23 Jan '20

23 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=47417 Bug ID: 47417 Summary: Overwatch doesn't capture mouse movement to croshairs Product: Wine-staging Version: 4.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)junaru.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- As of wine-staging 4.10 mouse movement is no longer captured to the crosshairs while in game. Mouse works as expected in main menu and up to the point where you enter game world. When the map loads mouse cursor is still present on screen and horizontal or vertical movement moves the cursor instead of the croshairs. Left and right mouse button clicks work as expected. Once every 10 or so game launches the mouse IS captured to the crosshairs and everything works as expected. (some race condition?) This issue is not present in wine-staging 4.8. (archlinux packaged wine-staging 4.9 has different issues that prevent testing) GPU: RX580 (amdgpu) DXVK 1.2.2 # pacman -Q|grep 'vulkan\|mesa\|linux\|xorg-server\|wine' lib32-mesa 19.1.0-2 lib32-vulkan-icd-loader 1.1.107-1 lib32-vulkan-radeon 19.1.0-2 linux 5.1.14.arch1-1 linux-api-headers 5.1-1 linux-firmware 20190618.acb56f2-1 linux-headers 5.1.14.arch1-1 mesa 19.1.0-3 vulkan-extra-layers 1.1.97.0+10340+118b2f331-1 vulkan-headers 1:1.1.111-1 vulkan-html-docs 1:1.1.111-1 vulkan-icd-loader 1.1.108-1 vulkan-radeon 19.1.0-3 vulkan-trace 1.1.97.0+10340+118b2f331-1 vulkan-validation-layers 1.1.107-1 wine-mono 4.9.0-1 wine-staging 4.11-1 wine_gecko 2.47-2 winetricks 20190615-1 xorg-server 1.20.5-1 xorg-server-common 1.20.5-1 xorg-server-devel 1.20.5-1 xorg-server-xdmx 1.20.5-1 xorg-server-xephyr 1.20.5-1 xorg-server-xnest 1.20.5-1 xorg-server-xvfb 1.20.5-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.

2 2

[Bug 47513] New: mailing-list-patches breaks gamepad input
by wine-bugs＠winehq.org 23 Jan '20

23 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=47513 Bug ID: 47513 Summary: mailing-list-patches breaks gamepad input Product: Wine-staging Version: 4.12.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sashok.olen(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 64902 --> https://bugs.winehq.org/attachment.cgi?id=64902 +tid,+pid,+plugplay,+hid,+hid_report,+hidp,+xinput,+dinput,+rawinput With mailing-list-patches patchset, all of my games are unable to detect a gamepad and receive no input from it. If I build staging with it reverted, the issues disappears. Attaching log with +tid,+pid,+plugplay,+hid,+hid_report,+hidp,+xinput,+dinput,+rawinput debug channels. -- 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.

2 17

[Bug 47834] New: Borderlands 1 (version 1.5.0) doesn't capture mouse
by WineHQ Bugzilla 23 Jan '20

23 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=47834 Bug ID: 47834 Summary: Borderlands 1 (version 1.5.0) doesn't capture mouse Product: Wine-staging Version: 4.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dron2065(a)rambler.ru CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Borderlands 1 (version 1.5.0) doesn't capture mouse - full 360 degree view with mouse is not possible. There is no this problem at previous version of Wine Staging (4.16) and Wine Devel of last version (4.17) -- 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.

1 16

[Bug 48433] New: Stalker Call of Pripyat and Stalker Clear Sky: no mouse input in menus since wine-staging 5.0rc3
by WineHQ Bugzilla 23 Jan '20

23 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=48433 Bug ID: 48433 Summary: Stalker Call of Pripyat and Stalker Clear Sky: no mouse input in menus since wine-staging 5.0rc3 Product: Wine-staging Version: 5.0-rc4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ritalat(a)fastmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 66200 --> https://bugs.winehq.org/attachment.cgi?id=66200 terminal output Mouse input in menus is broken since wine-staging 5.0rc3. Mouse still works in-game for movement if you start a new game by navigating the main menu with your keyboard. -- 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.

1 9

[Bug 48274] New: Initialization of wineprefix failed
by WineHQ Bugzilla 23 Jan '20

23 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=48274 Bug ID: 48274 Summary: Initialization of wineprefix failed Product: Wine Version: 4.21 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rmkk(a)atlas.cz Created attachment 65944 --> https://bugs.winehq.org/attachment.cgi?id=65944 Terminal output of failed wineprefix initialization Wine-staging was installed including 64-bit support, then I tried to initialize new wine prefix with errors, terminal output included -- 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.

1 32

[Bug 42988] New: Pocket Mirror causes heavy flickering in fullscreen mode on wine-staging
by wine-bugs＠winehq.org 23 Jan '20

23 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=42988 Bug ID: 42988 Summary: Pocket Mirror causes heavy flickering in fullscreen mode on wine-staging Product: Wine-staging Version: 2.7 Hardware: x86 URL: http://astralshiftpro.tumblr.com/pocket-mirror OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: ArchLinux Created attachment 58125 --> https://bugs.winehq.org/attachment.cgi?id=58125 short video of the issue Running the game Pocket Mirror in fullscreen leads on wine-staging to heavy flickering. About once or twice each second the desktop or some other image from the game is partially visible through the game. However, the issue does not appear in vanilla wine 2.7 I tried to make an apitrace, but it only shows a single frame, so there's something wrong there, too. If you need more info please tell me, I'd make a bisect but I don't know how to apply the staging patches partially since a lot of them depend on each other. Using Arch Linux with KDE 5.9.5-1, running 32bit wine program on 64bit OS. Game URL: http://astralshiftpro.tumblr.com/pocket-mirror Direct download: http://t.umblr.com/redirect?z=https%3A%2F%2Fmega.nz%2F%23%214YBSWIKb%21nbjS… -- 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.

2 6

[Bug 48255] New: AIMP4: throws an error when trying to play a file: Access violation at address 02D77CE1. Write of address 00008201.
by WineHQ Bugzilla 23 Jan '20

23 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=48255 Bug ID: 48255 Summary: AIMP4: throws an error when trying to play a file: Access violation at address 02D77CE1. Write of address 00008201. Product: Wine Version: 4.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 93.duke.xperia(a)gmail.com Distribution: --- Created attachment 65918 --> https://bugs.winehq.org/attachment.cgi?id=65918 terminal log AIMP v4.60, build 2161 gives an error when I try to play a file and freezes. https://www.aimp.ru/?do=download.file&id=4 cc14dd0631910858e96a44857fd2bed1ed6505c5 aimp_4.60.2161.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.

1 12

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs January 2020