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.
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.
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.
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.
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.
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.
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.
https://bugs.winehq.org/show_bug.cgi?id=47687
Bug ID: 47687
Summary: fail to run winrar installer
Product: Wine-staging
Version: 4.14
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: b1779506(a)trbvn.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Download url:
https://www.win-rar.com/download.html?&L=0
--
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=48063
Bug ID: 48063
Summary: World of Warcraft, Game Initialization fails, when run
from command line
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: eaglecomputers.ok(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
wine-4.19-158-g88d30985dd (Staging) is the version I just pulled from the git,
and compiled. the previous commit that I have is wine-4.19-85-g7f469b689a
(Staging) and it worked fine. Hope this helps you start regression testing.
--
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=48498
Bug ID: 48498
Summary: When I try to open the game 'Flower' it crashes. Crash
log attached
Product: Wine
Version: 5.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: slhodson013(a)yahoo.com
Distribution: ---
Created attachment 66294
--> https://bugs.winehq.org/attachment.cgi?id=66294
Crash report when game failed to open
I folowed the direction to install the game 'Flower' with PlayOnLinux. When I
open the game, a black scrren comes up, then immediately a Program Error box
which says "The program Flower.exe has encountered a serious problem and needs
to close. We are sorry for the inconvenience." In a secondary panel, it says
"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."
There are no tips in the database at this time.
Once I close that window, a POL window pops up "PlayOnLinux has encountered an
error. If the program you are installing does not work correctly, it might be
the cause of the problem. Visit www.playonlinux.com to get further
information." (was unable to find further information on that site) It also
says "Error in POL_Wine
Wine seems to have crashed"
--
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.