https://bugs.winehq.org/show_bug.cgi?id=37533
Bug ID: 37533
Summary: Dragon Age Origins: Crashes in some parts of the game
Product: Wine
Version: 1.6.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: claw(a)triple6.org
Distribution: ---
Created attachment 49953
--> https://bugs.winehq.org/attachment.cgi?id=49953
Backtrace of a crash
I noticed that Dragon Age Origins crashes in some parts of the game. See the
backtrace attached. Its always in the same locations or sequences.
I also noticed that lowering the graphical settings can help and i can pass
beyond this crashes.
I mostly happens when many textures need to be loaded.
This was tested on AMD (radeon driver 7.5.0), nvidia ( proprietary 340.46) and
intel ( 2.21.15 ).
There are also other graphics related issues in the game like video sequences
displaying just a black screen and sometimes glitches like black textures.
I'll test it against current 1.7 release of wine if i find some time to compile
it and wipe my ~/.wine.
Thanks for wine by the 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.
http://bugs.winehq.org/show_bug.cgi?id=32230
Bug #: 32230
Summary: Incanto does not display main screen background
Product: Wine
Version: 1.5.17
Platform: x86
URL: http://www.izzygames.com/incanto-t2952.html
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: andrew.millington(a)gmail.com
Classification: Unclassified
Good indicators of why it happens is it display a message a few times at the
start of which you have to dismiss to get to the main screen.
--*.frag--
Fragment shader failed to compile
Vertex shader failed to compile
Having d3dx9_36 does is not a workaround nor does it allow you to proceed into
the game but that could be unrelated.
--
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=50893
Bug ID: 50893
Summary: Wine cannot see home directory
Product: Wine
Version: 6.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winehome(a)dispostable.com
Distribution: ---
Created attachment 69703
--> https://bugs.winehq.org/attachment.cgi?id=69703
output of "wine explorer ~/"
Steps to reproduce: With a fresh install and prefix (WINEARCH 32 or 64 bit),
run "wine explorer" and navigate to /home.
Expected behaviour: A list of all folders in /home appears.
Actual behaviour: One user home folder, /home/user1, is missing from the list.
Other user home folders, e.g. /home/user2, are shown as expected.
Permissions for /home/user1 and /home/user2 are the same. The absence of
/home/user1 persists, regardless of whether wine is run under user1 or user2.
Running "wine explorer ~/" gives
0144:err:explorer:make_explorer_window Failed to create PIDL for
L"Z:\\home\\user1".
This also affects all file dialogs in other software and opening a file in
/home/user1 with an associated wine executable.
--
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=25759
Summary: crash when running game "Polda" and moving their
(game) window
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: prescott66(a)gmail.com
Created an attachment (id=32832)
--> (http://bugs.winehq.org/attachment.cgi?id=32832)
crash log game "Polda"
this bug is about one older game named "Polda".it is edited to works OK on
Windows XP and it works on real Windows XP.
But when i run it on Linux (Fedora 14, 32-bit, wine ver:1.3.11) game hangs and
when i try to move window, game crashes. log is attached.
i can upload somewhere that game if you will, thats no problem because its not
big game(cca 100MB).
--
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=55467
Bug ID: 55467
Summary: MAME 0.257: mame.exe -listxml crashes
Product: Wine
Version: 8.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: pernegger(a)gmail.com
Distribution: ---
Created attachment 75027
--> https://bugs.winehq.org/attachment.cgi?id=75027
wine 8.14 terminal output
Steps to reproduce:
Run "wine mame.exe -listxml".
Expected results:
Very long XML dump, followed by programme exit.
Actual result:
Things crash and burn (see log).
(This affects clrmamepro's ability to import data when being fed the MAME
executable.)
MAME's interactive mode, i.e. just "wine mame.exe" seems to work.
I haven't tested any older versions of MAME, just 0.257. WINE-side, I've tried
8.13 and 8.14, both via the official Ubuntu 22.04 packages available via
WINEHQ. So this isn't necessarily a regression.
--
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=54323
Bug ID: 54323
Summary: user32:input - test_SendInput() sometimes gets an
unexpected 0xc042 message on Windows 7
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:input - test_SendInput() sometimes gets an unexpected 0xc042 message on
Windows 7:
input.c:4583: Test failed: SendInput triggered unexpected message 0xc042
This failure has not happened in the WineTest runs yet.
The first known instance is from MR693 (2022-08-22) and 8 merge request
versoins have been impacted since, the latest of which is MR1949 where it
happened 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=56055
Bug ID: 56055
Summary: AVG Antivirus setup crashes on unimplemented function
ADVAPI32.dll.TreeSetNamedSecurityInfoW
Product: Wine
Version: 9.0-rc2
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
Created attachment 75711
--> https://bugs.winehq.org/attachment.cgi?id=75711
Terminal output
The installer crashes on start.
$ sha256sum avg_antivirus_free_setup.exe
3ef95ae5234fa730b262df8b60e8ba1f7969f3317723dfac588441ecafa32141
--
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=55835
Bug ID: 55835
Summary: putenv clobbers previous getenv
Product: Wine
Version: 8.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvcrt
Assignee: wine-bugs(a)winehq.org
Reporter: blitzkriegoutlaw(a)hotmail.com
Distribution: ---
Created attachment 75335
--> https://bugs.winehq.org/attachment.cgi?id=75335
Sample code
performing a putenv/_putenv_s to an empty string will clobber a previous
getenv. There may be other cases, but this is the one I ran into. I've attached
sample code.
On Windows it returns:
AMD64 Family 23 Model 1 Stepping 2, AuthenticAMD
AMD64 Family 23 Model 1 Stepping 2, AuthenticAMD
On Wine it returns:
x86 Family 6 Model 79 Stepping 1, GenuineIntel
Family 6 Model 79 Stepping 1, GenuineIntel
The string is globbered by the _setenv_s due to the shift in memory by removing
another environment variable.
--
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=53516
Bug ID: 53516
Summary: user32:input failed due to unexpected WM_TIMECHANGE
message
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:input failed due to unexpected WM_TIMECHANGE message:
input.c:4525: Test failed: SendInput triggered unexpected message 0x1e
https://test.winehq.org/data/patterns.html#user32:input
This happened on 2022-08-05 in the w10pro64-fr-64 test configuration.
But user32:msg has also received such an unexpected message on 2022-08-02 on
w10pro64-pt-BR-64 (see bug 53273).
It appears this message is sent by Windows when an application modifies the
system time. If the application is another test then it should make sure all
such messages have been sent before continuing.
But it is quite possible that this message is sent when Windows resynchronizes
with some internet time server in which case this message could arrive in any
test at any time.
--
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=51477
Bug ID: 51477
Summary: user32:input test_Input_blackbox() gets unexpected
00&41(A) keystate changes
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
test_Input_blackbox() gets unexpected 00&41(A) keystate changes:
https://test.winehq.org/data/patterns.html#user32:input
input.c:757: Test failed: 0 (a4/0): 00 from 00 -> 81 unexpected
input.c:757: Test failed: 0 (a4/0): 41 from 00 -> 01 unexpected
* This exclusively happens for the first sendinput_test entry which is supposed
to simulate pressing the left Alt key (VK_LMENU == 0xa1).
* I do not know what the 00 virtual key code corresponds to. According to the
failure message this key is getting pressed down and toggled.
* The 41 virtual key code should be the 'A' key but that's not a toggle key
(unlike, e.g., Caps Lock) so the low order bit should be meaningless. So it's
strange that it changed from off to toggled.
* These failures happen on the following machines:
(41 corresponds to 100% reproducible, some machines may have fewer than 41
runs)
17 2008_newtb-w2008s64-32
1 2008_newtb-w2008s64-64
5 win7_newtb-w7u-2qxl
7 win81_cw-rx460-32
4 win1507_cw-gtx560-1507-32
5 win1507_cw-rx460-1507-32
1 win1709_cw-rx460-1709-64
39 win2009_cw-gtx560-2009-32
39 win2009_cw-gtx560-2009-64
41 win2009_cw-rx460-2009-32
41 win2009_cw-rx460-2009-64
--
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=17414
Summary: user32/dde test crashes if +heap enabled
Product: Wine
Version: 1.1.15
Platform: PC
URL: http://test.winehq.org/data/6a1537c4b5037be5253c33021fda
3a02430533f7/wine_xp_ae-ub-810-heap/riched32:editor.html
OS/Version: Linux
Status: NEW
Keywords: download, source, testcase
Severity: enhancement
Priority: P2
Component: user32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Created an attachment (id=19484)
--> (http://bugs.winehq.org/attachment.cgi?id=19484)
backtrace in 1.1.15
wine: Unhandled page fault on read access to 0x00130000 at address 0x6045971b
(thread 0009), starting debugger...
...
=>0 0x6045971b CompareStringW+0x13b(lcid=1033, style=0, str1=0x130000, len1=0,
str2=0x6074c780, len2=-1)
[/home/austin/wine-git/dlls/kernel32/../../include/wine/unicode.h:216] in
kernel32 (0x0032f848)
1 0x6045bed4 lstrcmpW+0x64(str1=<register EDI not in topmost frame>,
str2=<register ESI not in topmost frame>)
[/home/austin/wine-git/dlls/kernel32/locale.c:2834] in kernel32 (0x0032f878)
2 0x60681d7a dde_server_wndprocW+0x3da(hwnd=0xe0028, msg=1000, wparam=458798,
lparam=<register EDI not in topmost frame>)
[/home/austin/wine-git/dlls/user32/tests/dde.c:1215] in user32_test
(0x0032f8b8)
3 0x6082337a WINPROC_wrapper+0x1a() in user32 (0x0032f8e8)
4 0x608237ca call_window_proc+0x6a(hwnd=<register EDI not in topmost frame>,
msg=<register ESI not in topmost frame>, wp=458798, lp=1204994,
result=0x32f998, arg=0x606819a0)
[/home/austin/wine-git/dlls/user32/winproc.c:458] in user32 (0x0032f928)
5 0x60828af7 WINPROC_call_window+0xf7(hwnd=<register EDI not in topmost
frame>, msg=1000, wParam=458798, lParam=1204994, result=0x32f998, unicode=1,
mapping=WMCHAR_MAP_DISPATCHMESSAGE)
[/home/austin/wine-git/dlls/user32/winproc.c:2218] in user32 (0x0032f968)
6 0x607e7ee6 DispatchMessageW+0x96(msg=<register EDI not in topmost frame>)
[/home/austin/wine-git/dlls/user32/message.c:3122] in user32 (0x0032f9a8)
7 0x607a4037 WDML_SyncWaitTransactionReply+0xe7(hConv=0x1254b8,
dwTimeout=<register ESI not in topmost frame>, pXAct=0x125508, ack=0x32fb84)
[/home/austin/wine-git/dlls/user32/dde_client.c:1069] in user32 (0x0032fa08)
8 0x607a4b21 DdeClientTransaction+0x651(pData="test dde command", cbData=17,
hConv=0x1254b8, hszItem=0xdead, wFmt=48879, wType=16464, dwTimeout=1000,
pdwResult=0x32fb84) [/home/austin/wine-git/dlls/user32/dde_client.c:1225] in
user32 (0x0032fa68)
9 0x60686158 test_dde_aw_transaction+0x638()
[/home/austin/wine-git/dlls/user32/tests/dde.c:1374] in user32_test
(0x0032fb98)
...
216 while (*s) s++;
Attached is the backtrace...I've stripped out +heap, so the output is readable,
but easily reproducible.
--
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=54089
Bug ID: 54089
Summary: user32:input - test_SendInput() sometimes gets an
unexpected 0x738 message on w1064v1709
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
test_SendInput() sometimes gets an unexpected 0x738 message on w1064v1709:
* 2022-060-14
input.c:4439: Test failed: SendInput triggered unexpected message 0x60
input.c:4457: Test failed: SendInput triggered unexpected message 0x738
* 2022-12-05
input.c:4560: Test failed: SendInput triggered unexpected message 0x60
input.c:4578: Test failed: SendInput triggered unexpected message 0x738
See https://test.winehq.org/data/patterns.html#user32:input
It's not clear why this only happens on w1064v1709.
I suspect this is a repeat of bug 48815 where this 0x738 message was being sent
to a message-only UserAdapterWindowClass window (but apparently that impacted
all Windows 10 >= 1709). If so maybe user32:input should selectively ignore
some messages like user32:win now does:
commit fa28e05cf5b0101fb046c4845391634791268200
Author: Rémi Bernon <rbernon(a)codeweavers.com>
Date: Mon Jan 31 14:18:07 2022 +0100
user32/tests: Ignore messages for UserAdapterWindowClass windows.
Wine-Bug: https://bugs.winehq.org//show_bug.cgi?id=48815
Signed-off-by: Rémi Bernon <rbernon(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
--
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=51473
Bug ID: 51473
Summary: user32:input Some SendInput() set LastError to
ERROR_ACCESS_DENIED on cw-rx460 19.11.3
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
More specifically some cw-rx460 machines have the following failures:
https://test.winehq.org/data/patterns.html#user32:input
input.c:4410: Test failed: SendInput returned 1, error 0x5
input.c:4413: Test failed: SendInput returned 16, error 0x5
input.c:4464: Test failed: SendInput returned 16, error 0x5
These fail not because SendInput() failed, but because it modified LastError,
setting it to ERROR_ACCESS_DENIED.
This only happens on the following machines which have in common that they use
the 19.11.3 Radeon driver which is the latest version that will run on these
Windows versions:
win1507_cw-rx460-1507-32
win1507_cw-rx460-1507-64
win81_cw-rx460-32
win81_cw-rx460-64
The failure is systematic on these machines.
--
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=51471
Bug ID: 51471
Summary: user32:input receives unexpected WM_SYSTIMER messages
in test_SendInput()
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:input sometimes receives unexpected WM_SYSTIMER messages in
test_SendInput():
https://test.winehq.org/data/patterns.html#user32:input
input.c:4477: Test failed: SendInput triggered unexpected message 0x118
Notes:
* This is random: there is no machine where it happens systematically; and
different machines don't necessarily have the issue on the same day.
* This does not happen on a specific Windows version though not all seem to be
impacted either. Specifically this issue has been seen on the following
machines:
win7_newtb-w7u-2qxl
win7_newtb-w7u-de
win7_newtb-w7u-el
win7_newtb-w7u-es
win7_newtb-w7u-pt-PT
2008_newtb-w2008s64
win81_cw-rx460
win1507_cw-gtx560-1507
win1507_cw-rx460-1507
win1909_cw-gtx560-1909
win2009_cw-gtx560-2009
win2009_cw-rx460-2009
* Maybe the following article can be useful:
https://devblogs.microsoft.com/oldnewthing/20160624-00/?p=93745
--
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=42784
Bug ID: 42784
Summary: Lost Planet dx10 demo black screen after starting new
game
Product: Wine
Version: 2.5
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andras(a)sth.sze.hu
Distribution: ---
Created attachment 57802
--> https://bugs.winehq.org/attachment.cgi?id=57802
+d3d11, + d3d_shader
After starting new game or performance test in Lost Planet dx10 demo, it shows
only black screen. It tries to create a geometry shader and fails. As far as I
see, it want to use a vertex shader as geometry shader.
See log file.
--
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=54223
Bug ID: 54223
Summary: [Wine 8.0-rc2] [Severe Performance Regression]
[Unigine Heaven Benchmark 4.0] Wine DirectX11 to
OpenGL Severely Low FPS
Product: Wine
Version: 8.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: CHECK_1234543212345(a)protonmail.com
Distribution: ---
⬤ System Information:
OS: Ubuntu 22.10
Kernel: 6.1.0
CPU: Ryzen 7 1700
GPU: XFX RX580 4GB
Window Manager: OpenBox
Compositor: No Compositor, Xorg TearFree Disabled
⬤ Issue:
Wine's DirectX11 to OpenGL was the fastest on Wine 6.0, but then got a little
slower on Wine 7.0 and got severely more slower when I tested with Wine 7.22
before I installed Wine 8.0-rc2.
⬤ Settings:
RX580 locked to 300Mhz core clock and 300Mhz memory clock
Quality: Low
Resolution: 1280x720
Fullscreen: Unchecked
⬤ Information:
Lutris was used to easily switch between Wine versions.
Scene 2 is where the screen was moving across the bridge looking at the boat.
You can switch scenes with in the Unigine Benchmark by using the "Backspace"
and "Enter" keyboard keys.
Unigine Heaven Benchmark 4.0 Results:
--------------------
Wine staging 8.0-rc2 DX11 to OpenGL
Scene 2: 41 FPS (41 FPS with WINEDEBUG=-all)
Scene 3: 24 FPS (24 FPS with WINEDEBUG=-all)
Wine staging 8.0-rc2 DX11 to Vulkan (winetricks renderer=vulkan)
Scene 2: 26 FPS (with WINEDEBUG=-all)
Scene 3: 15 FPS (with WINEDEBUG=-all)
Wine staging 8.0-rc2 DX11 to Vulkan (DXVK 2.0) (./setup_dxvk.sh install)
Scene 2: 84 FPS (with WINEDEBUG=-all)
Scene 3: 104 FPS (with WINEDEBUG=-all)
-
Wine staging 8.0-rc2 DX9 to OpenGL
Scene 2: 90 FPS (with WINEDEBUG=-all)
Scene 3: 97 FPS (with WINEDEBUG=-all)
Wine staging 8.0-rc2 DX9 to Vulkan (winetricks renderer=vulkan)
CRASHES with an error dialog when starting benchmark
Wine staging 8.0-rc2 DX9 to Vulkan (DXVK 2.0) (./setup_dxvk.sh install)
Scene 2: 57 FPS (with WINEDEBUG=-all)
Scene 3: 67 FPS (with WINEDEBUG=-all)
-
Wine staging 8.0-rc2 OpenGL to OpenGL
Scene 2: 91 FPS (with WINEDEBUG=-all)
Scene 3: 105 FPS (with WINEDEBUG=-all)
--------------------
Wine staging 7.22 DX11 to OpenGL
Same performance problem as wine 8.0-rc2
--------------------
Wine staging 7.0 DX11 to OpenGL
Scene 2: 61 FPS (74 FPS with WINEDEBUG=-all)
Scene 3: 32 FPS (61 FPS with WINEDEBUG=-all)
-
Wine staging 7.0 DX9 to OpenGL
Scene 2: 88 FPS (with WINEDEBUG=-all)
Scene 3: 83 FPS (with WINEDEBUG=-all)
--------------------
Wine staging 6.0 DX11 to OpenGL
Scene 2: 88 FPS (88 FPS with WINEDEBUG=-all)
Scene 3: 48 FPS (71 FPS with WINEDEBUG=-all)
-
Wine staging 6.0 DX9 to OpenGL
Scene 2: 88 FPS (with WINEDEBUG=-all)
Scene 3: 78 FPS (with WINEDEBUG=-all)
--------------------
Wine staging 5.1 DX11 to OpenGL
Scene 2: 71 FPS (71 FPS with WINEDEBUG=-all)
Scene 3: 48 FPS (55 FPS with WINEDEBUG=-all)
--------------------
Wine staging 4.0 DX11 to OpenGL
Scene 2: 75 FPS (84 FPS with WINEDEBUG=-all)
Scene 3: 41 FPS (64 FPS with WINEDEBUG=-all)
--------------------
Wine staging 3.0 DX11 to OpenGL
Scene 2: 48 FPS (61 FPS with WINEDEBUG=-all)
Scene 3: 27 FPS (44 FPS with WINEDEBUG=-all)
The Unigine Benchmark Launcher opened very quickly with wine 3.0
--------------------
⬤ Information:
I had "Output debugging info" "Enabled" in Lutris at first with the DX11 to
OpenGL tests and retested with "Output debugging info" "Disabled (default)" in
Lutris, which just added the "WINEDEBUG=-all" environmental variable.
The Wine 32-bit staging versions 7.0 to 3.0 was downloaded from:
https://www.playonlinux.com/wine/binaries/phoenicis/staging-linux-x86/
The Unigine Heaven Benchmark Launcher was closed after starting each benchmark
because the Unigine Heaven Benchmark Launcher was decreasing the FPS.
⬤ Conclusion:
DirectX11 to OpenGL was the fastest in Wine 6.0
Somewhere between Wine 6.0 and Wine 7.0, Wine's DirectX11 to OpenGL became a
bit more slower.
Somewhere between Wine 7.0 and Wine 7.22, Wine's DirectX11 to OpenGL became
severely more slower.
Wine's OpenGL to OpenGL is currently faster than:
DXVK (DXVK 2.0) (./setup_dxvk.sh install)
Wine's DirectX9/DirectX11 to OpenGL (renderer=gl).
Wine's DirectX9/DirectX11 to Vulkan (winetricks renderer=vulkan)
Unigine Heaven Benchmark crashes when using DirectX9 to Vulkan (winetricks
renderer=vulkan) but not with DXVK's DirectX9 to Vulkan (DXVK 2.0)
(./setup_dxvk.sh install).
Wine 3.0 Opens the Unigine Heaven Benchmark launcher very quickly. But then
with Wine 4.0 and above, the Unigine Heaven Benchmark launcher opens more
slower than Wine 3.0. I am using a HDD.
⬤ Warning if not fixed before Wine 8.0 stable gets released:
It would be good if this problem is fixed before Wine 8.0 stable get released
because Steam's Proton uses stable versions of Wine.
If this problem is not fixed by the time Wine 8.0 stable gets released and
proton updates to Wine 8.0. anyone using "PROTON_USE_WINED3D=1" on a DirectX11
Steam game can have severely Low FPS while Wine 7.0's DirectX11 to OpenGL is
only a little bit more slower than Wine 6.0's DirectX11 to OpenGL right 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=52595
Bug ID: 52595
Summary: Starts with black window
Product: Wine
Version: 7.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: k8auf1947(a)cometchaser.de
Distribution: ---
Created attachment 71920
--> https://bugs.winehq.org/attachment.cgi?id=71920
App starts with black window, Wine 7.2 on Bullseye
The application starts and shows a black window (application menue is shown).
After clicking into the black window, the application draws the window.
It worked until Wine 7.1, problem appears with Wine 7.2 on Debian Bullseye.
Happens also on Debian Bookworm.
File: test-2022-02-25_18.50.43.mp4
Wine 7.1 on Bookworm
File: test-2022-02-26_10.40.38.mp4
Wine 7.2 on Bullseye
--
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=50475
Bug ID: 50475
Summary: ENM (Externes Notenmodul / external mark module)
crashes on opening
Product: Wine
Version: 5.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sebastian.arnhold387(a)gmail.com
Distribution: ---
Created attachment 69111
--> https://bugs.winehq.org/attachment.cgi?id=69111
Terminal log
ENM is a teacher's tool for grading students, released by the government of the
state of North-Rhine Westphalia (NRW) in Germany.
Requirements for wine:
winetricks mdac28 msls31 riched30 vb6run winbind
Description of the bug:
When trying to install the latest version of ENM ("ENM-Setup 1.4.8.1 Stand
21.12.2020") downloaded from the official government website, the installer
works fine. When trying to open the installed executable, the program crashes
immediately with an "unhandled exception" error.
I tried to run it using both wine and wine-development package, trying both 64
bit and 32 bit prefix, on Ubuntu 20.04 amd64. Results are identical.
Terminal output log included.
Link to software (installer):
https://www.svws.nrw.de/system/files/zip_und_exe/2020-12/ENM-Setup_1_4_8_1.…
Link to WineHQ database entry (outdated and unmaintained):
https://appdb.winehq.org/objectManager.php?sClass=application&iId=9047
Additional problem solving analysis:
Older versions of the software definitely worked fine until June 2020, as e.g.
this blog entry proves (http://www.tohschneider.de/extnotmodlinux/). Suspected
a problem with ENM software itself, but when trying older version from before
that time, these versions that once worked fine now also throw an "unhandled
exception" error. This proves that something in wine must have changed.
Contacted developer of ENM software. Developer suspects a problem with the way
wine handles the ADO drivers. Other softwares from the government school
software suite show similar behaviour. Government institution sadly does not
support Linux, but is interested in getting ENM software to work again.
In the interest of free education, solution would be highly appreciated.
Thanks!
--
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=54362
Bug ID: 54362
Summary: BurnInTest calls unimplemented function
ntoskrnl.exe.ExAllocatePool2
Product: Wine
Version: 8.0-rc5
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntoskrnl
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
Created attachment 73935
--> https://bugs.winehq.org/attachment.cgi?id=73935
Console output
When BurnInTest starts, it tries several times to call ExAllocatePool2. Each
time, a black terminal window appears over the main window.
$ sha256sum bitwindows.exe
d90fd00445986b74c5af179a5cb1a381c9b6ab7be459afcb55fe342f12724296
--
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=51931
Bug ID: 51931
Summary: Dead Rising encounters infinite loading when starting
a new game (needs WMAudio Decoder DMO)
Product: Wine
Version: 6.20
Hardware: x86-64
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: xaudio2
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
073c:err:ole:com_get_class_object class {2eeb4adf-4578-4d10-bca7-bb955f56320a}
not registered
073c:err:ole:com_get_class_object no class object
{2eeb4adf-4578-4d10-bca7-bb955f56320a} could be created for context 0x1
wine-6.20-61-gababea0fd70
--
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=56119
Bug ID: 56119
Summary: Emperor - Rise of the Middle Kingdom: invisible menu
buttons
Product: Wine
Version: 8.18
Hardware: x86-64
URL: https://www.gamepressure.com/download.asp?ID=1725
OS: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: z.figura12(a)gmail.com
Regression SHA1: ee7d047dd55a4b2338eb2d64f85b7d984b39812f
Distribution: ---
Only the background is drawn in the menus, the menu buttons are invisible in
the game Emperor:Rise of the Middle Kingdom (GOG). Can be reproduced in the
demo version too.
Pharaoh is another city-building game using the same engine: here the screen
remains black when the game gets to the main menu.
Pharaoh demo:
https://archive.org/download/PharaohDemo/PharaohDemo.zip
Reverting commit ee7d047dd55a4b2338eb2d64f85b7d984b39812f
on top of Wine-9.0-rc3 fixes the problem in both games for me.
Plain terminal output doesn't show anything related.
PharaohDemo.zip (74 M)
md5:474872cf372acbd4312ca0a6caf75434
si_emperor_demo.exe (128 M)
md5:45052f088f699afb7a0d5e2ecfcb1804
--
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=51474
Bug ID: 51474
Summary: user32:input SendInput() triggers an unexpected
message 0x60 on Windows 10 1709
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Created attachment 70310
--> https://bugs.winehq.org/attachment.cgi?id=70310
Trace all window handles and 0x60 message
SendInput() triggers an unexpected message 0x60 in test_SendInput() on Windows
10 1709:
https://test.winehq.org/data/patterns.html#user32:input
input.c:4451: Test failed: SendInput triggered unexpected message 0x60
* This failure is almost but not 100% systematic on Windows 10 1709: it
happened 202 times out of 205.
* I could not find any documentation on this 0x60 message.
* But the attached patch shows that:
- The message is sent to a window belonging to our process.
- The test did not directly create that window.
- The window class is UserAdapterWindowClass which seems to be related to IME
despite these machines running in a regular en_US locale.
input.c:4404: 4404 hwnd=0000000000020274
input.c:4474: Test failed: SendInput triggered unexpected message 0x60
input.c:4480: hwnd=0000000000020274 pid=7016 tid=7012 now=64359
input.c:4481: hwnd=0000000000040048 message=0060 wParam=1 lParam=0 time=64359
pt=(512,384)
input.c:4485: wnd: pid=7016 tid=7012 class=22 L"UserAdapterWindowClass" text=0
L""
--
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.