https://bugs.winehq.org/show_bug.cgi?id=55569
Bug ID: 55569
Summary: mshtml:dom - The 32-bit test_attr_collection_attr()
crashes on Windows 10 2004+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: mshtml
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
mshtml:dom - The 32-bit test_attr_collection_attr() crashes on Windows 10
2004+:
dom.c:3679: this is the last test seen before the exception
1268:dom: unhandled exception c0000005 at 00000001
See https://test.winehq.org/data/patterns.html#mshtml:dom
This crash is systematic and started on 2023-08-30.
--
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=54769
Bug ID: 54769
Summary: major regression in dnSpy startup time
Product: Wine
Version: 8.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: galtgendo(a)o2.pl
Distribution: ---
(OK, this will be quite a bit different than what I've planned when I started
to write this)
Let's start with an oddity: only 32bit versions of dnSpy work, 64bit fail to
show anything besides the recently popular stack corruption line (it does not
terminate upon it, but fails to do anything else either).
The problem (initially observed in 6.1.8, but dnSpyEx 6.3.0 has the same
problem):
I'm not quite sure when this happened, but IIRC it was at most two releases
back, maybe it was the latest one.
Before, upon startup there was a minor delay before the window showed up and
every now and then (but relatively rarely) the window got filled with visual
garbage until it was refreshed.
Now, it *seems* corruption has been dealt with (though that needs more time to
be verified), but there's a crippling startup delay (over 2-3 min) between when
a blank window shows up and when it's filled with content.
--
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=54361
Bug ID: 54361
Summary: Winebus doesn't enumerate evdev devices in a
--without-sdl build unless SDL also disabled by
winebus registry key
Product: Wine
Version: 8.0-rc5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: j-r(a)online.de
Distribution: ---
Not sure what info to add.
--
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=53845
Bug ID: 53845
Summary: Regression in GetCalendarInfoEx et al
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: elpochodelagente(a)gmail.com
Distribution: ---
Created attachment 73375
--> https://bugs.winehq.org/attachment.cgi?id=73375
test case, succeeds in Windows and wine 6.0
The following line succeeds in Windows and used to work in Wine 6, but not in
Wine 7.19. Attached is a complete program test
GetCalendarInfoEx(0, CAL_GREGORIAN_US, 0, CAL_ITWODIGITYEARMAX |
CAL_RETURN_NUMBER, 0, 0, dwData); // returns 0
Looking at dlls/kernelbase/locale.c current git master I can see that now there
is an explicit check against CAL_GREGORIAN, and if I change the
CAL_GREGORIAN_US parameter in the call to CAL_GREGORIAN then GetCalendarInfoEx
succeeds.
--
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=21550
Summary: Winedbg's disassembler doesn't support SSE2
instructions
Product: Wine
Version: 1.1.37
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winedbg
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: b7.10110111(a)gmail.com
Winedbg doesn't support SSE2 instructions while gdb does.
--
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=56028
Bug ID: 56028
Summary: Yakuza 0 not launching on Mac 10.14 with Wine
Product: Wine
Version: 8.0.1
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dariooliviero09(a)gmail.com
Created attachment 75673
--> https://bugs.winehq.org/attachment.cgi?id=75673
Here is the error message
I don't know much when it comes to Wine, I installed the latest version the
site gave me for MAC. In fact, wine's settings should be the default ones,
running a Windows 10 system.
For a offline single player game such as Fallout New Vegas, Wine worked pretty
well.
Thanks to that, I decided to try a newer game: Yakuza 0.
After having bought it on GOG.com, I tried running the .exe file to no avail.
I admit that I didn't spot the issue as I am a bit clueless when it comes to
wine, but I should've attached the error message with this.
What do I have to do?
Thank you in advance
--
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=55665
Bug ID: 55665
Summary: Wine versions >=8.9 do not load Fallout 4 properly
Product: Wine
Version: 8.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: rcs777(a)proton.me
Distribution: ---
I'm sorry if this is a bit long, but I want to be as detailed as possible. In
short, I usually build Wine myself using TkGlitch's build scripts and put the
resulting build in Lutris's runtime path. I find that TkG Wine offers slightly
better performance for Games than my system-provided wine. However when Wine
8.9 rolled around, my self compiled builds stopped working with Fallout 4; the
game simply crashed before the intro played with no backtrace provided. My FO4
has its own logs thanks to mods and they told me it crashed in XAudio2_7.dll.
It's worth noting that for FO4 I have XAudio2_7 set to native in winecfg,
otherwise the audio that comes through is very muffled. It's pretty much a must
have for a playable experience. The first thing I did was try a plain
non-modified build of Wine from my package manager and a clean prefix, but had
no luck.
After some trial and error I found that FO4 works perfectly on plain Wine 8.8,
so I bisected between 8.8 and 8.9 and found that the startup failure was caused
by commit 354a8bb1f4a65bdec052606f2799db9e2907b5b1, "ntdll: Better match
Windows subheap sizes". However... Reverting that patch only works up to 8.10,
on plain 8.11 and up I was back to square one with crashing in XAudio before
the intro video. So after bisecting from 8.10 with that patch reverted just for
good measure (I don't know if it's actually needed past 8.9) and 8.11, I came
up with a82238fad52761114ab2488d422fad3f70dbb854, "ntdll: Allocate 64-bit and
kernel stacks in high memory". Assuming that reverting that patch would fix the
latest development version too, I jumped straight to 8.16 and reverted it. I
found that I also had to revert 3ac808e46e4795e14c5b999aa39fd9cd15f95279,
"ntdll: Set Wow64 user space limit based on LARGE_ADDRESS_AWARE" and
f473e31341a0dbc2eb5222cc1d1cfe468946bf0a, "ntdll: Load modules with a high base
address in high memory" too. I'm not sure if those last two patches actually
break anything, but they seem to depend on variables introduced in the 64-bit
Allocate patch so without reverting these too I got build time failures. In any
case, once these patches are reverted on Wine 8.16, I get a clean build and
Fallout 4 works perfectly again.
Here's where I'm confused... I grabbed a vanilla Wine 8.16 build from
https://github.com/Kron4ek/Wine-Builds... and it worked, unpatched, out of the
box. As far as I can tell from his build scripts, those Wine builds are
compiled on Ubuntu Bionic, which means those libraries and compilers are likely
far older than mine on Debian Sid. Maybe it's something that an older compiler
is doing different, seeing as how the reverted patches seem to have a lot to do
with memory allocation? If that were the case it might not even be a bug in
Wine.
In any case, here's my specs:
OS: Debian GNU/Linux trixie/sid x86_64
Kernel: 6.5.0-1-amd64
DE: Plasma 5.27.8
CPU: AMD Ryzen 7 5800X (16) @ 3.800GHz
GPU: AMD ATI Radeon RX 5600 OEM/5600 XT / 5700/5700 XT
Memory: 3931MiB / 32011MiB
GCC Version: gcc (Debian 13.2.0-4) 13.2.0
All build dependencies while running the configure script were satisfied except
for OSS, and I've never actually had satisfied.
--
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=55139
Bug ID: 55139
Summary: loader: regression - error running winecfg
Product: Wine
Version: 8.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: loader
Assignee: wine-bugs(a)winehq.org
Reporter: arusanu.bu(a)gmail.com
Distribution: ---
The switch to PIE loader seems to affect running wine on my system.
Running winecfg generates these errors:
'$ winecfg
wine: created the configuration directory '/home/iurt_build/.wine'
0024:err:environ:run_wineboot failed to start wineboot c00000e5
wine: could not load kernel32.dll, status c0000135'
The regression started with commit cc2cfb9b792bee681b96c5859084fd6d4d0bbed7.
Reverting that commit and
commit 78ed343842dcd8ffb95c416420953e121959d40d
commit c55578f3a54c63084657e7d79c043b22b10df989
commit ac1761d1dae8bf114a05e28ed6886deba6c2c860 ,
allows wine 8.11 to run fine.
System: Mageia 9(cauldron),
kernel-6.3.9 - x86_64., gcc-12.3.0, mingw-gcc-12.2.1
Wine specific configuration options used for x86_64/i586:
'
./configure --with-x --with-dbus --with-gstreamer --enable-win64
--with-system-dllpath=/usr/x86_64-w64-mingw32/sys-root/mingw/bin
--disable-tests
./configure --with-x --with-dbus --with-gstreamer
--with-system-dllpath=/usr/i586-w64-mingw32/sys-root/mingw/bin --disable-tests
'
--
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=49312
Bug ID: 49312
Summary: wineg++ - "invalid program stack in 64-bit code" on
exception catching - regression
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dd-tom(a)web.de
Distribution: ---
Created attachment 67324
--> https://bugs.winehq.org/attachment.cgi?id=67324
full crash log
Referencing this issue here:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1881293
When compiling the following C++ program with "wineg++ main.cpp":
#include <stdexcept>
#include <stdio.h>
int main() {
printf("start\n");
try {
throw std::runtime_error("desc");
} catch (std::exception &ex) {
printf("in catch\n");
}
printf("end\n");
}
Wine crashes with:
Unhandled exception: assertion failed, invalid program stack in 64-bit code
(0x00007f33f6c24781).
The full log is attached.
Tested with (not working):
- Debian Bullseye and wine 5.0 (packaged)
- wine 5.0 compiled from source on Debian Buster
Regression since wine 4.0, tested working with:
- Debian Buster and wine 4.0 (packaged)
- wine 4.0 compiled from source on Debian Buster
--
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.