https://bugs.winehq.org/show_bug.cgi?id=54259
Bug ID: 54259
Summary: Firefox displays virus for wine-8.0-rc2.tar.xz
Product: WineHQ Bugzilla
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bugzilla-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: juergen(a)luers-net.de
CC: austinenglish(a)gmail.com
Distribution: ---
Downloaded at https://www.winehq.org/news/ from "The source is available now."
Firefox shows that the file contains a virus or malware.
Downloading from https://dl.winehq.org/wine/source/8.0/wine-8.0-rc2.tar.xz does
not display that message. Both files differ.
Firefox is version 108.0.1 (64-Bit) under Ubuntu 22.04 64bit.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=54667
Bug ID: 54667
Summary: Microsoft Office 365 installer no longer runs on 8.2+
Product: Wine
Version: 8.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: danielzgtg.opensource(a)gmail.com
Distribution: ---
Created attachment 74182
--> https://bugs.winehq.org/attachment.cgi?id=74182
logs
The Microsoft Office 365 installer was working on 8.1 but it's no longer
working on 8.2 or master (fbfa4a3aed432257931efb436b53fb891afc5fb5). It
silently exits, and only one or two times did a white window display for a
split second. A git bisect and git revert traced this to
0692d07f85f30ee5191a781b8b6f51006f2ae407.
I downloaded OfficeSetup.exe from https://portal.office.com/account/#installs
while logged into my uOttawa account. I'm building wine to try and develop a
fix to another bug in the actual program, and Ubuntu 7.0~repack-8 had the
installer working fine.
--
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=54552
Bug ID: 54552
Summary: DiRT 3 Complete Edition crashes on launch
Product: Wine
Version: 8.1
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: ir50_32
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Regression SHA1: 3dd09ed8f9ecf99439a372b6d0be076cef8aaef3
Distribution: ---
Created attachment 74096
--> https://bugs.winehq.org/attachment.cgi?id=74096
backtrace
04e8:err:module:DelayLoadFailureHook failed to delay load
winegstreamer.dll.winegstreamer_create_video_decoder
wine: Call from 7B0125F6 to unimplemented function
winegstreamer.dll.winegstreamer_create_video_decoder, aborting
wine: Unimplemented function
winegstreamer.dll.winegstreamer_create_video_decoder called at address 7B0125F6
(thread 04e8), starting debugger...
--
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=54395
Bug ID: 54395
Summary: Norgate Data Updater
(https://norgatedata.com/downloads.php) crashed
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: yubiv116(a)gmail.com
Distribution: ---
Created attachment 73960
--> https://bugs.winehq.org/attachment.cgi?id=73960
Log of the crash
Norgate Data Updater (https://norgatedata.com/downloads.php) crashed when
trying to run after installing.
Running Crossover for Linux.
Traceback.txt 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=54447
Bug ID: 54447
Summary: Brew for Wine 8.1
Product: Wine
Version: 8.1
Hardware: arm
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cupidchan(a)hotmail.com
First of all, I am new to Wine. So, please forgive me if I put this request
here wrongly but I just cannot find a better place to put in this request.
I am using a Mac Ventura and learn that I can use brew to install Wine.
(https://formulae.brew.sh/cask/wine-stable#default) However, the current
version for that approach is 7.0, even though Wine is not at 8.1. How can I get
the installation for 8.1? 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.
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=54605
Bug ID: 54605
Summary: The 32-bit dbghelp:dbghelp cannot run on Windows <= 10
1607 due to IsWow64Process2() call
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: dbghelp
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
The 32-bit dbghelp:dbghelp cannot run on Windows <= 10 1607 due to an
IsWow64Process2() call:
dbghelp.c:0: Tests skipped: missing entry point (details below)
| dbghelp_test.exe - Entry Point Not Found
| The procedure entry point IsWow64Process2 could not be located in the dynamic
link library kernel32.dll.
See https://test.winehq.org/data/patterns.html#dbghelp:dbghelp
This call was introduced in the commit below:
commit 291daf542d906b11320128ad4fd17fb99d8fff4b
Author: Eric Pouech <eric.pouech(a)gmail.com>
Date: Sat Feb 25 17:50:56 2023 +0100
dbghelp/tests: Fix tests for process count in wow64.
Introduce get_process_kind() to discriminate configurations.
Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com>
I believe this was to fix some Windows 11 failures. This means cases where this
API is missing were not having failures so a GetProcAddress()-based workaround
can probably be found.
--
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=54507
Bug ID: 54507
Summary: psapi:psapi_main - The 32-bit
test_EnumProcessModulesEx() gets many pcs-3232
failures due to partial copy errors on Windows 11
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: psapi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
psapi:psapi_main - The 32-bit test_EnumProcessModulesEx() gets many pcs-3232
failures due to partial copy errors on Windows 11:
psapi_main.c:225: Test failed: pcs-3232: 1: didn't succeed 299
psapi_main.c:226: Test failed: pcs-3232: 1: not a multiple of sizeof(HMODULE)
cbNeeded=1966900330
psapi_main.c:231: Test failed: pcs-3232: 1: GetModuleBaseName failed: 299
(0/128=DEADBEEF)
psapi_main.c:233: Test failed: pcs-3232: 1: GetModuleFileNameEx failed: 299
(0/128=DEADBEEF)
psapi_main.c:236: Test failed: pcs-3232: 1: GetModuleInformation failed: 299
psapi_main.c:237: Test failed: pcs-3232: 1: expected DEADBEEF, got 00000000
psapi_main.c:238: Test failed: pcs-3232: 1: image size was 0
... repeats of lines 231 - 238 ...
psapi_main.c:299: Test failed: pcs-3232: 1: got error 299
psapi_main.c:300: Test failed: pcs-3232: 1: expecting notepad.exe but got ?
psapi_main.c:302: Test failed: pcs-3232: 1: got error 299
psapi_main.c:303: Test failed: pcs-3232: 1: expecting
c:\windows\syswow64\notepad.exe but got ?
psapi_main.c:306: Test failed: pcs-3232: 1: got error 299
psapi_main.c:307: Test failed: pcs-3232: 1: expected DEADBEEF, got 00000000
psapi_main.c:308: Test failed: pcs-3232: 1: image size was 0
psapi_main.c:299: Test failed: pcs-3232: 0: got error 299
psapi_main.c:300: Test failed: pcs-3232: 0: expecting notepad.exe but got ?
psapi_main.c:302: Test failed: pcs-3232: 0: got error 299
psapi_main.c:303: Test failed: pcs-3232: 0: expecting
c:\windows\syswow64\notepad.exe but got ?
psapi_main.c:306: Test failed: pcs-3232: 0: got error 299
psapi_main.c:307: Test failed: pcs-3232: 0: expected DEADBEEF, got 00000000
psapi_main.c:308: Test failed: pcs-3232: 0: image size was 0
psapi_main.c:299: Test failed: pcs-3232: 3: got error 299
psapi_main.c:300: Test failed: pcs-3232: 3: expecting notepad.exe but got ?
psapi_main.c:302: Test failed: pcs-3232: 3: got error 299
psapi_main.c:303: Test failed: pcs-3232: 3: expecting
c:\windows\syswow64\notepad.exe but got ?
psapi_main.c:306: Test failed: pcs-3232: 3: got error 299
psapi_main.c:307: Test failed: pcs-3232: 3: expected DEADBEEF, got 00000000
psapi_main.c:308: Test failed: pcs-3232: 3: image size was 0
See https://test.winehq.org/data/patterns.html#psapi:psapi_main
Where 299 == ERROR_PARTIAL_COPY
These tests and failures were introduced by the commit below:
commit 84a9a1c8fbc1e8ccc9c34cf0db375813b3ac2955
Author: Eric Pouech <eric.pouech(a)gmail.com>
AuthorDate: Mon Jan 30 13:45:46 2023 +0100
psapi: Add tests for EnumProcessModulesEx().
Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com>
See also bug 54504 which had partial copy errors before these tests were
introduced, and bug 54506 for 64-bit specific failures that were also
introduced by this commit.
--
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=54008
Bug ID: 54008
Summary: d3d9:device sometimes fails to create a D3D object in
Wine, crashes
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
d3d9:device sometimes fails to create a D3D object on the TestBot VMs, crashes.
The failure and ensuing crash can happen in many locations:
test_get_rt():
device.c:4821: Test failed: Received unexpected WM_SIZE message.
device.c:3016: Test failed: Failed to create a D3D object.
Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit
code (0x000000004154d5).
test_multi_adapter():
device.c:14264: Test failed: Failed to create a D3D object.
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code
(0x00459a93).
test_cursor_pos():
device.c:5241: Test failed: Failed to create a D3D object.
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code
(0x0041816a).
See https://test.winehq.org/data/patterns.html#d3d9:device
This failure can probably happen anywhere in the test.
--
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=54621
Bug ID: 54621
Summary: Wine 8.3 64-bit is missing in the Debian bookworm repo
Product: Wine
Version: 8.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: shtetldik(a)gmail.com
Distribution: ---
For some reason recent build of Wine 8.3 is missing 64-bit version in the
Debian repo (for bookworm):
https://dl.winehq.org/wine-builds/debian/dists/bookworm/main/binary-amd64/
Note how wine-devel_8.3~bookworm-1_amd64.deb is there, but
wine-devel-amd64_8.3~bookworm-1_amd64.deb is not.
--
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=54593
Bug ID: 54593
Summary: gdi32:dc - The SetDeviceGammaRamp() tests fails on
Windows 10 1909
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:dc - The SetDeviceGammaRamp() fails on Windows 10 1909:
dc.c:1271: Test failed: SetDeviceGammaRamp succeeded
dc.c:1276: Test failed: SetDeviceGammaRamp succeeded
dc.c:1288: Test failed: SetDeviceGammaRamp succeeded
See https://test.winehq.org/data/patterns.html#gdi32:dc
The tests tries to set 3 types of invalid gamma ramps and expects Windows to
reject them. These failures are 100% reproducible even when running the test on
its own (so the failures are not caused by interference from another test).
Up until Windows 10 1809 all the tests are skipped:
dc.c:1262: Tests skipped: SetDeviceGammaRamp failed, skipping tests
And on Windows 10 2004+ the tests succeed. So it looks like 1909 just did not
perform all the gamma ramp validation checks.
Except that on 2022-07-12 and 2022-11-11, the test had the exact same failures
(same lines too) on w1064-tsign which is Windows 10 21H2.
--
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=54298
Bug ID: 54298
Summary: d3d12:d3d12 - test_desktop_window() fails on Windows
10 1709
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
d3d12:d3d12 - test_desktop_window() fails on Windows 10 1709:
d3d12.c:1412: Test failed: Got unexpected hr 0x8007000e.
See https://test.winehq.org/data/patterns.html#d3d12:d3d12
Where 0x8007000e == E_OUTOFMEMORY.
* On w1064v1507 and w1064v1607 this test is skipped because init_test_context()
fails to create a device.
* On w1064v1809 and greater this specific test just succeeds (and another fails
instead).
* So w1064v1709 supports just enough of d3d12 to run the test, but not enough
to succeed.
Maybe just add a broken()?
https://gitlab.winehq.org/wine/wine/-/merge_requests/1961
--
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=54052
Bug ID: 54052
Summary: winhttp:notification times out randomly in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: winhttp
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
winhttp:notification times out randomly in Wine.
First, on 2022-11-24 Paul Gofman got a series of patches in that probably fixed
a bunch of these random timeouts (the situation on fg-deb64 and fgtb-debian11
seems better for one).
However the following merge requests got timeouts after the patches went in:
* MR!1553 on 2022-11-26
...
notification.c:117: Test failed: 892: expected status 0x20000 got 0x200000
winhttp:notification:0b98 done (258) in 120s 1148B
* MR!1557 on 2022-11-27
...
notification.c:117: Test failed: 988: expected status 0x80000 got 0x200000
winhttp:notification:06d0 done (258) in 120s 1148B
* MR!1560 on 2022-11-27
...
notification.c:1184: Test marked todo: got 3
winhttp:notification:052c done (258) in 120s 1118B
Where:
0x20000 == WINHTTP_CALLBACK_STATUS_HEADERS_AVAILABLE
0x80000 == WINHTTP_CALLBACK_STATUS_READ_COMPLETE
0x200000 == WINHTTP_CALLBACK_STATUS_REQUEST_ERROR
So there may still be some issue left.
--
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=53975
Bug ID: 53975
Summary: d3drm:d3drm sometimes fails to create an immediate
mode device in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
d3drm:d3drm sometimes fails to create an immediate mode device in Wine:
d3drm.c:5843: Test failed: Cannot create IM device, skipping tests.
This can happen in either test_create_device_from_d3d2() or
test_create_device_from_d3d3() and always comes with the following winediag
message repeated 3 times in the Wine log:
063c:err:winediag:d3d_device_create The application wants to create a Direct3D
device, but the current DirectDrawRenderer does not support this.
See https://test.winehq.org/data/patterns.html#d3drm:d3drm
So far this has only been seen on debian11 and debiant so it may be related to
their dual-screen configuration. Also this failure first happened on 2022-11-07
and there are 4 known instances so far (2 in the nightly runs and 2 TestBot job
false positives). So it is probably caused by some recent Wine change.
--
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=54491
Bug ID: 54491
Summary: regedit/regproc.c - export_key() is unable to return
TRUE
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: programs
Assignee: wine-bugs(a)winehq.org
Reporter: gonzomdx(a)gmail.com
Distribution: ---
export_key() function should return either TRUE if succeeded or FALSE if
failed.
Values are returned in lines 1459 and 1463 (hardcoded FALSE) as well as line
1471 (BOOL ret).
Due to the fact that ret get its value returned from the function
export_registry_data() (line 1466) which EVER returns an int of value 0, there
is no possibility that export_key() succeeds.
The easiest solution would be to simply return TRUE instead of ret.
The most elegant solution would be to let export_registry_data() sane data.
--
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=54168
Bug ID: 54168
Summary: kernel32:console - test_wait() sometimes fails on
Windows 8+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
kernel32:console - test_wait() sometimes fails on Windows 8+:
console.c:1198: Test failed: WaitForSingleObject returned 0
console.c:1200: Test failed: WaitForSingleObject returned 0
console.c:1202: Test failed: WaitForSingleObject returned 0
console.c:1204: Test failed: WaitForSingleObject returned 0
console.c:1206: Test failed: WaitForSingleObject returned 0
console.c:1208: Test failed: NtWaitForSingleObject returned 0
console.c:1211: Test failed: NtWaitForSingleObject returned 0
See https://test.winehq.org/data/patterns.html#kernel32:console
This happens a bit less that twice per month.
--
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.