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=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.
https://bugs.winehq.org/show_bug.cgi?id=37517
Bug ID: 37517
Summary: VideoReDo TVSuite H.264 crashes on loading video when
using VMR9
Product: Wine
Version: 1.7.30
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: quartz
Assignee: wine-bugs(a)winehq.org
Reporter: gordon.lack(a)dsl.pipex.com
Distribution: ---
Created attachment 49929
--> https://bugs.winehq.org/attachment.cgi?id=49929
backtrace saved from crash
VideoReDo TVSuite H.264 (http://www.videoredo.com/en/ProductTVS.htm) starts up
OK.
Under Tools/Options/Playback Devices you can select VMR9 as the Video Driver
(FYI: DirectX is also listed there, but it isn't supported any more, and
actually used VMR7 as well - the option is going away). This determines the
driver used when running the editing page.
If you now load a video (mpeg, or h.264) into the program it 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=21790
Summary: 3D Rad demo "BeltBall" can't use its bundled
mfc80u.dll?
Product: Wine
Version: 1.1.38
Platform: x86
URL: http://www.3drad.com/games/BeltBall%20v102.exe
OS/Version: Linux
Status: UNCONFIRMED
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
The smallest demo from http://www.3drad.com/free-pc-games.php is the 8MB
http://www.3drad.com/games/BeltBall%20v102.exe, sha1sum
d8827274480b0391ad200478b2ebe26a2658166d BeltBall v102.exe
It installs fine, but when you start it, it complains
fixme:actctx:parse_depend_manifests Could not find dependent assembly
L"Microsoft.VC80.CRT" (8.0.50727.762)
and puts up a dialog saying
"The dynamic link library 'MFC80U.DLL' could not be found"
even though it's installed in
./3D Rad Games/BeltBall v102/Microsoft.VC80.MFC/mfc80u.dll
Perhaps the installer forgot to set an app path or a manifest or something?
winetricks vc2005 works around the problem.
The game installs and runs fine on Vista; I guess we need to try it
on an old XP box that doesn't have vc2005 runtimes already and see
if it works there to confirm this bug.
(I checked on Vista, and there's no entry for the app in
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths, for what it's worth.
And there doesn't seem to be a manifest file next to the .exe.)
--
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=40690
Bug ID: 40690
Summary: Thin Basic Script Abends
Product: Wine
Version: 1.9.10
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fengshui(a)webleicester.co.uk
Distribution: ---
Created attachment 54561
--> https://bugs.winehq.org/attachment.cgi?id=54561
The trace of the Abend as produced by Wine ?
I've just installed Thinbasic 1.8.9 under Wine 1.9.10 (POL "install non listed
program" was used to manage the install & wine versions).
Linux Mint 17 Cinnamon desk top.
Upon executing the script in the ThinAir component of Thinbasic, TA abended
(please see attached file for diagnostics). TA & the script run fine in Windows
XP (SP3) 32bit & as a 32bit app in Windows 7 64bit.
I then tested against various versions of Wine. The script runs to completion
upto & including Wine 1.7.39. In later versions it abends (1.7.40, .43, .55 &
1.8.2 were tried) I also tried XP & W7 emulations.
--
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=54899
Bug ID: 54899
Summary: EA app launcher problem with text display
Product: Wine
Version: 8.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: igor.bz(a)list.ru
Distribution: ---
Created attachment 74401
--> https://bugs.winehq.org/attachment.cgi?id=74401
Wine log
Distro: Ubuntu 20.04 x64
CPU: Ryzen 7 1700
GPU: Radeon RX 580 8 Gb
Mesa: 23.0.3 (Kisak PPA)
EA app installer:
https://origin-a.akamaihd.net/EA-Desktop-Client-Download/installer-releases…
Steps to reproduce:
- Running the installation file (EAappInstaller.exe).
- Fonts are displayed as placeholder.
Installing corefonts using winetricks does not solve the problem.
--
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=54396
Bug ID: 54396
Summary: Rutoken driver cannot install.
Product: Wine
Version: 8.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: setupapi
Assignee: wine-bugs(a)winehq.org
Reporter: igor.bz(a)list.ru
Distribution: ---
Created attachment 73963
--> https://bugs.winehq.org/attachment.cgi?id=73963
Wine log.
Distro: Ubuntu 20.04 x64
Kernel: Linux 6.0.9
Download link:
https://download.rutoken.ru/Rutoken/Drivers/Current/rtDrivers.exe
Steps to reproduce:
- Running the installation file (rtDrivers.exe).
- An error is reported during the installation process: Error. Error code: 120
(0x00000078): Function not implemented
- Installation failure.
- The program cannot be installed.
Translation:
- Установить => Install
- Ошибка. Код ошибки: 120 (0x00000078): Функция не реализована => Error. Error
code: 120 (0x00000078): Function not implemented
- Ошибка. Код ошибки: 3758096907 (0xe000020b) => Error. Error code: 3758096907
(0xe000020b)
- 0x80070643 Сбой установки => 0x80070643 Installation failure.
--
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=16957
Summary: CreateProcess handles are inherited even when
bInheritHandles=FALSE
Product: Wine
Version: 1.1.2
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: kernel32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ben(a)salilab.org
Created an attachment (id=18729)
--> (http://bugs.winehq.org/attachment.cgi?id=18729)
test.c
The attached file uses CreateProcess to create a subprocess (gzip in this case)
with redirected standard output. In order for this to work properly, the output
handle created in this code must be inherited by the subprocess - thus the
bInheritHandles argument to CreateProcess must be TRUE. And indeed if this
program is compiled to test-true.exe, a simple text file 'test.in' and the gzip
binary are placed in the same directory, and then test-true.exe is run, it
successfully produces the output test.gz.
If the TRUE argument is switched to FALSE and the file is compiled again to
test-false.exe, when the program is run in the same way on a 'real' Windows
sytem (32 bit Vista Business in this case) the following is output:
gzip: stdout: Bad file descriptor
This is also fine and expected, since the output file handle was not passed to
gzip. *However* if the same test-false.exe program is run with Wine (the Fedora
10 wine-core-1.1.12-1.fc10.i386 package in this case) it runs in just the same
way as test-true.exe, generating the test.gz output.
This suggests to me that the bInheritHandles argument is ignored by Wine. As
stated, this is a minor bug but it would be nice if Wine behaved the same way
as Windows here. (In our case we discovered this problem after we tested our
program successfully under Wine, but then had it fail on a real Windows
system.) I am not familiar with the code, but hopefully it should be
straightforward enough to provide the subprocess with invalid handles if
bInheritHandles=FALSE?
--
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.