https://bugs.winehq.org/show_bug.cgi?id=55434
Bug ID: 55434
Summary: socialclubhelper.exe serious problem in wine unable to
run GTA v via steam but worked for past 4 weeks
Product: Wine
Version: unspecified
Hardware: arm
OS: Windows
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: winedbg
Assignee: wine-bugs(a)winehq.org
Reporter: lynxmyster(a)gmail.com
Created attachment 74995
--> https://bugs.winehq.org/attachment.cgi?id=74995
error log report
/Users/lyntonhartill/Downloads/backtrace.txt
--
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=55420
Bug ID: 55420
Summary: The Legend of Sisyphus by Andromeda Software
Development fails to run
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: arabek+wine(a)gmail.com
Distribution: ---
Created attachment 74980
--> https://bugs.winehq.org/attachment.cgi?id=74980
backtrace.txt
Source:
https://files.scene.org/view/parties/2023/assembly_summer23/demo/asd-theleg…
(free download)
Problem: ubuntu-23.04, clean prefix, wine-staging-8.13 installed from winehq
repo - demo fails to run.
Attached is the backtrace.txt generated.
--
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=55441
Bug ID: 55441
Summary: after update rawinput patch scroll wheel is not
working on some game.
Product: Wine-staging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: l12436(a)yahoo.com.tw
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
After latest rawinput update. I found the code x11drv_xinput_disable() is
added, seems due to this code. the scroll wheel is no longer working.
I fallback to 8.13 it working again.
--
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=55440
Bug ID: 55440
Summary: StarCraft 2: can no longer input Chinese via fcitx5
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: allfoxwy(a)gmail.com
Distribution: ---
Greetings. I'm switching from Wine-staging 8.5 to Wine-staging 8.13. Then I see
that in StarCraft 2 I can no longer input Chinese into the game via fcitx 5.
In the game, I could use key shortcut to call up fcitx 5 into Chinese mode. I
press some key then I could see the word candidates in the top left corner of
the screen (not following the cursor). However if I select one of them, nothing
goes into the game's textbox.
I also tried wine notepad, I could input Chinese in it.
The Battle.net client also work.
But the actual StarCraft 2 game do not accept my input.
StarCraft 2 version 5.0.11.90136
fcitx 5 from Debian version 5.0.23-2
Wine-staging-amd64 8.13 from
https://github.com/Kron4ek/Wine-Builds/releases/tag/8.13
In fact, it's not only StarCraft 2, Diablo 4 also have such symptom. However
StarCraft 2 is a free game so it's easier to get and debug:
https://starcraft2.blizzard.com
And I read the Wine What's New and see that there are some work going into IME
recently. There is a FIXED bug report:
https://bugs.winehq.org/show_bug.cgi?id=54991 It says Wine 8.8 was working, so
I tried it, and yes in Wine 8.8 I could input in StarCraft 2 either. However
the supposed fix which was landed in Wine 8.10 did NOT fix the problem in
StarCraft 2.
I tried to get a console log. However this game need Battle.net client to
bootstrap up. If I run wine "Battle.net Launcher.exe" & > sc2log.txt" the
resulting file is empty.
Any help is appreciated.
--
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=54664
Bug ID: 54664
Summary: ZeroMQ 4.3.4#6 (from vcpkg) hangs in wine on macOS
Catalina
Product: Wine
Version: 8.3
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winsock
Assignee: wine-bugs(a)winehq.org
Reporter: steven.schumacher(a)dtn.com
Created attachment 74179
--> https://bugs.winehq.org/attachment.cgi?id=74179
Example app with source and results
Attached is a sample ZMQ pub/sub app including source (and project files but
they might need tweaking) code built against zeromq4.0.5 as a static lib vs
zeromq4.3.4#6 as a dll from vcpkg (at the time of submission, this is the
current version).
Unfortunately I've had issue building newer versions of zmq from source and zmq
no longer maintains windows builds ever since MS took over with vcpkg.
The build environment is VS 2019 on windows 10 (both fully updated).
Both versions of the app run the same on windows. On macOS Catalina (not sure
about earlier or later...my macOS resources are slim) under wine (both
Crossover 22.0.1 and bare wine 8.3), only the version usign zmq4.0.5 works with
the 4.3.4 version of zmq hangs as soon as zmq is initialized.
Text files with output for both on both OS is also included.
--
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=55438
Bug ID: 55438
Summary: Some D3D10 applications crashes on NVIDIA SM4 GPUs
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Windows
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: svyatpro(a)gmail.com
Created attachment 74998
--> https://bugs.winehq.org/attachment.cgi?id=74998
log for d3d10featuredemo.exe
For example NVIDIA DX10FeatureDemo crashes.
047c:err:d3d_shader:shader_glsl_load_sampler_handles No uniform location at 0,
ps_sampler0
https://developer.download.nvidia.com/SDK/10/Samples/DX10FeatureDemo.zip
--
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=50206
Bug ID: 50206
Summary: Cinebench R23 fails to start (needs dcomp.dll
implementation?)
Product: Wine
Version: 5.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: aidas957(a)gmail.com
Distribution: ---
Created attachment 68717
--> https://bugs.winehq.org/attachment.cgi?id=68717
Cinebench R23 Windows 10 Wine log
As I've said in the title, CInebench R23 fails to start probably because of
missing dcomp.dll which is needed by one of the app's important libraries and
thus the app spits out a bunch of warnings and then closes (with both Windows 7
and Windows 10 versions set in Wine)
I've tried to copy a 64-bit dcomp.dll from a Windows 10 installation, but there
are even more errors of libraries missing (and I can't locate them all)
I'm also using wine-staging. but I doubt that's going to affect anything in
this case
Log with Windows 10 version 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=50459
Bug ID: 50459
Summary: Unimplemented function
dcomp.dll.DCompositionCreateDevice called in 64-bit
code (Studio One 5)
Product: Wine
Version: 6.0-rc5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: moseskim84(a)gmail.com
Distribution: ---
Created attachment 69083
--> https://bugs.winehq.org/attachment.cgi?id=69083
Winedbg log file
I'm running Ubuntu 20.10, Wine-6.0-rc5 and have installed Studio One 5
Professional (music production program) into it's own prefix. The program does
not open at all and crashes when I run it with the following error:
wine: Call from 000000007B01135E to unimplemented function
dcomp.dll.DCompositionCreateDevice, aborting
wine: Unimplemented function dcomp.dll.DCompositionCreateDevice called at
address 000000007B01135E (thread 0244), starting debugger...
I have installed the following libraries: corefonts, atmlib, d3dcompiler43,
d3dx9, d9vk/dxvk, fontsmooth-rgb, gdiplus_winxp, msxml3, msxml6, vcrun2008,
vcrun2010, vcrun2012
I have tried it on wine-stable as well (5.0) but it still won't load. Any help
would be appreciated. Thanks!
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50357
Bug ID: 50357
Summary: Star Stable Online crashes with unimplemented function
dcomp.dll.DCompositionCreateDevice2
Product: Wine
Version: 6.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: vojtech.dockal(a)gmail.com
Distribution: ---
Created attachment 68955
--> https://bugs.winehq.org/attachment.cgi?id=68955
Backtrace
Star Stable Online crashes with unimplemented function
dcomp.dll.DCompositionCreateDevice2 called in 32-bit code (0x7b010bf6).
Steps to reproduce:
1) Download installer from
https://launcher-data.starstable.com/Star+Stable+Online+Setup+2.6.0.exe and
install it
- Run launcher
- Launcher crashes
Backtrace is included in attachment.
--
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=54933
Bug ID: 54933
Summary: Wine slow on certain fuse filesystems, with fix
Product: Wine
Version: 8.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: hwertz10(a)gmail.com
Distribution: ---
Created attachment 74452
--> https://bugs.winehq.org/attachment.cgi?id=74452
CIOPFS speed patch
I found a description of users experiencing slowdowns (even using explorer.exe)
on an MTP filesystem, and I experienced similar slowdowns on an s3ql
filesystem. In short, even using explorer on certain filesystems is slow, and
opening programs that open up more than a handful of files is very slow off
these filesystems.:
https://forum.winehq.org/viewtopic.php?t=36400
I found the root cause courtesy of strace -- in dlls/ntdll/unix/file.c in
get_dir_case_sensitivity_stat (which is called very frequently, I think on any
file open or creation, among others), there is a fstatat system call, then a
check on that result to see if the filesystem is a FUSE filesystem, then if it
is it looks for a .ciopfs directory (because presumably CIOPFS -- Case
Insensitive On Purpose Filesystem -- places a .ciopfs in every directory
specifically so wine can do this test.) It turns out the fstatat call gets
used and free inode count, used and free disk space, etc. along with filesystem
type, and on my large s3ql filesystem at least this takes *8/10ths* of a
second, versus the .ciopfs lookup being in dentry cache -- I don't recall if it
used 0.0001 or 0.00001 seconds, but either way extremely fast compared to the
other call.
Reversing the order of these calls (check for .ciopfs first, then if it's there
run fstatat and check result to see if it's a FUSE filesystem) should not cause
a performance regression on any filesystem (since it's usually going to be out
of the dentry cache) while avoiding this slowdown on a filesystems with slow
filesystem stats.
Just a note, I see the equivalent "is filesystem case sensitive?" check for
MacOS actually only runs any tests once then caches the results; using a
similar "case sensitivity" cache for Linux would also be effective (since it
would only run this piece of code once per wine run then.)
Finally, I wonder if CIOPFS is actually used? I see the last update on it is
from 2011, it may have turned out that Wine's case insensitivity support is
fast enough that CIOPFS did not prove useful. If it's not actually being used
by anyone, removing the CIOPFS tests from file.c could be a reasonable thing to
do.
Please find attached a small patch to implement this change for Linux -- it
simply reverses the order of 3 lines of code, so it runs the (fast) .ciopfs
directory existence test first, then only runs the (on some filesystems much
slower) fstatat call and "is it FUSE filesystem?" test if the.ciopfs directory
actually exists.
Thanks, and keep up the good work!!!
--Henry
--
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=30550
Bug #: 30550
Summary: Invisibles sprites in Rayman Origins
Product: Wine
Version: 1.5.3
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: olivier.luraine(a)gmail.com
Classification: Unclassified
Created attachment 39961
--> http://bugs.winehq.org/attachment.cgi?id=39961
Screenshot that shows the bug.
They are missing sprites on rayman origins. For exemple ropes and other things
that rayman catch are invisible. I'm using an up to date archlinux with nvidia
295.40. The game run smoothly.
--
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=37355
Bug ID: 37355
Summary: Tages Protection v5.x needs ntoskrnl
'MmMapLockedPagesSpecifyCache' implementation
Product: Wine
Version: 1.7.27
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntoskrnl
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Hello folks,
reported here: https://github.com/compholio/wine-compholio/issues/80
Michael Müller from FDS team:
--- quote ---
Sadly this is not enough to make the Tages copy protection happy. The issue you
are now running into is:
fixme:ntoskrnl:MmMapLockedPagesSpecifyCache (0x111988, 0, 1, (nil), 0, 32):
stub
The MmMapLockedPagesSpecifyCache command is used to map memory of a process
into the kernel, so that a kernel driver can write / read it. This is necessary
since the kernel does not share the same address space as the process. The
problem is that this command is a stub and always returns 0 as mapped address.
The Tages protection does not check for NULL pointers and tries to write to the
address resulting in:
wine: Unhandled page fault on write access to 0x00000000 at address 0x57fe27
(thread 0018), starting debugger...
The problem is that there is no way to properly implement this on Linux since
there is no way to simply map the memory of a different process if you are not
inside the kernel. Since wine is no kernel module it can only use memory of
different processes, when they explicitly create it as shared memory block.
Sadly you can not declare a memory block as shared after it was allocated, so
this does not help implementing this command.
Anyway in the case of the Tages protection we have some luck since it seems
like the process is paused (I think it was waiting for the response of the
DeviceIoControl function) while the memory is changed by the windows kernel
driver. This allows us to emulate the mapping of the memory by using
ReadProcessMemory and WriteProcessMemory. I wrote some hack to implement this,
but this only prevented the crash and made the application to exit silently. I
either made a mistake in my hack or there is still something else which
prevents it from working.
--- quote ---
Regards
--
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=55431
Bug ID: 55431
Summary: wine-staging to have same Component as wine
Product: WineHQ Bugzilla
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: bugzilla-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: leslie_alistair(a)hotmail.com
CC: austinenglish(a)gmail.com
Distribution: ---
Could wine-staging bugs have the same Component list as wine?
--
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=47996
Bug ID: 47996
Summary: Battlefield 2 - d3d:debug_d3dformat Unrecognized
0x4642564e - Unhandled exception
Product: Wine
Version: 4.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: consolelogger(a)rhyta.com
Distribution: ---
Created attachment 65519
--> https://bugs.winehq.org/attachment.cgi?id=65519
console log with WINEDEBUG=+loaddll
Ubuntu 19.10 - wine-mono-4.9.3.msi
Battlefield 2 crashes during startup.
Console log is attached.
I am happy to provide more details and do tests when asked to.
--
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=55416
Bug ID: 55416
Summary: psapi:psapi_main - check_QueryWorkingSetEx() sometimes
fails on Windows 10
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 - check_QueryWorkingSetEx() sometimes fails on Windows 10:
psapi_main.c:1165: Test failed: exe expected Valid=1 but got 0
psapi_main.c:1169: Test failed: exe expected Win32Protection=2 but got 0
See https://test.winehq.org/data/patterns.html#psapi:psapi_main
This first happened on 2023-07-11 and there has been three instances so far:
* 2023-07-11 win22H2_fgtb-w10pro64-32
* 2023-07-19 win21H2_gitlab-win10-21h2-32
* 2023-08-04 win22H2_newtb-w1064-32
--
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=55426
Bug ID: 55426
Summary: user32:msg - test_swp_paint_region_on_show() sometimes
fails on w7u
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:msg - test_swp_paint_region_on_show() sometimes fails on w7u:
msg.c:9471: Test failed: GetRgnBox (on parent) returned 1
msg.c:9475: Test failed: parent update region: got (0,0)-(0,0), expected
(10,10)-(100,100)
msg.c:9508: Test failed: GetRgnBox (on parent) returned 1
msg.c:9512: Test failed: parent update region: got (0,0)-(0,0), expected
(20,20)-(120,120)
See https://test.winehq.org/data/patterns.html#user32:msg
This first happened on 2023-07-13 and has happened about once a week since,
always on w7u. In particular it does not happen on w7pro64 but then that VM
only runs 64-bit tests so maybe this is just 32-bit-specific.
* 2023-07-13 win7_newtb-w7u-pt-PT_1
* 2023-07-14 win7_newtb-w7u-de
* 2023-07-19 win7_newtb-w7u-es
* 2023-08-01 win7_newtb-w7u-2qxl
See also bug 55425 which is similar but happens in
test_swp_paint_region_on_extend_zerosize() and started one month earlier.
--
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=55425
Bug ID: 55425
Summary: user32:msg -
test_swp_paint_region_on_extend_zerosize() sometimes
fails on w7u
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:msg - test_swp_paint_region_on_extend_zerosize() sometimes fails on w7u:
msg.c:9569: Test failed: parent update region: got (10,10)-(100,58), expected
(10,10)-(100,100)
See https://test.winehq.org/data/patterns.html#user32:msg
This first happened on 2023-06-13 and has happened about twice a week since,
always on w7u. In particular it does not happen on w7pro64 but then that VM
only runs 64-bit tests so maybe this is just 32-bit-specific.
* 2023-06-13 win7_newtb-w7u-adm
* 2023-06-22 win7_newtb-w7u-2qxl
* 2023-06-23 win7_newtb-w7u
* 2023-06-26 win7_newtb-w7u-2qxl
* 2023-07-13 win7_newtb-w7u-2qxl_1
* 2023-07-19 win7_newtb-w7u-el
* 2023-08-01 win7_newtb-w7u-adm
* 2023-08-08 win7_newtb-w7u-adm
--
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=55381
Bug ID: 55381
Summary: installing synaptics fingerprint reader driver fails
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: usb
Assignee: wine-bugs(a)winehq.org
Reporter: alois.schloegl(a)gmail.com
Distribution: ---
Created attachment 74955
--> https://bugs.winehq.org/attachment.cgi?id=74955
log file trying to install synaptics fingerprint reader driver
Attached is the log file when trying to install the synaptics fingerprint
reader driver
https://download.lenovo.com/pccbbs/mobiles/nz3gf09w.exe
It seems to fail with this error:
012c:err:ntdll:NtQueryInformationToken Unhandled token information class 26
When selecting to "extract only" (and not install), this error is not shown.
The files are extracted in both cases, when selecting extract only, as well as
"install".
--
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=54095
Bug ID: 54095
Summary: quartz:filtermapper sometimes crashes on exit in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: quartz
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
quartz:filtermapper sometimes crashes on exit in Wine:
quartz:filtermapper start dlls/quartz/tests/filtermapper.c
0c18:filtermapper: 251 tests executed (0 marked as todo, 0 as flaky, 0
failures), 0 skipped.
quartz:filtermapper:0c18 done (-1073741819) in 0s 94B
See https://test.winehq.org/data/patterns.html#quartz:filtermapper
Where -1073741819 == 0xc0000005
The crash is pretty rare: one per month on average but there are some two
months stretches with no crash.
What's interesting is that the invalid memory access happens after the main
process has printed the 'test summary' line, which means the crash happened on
exit. So it must be caused by previous memory corruption.
Also MR!1703 got a timeout on exit which is probably the same underlying issue:
quartz:filtermapper start dlls/quartz/tests/filtermapper.c
0af0:filtermapper: 253 tests executed (0 marked as todo, 0 as flaky, 0
failures), 0 skipped.
quartz:filtermapper:0af0 done (258) in 120s 94B
--
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=54845
Bug ID: 54845
Summary: Fusion 360: key_import_pair unsupported key type
L"CAPIPRIVATEBLOB"
Product: Wine
Version: 8.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bcrypt
Assignee: wine-bugs(a)winehq.org
Reporter: benjackson990(a)gmail.com
Distribution: ---
The recent update has changed the login process to allow for a Single Sign On,
but in the process seemingly used a encryption not supported in any version of
Wine that I'm aware of.
Can anyone please advise how I should go about resolving the following issue
```
0178:fixme:bcrypt:key_import_pair unsupported key type L"CAPIPRIVATEBLOB"
0178:fixme:bcrypt:get_key_property unsupported algorithm 9
```
--
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=53712
Bug ID: 53712
Summary: ole32:moniker is broken on Windows 7 in the GitLab
WineTest builds
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:moniker is broken on Windows 7 in the GitLab WineTest builds:
moniker.c:2280: ACP is 1252
0a18:4þ": 5504 tests executed (0 marked as todo, 0 as flaky, 0 failures), 0
skipped.
ole32:moniker:0a18 done (-1073740791) in 0s 115B
Test failed: crash (c0000409)
https://test.winehq.org/data/patterns.html#ole32:moniker
Where 0xc0000409 == STATUS_STACK_BUFFER_OVERRUN.
The failures started on 2022-07-26 which is when the WineTest builds switched
from the old build system to GitLab. A test with winetest-889fe64d9f2e.exe
(built on 2022-07-25) confirms that this test still succeeds when using
binaries from the old build system.
--
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=54545
Bug ID: 54545
Summary: ieframe:webbrowser test_WebBrowser() gets unexpected
OnFocus_FALSE calls on Windows 7
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: ieframe
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ieframe:webbrowser - test_WebBrowser() gets unexpected OnFocus_FALSE calls on
Windows 7.
For instance:
webbrowser.c:1202: Test failed: unexpected call OnFocus_FALSE
and sometimes a second failure happens later:
webbrowser.c:3434: Test failed: expected OnFocus_FALSE
See https://test.winehq.org/data/patterns.html#ieframe:webbrowser
The unexpected calls don't happen during a specific test_WebBrowser() call.
Up to 2022-11-04 this failure was only happening on w1064v1709 when that
stopped. Then on 2023-01-25 is started happening about 3 times per month on the
w7u* TestBot VM.
--
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=55430
Bug ID: 55430
Summary: ddraw:ddraw1, ddraw:ddraw2 & ddraw:ddraw7 -
test_coop_level_mode_set() is sometimes missing
WM_DISPLAYCHANGE on Windows
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
ddraw:ddraw1, ddraw:ddraw2 & ddraw:ddraw7 - test_coop_level_mode_set() is
sometimes missing WM_DISPLAYCHANGE on Windows:
ddraw1.c:3141: Test failed: Expected message 0x7e, but didn't receive it.
ddraw1.c:3144: Test failed: Expected (0,0)-(640,480), got (0,0)-(1024,768).
ddraw1.c:3148: Test failed: Got unexpected screen size 1024x768.
See https://test.winehq.org/data/patterns.html#ddraw:ddraw1https://test.winehq.org/data/patterns.html#ddraw:ddraw4https://test.winehq.org/data/patterns.html#ddraw:ddraw7
Where 0x7e == WM_DISPLAYCHANGE
This first happened on 2023-04-11 [1] and has happened a bit over once per
month since on both Windows 8 and 10. Most of the time it's the first failure
in the WineTest run.
* 2023-04-11 win81_newtb-w8 (ddraw:ddraw4)
* 2023-04-13 win81_newtb-w8adm (ddraw:ddraw1)
* 2023-04-25 win81_newtb-w8 (ddraw:ddraw7)
* 2023-05-25 win21H1_newtb-w10pro64-he-64 (ddraw:ddraw7)
* 2023-05-25 win81_newtb-w8adm (ddraw:ddraw4, preceded by clip rect failures in
ddraw 1, 2, 4)
* 2023-08-01 win21H1_newtb-w10pro64-ar-64 (ddraw:ddraw4)
* 2023-08-03 win81_newtb-w8adm (ddraw:ddraw1)
[1] There are older instances but I think those were the consequence of
previous failures.
--
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=55429
Bug ID: 55429
Summary: psapi:psapi_main - test_GetPerformanceInfo() sometimes
fails on Windows
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 - test_GetPerformanceInfo() sometimes fails on Windows:
psapi_main.c:716: Test failed: expected approximately 1131 but got 1125
See https://test.winehq.org/data/patterns.html#psapi:psapi_main
There are three known instances so far:
* 2023-06-16 win1607_newtb-w1064v1607-32
* 2023-06-28 win21H1_newtb-w10pro64-pt-BR-64
* 2023-08-08 win2004_newtb-w10pro64v2004-64
The test counts the total number of threads on the machine in two different
ways and expects to find the same or a close enough result. In this case some
process with 6 threads must have stopped while the test was running, thus
causing the failure.
The test also counts handles and processes, both of which could probably also
fail in the same way.
I think this is another good candidate for the tryok() patch from MR!3418.
--
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=44051
Bug ID: 44051
Summary: Rendering compressed .avi outputs error on program or
crashes it
Product: Wine
Version: 2.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvidc32
Assignee: wine-bugs(a)winehq.org
Reporter: lanfrda1(a)gmail.com
Distribution: Ubuntu
Created attachment 59727
--> https://bugs.winehq.org/attachment.cgi?id=59727
msvidc32 compressed avi render bug log.
If you use any codec, it will make an error on the program (E.G. Flash 8), or
the program will crash (E.G. SidWiz 2).
--
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=12428
Summary: win16 test suite: profile test fails
Product: Wine
Version: CVS/GIT
Platform: PC
URL: http://win16test.googlecode.com
OS/Version: Linux
Status: NEW
Keywords: download, source, testcase
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Created an attachment (id=11967)
--> (http://bugs.winehq.org/attachment.cgi?id=11967)
Backtrace in git
+++ This bug was initially created as a clone of Bug #9850 +++
The code can be downloaded
from http://win16test.googlecode.com with svn,
and is quite easy to run; see
http://win16test.googlecode.com/svn/trunk/src/README
for instructions.
The profile test crashes in current git. Attached is the backtrace in current
git.
--
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=55427
Bug ID: 55427
Summary: ddraw:ddraw7 - test_lighting() sometimes fails on
Windows
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
ddraw:ddraw7 - test_lighting() sometimes fails on Windows:
ddraw7.c:4728: Test failed: Lit quad without normals has color 0x00ffff00,
expected 0x00000000.
ddraw7.c:4741: Test failed: Lit quad with normals has color 0x00ffff00,
expected 0x00000000.
ddraw7.c:4786: Test failed: Lit quad with light has color 0x00ffffff.
ddraw7.c:4786: Test failed: Lit quad with singular world matrix has color
0x00ffffff.
ddraw7.c:4786: Test failed: Lit quad with transformation matrix has color
0x00ffffff.
ddraw7.c:4786: Test failed: Lit quad with non-affine matrix has color
0x00ffff00.
See https://test.winehq.org/data/patterns.html#ddraw:ddraw7
The number of test failures changes from one run to the next, as well as the
unexpected color, although it's always a mix of ff and 00. This issue has been
there since at least 2023-01-20 and has happened regularly, about 1.5 times per
month, on Windows 8 to Windows 10 22H2.
--
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=55374
Bug ID: 55374
Summary: user32:msg - test_swp_paint_region_on_show() sometimes
gets a NULLREGION on Windows 7
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:msg - test_swp_paint_region_on_show() sometimes gets a NULLREGION on
Windows 7:
msg.c:9471: Test failed: GetRgnBox (on parent) returned 1
msg.c:9475: Test failed: parent update region: got (0,0)-(0,0), expected
(10,10)-(100,100)
msg.c:9508: Test failed: GetRgnBox (on parent) returned 1
msg.c:9512: Test failed: parent update region: got (0,0)-(0,0), expected
(20,20)-(120,120)
See https://test.winehq.org/data/patterns.html#user32:msg
The oldest known failure happened on 2023-06-22 and it has happened a bit over
once per week since, always on a w7u test configuration:
* 2023-06-22 win7_newtb-w7u-2qxl
* 2023-06-23 win7_newtb-w7u
* 2023-06-26 win7_newtb-w7u-2qxl
* 2023-07-13 win7_newtb-w7u-2qxl_1
* 2023-07-14 win7_newtb-w7u-de
* 2023-07-14 win7_newtb-w7u-de
* 2023-07-19 win7_newtb-w7u-es
* 2023-07-19 win7_newtb-w7u-es
--
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=12427
Summary: win16 test suite: printdlg test fails
Product: Wine
Version: CVS/GIT
Platform: PC
URL: http://win16test.googlecode.com
OS/Version: Linux
Status: NEW
Keywords: download, source, testcase
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Created an attachment (id=11966)
--> (http://bugs.winehq.org/attachment.cgi?id=11966)
Backtrace in git
+++ This bug was initially created as a clone of Bug #9850 +++
The code can be downloaded
from http://win16test.googlecode.com with svn,
and is quite easy to run; see
http://win16test.googlecode.com/svn/trunk/src/README
for instructions.
The printdlg test crashes in current git. Attached is the backtrace in current
git.
--
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=55423
Bug ID: 55423
Summary: dinput:device8 - test_mouse_keyboard() sometimes gets
access denied on Windows 10
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: dinput
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
dinput:device8 - test_mouse_keyboard() sometimes gets access denied on Windows
10:
device8.c:695: Test failed: IDirectInputDevice8_Acquire failed: 0x80070005
device8.c:698: Test failed: IDirectInputDevice8_Acquire failed: 0x80070005
device8.c:703: Test failed: GetRegisteredRawInputDevices returned 1,
raw_devices_count: 3
device8.c:705: Test failed: Unexpected raw device flags: 0
device8.c:707: Test failed: Unexpected raw device flags: 0
See https://test.winehq.org/data/patterns.html#dinput:device8
Where 0x80070005 == E_ACCESSDENIED
This failure mode has been jumping around:
* From 2023-01-06 to 2023-03-20 this was happening exclusively on w7u, with one
exception, w10pro64-ru-64 on 2023-01-13 (all with "raw_devices_count: 3").
* Then from 2023-03-21 to 2023-05-16 it happened exclusively on various
debian11-win32 locales, but with "raw_devices_count: 1".
* And since 2023-05-30 it has been happening exclusively on w1064v1507 and
w10pro64v2004 (both in 32 and 64-bit) with 12 instances so far, all with
"raw_devices_count: 3".
See also bug 54558 about other access denied errors in dinput:device8.
--
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=55413
Bug ID: 55413
Summary: ddraw:ddraw1 sometimes fails and crashes on w1064v1507
and w1046v2004
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
ddraw:ddraw1 sometimes fails on w1064v1507 and w1046v2004:
ddraw1.c:2495: Test failed: Expected message 0x46, but didn't receive it.
ddraw1.c:2618: Test failed: Failed to set foreground window.
ddraw1.c:2626: Test failed: Failed to set foreground window.
ddraw1.c:2652: Test failed: Expected window style 0x14cf0000, got 0x4cf0000.
ddraw1.c:2655: Test failed: Expected window extended style 0x108, got 0x100.
ddraw1.c:2662: Test failed: Expected window extended style 0x108, got 0x100.
ddraw1.c:2671: Test failed: Expected window extended style 0x108, got 0x100.
ddraw1.c:2680: Test failed: Expected window extended style 0x108, got 0x100.
ddraw1.c:2683: Test failed: Failed to set foreground window.
ddraw1.c:2690: Test failed: Expected window style 0x14cf0000, got 0x4cf0000.
ddraw1.c:2693: Test failed: Expected window extended style 0x108, got 0x100.
ddraw1.c:2706: Test failed: Failed to set foreground window.
ddraw1.c:2731: Test failed: Failed to set foreground window.
ddraw1.c:2746: Test failed: Failed to set foreground window.
ddraw1.c:2755: Test failed: Expected window extended style 0x108, got 0x100.
ddraw1.c:2775: Test failed: Expected window extended style 0x108, got 0x100.
ddraw1.c:2778: Test failed: Failed to set foreground window.
ddraw1.c:2781: Test failed: Expected window style 0x34cf0000, got 0x14cf0000.
ddraw1.c:2784: Test failed: Expected window extended style 0x108, got 0x100.
ddraw1.c:3129: Test failed: Failed to set foreground window.
ddraw1.c:3130: Test failed: Expected message 0x6, but didn't receive it.
ddraw1.c:3135: Test failed: Got unexpected screen size 800x600.
ddraw1.c:867: Test failed: Got unexpected wparam 0 for message 0x1c, expected
0x1.
ddraw1.c:3141: Test failed: Expected message 0x5, but didn't receive it.
ddraw1.c:3144: Test failed: Expected (0,0)-(640,480), got
(-32000,-32000)-(-31840,-31972).
ddraw1.c:3148: Test failed: Got unexpected screen size 1024x768.
ddraw1.c:3161: Test failed: Expected message 0x46, but didn't receive it.
[...]
ddraw1.c:3609: Test failed: Expected (0,0)-(640,480), got (-8,-8)-(648,448).
ddraw1.c:4338: Test failed: Expected WM_ACTIVATEAPP, but did not receive it.
ddraw1.c:4350: Test failed: Expected WM_ACTIVATEAPP, but did not receive it.
ddraw1.c:4362: Test failed: Expected WM_ACTIVATEAPP, but did not receive it.
ddraw1.c:4384: Test failed: Expected WM_ACTIVATEAPP, but did not receive it.
ddraw1.c:8051: Test failed: Failed to set foreground window.
ddraw1.c:8053: Test failed: Got unexpected hr 0.
ddraw1.c:8055: Test failed: Got unexpected hr 0.
ddraw1.c:8057: Test failed: Got unexpected hr 0.
ddraw1.c:8059: Test failed: Got unexpected hr 0.
ddraw1.c:8069: Test failed: Got unexpected hr 0.
ddraw1.c:8071: Test failed: Got unexpected hr 0.
ddraw1.c:8073: Test failed: Got unexpected hr 0.
ddraw1.c:8077: Test failed: Failed to set foreground window.
ddraw1.c:8079: Test failed: Got unexpected hr 0.
ddraw1.c:8081: Test failed: Got unexpected hr 0.
ddraw1.c:8087: Test failed: Got unexpected hr 0.
ddraw1.c:8135: Test failed: Failed to set foreground window.
ddraw1.c:8147: Test failed: Failed to set foreground window.
ddraw1.c:13670: Test failed: WM_KILLFOCUS was not received.
ddraw1.c:13706: Test failed: Got unexpected hr 0x887600e1.
ddraw1.c:13709: Test failed: Got unexpected hr 0x887600ff.
0a60:ddraw1: unhandled exception c0000005 at 00007FF6FFAE2567
See https://test.winehq.org/data/patterns.html#ddraw:ddraw1
Where 0x46 == WM_WINDOWPOSCHANGING
and the test window does not seem to be visible:
expected: 0x14cf0000 == WS_VISIBLE | 0x04cf0000
This failure happens irregularly and only on w1064v1507 and w1046v2004 so far:
* 2022-12-14 win1507_newtb-w1064v1507-64
* 2022-12-15 win1507_newtb-w1064v1507-64
* 2023-01-31 win1507_newtb-w1064v1507-64
* 2023-02-16 win1507_newtb-w1064v1507-64
* 2023-06-07 win1507_newtb-w1064v1507-64
* 2023-06-09 win1507_newtb-w1064v1507-32
* 2023-07-13 win1507_newtb-w1064v1507-64
* 2023-07-27 win2004_newtb-w10pro64v2004-64
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55388
Bug ID: 55388
Summary: d3d9:visual - add_dirty_rect_test() fails on
w11pro64-amd
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
d3d9:visual - add_dirty_rect_test() fails on w11pro64-amd:
visual.c:19496: Test failed: Failed to draw, hr 0x80004005.
visual.c:19792: Test failed: Got unexpected color 0x0000ff00.
See https://test.winehq.org/data/patterns.html#d3d9:visual
These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In
particular they do not happen on fgtb-w10pro64-rx550 the only other test
machine to have an AMD GPU, nor do they happen on the other Windows 11 test
machines (w11pro64 and w11pro64-nv).
--
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=53423
Bug ID: 53423
Summary: Baldur's gate 3 need allocation callbacks for
winevulkan
Product: Wine
Version: 7.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winevulkan
Assignee: wine-bugs(a)winehq.org
Reporter: charles2000wang(a)gmail.com
Distribution: ---
Baldur's gate 3 crashes on startup when using the vulkan renderer. These are
the error messages in terminal
0140:fixme:vulkan:wine_vkCreateWin32SurfaceKHR Support for allocation callbacks
not implemented yet
0140:fixme:vulkan:__wine_create_vk_device_with_callback Support for allocation
callbacks not implemented yet
It seems that winevulkan does not have allocation callbacks.
--
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=51122
Bug ID: 51122
Summary: 5.0.3 vs 6.x - slow performance in graphics
Product: Wine
Version: 6.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mondane.woodworker(a)gmail.com
Distribution: ---
When I use 6.x, even 'winecfg' starts like a slideshow. This doesn't happen
with 5.0.3 . No application can be ran like this.
Using:
* Wine 6.0 - 6.7
* Ubuntu Unity 20.04.1 ( https://ubuntuunity.org/ )
* Laptop: Dell Precision 7550
* Graphics: NVIDIA TU117GLM [Quadro T2000 Mobile / Max-Q]
** Using nvidia-driver-460
--
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=55419
Bug ID: 55419
Summary: dxgi:dxgi - test_video_memory_budget_notification() is
sometimes missing an event 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: ---
dxgi:dxgi - test_video_memory_budget_notification() is sometimes missing an
event in Wine:
dxgi.c:7876: Test failed: Expected event fired.
See https://test.winehq.org/data/patterns.html#dxgi:dxgi
The first known instance goes back to 2023-01-26 and it has been happening a
bit over twice per month since, mostly on the debiant VM but also on the GitLab
CI environment and fg-deb64 (my desktop).
--
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=55418
Bug ID: 55418
Summary: quartz:vmr9 - test_surface_allocator_notify_refcount()
sometimes crashes on w11pro64_nv
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: quartz
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
quartz:vmr9 - test_surface_allocator_notify_refcount() sometimes crashes on
w11pro64_nv:
vmr9.c:3475: this is the last test seen before the exception
1828:vmr9: unhandled exception c0000005 at 000000000049805A
See https://test.winehq.org/data/patterns.html#quartz:vmr9
This is crash happened only twice so far and both times on w11pro64_nv, the
TestBot's Windows 11 Nvidia RTX 3050 VM:
* 2023-08-04 w11pro64-nv-64
* 2023-03-03 w11pro64-nv-64
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55396
Bug ID: 55396
Summary: advapi32:registry breaks test_registerOIDFunction() in
crypt32:oid on w8adm
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: crypt32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
advapi32:registry breaks test_registerOIDFunction() in crypt32:oid on w8adm:
oid.c:297: Test failed: CryptUnregisterOIDFunction failed: 2
oid.c:303: Test failed: CryptUnregisterOIDFunction failed: 2
oid.c:305: Test failed: Could not delete bogus key
oid.c:314: Test failed: CryptUnregisterOIDFunction failed: 2
oid.c:321: Test failed: CryptUnregisterOIDFunction failed: 2
oid.c:325: Test failed: Could not delete CryptDllEncodeObject key
oid.c:336: Test failed: CryptUnregisterOIDFunction failed: 2
oid.c:340: Test failed: Could not delete CryptDllEncodeObject key
oid.c:343: Test failed: Could not delete 'EncodingType 3' key
oid.c:377: Test failed: Expected ERROR_FILE_EXISTS, got 00000000
oid.c:382: Test failed: Expected ERROR_FILE_EXISTS, got 00000000
oid.c:390: Test failed: Expected key to exist, RegOpenKeyA failed: 2
oid.c:412: Test failed: CryptUnregisterDefaultOIDFunction failed: 00000002
oid.c:416: Test failed: CryptUnregisterDefaultOIDFunction failed: 00000002
oid.c:430: Test failed: CryptUnregisterDefaultOIDFunction failed
See https://test.winehq.org/data/patterns.html#crypt32:oid
More precisely these failures only happen if running advapi32:registry before
crypt32:oid.
Furthermore the failures started on 2023-07-27 which is when the w8 VM's memory
was increased to 4GB, and older WineTest builds still produce the failures. So
the 2023-07-27 VM change is the cause of these failures but it's not clear why.
--
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=657
Bartosz <gang65(a)poczta.onet.pl> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gang65(a)poczta.onet.pl
--
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=55412
Bug ID: 55412
Summary: Super Bubsy crashes before the intro
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: spzakulec(a)gmail.com
Distribution: ---
Created attachment 74972
--> https://bugs.winehq.org/attachment.cgi?id=74972
wine console output and backtrace from crash
When I try to install & run Super Bubsy as specified in the AppDB page:
https://appdb.winehq.org/objectManager.php?sClass=version&iId=19820 the game
crashes right away.
Per the AppDB instructions (reproduced below), I've tried to install the game
and run it with the videomemorysize=512M winetricks verb.
WINEPREFIX="$HOME/SuperBubsy" WINEARCH=win32 wine wineboot
WINEPREFIX="$HOME/SuperBubsy" winecfg ---> set Windows 95, do not allow to
decorate windows, emulate desktop
WINEPREFIX="$HOME/SuperBubsy" winetricks videomemorysize=512
Install the game and to run it:
WINEPREFIX="$HOME/SuperBubsy" wine $HOME/SuperBubsy/drive_c/SUPER\
BUBSY/Bubsy.exe
I'm on KDE Neon 5.27, using Wine 8.13.
--
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=54825
Bug ID: 54825
Summary: Visual Studio C++ Build Tools fails to install with
'Could not find Windows Runtime type'
Product: Wine-staging
Version: 8.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lupino8211(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 74328
--> https://bugs.winehq.org/attachment.cgi?id=74328
full_install.log
I'm trying to install MSVC toolchain in wine in docker, but didn't succeed. I'm
installing tools in following order:
- dotnet48
- winecfg /v win10
- Visual Studio C++ Build Tools
Installation ends in the following error (from logs which can be found in wine
user's Temp directory):
[025c:000a][2023-04-13T20:48:57] Error 0x80131522: Rethrowing the exception
from the engine: Could not find Windows Runtime type
'Windows.Networking.Connectivity.NetworkCostType'.
but how I can inspect, these DLL's exist in the following paths:
/root/.wine/drive_c/windows/system32/windows.networking.connectivity
/root/.wine/drive_c/windows/syswow64/windows.networking.connectivity
and should contain mentioned type.
How to reproduce:
Download vs_BulidTools.exe from
https://download.visualstudio.microsoft.com/download/pr/d24d0627-f1e2-4a69-…
Install it via:
wine cmd /c start /wait vs_BuildTools.exe \--quiet --add
"Microsoft.VisualStudio.Workload.VCTools;includeRecommended" --add
"Microsoft.VisualStudio.Workload.MSBuildTools;includeRecommended" --add
"Microsoft.VisualStudio.Workload.ManagedDesktopBuildTools;includeRecommended"
--add "Microsoft.VisualStudio.Component.VC.Tools.x86.x64;includeRecommended"
--
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=25100
Summary: the program don't start...
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: salvatore91salvatore(a)yahoo.it
....
--
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=55406
Bug ID: 55406
Summary: mIRC hangs on receiving a new PM
Product: Wine
Version: 8.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kooldioxide(a)gmail.com
Distribution: ---
This problem started once I upgraded mIRC to version 7.74.
When someone sends me a PM and this causes mIRC to open a new window, mIRC
hangs entirely, and the process keeps using a lot of CPU according to htop.
Only thing I can do at that point is kill the process.
The problem doesn't occur if I already have a query window open with the person
sending me a message.
An easy way to reproduce this is to connect to an IRC server, then from the
status window:
/msg <my_own_nick> hello
That will open a query window to yourself which triggers this behaviour as
well.
This problem occurs on two different Linux installations I tried, one with Wine
8.12 and one with Wine 8.0.2.
--
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=32900
Bug #: 32900
Summary: The Bat 5.2.2 - keyboard keys stick
Product: Wine
Version: 1.1.22
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: sprog(a)online.ru
Classification: Unclassified
It happens rarely and may be related to RU keyboard layout.
You press Cntr-N a new message form is created but pressing letters on a
keyboard won't work as expected. If fact it's like you're constantly holding
right CTL key. You press right CTL again and the bug disappears....
The same happens happens with ALT key too. The probles was in Wine versions
starting from 1.4.1
Unfortunately I can't give you the conditions how to reproduce the bug. This
report is more like "think about what could go wrong". If you can advise how to
trace this problem - I'll do it.
The Bat all so has problems with ole32. From to time the Connection Center
causes OLE32 error. The conditions are unkown. It happens once if 2-3 days.
After that the connection center works but the status bar is showing OLE32
error...
--
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=55393
Bug ID: 55393
Summary: The process which started "The Bat!" is still running
after the app ist quieted
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mywine(a)schiermeier-it.de
Distribution: ---
Created attachment 74957
--> https://bugs.winehq.org/attachment.cgi?id=74957
Part of "ps faux" command
Setting: "The Bat!" is installed by its installer and "GnuPG" is also installed
with its installer. "The Bat!" is starting normally and the encrypting is
working.
A mail was created, encrypted, or signed and sent.
Now "The Bat!" is quieted by its menu entry.
The GUI disappears.
Now "(h)top" or "ps" shows still some processes running and can only be quieted
with "kill":
---ps faux---
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
(...)
joerg 3281 3.4 0.0 19668 19144 ? Ss 00:59 0:08
/opt/wine-devel/bin/wineserver
joerg 3285 0.0 0.0 2380696 16724 ? Ssl 00:59 0:00
C:\windows\system32\services.exe
joerg 3288 0.1 0.0 2055360 15552 ? Ssl 00:59 0:00
C:\windows\system32\winedevice.exe
joerg 3297 0.8 0.0 2297900 38264 ? Ssl 00:59 0:02
C:\windows\system32\winedevice.exe
joerg 3306 0.1 0.0 2142560 29912 ? Ssl 00:59 0:00
C:\windows\system32\plugplay.exe
joerg 3314 0.0 0.0 1919060 9596 ? Ssl 00:59 0:00
C:\windows\system32\svchost.exe -k LocalServiceNetworkRestricted
joerg 3325 0.1 0.1 2169640 86012 ? Sl 00:59 0:00
C:\windows\system32\explorer.exe /desktop
joerg 3330 0.0 0.0 2247080 14336 ? Ssl 00:59 0:00
C:\windows\system32\rpcss.exe
joerg 3618 0.4 0.0 2704816 30700 ? Ss 01:00 0:00
z:\opt\winprog\GnuPG\bin\gpg-agent.exe --homedir
c:\users\username\appdata\roaming\gnupg-tb --use-standard-socket --daemon
---///---
See also the attached log file.
Internally the GnuPG is started from The Bat! via the command line. For another
purpose (and wine bug) I wrote a little wrapper to log the commands which The
Bat!s hands over to GnuPGs exe-file (gpg.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=49845
Bug ID: 49845
Summary: Sacred Gold: very bad performance (low fps) when
zoomed out
Product: Wine
Version: 5.0.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: phaidros(a)gmx.at
Distribution: ---
Sacred 1 Gold provides 3 zoom levels: Very close, middle and zoomed out. I
guess most people really only use the zoomed out setting, the other two show
such a small portion of the world that i don't know how anybody could enjoy the
experience.
Unfortunately the zoomed out setting gives very bad performance, around 20fps
on a Ryzen 2700X @ 3.7GHz. Using the middle zoom setting fps go up to about
30-35fps and the very close zoom setting gives 55-60fps.
I don't really understand what's going on, I think this is a very old game and
a 8-core 3.7GHz CPU should have no problem whatsoever to run it. The 20fps i'm
getting make the game really unenjoyable to the extent where i would rather
boot windows to play it (where i'm getting 60fps at all zoom levels).
I tried with and without CSMT, fixing the process to a single CPU core etc.
Unfortunately no luck. It is really strange that the game would run at almost
60fps when zoomed in and then take such a massive performance hit when zooming
out.
--
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=53956
Bug ID: 53956
Summary: Sacred Underworld crashes after launching
Product: Wine
Version: 7.21
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: Alexandr42suv(a)mail.ru
Distribution: ---
Created attachment 73536
--> https://bugs.winehq.org/attachment.cgi?id=73536
automatically generated backtrace
When I was trying to run Sacred Underworld 2.28, I got an error message and
game crashes. Other games or windows programs works well
CPU: Intel Core i3-4005u
GPU: Intel HD Graphics 4400
--
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=54124
Bug ID: 54124
Summary: Sacred Underworld black screen hanging
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: VladimirVSC(a)yandex.ru
Distribution: ---
Created attachment 73656
--> https://bugs.winehq.org/attachment.cgi?id=73656
Sacred Underworld crash report
When starting the game, the black screen appears which hangs until you press
Escape or anything else. Then "Application is not responding" message appears
and the game crashes to desktop. The same for stable 7.0.1 and 8.0-rc1.
--
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=39236
Bug ID: 39236
Summary: shell32:shlfileop fails if privileges not high enough
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
If the user cannot write to the root of the c: drive the test fails with the
following errors:
shlfileop.c:2497: Test failed: The file does not exist
shlfileop.c:2499: Test failed: File is not removed, ErrorCode: 1026
shlfileop.c:94: Test failed: Failure to open file
shlfileop.c:2505: Test failed: The file does not exist
shlfileop.c:2507: Test failed: File is not removed, ErrorCode: 1026
In particular one can notice this bug on the following WineTest box:
fg-win2000-rusr: Windows 2000 with a Restricted user account
The test should try to write its Unicode file in the temporary directory.
The test regression was introduced by this commit:
commit 1fc0cb75eebeb011a1f620fb96f32245d886916c
Author: Nigel Liang <ncliang(a)gmail.com>
Date: Fri Jun 8 14:25:24 2007 -0700
shell32: Conformance tests for unicode filenames and fix a bug for file
deletion.
--
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=55395
Bug ID: 55395
Summary: dinput:force_feedback - test_device_managed_effect()
sometimes fails on w8
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: dinput
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
dinput:force_feedback - test_device_managed_effect() sometimes fails on w8:
driver_bus.c:290: Test failed: id 1: force_feedback.c:4180 got spurious packet
driver_bus.c:1098: Test failed: id 1: force_feedback.c:4180 expect[0]: got
0xb000f, expected 0
driver_bus.c:1099: Test failed: id 1: force_feedback.c:4180 expect[0]: got id 6
driver_bus.c:1100: Test failed: id 1: force_feedback.c:4180 expect[0]: got len
2
See https://test.winehq.org/data/patterns.html#dinput:force_feedback
These failures are specific to the 32-bit Windows 8 TestBot VM, w8, and they
happened 5 times over the past 8 months:
* 2022-12-09 win81_newtb-w8
* 2023-01-31 win81_newtb-w8
* 2023-05-05 win81_newtb-w8
* 2023-05-26 win81_newtb-w8
* 2023-07-27 win81_newtb-w8
--
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=55298
Bug ID: 55298
Summary: gdi32:font fails the MS Shell Dlg tests in the Arabic,
Japanese and Chinese locales in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
gdi32:font fails the MS Shell Dlg tests in the Arabic, Japanese and Chinese
locales in Wine:
test_nonexistent_font()
font.c:4181: Test failed: MS Shell Dlg should be enumerated
font.c:4183: Test failed: MS Shell Dlg should be enumerated
font.c:4192: Test failed: expected MS Shell Dlg, got Arial
font.c:4205: Test failed: expected MS Shell Dlg, got Arial
font.c:4181: Test failed: MS Shell Dlg should be enumerated
font.c:4183: Test failed: MS Shell Dlg should be enumerated
font.c:4192: Test failed: expected MS Shell Dlg, got Arial
font.c:4205: Test failed: expected MS Shell Dlg, got Arial
font.c:4181: Test failed: MS Shell Dlg should be enumerated
font.c:4183: Test failed: MS Shell Dlg should be enumerated
font.c:4192: Test failed: expected MS Shell Dlg, got Arial
font.c:4205: Test failed: expected MS Shell Dlg, got Arial
font.c:4181: Test failed: MS Shell Dlg should be enumerated
font.c:4183: Test failed: MS Shell Dlg should be enumerated
font.c:4192: Test failed: expected MS Shell Dlg, got Arial
font.c:4205: Test failed: expected MS Shell Dlg, got Arial
font.c:4181: Test failed: MS Shell Dlg should be enumerated
font.c:4183: Test failed: MS Shell Dlg should be enumerated
font.c:4192: Test failed: expected MS Shell Dlg, got Arial
font.c:4205: Test failed: expected MS Shell Dlg, got Arial
test_EnumFonts_subst()
font.c:5507: Test failed: MS Shell Dlg should be enumerated
font.c:5509: Test failed: MS Shell Dlg should be enumerated as a TrueType font
font.c:5529: Test failed: MS Shell Dlg should be enumerated
font.c:5530: Test failed: MS Shell Dlg should be enumerated
See https://test.winehq.org/data/patterns.html#gdi32:font
This happens on both the TestBot's Debian11 and Testing VMs.
--
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=55339
Bug ID: 55339
Summary: d3d9:visual - add_dirty_rect_test() fails on
w11pro64_nv
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
d3d9:visual - add_dirty_rect_test() fails on w11pro64_nv:
visual.c:19792: Test failed: Got unexpected color 0x00adbeef.
See https://test.winehq.org/data/patterns.html#d3d9:visual
This failure goes back to at least 2022-11-23, is systematic and specific to
w11pro64_nv, the TestBot's only NVidia test configuration.
--
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=55392
Bug ID: 55392
Summary: d3d9:visual - test_color_clamping() fails on
w11pro64-amd
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
d3d9:visual - test_color_clamping() fails on w11pro64-amd:
visual.c:24213: Test failed: Got unexpected color 0x00000000, case 1.
See https://test.winehq.org/data/patterns.html#d3d9:visual
This failure is systematic and only happens on w11pro64-amd (AMD RX 6600). In
particular it does not happen on fgtb-w10pro64-rx550 the only other test
machine to have an AMD GPU, nor does it happen on the other Windows 11 test
machines (w11pro64 and w11pro64-nv).
--
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=55391
Bug ID: 55391
Summary: d3d9:visual - test_uninitialized_varyings() fails on
w11pro64-amd
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
d3d9:visual - test_uninitialized_varyings() fails on w11pro64-amd:
visual.c:23014: Test failed: Got unexpected color 0x00000000, case 3.
visual.c:23014: Test failed: Got unexpected color 0x00000000, case 6.
See https://test.winehq.org/data/patterns.html#d3d9:visual
These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In
particular they do not happen on fgtb-w10pro64-rx550 the only other test
machine to have an AMD GPU, nor do they happen on the other Windows 11 test
machines (w11pro64 and w11pro64-nv).
--
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=55390
Bug ID: 55390
Summary: d3d9:visual - test_updatetexture() fails on
w11pro64-amd
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
d3d9:visual - test_updatetexture() fails on w11pro64-amd:
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 0,
12.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 0,
13.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 0,
14.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 0,
15.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 1,
12.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 1,
13.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 1,
14.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 1,
15.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2,
5.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2,
7.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2,
10.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2,
11.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2,
12.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2,
13.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2,
14.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2,
15.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2,
18.
See https://test.winehq.org/data/patterns.html#d3d9:visual
These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In
particular they do not happen on fgtb-w10pro64-rx550 the only other test
machine to have an AMD GPU, nor do they happen on the other Windows 11 test
machines (w11pro64 and w11pro64-nv).
--
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=55389
Bug ID: 55389
Summary: d3d9:visual - test_per_stage_constant() fails on
w11pro64-amd
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
d3d9:visual - test_per_stage_constant() fails on w11pro64-amd:
visual.c:20134: Test failed: Got unexpected color 0x000000ff.
visual.c:20152: Test failed: Got unexpected color 0x000000ff.
visual.c:20170: Test failed: Got unexpected color 0x000000ff.
See https://test.winehq.org/data/patterns.html#d3d9:visual
These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In
particular they do not happen on fgtb-w10pro64-rx550 the only other test
machine to have an AMD GPU, nor do they happen on the other Windows 11 test
machines (w11pro64 and w11pro64-nv).
--
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=55387
Bug ID: 55387
Summary: d3d9:visual - test_fetch4() fails on w11pro64-amd
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
d3d9:visual - test_fetch4() fails on w11pro64-amd:
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff131313 at
(40, 30).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff121212 at
(200, 30).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff111111 at
(360, 30).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff101010 at
(520, 30).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff020202 at
(40, 150).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xfff2f2f2 at
(200, 150).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xfff1f1f1 at
(360, 150).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff010101 at
(520, 150).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff040404 at
(40, 270).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xfff4f4f4 at
(200, 270).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xfff3f3f3 at
(360, 270).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff030303 at
(520, 270).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff232323 at
(40, 390).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff222222 at
(200, 390).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff212121 at
(360, 390).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff202020 at
(520, 390).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(40, 30).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(200, 30).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(360, 30).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(520, 30).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(40, 150).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(200, 150).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(360, 150).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(40, 270).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(200, 270).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(360, 270).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(520, 270).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(40, 390).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(200, 390).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(360, 390).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(520, 390).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff131313 at
(40, 30).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff121212 at
(200, 30).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff111111 at
(360, 30).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff101010 at
(520, 30).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff020202 at
(40, 150).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xfff2f2f2 at
(200, 150).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xfff1f1f1 at
(360, 150).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff010101 at
(520, 150).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff040404 at
(40, 270).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xfff4f4f4 at
(200, 270).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xfff3f3f3 at
(360, 270).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff030303 at
(520, 270).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff232323 at
(40, 390).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff222222 at
(200, 390).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff212121 at
(360, 390).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff202020 at
(520, 390).
See https://test.winehq.org/data/patterns.html#d3d9:visual
These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In
particular they do not happen on fgtb-w10pro64-rx550 the only other test
machine to have an AMD GPU, nor do they happen on the other Windows 11 test
machines (w11pro64 and w11pro64-nv).
--
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=55382
Bug ID: 55382
Summary: d3d9:device - test_draw_primitive() fails on
w11pro64-amd
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
d3d9:device test_draw_primitive() fails on w11pro64-amd:
device.c:3194: Test failed: DrawIndexedPrimitive failed, hr 0x80004005.
See https://test.winehq.org/data/patterns.html#d3d9:device
Where 0x80004005 == E_FAIL
This failure is systematic and only happens on w11pro64-amd (AMD RX 6600). In
particular it does not happen on fgtb-w10pro64-rx550 the only other test
machine to have an AMD GPU, nor does it happen on the other Windows 11 test
machines (w11pro64 and w11pro64-nv).
--
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=55386
Bug ID: 55386
Summary: d3d9:visual - depth_clamp_test() fails on w11pro64-amd
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
d3d9:visual - depth_clamp_test() fails on w11pro64-amd:
visual.c:14932: Test failed: color 0x0000ff00.
visual.c:14934: Test failed: color 0x0000ff00.
visual.c:14936: Test failed: color 0x0000ff00.
visual.c:14938: Test failed: color 0x0000ff00.
visual.c:14940: Test failed: color 0x0000ff00.
See https://test.winehq.org/data/patterns.html#d3d9:visual
These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In
particular they do not happen on fgtb-w10pro64-rx550 the only other test
machine to have an AMD GPU, nor do they happen on the other Windows 11 test
machines (w11pro64 and w11pro64-nv).
--
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=55384
Bug ID: 55384
Summary: d3d9:device - test_update_volumetexture() fails on
w11pro64-amd
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
d3d9:device - test_update_volumetexture() fails on w11pro64-amd:
device.c:10425: Test failed: Failed to update texture, hr 0x80004005, case 6.
device.c:10425: Test failed: Failed to update texture, hr 0x80004005, case 7.
See https://test.winehq.org/data/patterns.html#d3d9:device
Where 0x80004005 == E_FAIL
These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In
particular they do not happen on fgtb-w10pro64-rx550 the only other test
machine to have an AMD GPU, nor do they happen on the other Windows 11 test
machines (w11pro64 and w11pro64-nv).
--
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=55385
Bug ID: 55385
Summary: d3d9:device - test_surface_format_null() fails on
w11pro64-amd
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
d3d9:device - test_surface_format_null() fails on w11pro64-amd:
device.c:9328: Test failed: Expected non-zero pitch, got 0.
device.c:9329: Test failed: Expected non-NULL pBits, got 0000000000000000.
See https://test.winehq.org/data/patterns.html#d3d9:device
These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In
particular they do not happen on fgtb-w10pro64-rx550 the only other test
machine to have an AMD GPU, nor do they happen on the other Windows 11 test
machines (w11pro64 and w11pro64-nv).
--
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=43859
Bug ID: 43859
Summary: Snake Pass: In-game textures appear Black, White or
Fuchsia and are extremely bright.
Product: Wine
Version: 2.17
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jason.bagavatsingham(a)gmail.com
Distribution: ---
Created attachment 59430
--> https://bugs.winehq.org/attachment.cgi?id=59430
Terminal Log
Found:
Upon reaching in-game, the worlds geometry is rendered correctly, but all
assets are extremely bright and appear Black, White or Fuchsia. Some colours
are visible, but overshadowed by the bloominess of the aforementioned colours.
Steps to reproduce:
# Launch Steam.
# Launch Snake Pass.
# Select New Game / Continue and select a level.
Actual Results:
In-game rendering is extremely bright and many of the textures appear
completely White, Black or colours ranging around Fuchsia.
Expected Results:
Texture appears correctly on all assets while in-game.
*Reproduction Rate:*
5/5.
Notes:
Menus / 2D assets appear correctly.
See link below for video of the issues:
https://www.youtube.com/watch?v=f5KtPyHnJyI
Environment:
Wine-Staging 2.18
--
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=42424
Bug ID: 42424
Summary: Error occurs while installing
Renesas_Flash_Programmer_Package_V30201_free.exe.
Product: Wine
Version: 2.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kiwamu(a)debian.or.jp
Distribution: ---
Created attachment 57250
--> https://bugs.winehq.org/attachment.cgi?id=57250
Screen shot when the error occurs
The issue is reproduced by following:
1. Download Renesas_Flash_Programmer_Package_V30201_free.exe from following:
https://www.renesas.com/ja-jp/software/D4000308.html
2. Run the Renesas_Flash_Programmer_Package_V30201_free.exe with following:
$ wine Renesas_Flash_Programmer_Package_V30201_free.exe
3. You should see attached screen shot named "shot.png".
Could you support this issue?
Best regards,
--
Kiwamu Okabe
--
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=47588
Bug ID: 47588
Summary: AmiKitXE crashes on PlayOnLinux 4.3 with Wine
3.21-staging
Product: Wine-staging
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mortenweb43(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 64993
--> https://bugs.winehq.org/attachment.cgi?id=64993
AmiKitXE crashes on PlayOnLinux 4.3 with Wine 3.21-staging
AmiKitXE crashes on PlayOnLinux 4.3 with Wine 3.21-staging
Please help make it work again :-)
Error log is attached.
Thanks
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55380
Bug ID: 55380
Summary: d3d9:d3d9ex - test_swapchain_parameters() fails on
w11pro64-amd
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
d3d9:d3d9ex - test_swapchain_parameters() fails on w11pro64-amd:
d3d9ex.c:3763: Test failed: Expected hr 0, got 0x80004005, test 23.
d3d9ex.c:3799: Test failed: Expected hr 0, got 0x80004005, test 23.
d3d9ex.c:3763: Test failed: Expected hr 0, got 0x80004005, test 25.
d3d9ex.c:3799: Test failed: Expected hr 0, got 0x80004005, test 25.
See https://test.winehq.org/data/patterns.html#d3d9:d3d9ex
Where 0x80004005 == E_FAIL
These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In
particular they don't happen on fgtb-w10pro64-rx550 the only other test machine
to have an AMD GPU, nor do they happen on the other Windows 11 test machines
(w11pro64 and w11pro64-nv).
--
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=41395
Bug ID: 41395
Summary: CreateFile returns a wrong LastError Code when you
pass an invalid path
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: Christoph(a)ApiViewer.de
Distribution: ---
CreateFile returns a wrong LastError Code when you pass an invalid path.
Testcase:
CreateFileA("C:C:\\Windows", GENERIC_READ, FILE_SHARE_READ,
NULL, OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, NULL);
todo_wine ok( GetLastError() == ERROR_INVALID_NAME, "Wrong LastError %d,
expected ERROR_INVALID_NAME\n", GetLastError() );
Which also means the code in cryptnet_main:1025 to line 1048 must be wrong.
--
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=55379
Bug ID: 55379
Summary: kernel32:loader sometimes gets a bad thread count on
Windows 10 in phase 0/1
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:loader sometimes gets a bad thread count on Windows 10 in phase 0/1.
So far there are only two instances, both in the 64-bit tests:
* 2023-07-31 w1064-adm 64-bit tests
loader.c:2875: phase 1: writing 00007FF633B64570 at 0x202
loader.c:2514: dll: 0000000010000000, DLL_PROCESS_ATTACH, 0000000000000000
loader.c:2784: dll: 0000000010000000, DLL_THREAD_ATTACH, 0000000000000000
loader.c:2399: 1eb0: mutex_thread_proc: starting
loader.c:2784: dll: 0000000010000000, DLL_THREAD_ATTACH, 0000000000000000
loader.c:2784: dll: 0000000010000000, DLL_THREAD_ATTACH, 0000000000000000
loader.c:2954: Test failed: attached thread count should be 2
* 2023-06-07 fgtb-w10pro64 64-bit tests
loader.c:2875: phase 0: writing 000000000048FED0 at 0x202
loader.c:2514: dll: 0000000010000000, DLL_PROCESS_ATTACH, 0000000000000000
loader.c:2784: dll: 0000000010000000, DLL_THREAD_ATTACH, 0000000000000000
loader.c:2399: 1414: mutex_thread_proc: starting
loader.c:2784: dll: 0000000010000000, DLL_THREAD_ATTACH, 0000000000000000
loader.c:2784: dll: 0000000010000000, DLL_THREAD_ATTACH, 0000000000000000
loader.c:2954: Test failed: attached thread count should be 2
See https://test.winehq.org/data/patterns.html#kernel32:loader
--
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=55378
Bug ID: 55378
Summary: Can't get resolutions list for scanner
Product: Wine
Version: 8.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ilya.docin(a)contentai.ru
Distribution: ---
Created attachment 74954
--> https://bugs.winehq.org/attachment.cgi?id=74954
Twister Analysis of HP LaserJet MFP M426fdn
OS: Ubuntu 20.04.1
Component: sane.ds
I use Twister utility to analyze some scanners on Wine. Many scanners return
resolutions in a form of array. E.g., HP LaserJet MFP M426fdn. Twister
indicates that getting resolutions for such scanners is unsupported.
Screenshot 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=55375
Bug ID: 55375
Summary: Can't set color mode for scanner
Product: Packaging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: ilya.docin(a)contentai.ru
CC: dimesio(a)earthlink.net
Distribution: ---
Created attachment 74952
--> https://bugs.winehq.org/attachment.cgi?id=74952
Twister analyze for HP LaserJet Pro M428-M429f
OS: Ubuntu 20.04.1
Wine version: wine-8.0.2
Component: sane.ds
I use Twister utility to analyze some scanners on Wine. When it tries to set
color mode to any scanner, both report and Wine log says, that value is not
set.
I attached screenshot with report.
--
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=55376
Bug ID: 55376
Summary: [USER32/NTUSER] Keyboard app accents doesn't change
the keys correctly.
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: julenuri(a)hotmail.com
Distribution: ---
Wine version: 8.13
Environment: Debian 11
Software tested: Accents 1.0 from this web:
https://www.dcmembers.com/skrommel/download/accents/#
Steps to reproduce: The functionality is simple. After 3 or more keyboard
inputs in the letters A, E, I, O, U or Y, you will have accent mark.
1. start the software accents
2. start wine notepad or whatever notepad you want.
3. input 3 "a"
There is a failure somewhere into key hooking process: WH_KEYBOARD_LL,
WM_USER+(number), DWL_MSGRESULT, PM_NOREMOVE, VK_LSHIFT [have a bad value
(-32768)], GetAsyncKeyState, CharLowerA, SetWindowsHookExA, CallNextHookEx,
VkKeyScanExA, MapVirtualKeyA. I'm not sure where because I'm not developer and
I have zero time to check where is exactly the failure.
Expected behavior: It should write å.
Issue: But in fact, it only deletes the input.
Video of the issue: https://youtu.be/B56TUdg3zQ8
Video of example of no issue:
https://www.dcmembers.com/skrommel/wp-content/uploads/sites/2/2017/10/Accen…
We detected the same behaviour in ReactOS too long time ago, but I guess no-one
tested in Wine before: https://jira.reactos.org/browse/CORE-5627
--
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=55332
Bug ID: 55332
Summary: 00d8:fixme:setupapi:CM_Get_Device_Interface_List_SizeW
000000000011F5B8 0000000180045FD8 (null) 0x00000000:
stub
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: usb
Assignee: wine-bugs(a)winehq.org
Reporter: alois.schloegl(a)gmail.com
Distribution: ---
Created attachment 74926
--> https://bugs.winehq.org/attachment.cgi?id=74926
log about trying to run "wine usbip.exe attach ..."
Trying to run
wine usbip.exe attach -r <USBIB_SERVER> -b 1-1.2.4.2
fails with the attached error. The same command on linux
usbip attach -r <USBIB_SERVER> -b 1-1.2.4.2
is working fine. In order to reproduce this, you need
- an usbip server running some linux with hostname or IP-ddress <USBIP-SERVER>,
with some usb-device attached,
- start the usbip deamon with this command:
usbipd -D
- check the busid of the usb device with
usbip list --local
- bind the usb device,
usbip bind --busid=1-1.2.4.2
This provides remote access (port 3240 by default).
Next you install usbip-win2 from
https://github.com/vadimgrn/usbip-win2/releases
in wine, and try to connect to the usbip server with
usbip list --remote=<USBIB_SERVER>
This should show the exported USB devices.
However, the command
wine usbip.exe attach -r <USBIB_SERVER> -b 1-1.2.4.2
will fail with the attached 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.
http://bugs.winehq.org/show_bug.cgi?id=34529
Bug #: 34529
Summary: Game attempts to create and read from root Z:\ drive
instead of C:\ (c_drive) directory.
Product: Wine
Version: 1.7.1
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: nemstar(a)zoho.com
Classification: Unclassified
When running the PC version of the game Shadowgun: Deadzone
(http://www.madfingergames.com/deadzone/) which is free to download and play,
I encounter a problem. The game is attempting to write to the root directory
which is the Z:\ drive by default in wine. It attempts to create a directory
named /users/<player name> with data files that pertain to the game. I know
this because I set up a test bed and used root and the directory /users/<player
name> and files within it were created successfully and the game ran as
intended.
If the Z:\ drive is removed using winecfg (as none root user) and the file is
placed or created in ~/.wine/c_drive/users/<player name>, then the game will
read the correct file on the C: drive and run as intended. If the Z:\ drive is
re-enabled, then the game will try to read from the root file system on Z: and
can not find /user/<player name> so it will not connect to a match or save
settings.
This is the case when ran as any user.
Obviously the game should not be trying to create a new directory under
C:\users in any circumstance, or as Z:\users if root is mounted as Z:\.
--
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=55355
Bug ID: 55355
Summary: My Tally prime server application crashes after some
time
Product: Wine
Version: 6.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winsock
Assignee: wine-bugs(a)winehq.org
Reporter: vikasy.enjay(a)gmail.com
Distribution: ---
Following installation, the application launches when I run tallyserver.exe,
however after a while it fails and displays the message "Tallygateway server
not found" as seen below in the logs:
02d8:fixme:dbghelp_dwarf:dwarf2_parse_variable Unsupported constant (parameter)
"pEncodePara" in function
02d8:fixme:dbghelp_dwarf:dwarf2_parse_variable Unsupported constant (parameter)
"dwFlags" in function
02d8:fixme:dbghelp:MiniDumpWriteDump NIY MiniDumpWithHandleData
02d8:fixme:dbghelp:MiniDumpWriteDump NIY MiniDumpScanMemory
02d8:fixme:dbghelp:x86_64_fetch_minidump_module RunTime_Function outside
IMAGE_DIRECTORY_ENTRY_EXCEPTION unimplemented yet!
02d8:fixme:dbghelp:x86_64_fetch_minidump_module RunTime_Function outside
IMAGE_DIRECTORY_ENTRY_EXCEPTION unimplemented yet!
01dc:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA,
000000000326EBD0
02e0:err:service:process_send_command service protocol error - failed to write
pipe!
02e8:err:service:process_send_command service protocol error - failed to write
pipe!
02f0:err:service:process_send_command service protocol error - failed to write
pipe!
0308:err:service:process_send_command service protocol error - failed to write
pipe!
0310:err:service:process_send_command service protocol error - failed to write
pipe!
0318:err:service:process_send_command service protocol error - failed to write
pipe!
0320:err:service:process_send_command service protocol error - failed to write
pipe!
0328:err:service:process_send_command service protocol error - failed to write
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=55368
Bug ID: 55368
Summary: NtCreateFile broken for non-ASCII with RootDirectory
Product: Wine
Version: 8.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: novae.harpist06(a)icloud.com
Distribution: ---
Created attachment 74950
--> https://bugs.winehq.org/attachment.cgi?id=74950
Reproducer
Output on Windows:
00000000
Output on Wine:
C000003B
relevant logs with +file:
0114:trace:file:NtCreateFile handle=0x11fd38 access=00100001
name=L"\\??\\C:\\test" objattr=00000040 root=(nil) sec=(nil) io=0x11fd40
alloc_size=(nil) attr=00000080 sharing=00000003 disp=3 options=00204021
ea=(nil).0x00000000
0114:trace:file:nt_to_unix_file_name_no_root L"\\??\\C:\\test" ->
"/root/.wine/dosdevices/c:/test"
0114:trace:file:NtCreateFile handle=0x11fd18 access=c0110000 name=L"\0171.txt"
objattr=00000040 root=(nil) sec=(nil) io=0x11fd40 alloc_size=(nil)
attr=00000080 sharing=00000000 disp=3 options=00000020 ea=(nil).0x00000000
0114:warn:file:NtCreateFile L"\0171.txt" not found (c000003b)
--
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=55370
Bug ID: 55370
Summary: ddraw:ddraw4 - test_clipper_blt() sometimes gets an
unexpected bounding rect on Windows and Wine
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
ddraw:ddraw4 - test_clipper_blt() sometimes gets an unexpected bounding rect in
Wine:
ddraw4.c:1115: Test failed: Got unexpected count 0.
ddraw4.c:1116: Test failed: Got unexpected bounding rect (0,0)-(0,0), expected
(18,41)-(642,482).
See https://test.winehq.org/data/patterns.html#ddraw:ddraw4
This is happening on both Windows and Wine and, so far, seems to only happen
during full WineTest runs:
* 2022-12-01 linux_lastestmaster
* 2022-12-03 linux_fgtb-debian11-wow32
* 2022-12-07 win81_newtb-w8
* 2023-01-07 linux_fgtb-debian11-wow32
* 2023-01-13 linux_fg-deb64-t32
* 2023-01-13 linux_fg-deb64-wow64
* 2023-02-02 linux_fgtb-debian11-win32
* 2023-02-11 linux_fgtb-debian11-win32
* 2023-02-28 linux_fgtb-debian11-win32
* 2023-04-13 win22H2_fgtb-w10pro64-rx550-64
* 2023-07-27 win81_newtb-w8
--
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=55369
Bug ID: 55369
Summary: Halo Online / Eldewrito - Dedicated Server errors and
fast upcount
Product: Wine
Version: 8.0.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bogdan17(a)garglob.com
Distribution: ---
When you run the DedicatedServer.bat in Wine, the bat files open in a Wine CMD
window and shows the following...
ElDewrito dedicated server is running! (xxxx)
Can't reconize 'timeout 10 / nobreak ' as an internal or external command, or
batch script
On Windows when you run the DedicatedServer.bat, command prompt will open up
and only display this...
ElDewrito dedicated server is running! (xxxx)
Also the (xxxx) in the brackets are an upcount, on Windows this upcount is slow
and seems to increase by 1 every 10 seconds, on Linux in Wine, it is counting
up raipidly fast.
How it looks in the terminal when I run DedicatedServer.bat and its output...
$ env WINEPREFIX="/path/to/wine/prefix/" "wine "C:\windows\command\start.exe"
/Unix "/path/to/wine/prefix/drive_c/HaloOnline/mods/server/DedicatedServer.bat"
002c:err:wineboot:process_run_key Error running cmd
L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (2).
0074:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0074:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0074:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0074:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0074:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0074:fixme:xinput:pdo_pnp IRP_MN_QUERY_ID type 5, not implemented!
0074:fixme:xinput:pdo_pnp IRP_MN_QUERY_ID type 5, not implemented!
0074:fixme:xinput:pdo_pnp IRP_MN_QUERY_ID type 5, not implemented!
0074:fixme:xinput:pdo_pnp IRP_MN_QUERY_ID type 5, not implemented!
0024:fixme:exec:SHELL_execute flags ignored: 0x00000100
don@homepc:~$ 00e0:fixme:imm:ImeSetActiveContext (00010026, 0): stub
00e0:fixme:imm:ImmReleaseContext (00010020, 00010026): stub
00d8:fixme:imm:ImeSetActiveContext (00010052, 1): stub
00d8:fixme:imm:ImmReleaseContext (0002004A, 00010052): stub
And then the terminal spits out the following output over and over again at a
rapid pase...
012c:fixme:tasklist:wmain stub: L"tasklist" L"/v" L"/fi" L"IMAGENAME eq
eldorado.exe" L"/fi" L"STATUS eq Running"
0134:fixme:findstr:wmain stub: L"findstr" L"eldorado.exe"
013c:fixme:tasklist:wmain stub: L"tasklist" L"/v" L"/fi" L"IMAGENAME eq
eldorado.exe" L"/fi" L"STATUS eq Running"
0144:fixme:findstr:wmain stub: L"findstr" L"eldorado.exe"
014c:fixme:tasklist:wmain stub: L"tasklist" L"/v" L"/fi" L"IMAGENAME eq
eldorado.exe" L"/fi" L"STATUS eq Running"
012c:fixme:tasklist:wmain stub: L"tasklist" L"/v" L"/fi" L"IMAGENAME eq
eldorado.exe" L"/fi" L"STATUS eq Running"
0134:fixme:findstr:wmain stub: L"findstr" L"eldorado.exe"
013c:fixme:tasklist:wmain stub: L"tasklist" L"/v" L"/fi" L"IMAGENAME eq
eldorado.exe" L"/fi" L"STATUS eq Running"
0144:fixme:findstr:wmain stub: L"findstr" L"eldorado.exe"
014c:fixme:tasklist:wmain stub: L"tasklist" L"/v" L"/fi" L"IMAGENAME eq
eldorado.exe" L"/fi" L"STATUS eq Running"
012c:fixme:tasklist:wmain stub: L"tasklist" L"/v" L"/fi" L"IMAGENAME eq
eldorado.exe" L"/fi" L"STATUS eq Running"
0134:fixme:findstr:wmain stub: L"findstr" L"eldorado.exe"
013c:fixme:tasklist:wmain stub: L"tasklist" L"/v" L"/fi" L"IMAGENAME eq
eldorado.exe" L"/fi" L"STATUS eq Running"
0144:fixme:findstr:wmain stub: L"findstr" L"eldorado.exe"
014c:fixme:tasklist:wmain stub: L"tasklist" L"/v" L"/fi" L"IMAGENAME eq
eldorado.exe" L"/fi" L"STATUS eq Running"
--
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=53806
Bug ID: 53806
Summary: Archicad 26: crash at launch
Product: Wine
Version: 7.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: doubleboogieblues(a)yahoo.it
Distribution: ---
Created attachment 73316
--> https://bugs.winehq.org/attachment.cgi?id=73316
terminal output
Wine crash when launched archicad.exe
installation ok, but the software does not start
installed: dotnet452, vcrun2019, vcrun2013
download DEMO Archicad 26:
https://graphisoft.com/dl/AC/26/INT/Archicad-26-INT-3001-1.1.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=52844
Bug ID: 52844
Summary: Call of Duty: Black Ops II stucks with a black screen
after intro
Product: Wine
Version: 7.6
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 72240
--> https://bugs.winehq.org/attachment.cgi?id=72240
log
wine-7.6-211-ge254680ed15
--
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=21448
Summary: RollerCoaster Tycoon 3 does not accept the original
disc
Product: Wine
Version: 1.1.36
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: thomas.mertes(a)gmx.at
Created an attachment (id=25828)
--> (http://bugs.winehq.org/attachment.cgi?id=25828)
Error log and content of message box when starting RollerCoaster Tycoon 3
When starting RollerCoaster Tycoon 3 it asks for the original disc although the
original disk is in. There are some errors logged (see attachment) and then a
message box appears:
Please insert the original disc instead of a backup. See
www.securom.com/copy for more details
Greetings Thomas
--
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=55364
Bug ID: 55364
Summary: Shadow Empire crashes on startup with an error related
to SharpDX and Direct2D.
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kindaro(a)gmail.com
Distribution: ---
_Shadow Empire_ is a computer game. It can be obtained, for example, from Steam
or Good Old Games. I installed what I believe to be version 1.21.00.
This is the gist of the error message that the game gives me:
```
SharpDX.SharpDXException: HRESULT: [0x88990028], Module: [SharpDX.Direct2D1],
ApiCode: [D2DERR_EFFECT_IS_NOT_REGISTERED/EffectIsNotRegistered], Message:
Unknown
```
When I run it as `WINEDEBUG=+d2d wine ShadowEmpire.exe`, I see the following
warning from Wine:
```
0114:warn:d2d:d2d_effect_create Effect id
{9daf9369-3846-4d0e-a44e-0c607934a5d7} not found.
```
I shall be attaching the full text of the error and Wine's output.
My operating system is Arch Linux, recently updated. The failure occurs both
with `wine` and `wine-staging`.
--
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=55232
Bug ID: 55232
Summary: Sierra Chart (All versions): Out of order overlapped
network I/O receive buffers
Product: Wine
Version: 6.0.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: winsock
Assignee: wine-bugs(a)winehq.org
Reporter: sc(a)sierrachart.com
Distribution: ---
Created attachment 74837
--> https://bugs.winehq.org/attachment.cgi?id=74837
Terminal output
We have a code which is working fine for years on Windows OS, but on Linux
using Wine it produces an IO error. Investigation shows that IO
Completion/Overlapped of Wine provides some buffers with received data out of
order. Our code relies on correct order of the received buffers.
Our code provides to OS some minimum number of buffers available to receive a
data. We expect the FIFO logic of the buffer processing: the first provided
available buffer will first receive the data.
Invoke `WSARecv` with a buffer to receive data. The operation is overlapped
using Completion Port.
In a worker thread the function `GetQueuedCompletionStatus` is used to get the
completion notification about received data in the buffer. At this point we
observe a buffer, received out of order. Usually it is happened at beginning of
handling buffers: we provide to OS some set of buffers (in common 16), handle
all of them with received data, reuse available buffers again to OS to support
the minimum set of buffers for OS and most probably the first (or close to
first) reused buffer will be received out of the order.
Also we observe the out-of-order buffer is returned in the same time slot as it
was issued to OS.
Relevant WindowsOS functions used:
CreateIoCompletionPort
WSARecv
GetQueuedCompletionStatus
Download link:
https://www.sierrachart.com/downloads/ZipFiles/SierraChart2522.zip
--
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=55365
Bug ID: 55365
Summary: ntdll:file - test_file_full_size_information()
sometimes gets a bad AvailableAllocationUnits value on
Windows and Wine
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
ntdll:file - test_file_full_size_information() sometimes gets a bad
AvailableAllocationUnits value on Windows and Wine:
file.c:1320: Test failed: [ffsi] CallerAvailableAllocationUnits error
fsi:0x12dbfb5, ffsi: 0x12dbfb6
See https://test.winehq.org/data/patterns.html#ntdll:file
This is very rare as there are only 3 known instances:
* 2023-03-27 linux_gitlab-debian-32
* 2023-06-23 linux_gitlab-debian-32
* 2023-07-27 win21H2_gitlab-win10-21h2-64
This looks very much like a race condition with some other process allocating
or freeing disk space in between the FileFsFullSizeInformation and
FileFsSizeInformation calls. So this is something that should be fixable with
the tryok() API.
https://gitlab.winehq.org/wine/wine/-/merge_requests/3418
--
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=55363
Bug ID: 55363
Summary: Wine depends on a manual user intervention to increase
the soft limit of file descriptors.
Product: Wine
Version: 8.11
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: o.dierick(a)piezo-forte.be
Distribution: ---
Hello,
I recently installed Debian 12 after using Debian 8 for years.
After I reproduced my building environment and successfully build the same Wine
version as the last built on Debian 8, a game that was working fine in Debian 8
did fail to run on Debian 12 with the error 'too many file descriptors open,
you should probably increase ulimit -n'.
The difference is that the default soft/hard limit in Debian 12 is
1024/1048576. In Debian 8 it was 65536/65536. I can increase the soft limit by
running 'ulimit -n 65536' before hand and then the game runs fine.
I could not set the soft limit increase to be permanent and I filed a bug at
Debian for that, but that's not what this bug is about. After reading a bit
about the reason why the soft limit was reduced to 1024 (for compatibility with
select()), my understanding is that a program that is more modern and doesn't
use select(), should be aware of its file descriptor needs and ask for a higher
soft limit. That's what Debian says about its choice to set the soft limit of
1024 and a hard limit of 1048576 by default.
Since the hard limit permits it, I wondered why Wine couldn't increase the soft
limit itself. We know that 1024 is not a reasonable amount of file descriptors
in this time and day and that a number of windows applications requires more
than that. Maybe Wine should set the soft limit to something reasonable itself,
rather than requiring the user to set it like explained in the FAQ? It would
even be better if it was configurable per-application.
Regards.
--
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=55324
Bug ID: 55324
Summary: AllDup doesn't start in win10 mode: "OS not supported"
Product: Wine
Version: 8.13
Hardware: x86-64
URL: https://www.alldup.info/download/AllDupSetup.zip
OS: Linux
Status: NEW
Keywords: download, patch
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Distribution: Debian
Created attachment 74920
--> https://bugs.winehq.org/attachment.cgi?id=74920
patch for IsOS
This program was tried out by someone on the forum.
In default windows 10 mode it pops up a messagbox "OS not supported" and exits.
The attached patch is enough to fix this bug.
--
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=55352
Bug ID: 55352
Summary: NtTerminateThread should accept handle==0 as current
thread
Product: Wine
Version: 8.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: ake.rehnman(a)gmail.com
Distribution: ---
Created attachment 74936
--> https://bugs.winehq.org/attachment.cgi?id=74936
Example using thread handle 0 to NtTerminateThread
Windows accepts thread handle 0 as current thread.
See attached example
Output from example:
c:\temp>test_ntterminatethread.exe
h=0000000000000020
call NtTerminateThread h=0
thread exitcode=1234
--
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=55359
Bug ID: 55359
Summary: SCICompanion crashes when trying to compile
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: menotu3169(a)hotmail.com
Distribution: ---
Created attachment 74940
--> https://bugs.winehq.org/attachment.cgi?id=74940
debugging log
Using SCICompanion ver3.0.1.7
(http://scicompanion.com/Downloads/SCICompanion.zip) the program freezes when
trying to compile. Have only tried it with SCI0 and not SCI1. Doesn't seem to
matter if I try to 'compile all' or just compile a single script. Program
worked fine when tested on Windows 10.
Program will pop-up with a message box saying 'Compiling scripts' but progress
bar doesn't progress and entire program freezes. When frozen, I cannot click on
anything or do anything and have to kill the program.
Program provides a template game which can be used to replicate the issue.
FILE->CREATE NEW GAME-> TEMPLATE: SCI0
then
SCRIPT-> COMPILE or COMPILE ALL
Linux Mint 19 - 4.15.0-213-generic
AMD A6-4400M APU with Radeon(tm) HD Graphics
--
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=55348
Bug ID: 55348
Summary: Hang when running executables built with
AddressSanitizer
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: yshuiv7(a)gmail.com
Distribution: ---
C code:
int main(int argc, char * const* argv){
return 0;
}
Step to reproduce:
1. Build C code with MSVC: `cl /fsanitize=address /Zi a.c`.
2. Run the resulting executable.
Result when running from wine:
0110:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 004B3CC4, 34) stub
0110:err:sync:RtlpWaitForCriticalSection section 00F8C0E0 "?" wait timed out in
thread 0110, blocked by 0000, retrying (60 sec)
0110:err:sync:RtlpWaitForCriticalSection section 00F8C0E0 "?" wait timed out in
thread 0110, blocked by 0000, retrying (60 sec)
...
--
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=55345
Bug ID: 55345
Summary: WRC 4 changing audio volume level has no effect
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: xactengine
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
08f8:fixme:xaudio2:IXACT3CueImpl_SetOutputVoiceMatrix (48AA3F18)->(052BA034 1 2
4AC3D778): stub!
And also there is missing one more parameter.
8.13-43-gb5e19a33c93
--
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=52242
Bug ID: 52242
Summary: Mouse cursor disappears in GTA V when Social Club
overlay is on
Product: Wine
Version: 6.23
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: vutov.martin97(a)gmail.com
Distribution: ---
Whenever you try to open the Social Club overlay, the cursor disappears. If you
manage to press something with it, it works, it just can't be seen.
Sometimes it works, but very rarely. Haven't figured why it works in said
cases.
To reproduce:
Start GTA V
Wait for it to load to home screen
Press "Home" button for Social Club overlay to appear
No mouse
I am new when it comes to Linux so I've no idea where to get a log from. If
someone tells me how I'll be more than glad to do so. I am launching the game
via Lutris with the Rockstar Games Launcher installer.
--
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=55358
Bug ID: 55358
Summary: user32:sysparams - Unexpected value for SM_C*MENUCHECK
on Windows for mixed locale
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:sysparams - Unexpected value for SM_C*MENUCHECK on Windows for mixed
locale:
sysparams.c:2877: Test failed: GetSystemMetrics(SM_CXMENUCHECK): expected 11
actual 15
sysparams.c:2879: Test failed: GetSystemMetrics(SM_CYMENUCHECK): expected 11
actual 15
See https://test.winehq.org/data/patterns.html#gdi32:font
This test succeeds in the other locales which means it fails because the values
it compares depend on two different Windows locales. For reference,
w10pro64-mx-MX is configured with the following locales:
SystemDefaultLCID 0411
UserDefaultLCID 040c
ThreadLocale 0411
SystemPreferredUILanguages 0412,0409
UserDefaultUILanguage 0412
ThreadUILanguage 0412
--
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=55337
Bug ID: 55337
Summary: user32:sysparams - Some fonts are not enumerated in
test_GetSystemMetrics() for the mixed locale
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:sysparams - Some fonts are not enumerated in test_GetSystemMetrics() for
the mixed locale:
sysparams.c:2733: Test failed: font ?? ?? should be enumerated
sysparams.c:2734: Test failed: font ?? ?? should be enumerated
sysparams.c:2735: Test failed: font ?? ?? should be enumerated
sysparams.c:2736: Test failed: font ?? ?? should be enumerated
sysparams.c:2737: Test failed: font ?? ?? should be enumerated
sysparams.c:2877: Test failed: GetSystemMetrics(SM_CXMENUCHECK): expected 11
actual 15
sysparams.c:2879: Test failed: GetSystemMetrics(SM_CYMENUCHECK): expected 11
actual 15
[...]
See https://test.winehq.org/data/patterns.html#gdi32:font
This test succeeds in the other locales which means it fails because the values
it compares depend on two different Windows locales. For reference,
w10pro64-mx-MX is configured with the following locales:
SystemDefaultLCID 0411
UserDefaultLCID 040c
ThreadLocale 0411
SystemPreferredUILanguages 0412,0409
UserDefaultUILanguage 0412
ThreadUILanguage 0412
--
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=55299
Bug ID: 55299
Summary: gdi32:font - test_stock_fonts() gets unexpected
heights in Arabic en Hebrew locales in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
gdi32:font - test_stock_fonts() gets unexpected heights in Arabic en Hebrew
locales in Wine.
In the ar_MA locale:
font.c:6484: Test failed: 0(0): expected height 12, got 13
font.c:6484: Test failed: 4(14): expected height 13, got 14
In the he_IL locale:
font.c:6484: Test failed: 0(1): expected height 12, got 13
font.c:6484: Test failed: 4(14): expected height 13, got 14
See https://test.winehq.org/data/patterns.html#gdi32:font
This happens on both the TestBot's Debian11 and Testing VMs.
--
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=38690
Bug ID: 38690
Summary: corrupted serial communications
Product: Wine
Version: 1.7.38
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jpyle490(a)gmail.com
Distribution: ---
Serial communications are corrupted/laggy/ugly. Tested on a Dell Latitude D630
running Linux Mint 17.1 and Wine 1.7.38 from WineHQ PPA, as well as Wine 1.6.2
on the same hardware from the Ubuntu repo. The issue occurs whether it's the
hardware 16550 serial port or a USB attached one. (In this Linux system case
the USB adapter was Prolific-based.)
I observed the same symptoms on Mac OS X Mavericks, compiling Wine 1.7.43 via
Macports, using an FTDI-based USB adapter.
The primary test scenario included Tera Term 4.87 talking to a Cisco router's
console port at 9600 N,8,1 without flow control. Data back from the Cisco was
incomplete, latent and just generally ugly. Using the same hardware and
minicom running natively in either Linux or OS X there were no issues.
Tera Term to a router provided the cleanest environment in which to observe
what was happening. I can't get serial communications to work properly
regardless of the Windows app or the serially-connected device.
--
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=55323
Bug ID: 55323
Summary: Windows Program Can not find USB Device
Product: Wine
Version: 8.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: usb
Assignee: wine-bugs(a)winehq.org
Reporter: 372909853(a)qq.com
Distribution: ---
Created attachment 74918
--> https://bugs.winehq.org/attachment.cgi?id=74918
wineusb trace log
lsusb:
Bus 003 Device 008: ID 0403:6011 Future Technology Devices International,
Ltd FT4232H Quad HS USB-UART/FIFO IC
Key parts of the log:
0088:trace:wineusb:add_usb_device Adding new device 0x7f738800a810, vendor
0403, product 6011.
0088:trace:wineusb:add_unix_device Adding new device 00007F738801FAF0, vendor
0403, product 6011.
0088:trace:wineusb:add_unix_device Adding new device 00007F738801F9E0, vendor
0403, product 6011.
0088:trace:wineusb:add_unix_device Adding new device 00007F7388014EF0, vendor
0403, product 6011.
0088:trace:wineusb:add_unix_device Adding new device 00007F7388014E50, vendor
0403, product 6011.
0088:trace:wineusb:add_unix_device Adding new device 00007F7388014190, vendor
0403, product 6011.
I did not find any error message about my usb device.
But when I click connect button the windows program report can not find the usb
device.
--
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=54822
Bug ID: 54822
Summary: ddraw:visual - createObjects() crashes on fg-deb64
(Intel GPU)
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: ---
Created attachment 74321
--> https://bugs.winehq.org/attachment.cgi?id=74321
ddraw/tests: Prevent the visual tests from crashing the X server on Intel GPUs.
ddraw:visual - createObjects() crashes on fg-deb64 (Intel GPU[1]):
ddraw:visual start dlls/ddraw/tests/visual.c
ddraw:visual:06d0 done (0) in 2s 0B
See https://test.winehq.org/data/patterns.html#ddraw:visual
So this is a case of premature exit. A look at the logs immediately reveals the
cause of the silent crash:
X Error of failed request: BadValue (integer parameter out of range for
operation)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 7 (RRSetScreenSize)
Value in failed request: 0x0
Serial number of failed request: 35
Current serial number in output stream: 36
Running the test with WINETEST_REPORT_SUCCESS=1 and adding some traces shows
the X error happens on this createObjects() line:
112 hr = IDirectDraw7_SetDisplayMode(DirectDraw, 640, 480, 32, 0, 0);
Replacing the 32 bit depth with 24 results in the call returning 0x80004001
(E_NOTIMPL) instead of crashing (that's an odd error code btw). So an easy
workaround would be to use the attached patch.
However:
* This causes most (if not all) of the tests to be skipped.
* My GPU and screen do support 640x480.
* Also running ddraw:visual from my development tree results in 0 skips and 0
failures!
So getting successful runs should be possible (just not in the 3 clean
out-of-tree builds I use to run WineTest :-( ). It's either a matter of
figuring out which is the miraculous patch or where the memory corruption comes
from.
[1] This is an Intel HD Graphics 4600 GPU (comes in the i7-4790K CPU).
--
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.