http://bugs.winehq.org/show_bug.cgi?id=18775
Summary: WINE can load DLL with full path second time
Product: Wine
Version: 1.1.22
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: amorozov(a)etersoft.ru
Windows LoadLibrary does not load dll second time if full path is specified.
Attached test print "OK" on WinXP and "FAIL" on WINE.
--
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=53249
Bug ID: 53249
Summary: ole32:compobj - test_CoGetPSClsid() sometimes fails
due to REGDB_E_IIDNOTREG on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: ole32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ole32:compobj - test_CoGetPSClsid() sometimes fails due to REGDB_E_IIDNOTREG on
Windows:
compobj.c:1382: Test failed: got 0x80040155
compobj.c:1383: Test failed: got clsid {00000000-0000-0000-0000-000000000000}
compobj.c:1387: Test failed: got 0x80040155
compobj.c:1388: Test failed: got clsid {00000000-0000-0000-0000-000000000000}
compobj.c:1398: Test failed: got clsid {52222222-1234-1234-1234-56789abcdef0}
compobj.c:1402: Test failed: Failed to get PS CLSID, hr 0x80040155.
compobj.c:1403: Test failed: Unexpected CLSID
{00000000-0000-0000-0000-000000000000}.
https://test.winehq.org/data/patterns.html#ole32:compobj
These failures happen on Windows 7 to Windows 10 1709.
On Windows 8 to Windows 10 1709 there is sometimes an additional error in
test_CoRegisterClassObject():
compobj.c:1670: Test failed: Unexpected hr 0.
This failure looks like it should be independent but never happens without the
previous ones.
--
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=14771
Summary: Firefox 3 complains it is not the default browser on
every startup
Product: Wine
Version: 1.1.2
Platform: PC
URL: http://www.mozilla.com/en-US/firefox/all.html
OS/Version: Linux
Status: UNCONFIRMED
Keywords: download
Severity: trivial
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: thestig(a)google.com
Everytime I start Firefox 3, it complains it's not the default browser. I hit
Yes when it asks me to set is as the default browser, but on the next start up,
it complains again.
--
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=39644
Bug ID: 39644
Summary: WineTest.exe should detect left-over UAC prompts
Product: Wine
Version: 1.8-rc1
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: testcases
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
There was a problem where the cmd.exe:batch would try to run regedit from an
account without elevated privileges. This caused Windows to pop up the UAC
dialog, causing the test to stall. Timeout would happen, WineTest would kill
the cmd.exe:batch process but doing so, and even extending it to all process
tree, does not close the UAC because it's under the control of another Windows
element. So WineTest would run the following tests with the UAC dialog still up
which caused them to fail as they could not put their windows in the
foreground.
The cmd.exe:batch bug has been fixed. However it could make sense for WineTest
to do more to handle this situation more nicely:
* If possible it could dismiss the UAC dialog (not click 'Yes' obviously, just
deny the request).
* It could detect the UAC dialog is up and wait. It seems the UAC dialog goes
away on its own after about two minutes.
* If we cannot detect if an UAC dialog is up we could systematically wait for
an extra 2 minutes after a timeout, just in case.
* Even more basic, we could increase our test timeout so it's longer than the
UAC timeout, in the hope an UAC would go away before we time out.
* Even though it does not solve the UAC issue it could still make sense to
kill the whole subprocess tree, just to be sure one of them is not going to
break the following tests.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53206
Bug ID: 53206
Summary: user32:win - test_topmost() has some rare failures in
Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
user32:win - test_topmost() has some rare failures in Wine:
win.c:11770: Test succeeded inside todo block: child should be topmost
win.c:11772: Test marked todo: child2 should be topmost
win.c:11773: Test failed: grandchild should be topmost
win.c:11781: Test failed: child should NOT be topmost
win.c:11784: Test succeeded inside todo block: grandchild should NOT be topmost
win.c:11787: Test failed: 008E0096: expected NOT topmost
win.c:11606: Test succeeded inside todo block: 5: hwnd 01AA006E is still
topmost
https://test.winehq.org/data/patterns.html#user32:win
These failure don't seem to depend on the locale and happen on the TestBot VMs
which run fvwm. They did not happen on my box under KDE but they are pretty
rare (~1% failure rate) so there may not be enough data to draw conclusions.
They also happen outside of WineTest and have caused false positives.
--
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=9404
Summary: cannot select TWAIN source in irfanview
Product: Wine
Version: 0.9.43.
Platform: PC
URL: http://www.irfanview.com/
OS/Version: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: wine-misc
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: thestig(a)google.com
In Irfanview, users should be able to select the TWAIN source via file ->
select TWAIN source. Clicking that menu item should bring up a dialog box to
let users pick which scanner to use. In Wine, no dialog box ever comes up, so
the program uses the first TWAIN source it finds, which is the gphoto2 driver.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=35319
Bug ID: 35319
Summary: Wolverine: install game crash
Product: Wine
Version: 1.7.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: legluondunet(a)free.fr
Classification: Unclassified
Created attachment 47105
--> http://bugs.winehq.org/attachment.cgi?id=47105
Wolverine install crash log
Hello,
when installing Wolverine game, the install window suddenly disappear, without
any error message. Fortunately it seems the crash happened after install all
files.
I joined you the wine terminal log from start to the end of the install
process.
--
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=33807
Bug #: 33807
Summary: Objects disappear at certain camera angles in Ground
Control
Product: Wine
Version: 1.6-rc2
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: tdsbug(a)gmail.com
Classification: Unclassified
Created attachment 44813
--> http://bugs.winehq.org/attachment.cgi?id=44813
Terminal output without WINEDEBUG
Game: Ground Control, version 1.0.0.5, crack for version 1.0.0.7 (versions have
no effect on this issue)
***Problem***:
Some objects become invisible at random times. When this happens, shadows still
work properly. Often only certain parts of an object become invisible, like
only chassis of tank. This doesn't happen with visual effects, like lights and
fire. Camera angle has some limited effect on the moment when this happens.
I am running the game in hardware rendering mode. (Game also has software
rendering mode, but only for 640x480 resolution. Some similar glitches appear
in software mode too)
According to appdb, this has been happening forever and is not a regression.
The game uses directx 7. Logs attached.
***Additional details***:
During installation, the game asked to install directx 7.0a, which I clicked
no. Also tried clicking yes, but it has no effect. No dll overrides, winetricks
or anything was used.
The game also suffers from input slowdown at certain times, but it's probably a
different bug.
Also, this game is a free download now, so you can try yourself if you wish.
--
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=52389
Bug ID: 52389
Summary: OpenCL - regression. OpenCL demo does not work
Product: Wine
Version: 6.23
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cybermax(a)dexter.no
Distribution: ---
Created attachment 71614
--> https://bugs.winehq.org/attachment.cgi?id=71614
Log from running GPU Caps Viewer
OpenCL does not seem to initialize after
f91c009786fa09723976dce0233592f69df5cead.
Tested with GPU Caps Viewer (From Geeks3D) - the OpenCL "Info" tab does not
show any devices. The CL Platform is listed.
None of the CL Demos work.
Graphics adapter: nVidia RTX2070
Wine-dev+GIT@76c9fc8a761c9faff72f97ab508a1afcb28eeb12
WINEDEBUG=+opencl
Log 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=50469
Bug ID: 50469
Summary: The Void crashes with builtin d3dx9_36 (needs
D3DXDisassembleShader implementation)
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d-util
Assignee: wine-bugs(a)winehq.org
Reporter: titan.costa(a)gmail.com
Distribution: ---
The game version is from GOG.
After making D3DXFillCubeTextureTX() return S_OK (bug #48528), the game crashes
after D3DXDisassembleShader call as it does not check the returned value.
--
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=38905
Bug ID: 38905
Summary: In dlls/mshtml/tests, "make test" failed when some
Chinese fonts are used
Product: Wine
Version: 1.7.47
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: litimetal(a)gmail.com
Distribution: ---
Created attachment 51840
--> https://bugs.winehq.org/attachment.cgi?id=51840
backtrace.txt
0. Copy some Chinese fonts from C:\windows\fonts in Windows XP to ~/.fonts[1]
1. fc-cache -fv
2. run "make test" in dlls/mshtml/tests
3. crashed
[1]: The fonts I copied to Linux:
文鼎CS长宋体繁.TTF 文鼎粗行楷简.TTF 文鼎粗圆简.TTF 文鼎琥珀繁.TTF 文鼎特粗宋简.TTF 文鼎小标宋简.TTF
文鼎报宋简.TTF 文鼎粗黑繁.TTF 文鼎大标宋简.TTF 文鼎书宋繁.TTF 文鼎习字体.TTF 文鼎新艺体简.TTF
文鼎齿轮体.TTF 文鼎粗魏碑简.TTF 文鼎古印体繁.TTF 文鼎特粗黑简.TTF 文鼎细仿宋繁.TTF
I don't know how to determine which font caused this problem
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53225
Bug ID: 53225
Summary: gameux:gamestatistics has a rare pair of failures on
Windows 8
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: gameux
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
gameux:gamestatistics has a rare pair of failures on Windows 8:
gamestatistics.c:59: Test failed: got 0x80004005
gamestatistics.c:201: statistics file path:
L"C:\\Users\\winetest\\AppData\\Local\\Microsoft\\Windows\\GameExplorer\\GameStatistics\\{17A6558E-60BE-4078-B66F-9C3ADA2A32E6}\\{17A6558E-60BE-4078-B66F-9C3ADA2A32E6}.gamestats"
gamestatistics.c:75: Test failed: got 0x80070057
https://test.winehq.org/data/patterns.html#gameux:gamestatistics
Only one known instance on 2022-06-20 on w8adm 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=53239
Bug ID: 53239
Summary: dpnet:client - test_enum_hosts() and
test_enum_hosts_peer() fail randomly on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: directx-dplay
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
dpnet:client - test_enum_hosts() and test_enum_hosts_peer() fail randomly on
Windows:
client.c:323: Test failed: got 0x80004005
or
client.c:753: Test failed: got 0x80004005
https://test.winehq.org/data/patterns.html#dpnet:client
In both cases the API that fails is IDirectPlay8Client_CancelAsyncOperation()
so this looks like a race condition.
The failure rate (~4.4%) is low enough to cause false positives. Strangely
enough all but one of the failures happened on w7u, w7pro64 and w10pro64
(21H1). That means none of the failures happened on Windows 10 1507 to 2009!
--
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=38673
Bug ID: 38673
Summary: valgrind shows uninitialized memory in
dlls/kernel32/sync.c:ConnectNamedPipe()
Product: Wine
Version: 1.7.42
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase, valgrind
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: Fedora
../../../tools/runtest -q -P wine -T ../../.. -M hlink.dll -p hlink_test.exe.so
hlink && touch hlink.ok
==14126== Thread 3:
==14126== Syscall param writev(vector[...]) points to uninitialised byte(s)
==14126== at 0x4F7A0F4B: ??? (in /usr/lib/libc-2.21.so)
==14126== by 0x7BC7A9C5: send_request (server.c:228)
==14126== by 0x7BC7AB52: wine_server_call (server.c:309)
==14126== by 0x7BC7B8CD: server_select (server.c:607)
==14126== by 0x7BC85426: NtWaitForMultipleObjects (sync.c:976)
==14126== by 0x7BC85471: NtWaitForSingleObject (sync.c:985)
==14126== by 0x7BC45DFF: server_ioctl_file (file.c:1539)
==14126== by 0x7BC46565: NtFsControlFile (file.c:1786)
==14126== by 0x7B87406B: ConnectNamedPipe (sync.c:1615)
==14126== by 0x49255A5: listen_thread (rpc_transport.c:132)
==14126== by 0x7BC81BB7: ??? (signal_i386.c:2682)
==14126== by 0x7BC81BFE: call_thread_func (signal_i386.c:2741)
==14126== by 0x7BC81B95: ??? (signal_i386.c:2682)
==14126== by 0x7BC88D78: start_thread (thread.c:443)
==14126== by 0x4F88F37F: start_thread (in /usr/lib/libpthread-2.21.so)
==14126== by 0x4F7ABD4D: clone (in /usr/lib/libc-2.21.so)
==14126== Address 0x4cee5c4 is on thread 1's stack
==14126== Uninitialised value was created by a stack allocation
==14126== at 0x7B873FA5: ConnectNamedPipe (sync.c:1601)
==14126==
also shows in ieframe/webbrowser, kernel32/pipe,
--
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=48538
Bug ID: 48538
Summary: Cricut design space: crashes on installing
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: vo1xa.brad(a)gmail.com
Distribution: ---
Created attachment 66346
--> https://bugs.winehq.org/attachment.cgi?id=66346
output of error log
Cricut design space fails to install encounters major error
--
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=50596
Bug ID: 50596
Summary: Sacred 2 crashes with D3DXCompileShader (d3dx9_36
builtin)
Product: Wine
Version: 6.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d-util
Assignee: wine-bugs(a)winehq.org
Reporter: berillions(a)gmail.com
Distribution: ---
Created attachment 69281
--> https://bugs.winehq.org/attachment.cgi?id=69281
+d3dx log
Hi,
The game crashes at launch with this trace before crash :
------
0024:trace:d3dx:D3DXCompileShader data "#include
\"ui_include.shader\"\n\n\nstruct pixdata {\n\tfloat4 hposition :
POSITION;\n\tfloat4 texcoord0 : TEXCOORD0;\n\tfloat4 texcoord1 :
TEXCOORD1;\n\tfloat4 texcoord2 : TEXCOORD2;\n\tfloat4 light_dir :
TEXCOORD3;\n\tfloat4 color : COLOR;\n};\n\n\nstruct fragout {\n\tfloat4 col
"..., length 1410, defines 00000000, include 0031E318, function "mainVS",
profile "vs_1_1", flags 0, shader 0031E330, error_msgs 0031E310, constant_table
0031E308.
------
Set d3dx9_36 to native fix the issue.
I attach +d3dx log
--
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=45884
Bug ID: 45884
Summary: Just Cause 2 crashed at start
Product: Wine
Version: 3.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: legluondunet(a)free.fr
Distribution: ---
Created attachment 62390
--> https://bugs.winehq.org/attachment.cgi?id=62390
Just Cause 2 crashed at start terminal log
Hello,
Just Cause II crashed at start, you can reproduce this crash at each launch.
I joined you the log terminal.
Thank you for your help.
LGDN.
--
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=40569
Bug ID: 40569
Summary: application crashes with exception in
ddraw_allocate_handle (win98)
Product: Wine
Version: 1.9.9
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: o.dierick(a)piezo-forte.be
Distribution: ---
Created attachment 54407
--> https://bugs.winehq.org/attachment.cgi?id=54407
Terminal output (wine 1.9.9)
I get a page fault in 32-bit code when starting a game in TOCA Touring Car
Championship. This is an old game that requires windows version <= win98.
The demo also has the bug.
---begin quote---
...
wine: Unhandled page fault on read access to 0x00000110 at address 0x7e7fcf1d
(thread 0028), starting debugger...
Unhandled exception: page fault on read access to 0x00000110 in 32-bit code
(0x7e7fcf1d).
...
Backtrace:
=>0 0x7e7fcf1d ddraw_allocate_handle+0x1d(t=0x10c, object=0x15f960,
type=DDRAW_HANDLE_MATERIAL)
[/home/olivier/Projets/wine-builds/1.9.9_x86/dlls/ddraw/../../../wine-git/dlls/ddraw/main.c:118]
in ddraw (0x0033f478)
...
---end quote---
This is with git wine 1.9.9-35-gbd2999d and no patch.
--
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=51481
Bug ID: 51481
Summary: Why is the Epson printer printing blank pages?
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: baroncorrz(a)gmail.com
Distribution: ---
Epson printer printing blank pages because there must be some problem related
to the cartridge ink or the nozzle. The cartridge ink must have been depleted.
You need to check the level of ink by comparing the ink level with the marker
on the ink tank. If the ink level is low, then it means that you need to put in
a new cartridge. If you have an ink tank with a low ink level, then fill the
ink tank with the ink. The problem can also be due to the clogging of the
nozzle. You need to clean the nozzle if this happens. One of the best ways to
prevent this is by giving fewer jobs to the printer.
https://www.epsonprintersupportpro.us/blog/printer-printing-blank-pages/
--
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=21158
Summary: Hitman: Contracts ignores mouse press events
Product: Wine
Version: 1.1.35
Platform: x86
URL: http://www.gamershell.com/download_5663.shtml
OS/Version: Linux
Status: NEW
Keywords: download, regression
Severity: minor
Priority: P2
Component: directx-dinput
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: arethusa26(a)gmail.com
CC: vitaliy(a)kievinfo.com
With wine-1.1.35-180-g20a50f3, after launching Hitman: Contracts, mouse press
events at the main menu are ignored by the game. Since a user reported that the
game worked normally in wine-1.1.9, a regression test was performed, which
indicated:
3743a1a7ca170c765cd779c61b9e362c5b1c5203 is first bad commit
commit 3743a1a7ca170c765cd779c61b9e362c5b1c5203
Author: Vitaliy Margolen <wine-patches(a)kievinfo.com>
Date: Sun Feb 1 13:11:46 2009 -0700
dinput: Consume mouse & keyboard events in exclusive mode.
:040000 040000 6ae6b43b3c100af38ed4f27384470dc4d2595bc1
700b35b9bc8fd27239ee8faaed8ca1c10cfc31d4 M dlls
Wine built prior to the indicated commit allows mouse input to work normally.
Interestingly, doing graphical mode changes (via keyboard input) makes mouse
input work again. The AppDB also suggests adding the strings:
UseDirectInputMouse
UseDirectInputKeyboard
to the HitmanContracts.ini configuration file to have mouse input work. The
only visible output under wine-1.1.35-180-g20a50f3 is:
fixme:dinput:SysMouseAImpl_Acquire Clipping cursor to (0,0)-(1280,1024)
fixme:win:EnumDisplayDevicesW ((null),0,0x32eb58,0x00000000), stub!
fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x253b060,0x253afa8): stub
fixme:dsound:DllCanUnloadNow (void): stub
fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x253b060,0x253afa8): stub
(Z:\code\hitman2\gui\MainMenu.cpp:554)Hitman Contracts build 171 (Apr 26 2004
14:42:27)
fixme:dsound:DllCanUnloadNow (void): stub
--
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=50129
Bug ID: 50129
Summary: Calibre-portable error initializing the bypy frozen
importer
Product: Wine
Version: 5.0.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bilbiliblus(a)gmail.com
Distribution: ---
When I try to run Calibre-portable.exe y have this message:
There was an error initializing the bypy frozen importer:
<class 'MemoryError'>:
Traceback (most recent call last):
File bypy-importer.py, line 250, in <module>
File bypy-importer.py, line 195, in __init__
It only happens since Calibre changed to version 5 and on.
This very morning I've tried with Calibre 5.3
Thank you
--
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=53205
Bug ID: 53205
Summary: user32:input - test_rawinput() has a rare pair of
failures in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
user32:input - test_rawinput() has a rare pair of failures in Wine:
input.c:2784: Test failed: 15: expected WM_INPUT message
input.c:2787: Test failed: 15: expected RIM_INPUT message
https://test.winehq.org/data/patterns.html#user32:input
These failures don't seem to depend on the locale or bitness. But there are
only two known instances of these failures in WineTest making them likely to
cause false positives (~0.5% failure rate).
--
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=52461
Bug ID: 52461
Summary: The Legend of Heroes: Trails of Cold Steel III usually
hangs on exit
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: patch
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: z.figura12(a)gmail.com
Distribution: ---
Created attachment 71749
--> https://bugs.winehq.org/attachment.cgi?id=71749
patch mitigating the race
To reproduce it's sufficient to install the game from Steam, get into the main
menu, and select the "exit" option (page down with the S key then press Enter).
Closing the window also works. The hang doesn't happen every time but does
happen most times I tested.
This is an application bug. There are two threads—a main thread and a worker
thread. The main thread closes the handle to a mutex, goes off and does some
other things, and then tries to wait on the mutex handle again (with a timeout
of INFINITE). The worker thread basically does a timed wait, in a loop, on a
set of handles, except that instead of passing a timeout to
WaitForMultipleObjects(), it repeatedly creates a non-periodic auto-reset timer
object, sets it for 1 ms, and adds it to the wait array, and then closes the
handle.
Because of the way handles are allocated in Wine (i.e. "lowest slot first"),
and because of the specific pattern of handle usage of the program, what
usually happens is that when the mutex handle is closed, the value is reused
for a timer handle in the worker thread. While the worker thread is sleeping on
the timer, the main thread also waits on it, and when the timer fires, it only
wakes up the worker thread (which is almost always first in the queue). Closing
the handle of a waitable object in Windows doesn't interrupt other waits in
progress, and because the timer is non-periodic and auto-reset, the main thread
ends up waiting forever.
It turns out that Windows doesn't allocate handles like this. Rather, it seems
to use a free list, much like we use in other places in Wine: testing shows
that handles are always allocated in the reverse order that they are freed,
including across multiple threads, and regardless of how many handles were just
allocated.
Changing Wine to use a free list like this actually does mitigate the problem.
Because the worker thread closes its timer handle and then immediately creates
a new one, it will almost always get back the same handle value. The main
thread will most likely close its mutex handle while the worker thread is still
sleeping, with the effect that the mutex handle won't be reallocated and the
subsequent wait will return STATUS_INVALID_HANDLE.
In theory the potential for the race is still there, however; it's still
possible for the mutex handle to be closed after the timer handle is closed but
before a new timer is created, in which case the mutex handle value will be
reused for the timer value as it is currently. In practice I'm not sure if this
happens more than a negligible fraction of the time. I certainly couldn't
reproduce it after 6 or so tries, although that's not very many. Note that
there are also reports of it hanging on Windows [1]...
[1] https://steamcommunity.com/app/991270/discussions/0/2145343189632898904/
--
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=51313
Bug ID: 51313
Summary: gdi32:driver sometimes fails with a
STATUS_GRAPHICS_PRESENT_OCCLUDED error
Product: Wine
Version: 6.10
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:driver sometimes gets one or two failures like these:
https://test.winehq.org/data/patterns.html#gdi32:driver
driver.c:649: Test failed: Got unexpected return code 0xc01e0006.
driver.c:689: Test failed: Got unexpected return code 0xc01e0006.
0xc01e0006 is STATUS_GRAPHICS_PRESENT_OCCLUDED. This has happened before but
the reason for this error was not identified:
https://www.winehq.org/pipermail/wine-devel/2019-July/148494.html
I initially suspected a leftover window from a previous test, specifically an
Internet Explorer first-run dialog. However the screenshots in the TestBot jobs
show that this happens even when there is no such dialog (or at least the
dialog is gone by the time the tests complete).
The failures always happen on the same two lines despite the occlusion status
being checked in other places. Also both failures happen right after minimizing
the windows. So it seems likely there is a race condition, either in the test
or in the underlying API (if so it spans Windows 10 1607 to 2009).
--
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=51040
Bug ID: 51040
Summary: msi:package fails on Windows 10 if privileges not high
enough
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: msi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
The following failures only happen if the test is run on a recent enough
Windows (i.e. Windows 10) in a user account with too few privileges.
package.c:5079: Test failed: Expected "keydata", got ""
package.c:5084: Test failed: Expected "field2", got ""
package.c:5089: Test failed: Expected "keydata,field2", got ""
package.c:5096: Test failed: Expected
"C:\Users\winetest\AppData\Local\Temp\FileName1", got ""
package.c:5107: Test failed: Expected "C:\Users\winetest\AppData\Local\Temp\",
got ""
package.c:5113: Test failed: Expected "C:\Users\winetest\AppData\Local\Temp\",
got ""
package.c:5123: Test failed: Expected "C:\Users\winetest\AppData\Local\", got
""
package.c:5136: Test failed: Expected
"C:\Users\winetest\AppData\Local\Temp\FileName2.dll", got ""
package.c:5147: Test failed: Expected
"C:\Users\winetest\AppData\Local\Temp\FileName4.dll", got ""
package.c:5651: Test failed: Expected , got winetest
In particular one can notice this bug on the TestBot's w1064_adm VM.
Note however that these tests seem to be run and succeed on wvistaadm and
w7u_adm.
See:
https://test.winehq.org/data/tests/msi:package.html
--
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.