https://bugs.winehq.org/show_bug.cgi?id=55638
Bug ID: 55638
Summary: mf:transform - test_h264_decoder_concat_streams()
sometimes fails on Windows 7
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: mfplat
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
mf:transform - test_h264_decoder_concat_streams() sometimes fails on Windows 7:
transform.c:4510: Test failed: GetElementCount returned 0x78
transform.c:4512: Test failed: sample 97: got 1 buffers
transform.c:4512: Test failed: sample 97: got sample time 14800000
transform.c:4512: Test failed: sample 97: got sample duration 400000
transform.c:1085: Test failed: sample 97: buffer 0: got unexpected buffer
See https://test.winehq.org/data/patterns.html#mf:transform
Note that the bad GetElementCount() return value is always 0x78 (120) and the
sample time and durations are always the same too.
This set of failure is quite rare with 1.5 to 2 instances per month. The first
known instance happened on 2023-06-01 (no instance in the previous 5 months):
* 2023-09-18 win7_newtb-w7u-es
* 2023-09-06 win7_newtb-w7pro64-64
* 2023-09-01 win7_newtb-w7u-2qxl
* 2023-08-28 MR!3636
* 2023-07-06 win7_newtb-w7u-de
* 2023-06-09 MR!3010
* 2023-06-01 MR!2893 (twice)
--
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=52883
Bug ID: 52883
Summary: Improve support for high-level graphic settings in The
Settlers: Heritage of Kings
Product: Wine
Version: 7.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: Markus.Elfring(a)web.de
Distribution: ---
Created attachment 72267
--> https://bugs.winehq.org/attachment.cgi?id=72267
screenshot for a questionable display of graphic settings
I wonder why I get hindered so far to switch the graphic settings to the
highest quality (which my hardware could support).
How will the software capabilities evolve further also for the game “The
settlers (gold edition)” after the software “Wine 7.7-1449.4”?
See also:
https://appdb.winehq.org/objectManager.php?sClass=version&iId=5360
--
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=45122
Bug ID: 45122
Summary: gdiplus/font test crashes under clang-5.0.1 but not
gcc-7.3.0
Product: Wine
Version: 3.7
Hardware: x86
URL: https://test.winehq.org/data/8dca6c35e11a104385242ed83
46ee05707b78ef7/linux_ae-gentoo-dbg-clang/gdiplus:font
.html
OS: Linux
Status: NEW
Keywords: download, source, testcase
Severity: normal
Priority: P2
Component: gdiplus
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: Gentoo
Backtrace:
=>0 0x7ec9e635 GdipMeasureString+0x1e5(graphics=<is not available>, string=<is
not available>, length=<has been optimized away by compiler>, font=<has been
optimized away by compiler>, rect=<has been optimized away by compiler>,
format=<is not available>, bounds=<has been optimized away by compiler>,
codepointsfitted=<has been optimized away by compiler>, linesfilled=<has been
optimized away by compiler>)
[/var/lib/jenkins/home/workspace/wine-clang/dlls/gdiplus/graphics.c:5427] in
gdiplus (0x0033f958)
1 0x7ed1385d in gdiplus_test (+0x2485c) (0x0033fac8)
2 0x7ed0f1c7 func_font+0x486() in gdiplus_test (0x0033fe08)
3 0x7ed7e968 main+0x457() in gdiplus_test (0x0033fea8)
4 0x7ed7ecaa in gdiplus_test (+0x8fca9) (0x0033fee0)
5 0x7b45df9c call_process_entry+0xb() in kernel32 (0x0033fef8)
6 0x7b45e0f3 start_process+0x122(entry=0x7ed7f5cb, peb=<is not available>)
[/var/lib/jenkins/home/workspace/wine-clang/dlls/kernel32/process.c:1099] in
kernel32 (0x0033ffdc)
7 0x7b45dfaa start_process_wrapper+0x9() in kernel32 (0x0033ffec)
0x7ec9e635 GdipMeasureString+0x1e5
[/var/lib/jenkins/home/workspace/wine-clang/dlls/gdiplus/graphics.c:5427] in
gdiplus: mulps %xmm1,%xmm1
5427 (pt[2].X-pt[0].X)*(pt[2].X-pt[0].X));
lmk what other logs/tests would be useful.
--
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=55972
Bug ID: 55972
Summary: Dolphin Emulator requires GetProcessInformation (since
5.0-16711)
Product: Wine
Version: 8.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: tinozzo123(a)tutanota.com
Distribution: ---
Dolphin Emulator doesn't launch anymore on Wine since version 5.0-16711, due to
requiring GetProcessInformation.
```
wine: Call from 00006FFFFFF7F308 to unimplemented function
KERNEL32.dll.GetProcessInformation, aborting
```
The commit that added it is the following:
https://github.com/dolphin-emu/dolphin/commit/2bd72dfc6f956c27337934e9a1a26…
--
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=55813
Bug ID: 55813
Summary: [Errno 9] Bad file descriptor
Product: Wine
Version: 8.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: naworldw(a)gmail.com
Distribution: ---
Created attachment 75302
--> https://bugs.winehq.org/attachment.cgi?id=75302
Unexecutable
"https://github.com/KurtBestor/Hitomi-Downloader/releases/download/Technical…"
I posted on the forum with the same title, but a different problem occurred.
First, the stable version seems to have incorrect support for qt6. The program
performed a full upgrade from qt5 to qt6 and was unable to run afterwards.
As a workaround in the forum, proceed to "When I copy
"C:\windows\system32\Windows.UI.dll" from a Windows 11 installation next to
"hitomi_downloader_GUI.exe" and start the program with:
WINEDLLOVERRIDES="window.ui=n"win hitomi_downloader_GUI.exe" and you will see
the program screen. However, the program has an internal browser. So, if you
press "options-network-embedded web browser" in the program, the program itself
is closed due to a fatal bug called "QtWebEngineProcess.exe." So I tried the
wine development version. It is displayed as an attachment, making it
impossible to execute itself.
--
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=55588
Bug ID: 55588
Summary: mf:mf - test_scheme_resolvers() crashes on Windows 7
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: mfplat
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
mf:mf - test_scheme_resolvers() crashes on Windows 7:
mf.c:6488: this is the last test seen before the exception
0958:mf: unhandled exception c0000005 at 000007FEFDD72817
See https://test.winehq.org/data/patterns.html#mf:mf
This started on 2023-08-23 with the commit that introduced the new tests:
commit fd3d0113f95d3cd4696497cdce5eb5d6d2aa26f5
Author: Rémi Bernon <rbernon(a)codeweavers.com>
Date: Fri Jul 28 08:54:05 2023 +0200
mf/tests: Add some network scheme resolver tests.
Note that the TestBot detected the crash but confused it with the random crash
from bug 54859 and thus considered it to not be new. That's the issue with
crashes: they all look the same.
--
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=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.
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=55927
Bug ID: 55927
Summary: RestoreDC appears to fail with printers
Product: Wine
Version: 8.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kadlecf(a)fzu.cz
Distribution: ---
My wine is packed within the OpenSuse Tumbleweed distribution. Since recently,
I experience problems with printing from a custom application which worked in
earlier wine versions. Its graphical output (mostly data represented as lines
and text) is normally shown on the screen where I encounter no problems.
However, currently, when the data is sent to a printer - either one with paper
or the CUPS pdf printer -, it is clipped to a rectangle defined by the SaveDC
function. This would be OK except that the function RestoreDC
BOOL RestoreDC
(
[in] HDC hdc,
[in]
int
nSavedDC
)
;
does not work properly with the device context hdc connected to a printer
device.
In brief, the sequence
SaveDC
(functions involving clipping of the output region)
RestoreDC
does not restore the clipping region to the original one for the printer
(however, it does for the screen device context).
--
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=55986
Bug ID: 55986
Summary: Gunner3 has flickering in fullscreen
Product: Wine
Version: 8.21
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
Since wine-6.1 there is flickering when running Gunner3 in fullscreen mode.
Also, from time to time old frame data is shown for a few moments making the
game
It works with winecfg virtual desktop mode, and making screenshots in
fullscreen is hard. It looks similar to the glitches in bug 45168 (but it is
unrelated).
Don't try to click on a level without having the fix from bug 41977 though, it
might crash. The menu is enough to reproduce the issue.
--
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=8051
--- Comment #190 from Alexandr Oleynikov <sashok.olen(a)gmail.com> ---
(In reply to Zeb Figura from comment #189)
> (In reply to Alexandr Oleynikov from comment #188)
> > What kind of an update do you want exactly?
> > It doesn't look like Wine 9.0-rc1 had any changes related to software vertex
> > processing, so the bug stands as it is. And it's probably unlikely that this
> > will change, especially with DXVK now being the preferred backend for games
> > (which like I mentioned before fully implements this feature).
>
> I don't know whom DXVK is "preferred" by, but it's not the position of the
> Wine project, and it's certainly our intent to implement software vertex
> processing mode. It's just not exactly trivial, and there are some
> unresolved design questions.
Of course, I was not stating it's an official position of the Wine project,
it's just merely what vast majority Linux gamers prefer for its far better
compatibility and performance for both D3D9 and D3D11 games (if hardware is
compatible), and what is used in Proton too.
--
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=56019
Bug ID: 56019
Summary: LOCAL_GetBlock not enough space in local heap
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: elias_0000_0000(a)yahoo.com
Distribution: ---
wine-8.0 (Debian 8.0~repack-4)
See this game:
https://archive.org/details/connections-1995
Same bug with that: https://bugs.winehq.org/show_bug.cgi?id=1490
both with win32 win64 prefix.
0180:err:local:LOCAL_GetBlock not enough space in local heap 076f for 1948
bytes
(etc.)
--
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=56018
Bug ID: 56018
Summary: Respondus LockDown Browser fatally hangs on loading
screen
Product: Wine
Version: 9.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: micah.haber(a)gmail.com
Distribution: ---
Created attachment 75659
--> https://bugs.winehq.org/attachment.cgi?id=75659
No backtrace available, list of deferred .dlls
Respondus LockDown Browser v. 2.1.1.05.
--
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=8051
--- Comment #189 from Zeb Figura <z.figura12(a)gmail.com> ---
(In reply to Alexandr Oleynikov from comment #188)
> What kind of an update do you want exactly?
> It doesn't look like Wine 9.0-rc1 had any changes related to software vertex
> processing, so the bug stands as it is. And it's probably unlikely that this
> will change, especially with DXVK now being the preferred backend for games
> (which like I mentioned before fully implements this feature).
I don't know whom DXVK is "preferred" by, but it's not the position of the Wine
project, and it's certainly our intent to implement software vertex processing
mode. It's just not exactly trivial, and there are some unresolved design
questions.
--
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.