https://bugs.winehq.org/show_bug.cgi?id=38872
Bug ID: 38872
Summary: 3DMark06 cannot be run without native d3d_* libraries:
proxycon_in.txt: D3DXCompileShader failed: Invalid
data (D3DXERR_INVALIDDATA)
Product: Wine
Version: 1.7.45
Hardware: x86
URL: http://www.futuremark.com/benchmarks/legacy
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: t.artem(a)mailcity.com
Distribution: ---
Created attachment 51801
--> https://bugs.winehq.org/attachment.cgi?id=51801
D3DXCompileShader failed: Invalid data (D3DXERR_INVALIDDATA)
fixme:hlsl_parser:hlsl_parse Check for valued return on void function.
fixme:hlsl_parser:hlsl_parse Implicit conversion to the return type if needed,
error out if conversion not possible.
err:d3dcompiler:compile_shader HLSL shader parsing failed.
--
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=42912
Bug ID: 42912
Summary: Death to Spies: Moment of Truth demo needs
d3dx9_skin_info_ConvertToIndexedBlendedMesh
Product: Wine
Version: 2.7
Hardware: x86-64
URL: http://files.aspyr.com/support/DTS_Demo_Installer.zip
OS: Linux
Status: NEW
Keywords: download
Severity: minor
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 58057
--> https://bugs.winehq.org/attachment.cgi?id=58057
screenshot
Crashes on level loading.
fixme:d3dx:d3dx9_skin_info_ConvertToIndexedBlendedMesh iface 0x10cac280,
mesh_in 0x633564c0, options 0, palette_size 69, adjacency_in 0x6c9cd58,
adjacency_out 0x6cb00e8, face_remap (nil), vertex_remap (nil), max_face_infl
0x32f88c, num_bone_combinations 0x32f860, bone_combination_table 0x32f86c,
mesh_out 0x32f830 stub!
fixme:d3dx:d3dx9_mesh_OptimizeInplace D3DXMESHOPT_VERTEXCACHE not implemented.
Native d3dx9_32 fixes 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.
http://bugs.winehq.org/show_bug.cgi?id=35129
Bug ID: 35129
Summary: Cloning Clyde refuses to start with built-in d3dx9_36
Product: Wine
Version: 1.7.8
Hardware: x86
URL: http://www.fileplanet.com/224883/220000/fileinfo/Cloni
ng-Clyde-Client-%28Trial%29
OS: Linux
Status: NEW
Keywords: download
Severity: minor
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: wine-bugs(a)winehq.org
Classification: Unclassified
Created attachment 46859
--> http://bugs.winehq.org/attachment.cgi?id=46859
terminal output (+d3dx traces)
The game won't start with the built-in d3dx9_36, it flashes a black window for
a brief moment then it quits without an error message.
+d3dx debug channel added only 4 lines to the terminal output as can be seen at
the end of the attached log file.
Please install ie8 via winetricks when testing with the demo version as the
launcher doesn't work with Wine's IE.
'winetricks d3dx9_36' is a workaround.
Fedora 19
Nvidia binary drivers 325.15
wine-1.7.8-88-gfb75292
--
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=52409
Bug ID: 52409
Summary: Regression: battle.net does not open when multiple
monitors are connected.
Product: Wine
Version: 7.0-rc6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: GloriousEggroll(a)gmail.com
Regression SHA1: 45dcaf02fcd9e929b406854b4b78371bc3886031
Distribution: ---
If more than one monitor is enabled on the system battle.net fails to open. If
I disable all but one monitor it then allows battle.net to load.
last known working version was 6.22, broke in 6.23. Bisected to first bad
commit 45dcaf02fcd9e929b406854b4b78371bc3886031
--
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=52083
Bug ID: 52083
Summary: Some test_TimerResolution() tests fail randomly in
ntdll:time
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Some test_TimerResolution() tests fail randomly in ntdll:time:
time.c:293: Test failed: expected requested timer resolution 156250, got 10006
time.c:298: Test failed: expected requested timer resolution 20000, got 10006
time.c:310: Test failed: expected new timer resolution 20000, got 10006
time.c:318: timer resolution: 5000(max) <= 5003(cur) <= 20000(prev) <=
156250(min)
time.c:322: Test failed: expected new timer resolution 20000, got 5003
time.c:322: Test failed: NtQueryTimerResolution() expected timer resolution
5003, got 20000
time.c:328: Test failed: expected requested timer resolution 5003, got 75011
https://test.winehq.org/data/patterns.html#ntdll:time
The number of failures varies and six seems to be a maximum. This appears to
only impact Windows 10 1709+ but impacts both the TestBot VMs and real test
machines (cw-gtx560 and cw-rx460).
Based on the current failure pattern it looks like the failures started on
2021-09-30. That is, there was no failure for any of the 252 builds from
2021-09-21 to 2021-09-29 and there has been at least one failure for every
build since.
Yet the failure is reproducible with the commit that introduced the tests
(6015fee5b218), and also with the one that fixed some of the issues a few days
later (b2c89b1a41fa):
commit 6015fee5b21870ddd57477843354173d2e7f9696
Author: François Gouget <fgouget(a)codeweavers.com>
AuthorDate: Thu Jul 29 17:24:15 2021 +0200
ntdll/tests: Add some Nt{Query,Set}TimerResolution() tests.
Signed-off-by: Francois Gouget <fgouget(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=48676
Bug ID: 48676
Summary: CD not detetected in Exact Audio Copy since wine 4.21
anymore
Product: Wine
Version: 4.21
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mountmgr.sys
Assignee: wine-bugs(a)winehq.org
Reporter: bastian.dev(a)gmail.com
Distribution: ---
When I insert a audio cd in the drive, Exact Audio Copy (v 1.3) doesn't detect
it. It just doesn't show anything. 4.20 was the last version it worked with.
I've also tried wine 4.21 and 5.0.
--
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=45328
Bug ID: 45328
Summary: Unusable GUI for ElsterFormular 19.5
Product: Wine
Version: 3.10
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: ---
It would be nice if I could use the application “ElsterFormular 19.5
(2018-06-14)” together with the software “Wine 3.10-820.1” finally.
https://www.elster.de/eportal/infoseite/elsterformularhttps://appdb.winehq.org/objectManager.php?sClass=application&iId=1925
elfring@Sonne:~> wine C:\\windows\\command\\start.exe /Unix
/home/elfring/.wine/dosdevices/c:/users/elfring/Start\
Menu/Programs/ElsterFormular/ElsterFormular.lnk
0009:fixme:exec:SHELL_execute flags ignored: 0x00000100
0009:fixme:exec:SHELL_execute flags ignored: 0x00004100
elfring@Sonne:~> 0036:fixme:file:FindFirstFileExW flags not implemented
0x00000002
0036:fixme:file:FindFirstFileExW flags not implemented 0x00000002
0036:fixme:msvcrt:type_info_name_internal_method type_info_node parameter
ignored
…
Its graphical user interface does not respond to mouse clicks so far.
--
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=41102
Bug ID: 41102
Summary: Alan Wake's American Nightmare crashes at launch
randomly with 'm->state == STATE_PASSIVE'
Product: Wine
Version: 1.9.16
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: winepulse.drv
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: aeikum(a)codeweavers.com
Distribution: ---
Crashes very randomly, so hard to reproduce.
Assertion 'm->state == STATE_PASSIVE' failed at pulse/mainloop.c:787, function
pa_mainloop_prepare(). Aborting.
wine: Assertion failed at address 0xf779ad49 (thread 0028), starting
debugger...
Unhandled exception: assertion failed in 32-bit code (0xf779ad49).
Backtrace:
=>0 0xf779ad49 __kernel_vsyscall+0x9() in [vdso].so (0x7c1bd2e8)
1 0xf73d95c9 gsignal+0x38() in libc.so.6 (0x7c1bd2e8)
2 0xf73daca7 abort+0x156() in libc.so.6 (0x7c1bd2e8)
3 0x7a9e9e47 pa_mainloop_prepare+0x286() in libpulse.so.0 (0x7c1bd2e8)
4 0x7a9ea923 pa_mainloop_iterate+0x32() in libpulse.so.0 (0x04a0dc98)
5 0x7aa512b3 pulse_test_connect+0x182()
[/wine/dlls/winepulse.drv/mmdevdrv.c:566] in winepulse (0x04a0dc98)
6 0x7aa58590 AUDDRV_GetPriority+0x2f()
[/wine/dlls/winepulse.drv/mmdevdrv.c:947] in winepulse (0x04a0dcc8)
7 0x7b8199bf init_driver+0x25e() [/wine/dlls/mmdevapi/main.c:103] in mmdevapi
(0x04a0e1c8)
8 0x7b81a21c DllGetClassObject+0x3b(rclsid=<couldn't compute location>,
riid=<couldn't compute location>, ppv=<couldn't compute location>)
[/wine/dlls/mmdevapi/main.c:282] in mmdevapi (0x04a0e1f8)
9 0x7e95fc1c apartment_getclassobject+0x11b(apt=<is not available>,
dllpath=<is not available>, apartment_threaded=<is not available>, rclsid=<is
not available>, riid=<is not available>, ppv=<is not available>)
[/wine/dlls/ole32/compobj.c:1372] in ole32 (0x04a0e268)
10 0x7e962bd5 get_inproc_class_object+0x114(apt=<is not available>,
regdata=<is not available>, rclsid=<is not available>, riid=<is not available>,
hostifnecessary=<is not available>, ppv=<is not available>)
[/wine/dlls/ole32/compobj.c:2930] in ole32 (0x04a0e4c8)
11 0x7e965565 CoGetClassObject+0x50f(rclsid=<is not available>,
dwClsContext=<is not available>, pServerInfo=<is not available>, iid=<is not
available>, ppv=<is not available>) [/wine/dlls/ole32/compobj.c:3068] in ole32
(0x04a0e578)
12 0x7e966be1 CoCreateInstanceEx+0x1db(rclsid=<is not available>,
pUnkOuter=<is not available>, dwClsContext=<is not available>, pServerInfo=<is
not available>, cmq=<is not available>, pResults=<is not available>)
[/wine/dlls/ole32/compobj.c:3305] in ole32 (0x04a0e5f8)
13 0x7e9670dd CoCreateInstance+0x67(rclsid=<is not available>, pUnkOuter=<is
not available>, dwClsContext=<is not available>, iid=<is not available>,
ppv=<is not available>) [/wine/dlls/ole32/compobj.c:3201] in ole32 (0x04a0e668)
14 0x01e8347b in fmodex (+0x347a) (0x04a0e694)
15 0x01f07e45 in fmodex (+0x87e44) (0x04a0e6bc)
16 0x01f07f7a in fmodex (+0x87f79) (0x04a0e6d4)
17 0x01f080b8 in fmodex (+0x880b7) (0x04a0e70c)
18 0x01ea2e74 in fmodex (+0x22e73) (0x04a0e728)
19 0x01e569b4 in snd_w32_f (+0x69b3) (0x04a0e900)
20 0x01e573fa in snd_w32_f (+0x73f9) (0x04a0e928)
21 0x01e57a9c in snd_w32_f (+0x7a9b) (0x04a0e948)
22 0x0042f4e4 in alan_wakes_american_nightmare (+0x2f4e3) (0x04a0e990)
23 0x0042fb0b in alan_wakes_american_nightmare (+0x2fb0a) (0x04a0e9c4)
24 0x006eded0 in alan_wakes_american_nightmare (+0x2edecf) (0x04a0e9f4)
25 0x00d99f02 in rl_w32_f (+0x59f01) (0x04a0ea08)
26 0x7bc7d8ac call_thread_func_wrapper+0xb() in ntdll (0x04a0ea18)
27 0x7bc80669 call_thread_func+0xa8(entry=0xd42b8a, arg=0x399d2a0,
frame=0x4a0eb18) [/wine/dlls/ntdll/signal_i386.c:2759] in ntdll (0x04a0eaf8)
28 0x7bc7d88a call_thread_entry_point+0x11() in ntdll (0x04a0eb18)
29 0x7bc88073 start_thread+0xa2(info=0x7ffd0fb8)
[/wine/dlls/ntdll/thread.c:453] in ntdll (0x04a0f368)
PulseAudio 8.0
--
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=52538
Bug ID: 52538
Summary: Regression: Yamaha Expansion Manager crashes
Product: Wine
Version: 7.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: joseskvolpe(a)gmail.com
Distribution: ---
I found out this application has got a regression on a older regression
Based on the test results history, it has got a platinum rating in Wine 6.0,
but the application crashes on the start-up on Wine 7.1 so it's rating is now
Garbage.
I tested it on a self-compiled Wine 6.0.2, the application works well on a
WoW64 prefix all-trial, but crashes on a 32-Bits prefix. I've downloaded newer
Wine binaries from Arch's packages archive
(https://archive.archlinux.org/packages/w/wine/) and tested the application
multiple-times, it works until Wine 6.9, older versions works but crashes
sometimes, so i've to try it 5 times to be sure it's not working. The
application won't work on Wine 6.9 no matter how much time you try it.
But i'm afraid i couldn't find the bad commit, there's something very weird on
this issue, let me explain.
That was my methodology for regression testing it:
1 - Erase the wineprefix
2 - Make the bisection (bisect start, bisect skip, bisect good or bisect bad)
3 - WoW64 Wine compile (wine-64 build, then wine-32 build)
4 - Create a new WoW64 wineprefix
5 - Try application multiple times, if it succeeds then it's bisect good, if it
crashes after trying it over 5 times, then it's bisect bad
However, the application could always succeed after compiling Wine before the
5th try, until the last bisection.
I tried again bisecting Wine 6.9 and Wine 6.10. The application were crashing
on both Wine 6.9 and Wine 6.10 from Arch's binary archive, but it could succeed
if i compile them.
I'd the same issue, although the application could indeed crash sometimes (wich
also occurs on older Wine versions), it were always succeeding before the 5th
try, so i couldn't find what was the commit that caused the regression.
¿Maybe is that a issue from who's compiling Wine for Arch?
¿Should i compile Wine 7.1 and try the application?
I planned to become a maintainer for the application only to add a proper
description and then leave, but now i'll stay maintaining this application for
a while until we can figure it out.
¿Can you devs reproduce the crash on other distributions?
Download: https://tw.yamaha.com/zh/support/updates/yem_win_v260.html
SHA1: b6255d5371679554b72f29a00008578438a1bfe6
Procedure:
1 - Run "Expansion Manager.exe"
--
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=52145
Bug ID: 52145
Summary: 2gis 3.16.3: error after exit
Product: Wine
Version: 6.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: v.yuzbekov(a)yandex.ru
Distribution: ---
Created attachment 71192
--> https://bugs.winehq.org/attachment.cgi?id=71192
backtrace
An error occurs after the ad window is displayed while exiting the program.
--
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=51135
Bug ID: 51135
Summary: Arturia Pigments 3 crashes when mousing over the
volume control
Product: Wine
Version: 6.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sgarman(a)zenlinux.com
Distribution: ---
Created attachment 70000
--> https://bugs.winehq.org/attachment.cgi?id=70000
Arturia Pigments 3 crash backtrace
Pigments 3 is a VST synthesizer plugin used in music production. It can be
found at:
https://www.arturia.com/products/analog-classics/pigments#en
and it installs successfully in Wine via Arturia's Software Center, which is
available at the top of this list:
https://www.arturia.com/support/downloads&manuals
Pigments seems to be working well, with one significant flaw - if you mouse
over the volume control knob icon (in the upper right corner of the UI), the
app freezes/crashes. I believe this is the only thing preventing this synth
plugin from working flawlessly.
I'll attach a backtrace of the crash report. I'm running the latest Wine
Staging (6.8) on an Ubuntu 20.04 system with kernel 5.9.16-050916-generic from
Ubuntu's kernel PPA.
--
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=50822
Bug ID: 50822
Summary: Sniper: Ghost Warrior 2 has rendering glitch in DX9
mode with OpenGL renderer
Product: Wine
Version: 6.4
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 69640
--> https://bugs.winehq.org/attachment.cgi?id=69640
example
wine-6.4-118-g2828d0820a1
--
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=50136
Bug ID: 50136
Summary: allow to disable wine's vulkan loader/driver
Product: Wine
Version: 5.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: winevulkan
Assignee: wine-bugs(a)winehq.org
Reporter: xantares09(a)hotmail.com
Distribution: ---
I'm trying to run mesa's software vulkan renderer driver with wine.
This means I want to use vulkan's icd loader and mesa's renderer libs I built
(outside of wine):
libvulkan-1.dll
libvulkan_lvp.dll
Unfortunately, building wine with --disable-vulkan does not seem to disable its
loader, it only disables the driver:
$ VK_ICD_FILENAMES=lvp_icd.x86_64.json wine vkcubepp.exe
0064:err:vulkan:get_vulkan_driver Wine was built without Vulkan support.
Is there a way to disable the loader 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=48112
Bug ID: 48112
Summary: The tests trigger heap and loader critical section
lockups
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The log of *some* WineTest runs contains critical section errors like the
following:
Running: httpapi:httpapi (222 of 670)
[...]
01d8:err:ntdll:RtlpWaitForCriticalSection section 0x110060
"../../../wine/dlls/ntdll/heap.
c: main process heap section" wait timed out in thread 01d8, blocked by 01d4,
retrying (60
sec)
01f8:err:ntdll:RtlpWaitForCriticalSection section 0x110060
"../../../wine/dlls/ntdll/heap.
c: main process heap section" wait timed out in thread 01f8, blocked by 01d4,
retrying (60
sec)
0201:err:ntdll:RtlpWaitForCriticalSection section 0x110060
"../../../wine/dlls/ntdll/heap.c: main process heap section" wait timed out in
thread 0201, blocked by 01d4, retrying (60 sec)
01d9:err:ntdll:RtlpWaitForCriticalSection section 0x7be970a0
"../../../wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread
01d9, blocked by 0201, retrying (60 sec)
01d7:err:ntdll:RtlpWaitForCriticalSection section 0x7be970a0
"../../../wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread
01d7, blocked by 0201, retrying (60 sec)
01f7:err:ntdll:RtlpWaitForCriticalSection section 0x110060
"../../../wine/dlls/ntdll/heap.c: main process heap section" wait timed out in
thread 01f7, blocked by 01d4, retrying (60 sec)
01d8:err:ntdll:RtlpWaitForCriticalSection section 0x110060
"../../../wine/dlls/ntdll/heap.c: main process heap section" wait timed out in
thread 01d8, blocked by 01d4, retrying (60 sec)
01f8:err:ntdll:RtlpWaitForCriticalSection section 0x110060
"../../../wine/dlls/ntdll/heap.c: main process heap section" wait timed out in
thread 01f8, blocked by 01d4, retrying (60 sec)
0201:err:ntdll:RtlpWaitForCriticalSection section 0x110060
"../../../wine/dlls/ntdll/heap.c: main process heap section" wait timed out in
thread 0201, blocked by 01d4, retrying (60 sec)
01d9:err:ntdll:RtlpWaitForCriticalSection section 0x7be970a0
"../../../wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread
01d9, blocked by 0201, retrying (60 sec)
01d7:err:ntdll:RtlpWaitForCriticalSection section 0x7be970a0
"../../../wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread
01d7, blocked by 0201, retrying (60 sec)
Running: ieframe:ie (223 of 670)
Running: ieframe:intshcut (224 of 670)
01dc:err:ntdll:RtlpWaitForCriticalSection section 0x110060
"../../../wine/dlls/ntdll/heap.c: main process heap section" wait timed out in
thread 01dc, blocked by 01d4, retrying (60 sec)
01da:err:ntdll:RtlpWaitForCriticalSection section 0x110060
"../../../wine/dlls/ntdll/heap.c: main process heap section" wait timed out in
thread 01da, blocked by 01d4, retrying (60 sec)
[... and more later on, all the way to...]
Running: wtsapi32:wtsapi (665 of 670)
01dc:err:ntdll:RtlpWaitForCriticalSection section 0x110060
"../../../wine/dlls/ntdll/heap.c: main process heap section" wait timed out in
thread 01dc, blocked by 01d4, retrying (60 sec)
[...]
It's always either the heap critical section or the loader one. Unfortunately
the ERR() message does not show the process id so it's impossible to know which
process got stuck. We can rule out httpapi:httpapi and the tests that ran
before because the WineTest report indicates that they ran for less than 1
second:
gdiplus:region:01ae done (0) in 0s
gdiplus:stringformat:01b4 done (0) in 0s
hid:device:01b7 done (0) in 1s
hlink:browse_ctx:01b9 done (0) in 0s
hlink:hlink:0118 done (0) in 0s
hnetcfg:policy:0112 done (0) in 0s
httpapi:httpapi:014f done (0) in 1s
* The lockups seem to continue until the end of the log. So they could be
happening in either WineTest.exe, or one of Wine's internal processes:
explorer.exe, plugplay.exe, services.exe or winedevice.exe.
* httpapi:httpapi is always where the lockups appear first.
* Since the initial timeout is 5 seconds, it could in fact be caused by a test
that ran up to 5 seconds before httpapi:httpapi. Unfortunately the WineTest
report has a 1 second granularity so it's hard to know how many tests ran in 5
seconds.
* When the lockups occur WineTest takes 2 to 5 minutes longer to run. So they
slow the tests down somehow.
--
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=10570
Summary: Thief 2: The Metal Age - fog not working
Product: Wine
Version: 0.9.49.
Platform: Other
URL: http://www.thief-thecircle.com/media/demos/
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: a.hurst(a)shef.ac.uk
In a notoriously foggy level (Life of The Party), the fog doesn't work.
Card is an nvidia GeForce 6200, with latest nvidia-driver.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46169
Bug ID: 46169
Summary: Zabaware Reade doesn't work properly
Product: Wine
Version: 3.20
Hardware: x86
URL: https://www.zabaware.com/download
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: luca.finizio.mgbx(a)hotmail.it
Distribution: Mint
Hi! I downloaded Zabaware reader from here https://www.zabaware.com/download
and it works,but not as in Windows. In fact the voices are very different and
very annoying to listen to. To reproduce the bug you need to download the free
version of the program, then install ZabawareReaderSetup.exe.
Now write a sentence and hear it both in WIndows and in Linux. You will note a
big difference.
--
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=44414
Bug ID: 44414
Summary: GetNamedPipeHandleState not properly implemented
Product: Wine
Version: 3.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: ossman(a)cendio.se
Distribution: ---
I'm getting these running the Windows version of the ThinLinc client:
002f:fixme:sync:GetNamedPipeHandleStateW 0x4c 0x84e300 (nil) (nil) (nil) (nil)
0: semi-stub
002f:fixme:sync:GetNamedPipeHandleStateW 0x4c 0x84e300 (nil) (nil) (nil) (nil)
0: semi-stub
002f:fixme:sync:GetNamedPipeHandleStateW 0x50 0x84e300 (nil) (nil) (nil) (nil)
0: semi-stub
002f:fixme:sync:GetNamedPipeHandleStateW 0x50 0x84e300 (nil) (nil) (nil) (nil)
0: semi-stub
002f:fixme:sync:GetNamedPipeHandleStateW 0x54 0x84e300 (nil) (nil) (nil) (nil)
0: semi-stub
002f:fixme:sync:GetNamedPipeHandleStateW 0x54 0x84e300 (nil) (nil) (nil) (nil)
0: semi-stub
It uses that call to set and remove PIPE_NOWAIT.
The client also locks up, but I'm not sure it is because of this stub or
something else.
--
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=29902
Bug #: 29902
Summary: Windows Live Messenger 8.5 does login, error 81000378
Product: Wine
Version: 1.4-rc3
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fael_mc(a)msn.com
Classification: Unclassified
Created attachment 38893
--> http://bugs.winehq.org/attachment.cgi?id=38893
Log, try entering the messenger
salutations (google translation)
I installed messenger through .msi package without problems in wine,
I went to winecfg, changed windows version to 2000, when I opened the messenger
if you could not type anything in the field username and password, then
Riched20 installed through winetricks, so I could enter my username and
password when I try to get in, get into normal, but not time to appear the
contacts of the error 81000378
"You cannot use Windows Live Messenger at this time because your contact list
is not available.Please try again later"
I made some test with Wine 1.1.30, and usually logged, but the messenger is
buggy
I want to run it under wine 1.4
thank you
--
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.
http://bugs.winehq.org/show_bug.cgi?id=29942
Bug #: 29942
Summary: Windows Live Messenger 8.5, lock in chat windows
Product: Wine
Version: 1.4-rc4
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fael_mc(a)msn.com
Classification: Unclassified
Created attachment 38969
--> http://bugs.winehq.org/attachment.cgi?id=38969
Terminal log
Greetings
I managed to run and log into Windows Live Messenger 8.5 on wine, the bug does
not login, (bug 29902) was solved with a patch disponiblizado by Juan Lang.
Now I have another problem, after logging all normal, see the contacts, can I
change nickname, phrase, image.
I open the chat window to talk, I type normal, but when I send the message, the
program crashes, and gets caught, taking 30% cpu.
to have Windows Live Messenger 8.5 on wine, follow these steps:
Download messenger: http://www.mediafire.com/?tlywu43id00
Normal installation in wine, and install riched20 msxml3 by winetricks, then
set the Wine version for Windows 2000, done that is possible to login.
But to login you must have wine with the patch:
http://www.winehq.org/pipermail/wine-patches/2012-February/111655.htmlhttp://www.winehq.org/pipermail/wine-patches/2012-February/111656.html
applied, but the Windows Live Messenger error 81000378 will
Post here the log of the terminal, since the messenger open, until it freezes
in the chat window
--
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=53270
Bug ID: 53270
Summary: test_WSARecv() fails when using wow64 thunks
[Wow64ApcRoutine() overwrites return value set by
NtContinue()]
Product: Wine
Version: 7.11
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: source, testcase
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: z.figura12(a)gmail.com
Distribution: ---
Created attachment 72642
--> https://bugs.winehq.org/attachment.cgi?id=72642
test diff
This might be a bit early since the wow64 path isn't exactly supported, but
(with a couple patches to ntdll to enable it in the first place) it works well
enough to expose a bug in its own implementation, which is more than a little
tricky to solve.
I'm attaching a diff to the tests, which I will submit upstream, which
demonstrates the root of the problem.
KiUserApcDispatcher can be called from three-ish places: wait functions,
NtTestAlert, and NtContinue. In the case of the former two KiUserApcDispatcher
will be passed a wow64 context which, among other things, has its %rax/%eax set
to STATUS_USER_APC or STATUS_SUCCESS respectively. In the latter case %rax/%eax
comes from the passed-in context.
Wow64ApcRoutine tries to translate the %rax from the 64-bit context into the
%eax that the 32-bit context will restore to. In the former two cases this is
STATUS_USER_APC or STATUS_SUCCESS and things work fine. In the latter case,
however, this overwrites %eax from the passed-in 32-bit context. Note that we
don't get the right %eax from ntdll either, because (a) ntdll gives us a 64-bit
context anyway, and (b) we don't use NtContinue but rather NtTestAlert. That
does mean we could fix it by using NtContinue and putting the %eax value into
%rax, which is a bit weird but I don't know if there's a better option.
This is wrong inherently, as the attached tests show, but it more saliently
ends up breaking LdrInitializeThunk, because on i386 RtlUserThreadStart is
called with %eax pointing to the thread procedure, and we then overwrite that
with zero.
--
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=49266
Bug ID: 49266
Summary: Amazon Games installs but won't start
Product: Wine
Version: 5.8
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maiktapwagner(a)aol.com
Distribution: ---
Created attachment 67270
--> https://bugs.winehq.org/attachment.cgi?id=67270
Console Output (wine 5.8)
Hello everyone,
I download the Amazon games installer from:
https://download.amazongames.com/AmazonGamesSetup.exe
and got it installed with wine 5.8 - Unfortunately the application doesn't
launch. Console output is attached.
--
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=53236
Bug ID: 53236
Summary: d3d9:device - test_wndproc() sometimes gets an
unexpected WM_DISPLAYCHANGE in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
d3d9:device - test_wndproc() sometimes gets an unexpected WM_DISPLAYCHANGE in
Wine:
device.c:4349: Test failed: Expected message 0x7e for window 0x1, but didn't
receive it, i=1.
device.c:4359: Test failed: Got unexpected hr 0x88760869.
https://test.winehq.org/data/patterns.html#d3d9:device
Where 0x007e == WM_DISPLAYCHANGE.
The second failure is not always present but does not seem to happen without
the first one so they are probably related.
These failures:
* Happen on my Debian 11 + Intel + KDE box (fg-deb64)
* Don't seem to happen on my Debian 11 + QXL + fvwm + single monitor VM
* Happen on the TestBot's Debian 11 + QXL + fvwm + dual monitor VM
* Happen on the TestBot's Debian Testing + QXL + fvwm + dual monitor VM
(very rarely but two wow64 instance have been seen)
--
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=47407
Bug ID: 47407
Summary: Hard Truck 2: King of The Road (GOG version): movies
don't play
Product: Wine
Version: 4.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: t6zm3v62fkp7fe5(a)yandex.ru
Distribution: ---
Created attachment 64755
--> https://bugs.winehq.org/attachment.cgi?id=64755
Screenshot from intro movie
In Hard Truck 2: King of The Road (GOG version), movies don't play: e.g. intro
logos and movie (screenshot-from-intro-movie.png) and movies when you're
arrested or robbed by mafia.
Lubuntu 18.04.2, Wine 4.11 from official PPA.
--
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=53182
Bug ID: 53182
Summary: shell32:shelllink - A save(NULL, TRUE) fails randomly
in test_load_save() on Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
A save(NULL, TRUE) fails randomly in test_load_save() on Wine:
shelllink.c:775: Test failed: save(NULL, TRUE) failed (0x80070020)
https://test.winehq.org/data/patterns.html#shell32:shelllink
This is probably the same issue as bug 28290, the only difference being that it
does not happen at a point that leads to a NULL pointer access.
--
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=52948
Bug ID: 52948
Summary: gdi32:font - test_EnumFonts() fails on Arial Bold on
Windows in Russian
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
gdi32:font - test_EnumFonts() fails on Arial Bold on Windows in Russian:
font.c:5409: Test failed: font Arial Bold is not enumerated
font.c:5412: Test failed: expected FW_BOLD got 400
font.c:5419: Test failed: font Arial Bold Italic is not enumerated
font.c:5421: Test failed: expected Arial got Arial Bold
font.c:5422: Test failed: expected FW_BOLD got 400
https://test.winehq.org/data/patterns.html#gdi32:font
Maybe this can happen in other locales, but among those that are tested this
only happens with the Russian one (w10pro64-ru).
--
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.