https://bugs.winehq.org/show_bug.cgi?id=51475
Bug ID: 51475
Summary: Unhandled exception code c0000005 flags 0 addr
0x42a3a7 when trying to install vcrun2015
Product: Wine-staging
Version: 6.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ryu.ketsueki(a)outlook.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Many applications need VCRUNTIME140.dll and naturally I looked up over
winetricks to install what was necessary. However, I noticed that every time I
try to do that, even when I manually download the executable and run straight
through wine and not winetricks, it gives that error. Last time I checked, that
error is characteristic of a regression.
The program in question that is asking for that DLL is a game, The Sims 4 to be
more precise. It never asked for that before, probably because it was such an
old prefix. Now I nuked it to start from scratch because the previous prefix
was giving errors. Turned out not to be the cause. Then I reinstalled Wine.
Didn't solve the problem. Then I tried standard wine instead of wine staging.
Also didn't work. I nuked the binaries and did a reinstall. Now wine is working
again but now it keeps asking for that DLL that I can't install because Wine is
giving that error.
Winetricks tried installing the 32bit package. I tried to manually install the
64bit one. Both gave the same error. Unhandled exception code c0000005 flags 0
addr 0x42a3a7
--
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=46645
Bug ID: 46645
Summary: DOOM 2016 Crashing on second loading screen on 99%
when Vulkan render is used
Product: Wine
Version: 4.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: linards.liepins(a)gmail.com
Distribution: ---
As the issue seems to be fixable by certain tweaks via various Windows
Utilities. I would say it is issue with applicable workaround in Wine and it
therefore falls into the Wine implementation garden as well. Reference:
https://steamcommunity.com/app/379720/discussions/0/358417461602906353/?ctp…
$ inxi -Gxxx
Graphics:
Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
vendor: XFX Pine driver: amdgpu v: kernel bus ID: 01:00.0
chip ID: 1002:67df
Display: x11 server: Fedora Project X.org 1.20.3 driver: amdgpu
compositor: gnome-shell v: 3.30.2 resolution: 1920x1080~60Hz
OpenGL: renderer: Radeon RX 580 Series (POLARIS10 DRM 3.27.0
4.20.6-200.fc29.x86_64 LLVM 7.0.1)
v: 4.5 Mesa 18.3.3 direct render: Yes
I will provide logs by EOB today as i will not be at my workstation for a while
now.
--
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=55452
Bug ID: 55452
Summary: Mouse doesn't work in multiple games
Product: Wine-staging
Version: unspecified
Hardware: x86-64
URL: https://archive.org/details/EvilGeniusDemo
OS: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
After Staging commit a1e634bca9f71627321b8d186ceb3556ae2c5224 the mouse doesn't
work in many of my games (Doom 64, Prey 2017, The Witcher 2-3, Quake 1-2
Enhanced). Some of the games have working mouse in the menus but not in the
game. For others the mouse no longer works in the menu.
Evil Genius demo can be used to reproduce the problem.
evil_genius_demo.exe (195 M)
md5: 58e4ea2c32dd981be4c02e579775aa43
wine-8.13-428-g5cd11ade210 (Staging)
--
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=54985
Bug ID: 54985
Summary: Wine-staging 8.9 build fails
Product: Wine-staging
Version: 8.9
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 74533
--> https://bugs.winehq.org/attachment.cgi?id=74533
Log from Debian Testing x86_64 failed build
Attaching the log from 64 bit Debian Testing; all the builds failed in the same
way.
--
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=53809
Bug ID: 53809
Summary: Using boxnet in warpem crashes on RTX2080 (Unhandled
exception: unimplemented function
nvcuda.dll.cuFuncSetAttribute called in 64-bit code.)
Product: Wine-staging
Version: 7.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alois.schloegl(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 73321
--> https://bugs.winehq.org/attachment.cgi?id=73321
backtrace
Using Boxnet in Warp (as described in [1]) runs fine one wine-staging (tested
with 7.17) when running on a machine with GTX1080 cards.
When running the same setup on a machine with RTX2080 cards, Warp crashes.
Running Boxnet/Warp on a Windows machine with RTX2080 cards works fine.
Therefore, I believe the issue is in winestaging.
The offending function call seems to be:
Unhandled exception: unimplemented function nvcuda.dll.cuFuncSetAttribute
called in 64-bit code (0x0000007b01394e).
Attached are the backtrace. If needed I can also provide the debug logs, for
both 1080 and 2080 cards.
[1] http://www.warpem.com/warp/?page_id=135
--
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=53797
Bug ID: 53797
Summary: Performance regression in Battle.net / Wow.exe using
wine-staging 7.18
Product: Wine-staging
Version: 7.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mewt.reaper(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Using wine-staging 7.18-1 (Arch package) Battle.net application performance
appears degraded, with UI turning black and application freezing randomly.
Application is also completely frozen after system suspend and must be killed
from terminal.
Similarly, loading times in World Of Warcraft are severely degraded with the
game freezing for several seconds on first load and then very slow loading of
new Zone data.
Both symptoms appear to be resolved when downgrading back to wine-staging 7.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=52045
Bug ID: 52045
Summary: The Witcher 3: crashes when launching
Product: Wine-staging
Version: 6.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gireham910(a)erpipo.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 71056
--> https://bugs.winehq.org/attachment.cgi?id=71056
The output from the wine app, after the crash
Hello,
I noticed that on Fedora 35, with the latest wine-staging package (6.21) "The
Witcher 3" fails to launch (I have attached the output that wine itself
generated and asked me to upload, as well as the output from the terminal when
I manually tried to launch the app using "wine witcher3.exe").
The program used to work on wine-staging 6.18, and stopped working immediately
after updating to 6.21 (on Fedora there were no 6.19 or 6.20 packages). I don't
have other windows apps installed.
--
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=42286
Bug ID: 42286
Summary: Shantae and the Pirate's Curse - cursor rendered with
an opaque background behind it
Product: Wine-staging
Version: 2.0-rc6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ikk_pl(a)yahoo.co.uk
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 56995
--> https://bugs.winehq.org/attachment.cgi?id=56995
Screenshot showing the problem
The cursor in the game is rendered with a white opaque square behind it.
(Note that the game doesn't run on vanilla wine, it needs staging patches for
the CreateDeferredContext call.)
--
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=55404
Bug ID: 55404
Summary: Mouse inverted/broken in Eve Online when multiple
clients open
Product: Wine
Version: 8.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kjandrews0(a)gmail.com
Distribution: ---
Created attachment 74964
--> https://bugs.winehq.org/attachment.cgi?id=74964
Mouse issue shown, close second client, then working correctly.
Opening multiple eve online clients, the click and drag to orient the ship in
space is now completely inverted on both X and Y axis. Can also be seen in the
station when "spinning" the ship.
Closing other clients and keeping only one running instantly fixes the issue,
starting another client once past character selection starts the issue again.
Downgrading from
wine-staging-8.11-1-x86_64.pkg.tar.zst
to
wine-staging-8.9.1-1-x86_64.pkg.tar.zst
Resolves the issue
Mouse pointer in game does work correctly when clicking areas of the UI, it's
just changing the direction of view via click and drag. Same issue in window
mode and fixed screen.
--
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=52853
Bug ID: 52853
Summary: Wine Staging is causing crashes when moving some IDA
Pro 7.2 subwindows
Product: Wine-staging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lorenzofer(a)live.it
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Hi After a post 7.6 rebase moving some of the subwindwos (the compiler
subwindow for example when detached) is crashing IDA Pro 7.2
The issue apparead in this commit:
0b3309a201cfe65098e93f0f23af82509d1c6c72 is the first bad commit
commit 0b3309a201cfe65098e93f0f23af82509d1c6c72
Author: Zebediah Figura <zfigura(a)codeweavers.com>
Date: Thu Apr 14 17:17:08 2022 -0500
Rebase against 121851955e697b3158cbcf31801164eb627e78e9.
patches/patchinstall.sh | 2 +-
...-Support-XInput2-events-for-individual-wi.patch | 6 +--
...SEND_HWMSG_RAWINPUT-flags-only-when-RAWIN.patch | 32 +++++++--------
...-Listen-to-RawMotion-and-RawButton-events.patch | 46 +++++++++++-----------
staging/upstream-commit | 2 +-
5 files changed, 44 insertions(+), 44 deletions(-)
The error is
m Files\IDA 7.2\ida.exe: ../dlls/ntdll/unix/thread.c:1737:
ntdll_set_exception_jmp_buf: asserzione "!jmp ||
!ntdll_get_thread_data()->jmp_buf" non riuscita.
m Files\IDA 7.2\ida.exe: ../dlls/ntdll/unix/thread.c:1737:
ntdll_set_exception_jmp_buf: asserzione "!jmp ||
!ntdll_get_thread_data()->jmp_buf" non riuscita.
011c:err:seh:call_stack_handlers invalid frame 000000000051F4E0
(0000000000022000-0000000000420000)
011c:err:seh:NtRaiseException Exception frame is not in stack limits => unable
to dispatch exception.
--
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.