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.