https://bugs.winehq.org/show_bug.cgi?id=55283
Bug ID: 55283
Summary: amstream:amstream systematically crashes and times out
on gitlab-debian-32
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: major
Priority: P2
Component: quartz
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
amstream:amstream systematically crashes and times out on gitlab-debian-32:
Unhandled exception: assertion failed in wow64 32-bit code (0xf7f19559).
Backtrace:
=>0 0xf7f9a559 __kernel_vsyscall+0x9() in [vdso].so (0xf7f34ff4)
1 0xf7da21d7 in libc.so.6 (+0x8a1d7) (0xf7f34ff4)
2 0xf7d510d1 in libc.so.6 (+0x390d1) (0xf7f34ff4)
3 0xf7d3a26a in libc.so.6 (+0x2226a) (0xf7f34ff4)
4 0x71a4de79 in libllvm-15.so.1 (+0x875e79) (0x0022e910)
5 0x00000040 (0x00000040)
0xf7f9a559 __kernel_vsyscall+0x9 in [vdso].so: pop %ebp
See https://test.winehq.org/data/patterns.html#amstream:amstream
The failures started on 2023-07-10 which corresponds to the GitLab CI switch to
Debian 12.
What makes this very bad is that the failure is systematic so every single
merge request has been getting a GitLab CI error since then.
So it is pretty urgent to either:
1. Fix the test if something is wrong with it.
2. Fix the gitlab-debian-32 test environment if it is wrong.
3. Skip amstream:amstream if neither of the above is doable in a reasonable
timeframe.
--
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=53171
Bug ID: 53171
Summary: advapi32:registry - test_performance_keys() sometimes
fails due to time going backwards!
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
advapi32:registry - test_performance_keys() sometimes fails due to time going
backwards:
registry.c:3757: Test failed: key FFFFFFFF80000004: value (null): got times
132999520626290092, 132999520626290092, 132967560392269933
registry.c:3763: Test failed: key FFFFFFFF80000004: value (null): got times
132999520626290092, 132999520626290000, 132967560392269933
https://test.winehq.org/data/patterns.html#advapi32:registry
This failure is pretty rate: I only found 4 cases (~0.9%):
win2009_newtb-w1064-tsign, win21H1_newtb-w10pro64-mx-MX, 2x
win21H2_fgtb-w10pro64.
The failure lines above happened on w10pro64-mx-MX on 2022-06-17. Here are the
corresponding timestamps:
systime1 = 132999520626290092 = 2022-06-17 15:07:42.629009
file_time = 132999520626290000 = 2022-06-17 15:07:42.629000
systime2 = 132967560392269933 = 2022-05-11 15:20:39.226993
file_time is a little lower than systime1 which is normal due to its
granularity.
What is totally wrong however is that systime2 is way lower than systime1. The
interesting part is that the live snapshot was created on 2022-05-11 which
matches systime2. This scenario is confirmed it two of the other instances; the
snapshot creation time for the last case is unknown but a match with systime2
is plausible.
After restoring the VM from the live snapshot LibvirtTool sets the VM time
through TestAgent::SetTime():
https://gitlab.winehq.org/winehq/tools/-/blob/master/testbot/bin/LibvirtToo…https://gitlab.winehq.org/winehq/tools/-/blob/master/testbot/src/testagentd…
So it looks like in rare cases the system time gets reset backwards precisely
between this test's two NtQuerySystemTime() calls, which is really unlucky...
or lucky: maybe it happens in other cases causing less obvious failures.
I don't know if TestAgentd sets the time wrong, if there's something wrong with
Windows, or if this is an artifact of the QEmu clocks:
<clock offset='localtime'>
<timer name='rtc' tickpolicy='delay'/>
<timer name='pit' tickpolicy='delay'/>
<timer name='hpet' present='yes'/>
<timer name='hypervclock' present='yes'/>
</clock>
--
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=52492
Bug ID: 52492
Summary: stack overflow from GdipFlattenPath
Product: Wine
Version: 7.1
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdiplus
Assignee: wine-bugs(a)winehq.org
Reporter: rjfeuerbach(a)gmail.com
Created attachment 71787
--> https://bugs.winehq.org/attachment.cgi?id=71787
test patch to replicate the curves and stack overflow
I have a third party application, unfortunately not available for download,
that is generating a virtual stack overflow error. Using +replay and
eventually +gdiplus messages, the cause was narrowed down to be due to calls to
GdipFlattenPath.
Attached is a patch to gdiplus/test/graphicspath.c to include the precise
curves that cause the stack overflow.
I believe the problem is due to the comparison of REALs with == in the
flatten_bezier helper function.
--
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=55422
Bug ID: 55422
Summary: mfmediaengine:mfmediaengine - test_GetDuration() fails
in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: mfplat
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
mfmediaengine:mfmediaengine - test_GetDuration() fails in Wine:
mfmediaengine.c:1961: Test failed: Unexpected res 0x102.
See https://test.winehq.org/data/patterns.html#mfmediaengine:mfmediaengine
This failure started with the commit that introduced the tests:
commit 613d7b099986828212299a8e98179f22c86b80ab
Author: Zhiyi Zhang <zzhang(a)codeweavers.com>
Date: Fri Aug 4 17:35:04 2023 +0800
mfmediaengine/tests: Test IMFMediaEngine::GetDuration().
--
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=54720
Bug ID: 54720
Summary: Spider-Man: Shattered Dimensions - dialogue audio
doesn't play
Product: Wine
Version: 8.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: xaudio2
Assignee: wine-bugs(a)winehq.org
Reporter: tinozzo123(a)tutanota.com
Distribution: ---
Created attachment 74226
--> https://bugs.winehq.org/attachment.cgi?id=74226
Logs taken with a clean 32 bit prefix with 32 bit Wine devel 8.4,
WINEDEBUG=+xactengine,+xaudio2,+x3daudio.
In Spider-Man: Shattered Dimensions, the audio that is supposed to be played by
the characters during in-game dialogues doesn't play.
All the other kinds of audio work.
A workaround to this is by installing xact with winetricks.
--
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=44816
Bug ID: 44816
Summary: Cygwin/MSYS2 `script -e` exit status forwarding
randomly returns zero for non zero child process
Product: Wine
Version: 3.4
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Distribution: ---
Hello folks,
to track
https://github.com/wine-staging/wine-staging/tree/master/patches/ntdll-Deal…
Mentioned here:
https://wine-staging.com/news/2015-08-23-release-1.7.50.html
--- quote ---
Do not allow to deallocate thread stack for current thread (MSYS2, Wine Staging
Bug #241)
--- quote ---
After some archaeology I found the Cygwin mailing list discussion here:
https://cygwin.com/ml/cygwin/2015-09/msg00114.html
--- quote ---
> Ah, ok. What OS does Wine emulate here? Have a look at
> https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/cygt…
>
> The terminate_thread_frees_stack flag is set to false for XP/2003 and to
> true for any newer OS. I guess this is a double-free because Wine's
> TerminateThread already freed the stack and Cygwin got the info it's
> supposedly running under XP/2003, so it tries to workaround the fact
> that TerminateThread on these systems didn't free the stack by themselves.
>
Wine emulates Windows XP here, I double checked Wine source code and I
can confirm Wine doesn't free the stack:
NtTerminateThread() -> abort_thread() -> terminate_thread()
https://github.com/wine-compholio/wine-patched/blob/8b3a785e97a7e28ff58731b…
Cygwin reports wincap as wincap_xpsp2 which is also correct here.
> we need to know what address ret=61005767 is refering to. addr2line would help.
As you point out, ret=61005767 is the call to VirtualFree() inside
cygthread::terminate_thread ()
https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/cygt…
After combine the information we have so far, I think the problem is
clear now. It's not Cygwin's fault, it's Wine's fault. Wine's
WaitForSingleObject() needs to wait long enough after the
TerminateThread() call, so the target thread has enough time to finish
the system cleanup and return correct exit_code before Cygwin call
VirtualFree to free the stack. But in our current implementation
Wine's WaitForSingleObject returns too early, it shouldn't return
before the system thread cleanup done, as a result there is a race
here. We are thinking of a solution in Wine. Thanks again for the
great help!
--- quote ---
$ wine --version
wine-3.4
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.
http://bugs.winehq.org/show_bug.cgi?id=30655
Bug #: 30655
Summary: GRID2: Low (1 - 3) FPS during race, but not in in-game
menus.
Product: Wine
Version: 1.5.2
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: linards.liepins(a)gmail.com
Classification: Unclassified
Created attachment 40128
--> http://bugs.winehq.org/attachment.cgi?id=40128
in-game benchmark test #!
Game itself installed with latest winetricks.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=28603
Bug #: 28603
Summary: Winedbg sometimes receives invalid parameters
Product: Wine
Version: 1.3.29
Platform: x86
URL: http://www.winehq.org/pipermail/wine-patches/2011-Sept
ember/106508.html
OS/Version: Linux
Status: NEW
Keywords: download, source, testcase
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
CC: julliard(a)winehq.org
Classification: Unclassified
Created attachment 36753
--> http://bugs.winehq.org/attachment.cgi?id=36753
relay,seh,tid,dbghelp,winedbg
I sent a patch to eliminate this dialog:
http://www.winehq.org/pipermail/wine-patches/2011-September/106508.html
but Alexandre said this should never happen. I see it occasionally on various
systems, but since I wrote the patch, haven't found a very reliable testcase.
I've found a reliable testcase with make test on Alpine Linux (which uses
uclibc).
It may not be the best testcase, since it's not using glibc (and also use PaX),
but AJ asked for a log, so here we go :).
relay,seh,tid,dbghelp,winedbg attached
the testcase used was oleaut32/tmarshal
wine-1.3.29-217-g5432611
--
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=55258
Bug ID: 55258
Summary: steam: small window floating on top of all windows
even in fullscreen mode
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: idarktemplar(a)mail.ru
Distribution: ---
Created attachment 74873
--> https://bugs.winehq.org/attachment.cgi?id=74873
steam_window_bug.png
When running steam with new versions of wine, I'm getting a small square window
which is always on top of all windows, even when I'm playing fullscreen game.
It's usually located around center of screen for me, but during bisecting I
also got a few builds when it appeared at top left corner.
I've tested it with following wine versions:
wine 7.0.2: win7 prefix: good
wine 7.0.2: win10 prefix: does not start
wine 8.0.1: win7 prefix: good
wine 8.0.1: win10 prefix: good
wine 8.9: win10 prefix: bad
wine 8.12: win10 prefix: bad
After that I ran git bisect with following build:
mkdir build32 build64
cd build64
../configure --with-mingw --enable-win64 --prefix=/tmp/wineinstall
cd ../build32
../configure --with-mingw --with-wine64=../build64 --prefix=/tmp/wineinstall
cd ../build64
make $JOBS
cd ../build32
make $JOBS
make $JOBS install
cd ../build64
make $JOBS install
My results are:
2504a2d7bca47fc77bb523114d7b0b6e60213116 is the first bad commit
commit 2504a2d7bca47fc77bb523114d7b0b6e60213116
Author: Rémi Bernon <rbernon(a)codeweavers.com>
Date: Mon Mar 27 11:58:50 2023 +0200
imm32: Keep the IME UI window on the default input context.
dlls/imm32/imm.c | 61 ++++++++++++++++++++++++++++++++------------------------
1 file changed, 35 insertions(+), 26 deletions(-)
$ git bisect log
# bad: [9ffeb2622d087a6189ca916553529824791010c3] Release 8.9.
# good: [d8b2687760f7c07eaf481aba2835b820d3092b3e] Release 8.0.1.
git bisect start 'wine-8.9' 'wine-8.0.1'
# skip: [6677c044abb711f423fadfb61f2c9a37da6ff686] Release 8.0.
git bisect skip 6677c044abb711f423fadfb61f2c9a37da6ff686
# good: [7771a9ae79930d112051cfe18b27dec1e5edd245] widl: Simplify attribute
creation with either int or ptr value.
git bisect good 7771a9ae79930d112051cfe18b27dec1e5edd245
# bad: [d1c317720ab6a92811c013408844ffd9e581b2a2] mfreadwrite: Fix an address
of operator typo.
git bisect bad d1c317720ab6a92811c013408844ffd9e581b2a2
# bad: [66bef6db20f72e88a38c4b264e13639015d7817d] msvcrt: Use the sinhf()
implementation from the bundled musl library.
git bisect bad 66bef6db20f72e88a38c4b264e13639015d7817d
# bad: [17fbef91929af9c6ab98e53fb2a54942f0f1a0a5] wmvcore/tests: Don't cast
NULL to another pointer type.
git bisect bad 17fbef91929af9c6ab98e53fb2a54942f0f1a0a5
# skip: [83f0862b43f7b1b7bd23830b4339894c35febea7] wineps: Handle
EMR_SETARCDIRECTION record in spool files.
git bisect skip 83f0862b43f7b1b7bd23830b4339894c35febea7
# good: [6a88500af29b82040f0518eb87171ca047fb95aa] hidparse.sys: Include
zero-count reports in cap count.
git bisect good 6a88500af29b82040f0518eb87171ca047fb95aa
# good: [62ef3c5be1d2c5374399984588a9daa75663d030] taskkill: Factor out
get_task_pid().
git bisect good 62ef3c5be1d2c5374399984588a9daa75663d030
# bad: [956541c9c823fb6048047893545dcee4c108730e] d3d10/effect: Add support for
umin/umax instructions.
git bisect bad 956541c9c823fb6048047893545dcee4c108730e
# good: [4b04d357739f261457316d55b79ecbcff9c0be84] imm32/tests: Add explicit
ImmLoadIME / ImmFreeLayout calls.
git bisect good 4b04d357739f261457316d55b79ecbcff9c0be84
# bad: [2504a2d7bca47fc77bb523114d7b0b6e60213116] imm32: Keep the IME UI window
on the default input context.
git bisect bad 2504a2d7bca47fc77bb523114d7b0b6e60213116
# good: [9117ce4185146a5edd47467d370b3e4dfa588191] imm32/tests: Test
ImmProcessKey with the installed IME.
git bisect good 9117ce4185146a5edd47467d370b3e4dfa588191
# good: [43e22eaa76a443e3053868df1bd8c5d4130a9fde] imm32/tests: Test IME UI
window and IME window presence.
git bisect good 43e22eaa76a443e3053868df1bd8c5d4130a9fde
# good: [0ddad3564f3260f53e5a50b615f6aa6ba27e032b] imm32: Update existing input
contexts on layout change.
git bisect good 0ddad3564f3260f53e5a50b615f6aa6ba27e032b
# first bad commit: [2504a2d7bca47fc77bb523114d7b0b6e60213116] imm32: Keep the
IME UI window on the default input context.
OS: Gentoo Linux Amd64
Kernel: 6.1.38-gentoo
DE: KDE 5.27.5
glxinfo:
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon RX 7900 XTX (gfx1100, LLVM 16.0.6, DRM 3.49,
6.1.38-gentoo.65)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 23.1.3
OpenGL core profile shading language version string: 4.60
--
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=54413
Bug ID: 54413
Summary: ws2_32:sock - DuplicateHandle(socket) sometimes look
like a socket in test_WSAGetOverlappedResult() on
Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: winsock
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ws2_32:sock - DuplicateHandle(socket) sometimes look like a socket in
test_WSAGetOverlappedResult() on Windows:
sock.c:12512: Test failed: got 1.
sock.c:12513: Test failed: got 0.
See https://test.winehq.org/data/patterns.html#ws2_32:sock
This failure is pretty rare, there are only 4 known instances:
* 2022-09-27 on w1064 64 bit (21h2)
* 2022-11-15 on w10pro64-hi-u8 64 bit (21h1)
* 2023-01-25 on w11pro64 64 bit (21h2)
* 2023-01-25 on w1064v2009 64 bit
The test creates a socket, treats it as a handle and duplicates it, then checks
whether the duplicate handle behaves like a socket which it normally does not,
causing WSAGetOverlappedResult() to fail (return 0) and WSAGetLastError() to be
set to WSAENOTSOCK.
But in these four cases WSAGetOverlappedResult() succeeded which would indicate
the duplicate handle looked like a socket?
--
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=44546
Bug ID: 44546
Summary: The Settlers II: 10th Anniversary runs very slow when
CSMT enabled
Product: Wine
Version: 3.2
Hardware: x86
URL: https://www.fileplanet.com/165168/160000/fileinfo/The-
Settlers-II:-10th-Anniversary-Demo-v9801
OS: Linux
Status: NEW
Keywords: performance
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
Distribution: ---
The game is running painfully slow in Wine 3.2. Can be observed while it is
playing the opening video, in the menus and during gameplay too. Loading times
are also incredibly long when csmt is enabled.
Disabling csmt makes the game run smoothly. There is nothing suspicious in the
terminal.
Can be reproduced with the demo version. I have native d3dcompiler_43 and
d3dx9_29 installed.
settlers2_demo2_multilang.exe (318M)
md5sum: c738916e0f5f4c9b780898f66e50941f
Wine 3.2
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 730/PCIe/SSE2
OpenGL core profile version string: 4.5.0 NVIDIA 390.25
--
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=55291
Bug ID: 55291
Summary: gdi32:dc - print_something() gets a bad signature on
fg-deb64-*
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:dc - print_something() gets a bad signature on fg-deb64-*:
dc.c:1501: Test failed: wrong signature:
See https://test.winehq.org/data/patterns.html#gdi32:dc
This does not depend on bitness, happens systematically and a bisect shows that
the failure started with the commit below:
commit d5373ef6f92d36971859db0746600188ada22a7d
Author: Piotr Caban <piotr(a)codeweavers.com>
Date: Sun Jul 9 13:05:42 2023 +0200
wineps: Buffer data sent to printer port.
--
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=55231
Bug ID: 55231
Summary: Warframe: camera/mouse stuck in X-axis
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: pmargeti34(a)gmail.com
Distribution: ---
Wine 8.12 introduces a regression in Warframe: there seems to be a hard limit
to how much camera can be turned on the X-axis. After spinning the camera in
the same direction a few times, it gets stuck and it's no longer possible to
turn in in that direction until it is first turned in the opposite direction.
This happens when Warframe is either in full screen mode or borderless
fullscreen mode. Windowed mode isn't affected.
Warframe is a free to play game and the installer can be obtained here:
https://www.warframe.com/download
OS: Archlinux Linux 6.4.3
--
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=55152
Bug ID: 55152
Summary: Crash in Notepad++ processing a WM_DRAWITEM message
Product: Wine
Version: 8.11
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: win32u
Assignee: wine-bugs(a)winehq.org
Reporter: julliard(a)winehq.org
Distribution: ---
Running the 32-bit Notepad++ 8.5.4 in new wow64 mode crashes on startup when
processing a WM_DRAWITEM message. The exception is swallowed by win32u so it
still works, but we get a message:
0024:err:seh:KiUserCallbackDispatcher ignoring exception
The root cause is that because Notepad++ added a WH_CALLWNDPROC hook, in win32u
process_message(), instead of returning to SendMessageW and have it call the
winproc, we call it ourselves through KeUserModeCallback. But at that point the
message has been converted to 64-bit so we pass a (truncated) 64-bit lparam to
the 32-bit winproc.
The crash was revealed by a82238fad52761114ab2488d422fad3f70dbb854, which moves
the 64-bit stack to high memory. Previously the lparam pointer would fit in
32-bit which avoided the crash, but it would still point to a 64-bit
DRAWITEMSTRUCT.
--
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=51443
Bug ID: 51443
Summary: Test fails in remove_dir_all crate when creating file
Product: Wine
Version: 6.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mikrutrafal(a)protonmail.com
Distribution: ---
Hi,
Steps to reproduce on clear wine-devel 6.12
```
wget https://static.rust-lang.org/dist/rust-1.53.0-x86_64-pc-windows-gnu.msi
msiexec /i rust-1.53.0-x86_64-pc-windows-gnu.msi
git clone https://github.com/XAMPPRocky/remove_dir_all.git
cd remove_dir_all
git checkout 9b164cecdb4a0590af68be8b22f9c747402237e3
wine cargo test
```
should print this
```
running 4 tests
test removes_read_only ... FAILED
test removes_empty ... ok
test removes_files ... ok
test removes_dirs ... ok
failures:
---- removes_read_only stdout ----
thread 'removes_read_only' panicked at 'called `Result::unwrap()` on an `Err`
value: Os { code: 5, kind: PermissionDenied, message: "Access denied." }',
tests\windows.rs:68:49
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
failures:
removes_read_only
test result: FAILED. 3 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out;
finished in 0.01s
error: test failed, to rerun pass '--test windows'
```
I tested it and this works fine in Windows Server 2019
Source code of failed test -
https://github.com/XAMPPRocky/remove_dir_all/blob/9b164cecdb4a0590af68be8b2…
```
fn removes_read_only() {
env_logger::init();
for i in 0..5 {
let path = format!("./readonly/{}/subdir", i);
fs::create_dir_all(&path).unwrap();
let file_path = format!("{}/file.txt", path);
{
let file = File::create(&file_path).unwrap();
```
--
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=55449
Bug ID: 55449
Summary: Yaesu Wires-X offline and no internet
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: oleacc
Assignee: wine-bugs(a)winehq.org
Reporter: michael.vencio(a)gmail.com
Distribution: ---
Created attachment 75008
--> https://bugs.winehq.org/attachment.cgi?id=75008
debug output
Yaesu Wires-X is an amateur radio application
https://www.yaesu.com/jp/en/wires-x/index.php
the application is installed and running but cannot connect to the internet.
attached is the debug log file.
--
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=34374
Bug #: 34374
Summary: Mac driver does not respect "Emulate a virtual
desktop" option
Product: Wine
Version: 1.7.0
Platform: x86
OS/Version: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winemac.drv
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: samael5(a)verizon.net
Classification: Unclassified
The Mac driver launches all apps in fullscreen mode, regardless of whether
"Emulate a virtual desktop" is set. Virtual desktop still functions as expected
when using the X11 driver on Mac.
--
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=39012
Bug ID: 39012
Summary: Game "Yesterday" crashes while being played (OS X
Yosemite)
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: deka95500(a)hotmail.com
Hi everyone,
I have a version of Yesterday that was built using a wrapper from this
website(external link).
Everything worked fine until I reached the 3rd stage. The game was stuck on a
loading screen and eventually crashed before showing a message saying:
"Yesterday.exe has encountered a serious problem and needs to close."
The wrapper is using Wineskin 2.5.8 / WS8Wine1.3.16. I'm using Mac OS X
Yosemite 10.10.3 on a 2013 MBP.
Can you please help me figure out what the issue is?
Thank you!
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=14713
Summary: Xara Xtreme 4: Resizing handles not visible
Product: Wine
Version: 1.1.2
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: info(a)linopus.de
Xara Xtreme 4: Resizing handles not visible
Xara Xtreme 4, the latest edition of the vector drawing application from Xara
(30 days trial available at http://www.xara.com/us/downloads/xtreme/ ), shows
no resizing handles when selecting an object. The resizing handles should be
visible when clicking an object with the select tool.
By contrast, the turning/shearing handles are visible. The turning/shearing
handels appear when clicking an object twice with the select tool.
Additionally, Bezier handles and points on curves do appear, but in wrong
colors (cyan instead of red). Bezier handles and points appear when using the
edit shape tool.
This is on a wine 1.1.2 install on Ubuntu Linux 8.04 in its standard settings.
The same bug is present when using Xara Xtreme X1, which is the thirdlast
edition. The bug is also present in earlier versions of wine (e.g. 0.9.56) and
CrossOver (e.g. 7.0.1).
Yours sincerely
Tobias Hilbricht
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=10471
Summary: Radmin viewer 3.1: Ungrayed disabled menu item in the
"Connection Properties" window
Product: Wine
Version: 0.9.48.
Platform: PC
URL: http://www.famatech.com/download/rview31.exe
OS/Version: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: wine-gui
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: bugs.radmin(a)gmail.com
We got an error:
1. Installed Radmin server 3.1 (http://www.famatech.com/download/rserv31.exe)
on a windows computer.
2. Installed Radmin viewer 3.1 on a linux computer with wine installed.
3. Started Radmin viewer and open "Connection Properties" window (can be
reached "Right click on connection icon" --> "Properties" or "Connection" -->
"Connect to").
The list of intermediate hosts in "Advanced settings" should be grayed
(disabled) until checkbox "Connect through host" is marked.
The error was tested on Fedora Core 7 installation with the last wine package
from fedora update site (fedora_mirror/fedora/linux/updates/7/i386/).
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41267
Bug ID: 41267
Summary: Black ops 2 crashes with "Unhandled exception caught"
Product: Wine
Version: 1.9.18
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: spleefer90(a)gmail.com
Distribution: ---
Created attachment 55567
--> https://bugs.winehq.org/attachment.cgi?id=55567
crash log when trying to launch the game(BO2:MP) from Steam
Game crashes on startup with the message:
"Error during initialization:
Unhandled exception caught"
--
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=55447
Bug ID: 55447
Summary: wine cannot parse valid javascript
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: jscript
Assignee: wine-bugs(a)winehq.org
Reporter: yshuiv7(a)gmail.com
Distribution: ---
jscript cannot parse the code below:
var O = { continue: 1 };
var x = {
label: O.continue
};
it reports:
0024:warn:jscript:script_parse parser failed around L"bel: O.continue\n
};\n});\n" in line L"sync_test(\"ASDF\", function() {"
Native Windows jscript doesn't have a problem with this.
The cause, I believe, is jscript inserted a semicolon after the "continue".
--
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=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=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.
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.
https://bugs.winehq.org/show_bug.cgi?id=55349
Bug ID: 55349
Summary: ddraw:ddraw7 - test_window_position() sometimes fails
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: ---
ddraw:ddraw7 - test_window_position() sometimes fails in Wine:
ddraw7.c:18843: Test failed: Expect window rect (0,0)-(800,600), got
(0,0)-(1024,768).
ddraw7.c:18899: Test failed: Expect window rect (0,0)-(800,600), got
(0,0)-(1023,767).
ddraw7.c:18906: Test failed: Expect window rect (0,0)-(800,600), got
(0,0)-(1023,767).
See https://test.winehq.org/data/patterns.html#ddraw:ddraw7
This is was pretty common until 2023-01-10 but then it stopped and only
happened a couple of times recently on the GitLab CI:
* 2023-07-26 MR!3413
* 2023-07-20 gitlab-debian-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=52065
Bug ID: 52065
Summary: Rockstar Games Launcher Installer is leaking memory
Product: Wine
Version: 6.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sashok.olen(a)gmail.com
Distribution: ---
When installing Rockstar Games Launcher via its installer, the installer never
quits and is shown to be stuck on the loading bar. During that, the app is
leaking memory really fast, filling up my 32GBs of ram in approximately 1
minute.
I can only track the issue down to 6.20 since that's the version the installer
started working at, but it's present in 6.22 too.
Strangely enough, after you kill its process, the installer actually succeeds
at its jos and successfully installs the launcher.
I don't know what I can provide to help with this, apart from the link to the
installer, so let me know.
--
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=54885
Bug ID: 54885
Summary: The child window flickers after using SetParent API to
set parent-child window between windows from different
processes.
Product: Wine
Version: 8.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bcjon07(a)gmail.com
Distribution: ---
After using the SetParent API to set parent-child window relationship between
windows from different processes, the child window flickers heavily. This issue
seriously affects the user experience of applications that has any different
processes parent-child window. For convenience, I have created a simple demo
program that can reproduce this issue and attached the download link.
Steps to Reproduce:
1.Download the demo program that can reproduce this issue and open it
(SetParentDemo.exe inside) with Wine tool.
2.Click the first button in the program window (the program may crash
occasionally, but it is not the focus of this bug report, just retry the
operation).
3.Drag child window or switch to activate parent child windows, or move mouse
to hover buttons, observe the display of the child window.
Download link of the demo program:
https://drive.google.com/file/d/1MCrnb1N6cLUzVoX_vO4tFO4qlS_qhAwi/view?usp=…
Other clues: After testing, this issue will occur in WPF form programs packaged
using. NET 6 standalone mode, but it does not occur in programs packaged under
the .NET Framework project (will run on wine mono). Unfortunately, many
applications released using Dotnet standalone mode will only run on their
built-in NET runtime and not on Wine Mono.
System architecture:
x86_64
Ubuntu 20.04
wine 8.6
I appreciate your attention to this matter. If you need further cooperation or
assistance, please feel free to contact me.
--
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=55320
Bug ID: 55320
Summary: Multiple games require vertex buffer output not lower
than 32.
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: patch
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 74914
--> https://bugs.winehq.org/attachment.cgi?id=74914
patch
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
16.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
17.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
18.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
19.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
20.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
21.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
22.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
23.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
24.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
25.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
26.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
27.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
28.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
29.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
30.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
31.
The following games are affected:
ACE COMBAT 7: SKIES UNKNOWN
Fallout 4
Grand Theft Auto V
Halo: The Master Chief Collection
Hellblade: Senua’s Sacrifice
State of Decay 2: Juggernaut Edition
Stray
The Dark Pictures Anthology: House of Ashes
The Dark Pictures Anthology: Little Hope
The Dark Pictures Anthology: Man of Medan
The Quarry
--
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=54189
Bug ID: 54189
Summary: Fail in SetupDiEnumDeviceInfo: err=259: No more data
available.
Product: Wine
Version: 8.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alois.schloegl(a)gmail.com
Distribution: ---
Created attachment 73724
--> https://bugs.winehq.org/attachment.cgi?id=73724
winedebug logfile trying to install winsupp.exe/ced1401 drivers under
wine/8.0rc1
Trying to install ced1401 drivers [1,2] fails with the attached debug log.
The attached log was generated with WINEARCH=win32, when using WINEARCH=win64
the same error is shown, only the 64bit driver is mentioned in the log file.
[1] https://ced.co.uk/files/winsupp.exe
[2] https://appdb.winehq.org/objectManager.php?sClass=version&iId=41230
--
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=38101
Bug ID: 38101
Summary: Devil May Cry 4 flickering/texture tearing to eventual
white screen
Product: Wine
Version: 1.7.34
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: shomari.sharpe(a)gmail.com
Distribution: ---
on starting the game (Directx 9c version) there is lots of flicker present.
Upon turning "ON" the VSYNC option in the game the flicker is reduced. The
title screen will display until it eventually turns to a black and white
alternating flickering.
--
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=39806
Bug ID: 39806
Summary: Devil May Cry 4 Frozen Screen Glitch
Product: Wine
Version: unspecified
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: dijscales(a)gmail.com
Created attachment 53141
--> https://bugs.winehq.org/attachment.cgi?id=53141
Details of the Problem
The screen will randomly freeze while I am playing the game. I can't even play
for very long before it freezes. I tried to fix it by changing the config.ini,
but that did nothing.
--
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=45711
Bug ID: 45711
Summary: Devil May Cry 4 DX10: Transparent sections of textures
rendered as solid black or grey
Product: Wine
Version: 3.14
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx10
Assignee: wine-bugs(a)winehq.org
Reporter: nenxvrr4.tgj(a)20mail.it
Distribution: ---
Created attachment 62142
--> https://bugs.winehq.org/attachment.cgi?id=62142
Forest level in Devil May Cry 4 illustrating problem.
Transparent sections of textures are rendered as solid black or grey e.g a leaf
appears as a leaf on a black rectangle. This also affects other assets such as
paintings.
--
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=45712
Bug ID: 45712
Summary: Devil May Cry 4 DX10: Shadows are rendered as
"lights", vice versa
Product: Wine
Version: 3.14
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx10
Assignee: wine-bugs(a)winehq.org
Reporter: nenxvrr4.tgj(a)20mail.it
Distribution: ---
Created attachment 62143
--> https://bugs.winehq.org/attachment.cgi?id=62143
Game screenshot showing light and shadow being reversed.
Shadows appear as "light" while light appears as shadows. This also causes
levels to be unusually dark.
--
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=50631
Bug ID: 50631
Summary: Old programs on https://www.winehq.org/irc
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jkfloris(a)dds.nl
Distribution: ---
On https://www.winehq.org/irc the following programs are mentioned.
X-Chat last update 2010
Sidenet last update 2006
WineDoors last update 2013
Cedega
IEs4Linux
Do people really still use these programs?
Perhaps the last four programs can be replaced by PlayOnLinux and PlayOnMac
--
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=50866
Bug ID: 50866
Summary: Accessing https://www.winehq.org/pipermail/ will make
the whole website inaccessible
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: huupoke12(a)gmail.com
Distribution: ---
After accessing https://www.winehq.org/pipermail/ (the trailing slash is
present), the user can't access any other www.winehq.org webpages.
--
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=52439
Bug ID: 52439
Summary: apt-key is deprecated (bookworm/Debian)
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: osamu(a)debian.org
Distribution: ---
apt-key(8) will last be available in Debian 11 and Ubuntu 22.04.
For Debian/bookworm (12) (and probably for Ubuntu 22.10), apt-key usage as
described.
This affects following pages:
* https://wiki.winehq.org/Debian
* https://wiki.winehq.org/Ubuntu
Specifically:
```
wget -nc https://dl.winehq.org/wine-builds/winehq.key
sudo apt-key add winehq.key
```
The above should be changed to:
* For Debian up to Buster(11):
```
wget -nc https://dl.winehq.org/wine-builds/winehq.key
sudo apt-key add winehq.key
```
* For Debian from Bookworm (12):
```
wget -nc https://dl.winehq.org/wine-builds/winehq.key
sudo cp winehq.key /etc/apt/trusted.gpg.d/winehq.gpg
```
I only tested this for Debian ....
Osamu
--
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=53356
Bug ID: 53356
Summary: Problems installing WineHQ on Ubuntu 22.04
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: Ulf.Zibis(a)gmx.de
Distribution: ---
1. Key and sources list are not saved as root owned files with your current
install procedure.
This is a SECURITY RISK !!!
Correct procedure could be:
sudo dpkg --add-architecture i386 # only on 64-bit-systems
wget -nc https://dl.winehq.org/wine-builds/winehq.key
F=winehq.key && chmod a-w,u+w $F && sudo chown 0:0 $F && sudo mv $F
/usr/share/keyrings/winehq-archive.key
wget -nc
https://dl.winehq.org/wine-builds/ubuntu/dists/jammy/winehq-jammy.sources
F=winehq-jammy.sources && chmod a-w,u+w $F && sudo chown 0:0 $F && sudo mv $F
/etc/apt/sources.list.d/ && sudo apt update
sudo apt install --install-recommends winehq-stable winetricks
2. There is on STABLE build for Ubuntu 22.04:
$ sudo apt install --install-recommends winehq-stable winetricks
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
E: Paket winehq-stable kann nicht gefunden werden.
workaround:
sudo apt install --install-recommends winehq-devel winetricks
--
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=54011
Bug ID: 54011
Summary: Page Says to Enter Your *login name* ... but it
Expects an *email address*
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winehq.machg(a)spamgourmet.com
Distribution: ---
1. Be logged out.
2. Goo to https://bugs.winehq.org/userprefs.cgi
At the bottom it says:
>If you have an account, but have forgotten your password, enter your login name below and submit a request to change your password.
Note the wording: "enter your login name".
3. Enter a "login name" and click Reset Password
4. Get an error page:
>The e-mail address you entered ... didn't pass our syntax checking for a legal email address.
5. Go back and ignore the page's instructions: enter an email address this time
6. It works as expected.
Simple fix: change the verbiage at the bottom of the page to say "email
address" instead of "login name".
--
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=30186
Bug #: 30186
Summary: Wine Bugzilla quick search return zero result for
keywords
Product: WineHQ Bugzilla
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bugzilla-unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fracting(a)gmail.com
Classification: Unclassified
If I remember correctly, it works yesterday.
Today I try to search some short keywords in Wine Bugzilla quick search box,
and found it doesn't work as before:
For example, search for "win","mac","wow", "aj", "a", the result is empty.
Here is a example URL:
http://bugs.winehq.org/buglist.cgi?query_format=specific&order=relevance%20…
Bug or feature?
--
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=52802
Bug ID: 52802
Summary: Dead/broken links / stale data
Product: WineHQ Bugzilla
Version: unspecified
Hardware: Other
OS: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bugzilla-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: aros(a)gmx.com
CC: austinenglish(a)gmail.com
Both:
Add Bugzilla to Sidebar (requires a Mozilla browser like Mozilla Firefox)
Install the Quick Search plugin (requires Firefox 2 or Internet Explorer 7)
Are dead and could be removed.
--
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=53605
Bug ID: 53605
Summary: Show times in UTC
Product: WineHQ Bugzilla
Version: unspecified
Hardware: Other
OS: other
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: bugzilla-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: aros(a)gmx.com
CC: austinenglish(a)gmail.com
Barely anyone in this world knows what CDT is. And then it's hard to convert to
your local TZ.
Is it possible to make Wine's bugzilla show dates in UTC, please?
--
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=21424
Summary: Cygwin 1.7.1 bash crashes
Product: Wine
Version: 1.1.36
Platform: x86
OS/Version: Linux
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
cygwin installs now, but one sees the following crash
10 [main] bash 9 _cygtls::handle_exceptions: Exception:
STATUS_ACCESS_VIOLATION
1271 [main] bash 9 open_stackdumpfile: Dumping stack trace to
bash.exe.stackdump
err:ntdll:RtlpWaitForCriticalSection section 0x736d2784 "loader.c:
loader_section" wait timed out in thread 0036, blocked by 003c, retrying (60
sec)
during postinstall, and also when running bash interactively.
--
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=53689
Bug ID: 53689
Summary: Starcraft remastered fails to start
Product: Wine
Version: 7.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: kohen.d(a)gmail.com
Distribution: ---
Created attachment 73096
--> https://bugs.winehq.org/attachment.cgi?id=73096
Run log
It seems like a D3D error, I saw a line in the log saying:
glSetPixelFormatWINE failed to set pixel format 27
--
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=52162
Bug ID: 52162
Summary: Ubuntu windows program has com1 the PIC micro
programmer has usb device shows on /dev/ttyUSB0
Product: Wine
Version: 6.23
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: usb
Assignee: wine-bugs(a)winehq.org
Reporter: mw0sbx(a)hotmail.com
Distribution: ---
marc@SPUPERMICRO-X9DRH-iF:~/.wine/drive_c/windows$ wine --version
wine-5.0 (Ubuntu 5.0-3ubuntu1)
Ubuntu - windows program has COM1 the PIC micro programmer has usb leed the
device shows up using dmesg -w as /dev/ttyUSB0
program is called MicroPro.exe
tried editing the wine registry as stated online by adding
HKEY local machine >>> software >> wine >> ports
string value COM1 >> DATA /dev/ttyUSB0
dmesg -w
[ 2059.674461] usb 2-1.2: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[ 2059.674466] usb 2-1.2: Product: USB <-> Serial
[ 2059.674469] usb 2-1.2: Manufacturer: FTDI
[ 2059.675373] ftdi_sio 2-1.2:1.0: FTDI USB Serial Device converter detected
[ 2059.675448] usb 2-1.2: Detected FT232BM
[ 2059.675906] usb 2-1.2: FTDI USB Serial Device converter now attached to
ttyUSB0
Still doesn't work no matter what i try program keeps reporting problem with
coms port.
--
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=55340
Bug ID: 55340
Summary: d3d9:visual - unbound_sampler_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 - unbound_sampler_test() fails on w11pro64_amd:
visual.c:17489: Test failed: Unbound sampler color is 0.
visual.c:17503: Test failed: Unbound sampler color is 0.
visual.c:17517: Test failed: Unbound sampler color is 0.
See https://test.winehq.org/data/patterns.html#d3d9:visual
This group of failures goes back to at least 2022-11-23, is systematic, and
specific to w11pro64_amd (AMD RX6600). Most notably it does not happen on
w10pro64_rx550 (Windows 10 + AMD RX550).
--
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=55338
Bug ID: 55338
Summary: d3d9:visual - test_clear_different_size_surfaces()
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 - test_clear_different_size_surfaces() fails on w11pro64_nv:
visual.c:1616: Test failed: Got unexpected color 0x00000000.
visual.c:1619: Test failed: Got unexpected color 0x00000000.
See https://test.winehq.org/data/patterns.html#d3d9:visual
This pair of failures 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=55335
Bug ID: 55335
Summary: gdi32:font - test_text_metrics() fails on Windows for
the Korean locale
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
gdi32:font - test_text_metrics() fails on Windows for the Korean locale
(ko_KR):
font.c:3991: Test failed: A: tmBreakChar for ���� ���� got 1f expected 02
font.c:4013: Test failed: W: tmBreakChar for ���� ���� got 1f expected 02
[...]
font.c:3991: Test failed: A: tmBreakChar for ���� ���� Semilight got 1f
expected 02
font.c:4013: Test failed: W: tmBreakChar for ���� ���� Semilight got 1f
expected 02
[... 270+ additional failures...]
See https://test.winehq.org/data/patterns.html#gdi32:font
This is similar to the tmDefaultChar failures in bug 52967.
--
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=52081
Bug ID: 52081
Summary: usbip: error: vhci driver is not loaded
Product: Wine
Version: 6.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alois.schloegl(a)gmail.com
Distribution: ---
When trying to install and use the usbip-win client
https://github.com/cezanne/usbip-win/releases/download/v0.3.5/usbip-win-0.3…
trying to attach a remote usb device fails with the
usbip: error: vhci driver is not loaded
This happens with the released version of usbip-win v0.3.5 as well as with a
self-compiled version of usbip-win where the has_certificate function is
disabled. Below are the steps to reproduce. In order to test this, are usbip
server (in my case this is on "donglerasp") where "usbipd -D" is running and a
usb device is exported with
usbip bind --busid=1-1.2.3
$ wine usbip.exe install -w
usbip: error: root driver already exist
0100:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA,
000000000011FC20
$ wine usbip.exe list -r donglerasp
Exportable USB devices
======================
- donglerasp
1-1.2.3: unknown vendor : unknown product (0529:0001)
:
/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2.3
: unknown class / unknown subclass / unknown protocol (ff/00/00)
: 0 - unknown class / unknown subclass / unknown protocol
(ff/00/00)
0100:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA,
000000000011FC20
$ wine usbip.exe attach -r donglerasp -b "1-1.2.3"
usbip: error: vhci driver is not loaded
0118:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA,
000000000011FC20
--
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=34497
Bug #: 34497
Summary: ProAIS2 Serial Port enumeration requires Registry
Local_Machine/…/Enum/SERIAL/COM1/COM1/*
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: winehq(a)paul.sladen.org
Classification: Unclassified
ProAIS2 (Marine AIS software from SRT in the UK, and re-badged by large numbers
of OEMs) performs Serial Port detection by enumerating the registry. The
following keys need to be added:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\SERIAL\COM1\COM1]
"ClassGUID"="{4D36E978-E325-11CE-BFC1-08002BE10318}"
"FriendlyName"="Serial Port (COM1)"
"PortName"="COM1"
in addition to the matching
ln -s /dev/ttyUSB0 ~/.wine/dosdevices/com1
If only the ClassGUID/FriendlyName are set, then the port will be found, but
immediately switched to in-case. PortName is being prefixed with "\\.\"
("\\\\.\\") to form "\\.\COM1".
Kudos to Doug Brown for tracking down most of the issue:
http://www.downtowndougbrown.com/2013/03/getting-x-ctu-in-wine-to-detect-yo…
--
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=49972
Bug ID: 49972
Summary: Termie 1.0 crashes after selecting a serial port.
Product: Wine
Version: 5.18
Hardware: x86-64
URL: http://termie.sourceforge.net/#downloads
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cedric.dewijs(a)eclipso.eu
Distribution: ArchLinux
Created attachment 68373
--> https://bugs.winehq.org/attachment.cgi?id=68373
Console messages
Summary
Termie 1.0 crashes after selecting a serial port.
Download location
http://termie.sourceforge.net/#downloadshttp://termie.sourceforge.net/Termie-1.0-Binary.zip
$ sha256sum Termie-1.0-Binary.zip
53469ffdb38058b985482cbfac3f4c0575eeafa4e1b766b5f0c2af43acb7cba6
Termie-1.0-Binary.zip
$ unzip Termie-1.0-Binary.zip
Steps to reproduce:
1)Start the program:
$ wine Termie.exe
After a long time (+- 20 seconds) the program opens.
2) Select one of the comm port. Now the program crashes.
3) Press ctrl-c in the console to kill wine.
4) restart Termie.
$ wine Termie.exe
Now wine gives this error.
"[ERROR] FATAL UNHANDLED EXCEPTION: System.IO.IOException: Broken pipe."
Every time Termie is restarted via step 3, it crashes the same way.
My versions
$ wine --version
wine-5.18 (Staging)
$ pacman -Q wine
wine-staging 5.18-1
uname -a
Linux cedric-p4 5.8.14-arch1-1 #1 SMP PREEMPT Wed, 07 Oct 2020 23:59:46 +0000
x86_64 GNU/Linux
--
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=49974
Bug ID: 49974
Summary: termite-3.4 can't connect to com5 -> /dev/ttyACM0
Product: Wine
Version: 5.18
Hardware: x86-64
URL: https://www.compuphase.com/software_termite.htm
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cedric.dewijs(a)eclipso.eu
Distribution: ArchLinux
Created attachment 68375
--> https://bugs.winehq.org/attachment.cgi?id=68375
console messages
Summary
termite-3.4 can't connect to com5 -> /dev/ttyACM0
Prepare wine:
$ rm -rf ~/.wine/
$ wineserver -k
$ wineboot
Download location
https://www.compuphase.com/software_termite.htmhttps://www.compuphase.com/software/termite-3.4.exe
$ sha256sum termite-3.4.exe
ca440b6c7f6eaa812ba5f8bf42aed86e02022ca50a1c72585168c9b671d0fe19
termite-3.4.exe
Steps to reproduce:
1) Install the program:
$ wine termite-3.4.exe
Accept the defaults.
Now termite starts.
2) Press settings.
The dropdown box only shows COM1. Choose baud rate 9600 and press OK.
Now termite reports "Failed to initialize the port. Please verify the COM port
settings."
3) Press "Connect".
Now that termite reports "Waiting for port"
4) Press close.
Now termite closes.
As a sanity test, I open moserial, choose /dev/ttyACM0 9600,8N1, press connect,
and I see the messages my MCP2221 serial to USB converter is sending to me.
/dev/ttyACM0 is detected by wine:
$ ls -l ~/.wine/dosdevices/
total 0
lrwxrwxrwx 1 cedric cedric 10 Oct 10 19:25 c: -> ../drive_c
lrwxrwxrwx 1 cedric cedric 10 Oct 10 19:35 com1 -> /dev/ttyS0
lrwxrwxrwx 1 cedric cedric 12 Oct 10 19:35 com5 -> /dev/ttyACM0
lrwxrwxrwx 1 cedric cedric 8 Oct 10 19:26 d:: -> /dev/sr0
lrwxrwxrwx 1 cedric cedric 1 Oct 10 19:25 z: -> /
My versions
$ wine --version
wine-5.18 (Staging)
$ pacman -Q wine
wine-staging 5.18-1
uname -a
Linux cedric-p4 5.8.14-arch1-1 #1 SMP PREEMPT Wed, 07 Oct 2020 23:59:46 +0000
x86_64 GNU/Linux
--
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=49752
Bug ID: 49752
Summary: Mikster MPC4 System: 'Selected serial port not exist'
Product: Wine
Version: 5.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: amad4wine2020(a)gmail.com
Distribution: ---
Log in as 'Adm' user, go to the 'Controllers list', press the 'Add' button,
select the appropriate 'Port COM' and 'Baud rate', press the 'Test' button, you
will probably get an error message containing the phrase 'Selected serial port
not exist'.
I have tried the following registry keys:
[System\\CurrentControlSet\\Enum\\SERIAL\\COM2\\COM2] 1598720497
#time=1d67e260ec36dbc
"ClassGUID"="{4D36E978-E325-11CE-BFC1-08002BE10318}"
"FriendlyName Value"="Serial Port (COM2)"
[Software\\Wine\\Ports] 1598713705
#time=1d67e163e9541c4
"COM2"="/dev/ttyS1"
Unfortunately, it makes no difference.
Download links from the software's website:
https://mikster.eu/en/download-center/https://mikster.eu/wp-content/uploads/2019/03/installmpc482ENG.zip
P.S. The installer will silently install FirebirdSQL 1.5 and enable Firebird
Guardian, it does not work well with winehq-devel.
Unpack the installmpc482ENG.exe and rename the included
installmpc482ENG/firebird/FirebirdWin32.exe before continuing with the
installation.
Install the renamed FirebirdWin32.exe manually (uncheck the 'Use the Guardian
to control the server?' option during the installation).
--
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=39810
Bug ID: 39810
Summary: Office 2010 Pro Plus uninstallation fails
Product: Wine
Version: 1.7.55
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: isiraseneviratne(a)yahoo.com
Distribution: ---
After launching the uninstaller (through either the CD Setup or Wine
Uninstaller), selecting the Remove option and then selecting Continue results
in a message saying that setup was unable to finish successfully.
--
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=35904
Bug ID: 35904
Summary: USB connection not recognized by Axon MultiClamp
Commander 700B.
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alois.schloegl(a)gmail.com
The "Axon MutiClamp Commander 700B" is a devices which connected with USB to
the PC. The software for controlling the device installs and runs well, but it
does not identify the USB device.
For this reason, the application "MutiClamp Commander 700B" in Winehq's AppDB
has currently status "Garbage".
--
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=55329
Bug ID: 55329
Summary: gdi32:font - test_text_metrics() gets unexpected
tmLastChar in Greek locale
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
gdi32:font - test_text_metrics() gets unexpected tmLastChar in Greek locale:
font.c:4011: Test failed: W: tmLastChar for Marlett got f8fb expected f0ff
font.c:4011: Test failed: W: tmLastChar for Symbol got f8fb expected f0ff
font.c:4011: Test failed: W: tmLastChar for Wingdings got f8fb expected f0ff
font.c:4011: Test failed: W: tmLastChar for Webdings got f8fb expected f0ff
See https://test.winehq.org/data/patterns.html#gdi32:font
--
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=54712
Bug ID: 54712
Summary: ntdll:rtl times out on Windows 10 1607
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:rtl times out on Windows 10 1607:
[...]
rtl.c:2790: Running test 23 (compressed_size=5, uncompressed_size=0,
status=0xc0000242)
ntdll:rtl:00a4 done (258) in 120s 2231B
See https://test.winehq.org/data/patterns.html#ntdll:rtl
The timeouts started on 2022-09-06 and have been systematic since. However when
run on its own the test does not time out and usually runs in under 1s.
The timeout always happens after the "test 23" trace which is also the last
test of test_RtlDecompressBuffer(). Given that the test usually runs pretty
fast it is probable that one of the tests that follows causes a freeze on
Windows 10 1607.
--
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=55326
Bug ID: 55326
Summary: msctf:inputprocessor gets unexpected deactivation
callbacks on Windows 7 for the Spanish locale
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: msctf
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
msctf:inputprocessor gets unexpected deactivation callbacks on Windows 7 for
the Spanish locale:
inputprocessor.c:1021: Test failed: Deactivation came unexpectedly
inputprocessor.c:656: Test failed: unexpected call
See https://test.winehq.org/data/patterns.html#msctf:inputprocessor
This pair of failures are systematic and only happen on w7u_es, that is Windows
7 Ultimate with the Spanish locale. In particular the other w7u configurations
don't get these failures. gitlab-win10-21h2 gets the first failure too but in a
different group of failures (see bug 55068).
--
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=52899
Bug ID: 52899
Summary: gdi32:font - test_fullname2() fails in non-English
Windows 7 locales
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
test_fullname2() fails in non-English Windows 7 locales. For instance in German
(I removed duplicate lines):
font.c:5710: Test failed: Arial: style names don't match: returned Regular,
expect Standard
[...]
font.c:5700: Test failed: Arial: font face names don't match: returned Arial
Italic, expect Arial Kursiv
font.c:5710: Test failed: Arial: style names don't match: returned Italic,
expect Kursiv
[...]
font.c:5700: Test failed: Arial: font face names don't match: returned Arial
Bold, expect Arial Fett
font.c:5710: Test failed: Arial: style names don't match: returned Bold, expect
Fett
[...]
font.c:5700: Test failed: Arial: font face names don't match: returned Arial
Bold Italic, expect Arial Fett Kursiv
font.c:5710: Test failed: Arial: style names don't match: returned Bold Italic,
expect Fett Kursiv
font.c:5710: Test failed: Tahoma: style names don't match: returned Regular,
expect Standard
[...]
font.c:5700: Test failed: Tahoma: font face names don't match: returned Tahoma
Bold, expect Tahoma Fett
font.c:5710: Test failed: Tahoma: style names don't match: returned Bold,
expect Fett
[...]
font.c:5710: Test failed: Webdings: style names don't match: returned Regular,
expect Standard
font.c:5710: Test failed: Wingdings: style names don't match: returned Regular,
expect Standard
https://test.winehq.org/data/patterns.html#gdi32:font
Spanish and Portuguese (pt_PT) get the same set of errors but with their own
localized names.
Mark these tests as broken on Windows 7? win_skip() them?
--
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=51391
Bug ID: 51391
Summary: On Windows 7 and 8.1 ntoskrnl.exe:ntoskrnl triggers a
network firewall dialog, breaks user32:win
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
On Windows 7 and 8.1 ntoskrnl.exe:ntoskrnl triggers a network firewall dialog
(see the screenshots for the TestBot WineTest runs on w7u_2qxl and w8). Despite
that ntoskrnl.exe:ntoskrnl succeeds.
However it leaves that dialog open which then causes two failures in
user32:win:
https://test.winehq.org/data/patterns.html#user32:win
win.c:3394: Test failed: GetActiveWindow() = 00000000
win.c:3394: Test failed: GetFocus() = 00000000
Notes:
* These are the same failures as in bug 51390. If it is decided that user32:win
is the test that needs fixing then this bug could be merged.
* But if the decision is that ntoskrnl.exe:ntoskrnl should either not trigger
such a dialog or close it, then this bug should remain separate.
* Most of ntoskrnl.exe:ntoskrnl is skipped on Wow64 so this issue does not
happen in newtb-w864-32.
* The 64-bit ntoskrnl.exe:ntoskrnl test also does not trigger that dialog for
some reason.
--
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=3845
Zeb Figura <z.figura12(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|-unknown |serial
--
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=19713
Summary: Some serial port communication functions behave
differently in Wine and Windows.
Product: Wine
Version: 1.1.27
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fenixk19(a)mail.ru
Created an attachment (id=23025)
--> (http://bugs.winehq.org/attachment.cgi?id=23025)
Test program
This makes test program to hang in Wine, but in MS it is ok. Test program
attached.
--
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=37846
Bug ID: 37846
Summary: Communication broken using FTDI USB Serial Device
converter (FT232RL) / Mostly send using CS-51PLUS
Product: Wine
Version: 1.7.30
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lgeorgieff(a)gmail.com
Distribution: ---
Created attachment 50402
--> https://bugs.winehq.org/attachment.cgi?id=50402
WINEDEBUG="+comm" wine .wine/drive_c/Program\ Files\
\(x86\)/Icom/CS-51PLUS/CS51PLUS.exe log
Hi,
I am using FTDI USB Serial Device converter to program ham radio.
Cable have FT232RL chip and software is CS-51PLUS.
Reading from radio is OK but when I try to write (send) configuration to the
radio communication is broken after while and I get error message.
The same cable and software on the same machine runs without problems on QEMM's
virtual windows.
--
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=13296
Summary: regression problem in upgrade to Ubuntu Hardy/1.0-rc1:
Palm Hotsync over serial Segmentation Fault
Product: Wine
Version: 1.0-rc1
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jan-winehq(a)h-i-s.nl
Created an attachment (id=13150)
--> (http://bugs.winehq.org/attachment.cgi?id=13150)
Logging output
I upgraded to Ubuntu Hardy, and wine 1.0-rc1.
Hotsync manager 1.0 for Palm Pilot worked fine before.
http://appdb.winehq.org/objectManager.php?sClass=version&iId=10362
Now it crashes half-way synchronising over the serial port, sometimes after a
few seconds, sometimes much later in the process.
These crashes reproduce well, and yield a segmentation fault without further
information
$ wine hotsync.exe
Segmentation fault
$
I do not know if this means that a part of Wine crashes, or just the
application.
I added logging, where it seems that the problem lies within the call below:
0009:CallTo16(func=111f:072a,ds=1087,118f,7404,0000,0006) ss:sp=1087:ffd0
I am not sure if the problem lies with wine, or that other problems with Ubuntu
Hardy may relate to this.
It is disappointing that an application that used to work fine, and I came to
depend on, is now broken.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=25083
Summary: HyperTerminal unable to loop back on COM1 (RS-232)
Product: Wine
Version: 1.3.6
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: graham(a)nerve.org.za
On a machine with an on-board RS-232 port at COM1, HyperTerminal (as shipped
with Windows XP) is firstly unable to detect the port until changes are made in
the WINE registry, thereafter, after attaching a simple loopback adapter (pins
2 and 3 of a DB9F shorted) no characters are echoed to the screen.
Obtaining the software:
>From a Windows XP installation, copy the files hypertrm.exe and htrn_jis.dll
from 'C:\Program Files\Windows NT' and hticons.dll and hypertrm.dll from
C:\Windows\System32' into a suitable directory below .wine/drive_c
or
Download a free 30 day trial of HyperTerminal Private Edition 7.0 from
http://www.hilgraeve.com/hyperterminal/
Create a symbolic link for COM1, documented here:
http://www.winehq.org/docs/wineusr-guide/misc-things-to-configure
ln -s /dev/ttyS0 ~/.wine/dosdevices/com1
At this point, starting HyperTerminal will result in no serial ports being
shown.
Now, create a registry entry in WINE for the serial port, mentioned in this bug
report:
http://bugs.winehq.org/show_bug.cgi?id=4282
Add the following lines to .wine/system.reg [Hardware\\Devicemap\\SerialComm]
"Serial0"="COM1"
Now HyperTerminal can be started, COM1 can be selected and configured, but no
characters are echoed to the screen.
However, the free terminal program, simply named 'Terminal' and available here:
https://sites.google.com/site/terminalbpp/
Does echo characters to the screen.
--
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=47873
Bug ID: 47873
Summary: kernel32:comm fails randomly
Product: Wine
Version: 4.17
Hardware: x86
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
kernel32:comm fails randomly on multiple Windows versions:
comm.c:708: Found Com port COM1. Connected devices may disturb results
comm.c:859: Test failed: WaitCommEvent failed with a timeout
comm.c:870: recovering after WAIT_TIMEOUT...
comm.c:880: Test failed: WaitCommEvent error 0
comm.c:881: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0
comm.c:885: WaitCommEvent for EV_TXEMPTY took 1500 ms (timeout 1500)
comm.c:886: Test failed: WaitCommEvent used 1500 ms for waiting
https://test.winehq.org/data/tests/kernel32:comm.html
These failures are random and have been seen on the following TestBot VM4
configurations:
wxppro
w2003std
w7pro64-32
w1064v1507-32
w1064v1607-32
w1064v1607-64
w1064v1709-64
w1064v1607-64
w1064v1809-32
w1064v1809-32
w1064v1809-64
w1064v1809-2scr-32
w1064v1809-fr-64
w1064v1809-ja-32
w1064v1809-ja-64
So it does not depend on the Windows version, bitness of the test, or locale.
However it only happens on QEmu VMs: it never happened on the fg-win7u64 VMware
VMs or on the real hardware machines, cw-rx460 and cw2-gtx560.
Yet the VMware VMs have two serial COM ports, and, according to dmesg | grep
tty, the real hardware machines do have a serial port too.
QEmu 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=46676
Bug ID: 46676
Summary: Serial port enumeration (get device description) on
Mac OS/X 10.9, 10.13
Product: Wine
Version: 4.0
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: setupapi
Assignee: wine-bugs(a)winehq.org
Reporter: martin(a)hinner.info
Created attachment 63628
--> https://bugs.winehq.org/attachment.cgi?id=63628
suspected problematic function
Tested on: Mac OS/X 10.9, 10.13
WineBottler (Wine 1.8) works fine; Wine 4.0 (from .pkg) does not work
Our application is trying to enumerate serial ports by using setupapi
functions. I have not checked where exactly is the problem as debugging on OS/X
is a bit difficult for me, however suspected function is attached (it's goal is
to get device description).
The affected apps are http://obdtester.com/ficom , http://obdtester.com/bimcom
, http://obdtester.com/fcom ;
I have tried to create symlink in dosdevices (required for WineBottler to get
it working), one OS/X 10.13 my link got deleted everytime I ran the app; on
OS/X 10.9 link persisted, but not possible to enumerate any serial port(s).
I can provide login for download by personal e-mail (not to be disclosed).
I have talked about this on wine mailing list a long time ago, it would be
super easy if Wine-enabled application can have a way to load system native .so
to talk directly to the host system, I have many examples of device drivers
that would be super easy to implement. FYI I have already written
"winegate.dll.so" which solves this real world problem, but it was rejected for
submission to Wine because of "Wine must be 100% transparent" ideology.
--
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=50778
Bug ID: 50778
Summary: TortoiseMerge closes before showing a window
Product: Wine
Version: 6.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lexlexlex(a)gmail.com
Distribution: ---
Created attachment 69576
--> https://bugs.winehq.org/attachment.cgi?id=69576
Terminal log for TortoiseMerge startup and subsequent closing with wine
Steps to reproduce:
1. Install TortoiseSVN in a 64-bit wine prefix.
2. Try to run TortoiseMerge.exe with the wine prefix mentioned in step 1. For
example, run "wine TortoiseMerge.exe" from a terminal if the default wine
prefix was used.
Current behavior:
TortoiseMerge closes before showing a window. No TortoiseMerge window appears.
Expected behavior:
TortoiseMerge is expected to start, allowing the user to compare and merge
files in a windowed GUI.
Additional information:
A download for the current version of the TortoiseSVN installer as of this
report is at
https://osdn.net/projects/tortoisesvn/storage/1.14.1/Application/TortoiseSV…
A log showing terminal output when trying to run "wine TortoiseMerge.exe" is
attached.
Opinion:
This is one of 2 bugs preventing using TortoiseSVN fully in wine. The other is
50756. If these 2 bugs are fixed, TortoiseSVN could be used fully, easing the
transition of users whose jobs rely on SVN to Linux. Currently some companies
still use SVN and I've tried all the free SVN clients for Linux, and none of
them come close to the level of convenience and intuitiveness that TortoiseSVN
provides. I have nemo actions ready to enable full usage in of TortoiseSVN in
Linux if these 2 bugs are fixed. This would help me personally tremendously,
as digging through old revisions in alternate SVN branches is part of my job
and extremely difficult with any SVN client other than TortoiseSVN using
TortoiseMerge. Thanks for reading this.
--
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=51212
Bug ID: 51212
Summary: i want to install itunes, it installed through wine
but giving some error while to launch the program
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: programs
Assignee: wine-bugs(a)winehq.org
Reporter: robinssgraphics(a)gmail.com
Distribution: ---
Created attachment 70086
--> https://bugs.winehq.org/attachment.cgi?id=70086
i want to install itunes, it installed through wine but giving some error while
to launch the program
i want to install itunes, it installed through wine but giving some error while
to launch the program
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53850
Bug ID: 53850
Summary: Mery, TeraPad : When using Japanese input method (IM),
undetermined strings are not displayed (regression)
Product: Wine
Version: 7.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: su_zu_me(a)hotmail.com
Distribution: ---
Created attachment 73380
--> https://bugs.winehq.org/attachment.cgi?id=73380
input after "そうか" ("souka"), but not displayed
Mery and TeraPad are text editors.
When using input method (IM) to input Japanese characters, undetermined strings
are not displayed.
Candidates are displayed.
Conversions are done successfully.
It occurs with Wine 7.13 or later.
Undetermined strings are displayed inline with Wine 7.12 or earlier, after
several conversion after starting the application.
note:
Right after starting the application, undetermined string is not displayed
with all tested version of Wine, but it should be another bug.
Application:
Mery (x86) Version 2.6.7
Download site:
https://forest.watch.impress.co.jp/library/software/mery/
SHA1:
edef7350aeed6bab083612e2d316607561f5f31c MerySetup-2.6.7.exe
tested Wine version:
6.0.3 (Ubuntu 6.0.3~repack-1)
7.11
7.12
7.13
7.15
7.19
Application:
TeraPad Version 1.09
Download site:
-
SHA1:
3ff8f3741ce82dcea54a385cea484b861007c260 tpad109.zip
tested Wine version:
6.0.3 (Ubuntu 6.0.3~repack-1)
7.11
7.12
7.13
7.15
7.19
Application:
TeraPad Version 1.10
Download site:
https://tera-net.com/library/tpad.html
SHA1:
ae28027af722c3ea7f6431d04c65582d16c60832 tpad110.exe
tested Wine version:
7.12
7.19
terminal output: N/A
OS:
Ubuntu 22.04.1 LTS (amd64)
Display server:
Wayland
Input Method Framework:
IBus
Input Method Engine:
Mozc
installed Wine:
winehq-devel
--
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=55018
Bug ID: 55018
Summary: d2d1:d2d1 sometimes times out on Linux
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: d2d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
d2d1:d2d1 sometimes times out on Linux. Apparently something causes the whole
test to lock up but because the test is multithreaded this can happen at any
point.
d2d1:d2d1 start dlls/d2d1/tests/d2d1.c
d2d1:d2d1:0810 done (258) in 120s 0B
or
d2d1:d2d1 start dlls/d2d1/tests/d2d1.c
d2d1.c:2692: Test marked todo: Surface does not match.
...
d2d1.c:10042: Test marked todo: Test 1: Got unexpected dpi_y 2.88000000e+002,
expected 0.00000000e+000.
d2d1.c:10039: Test marked todo: Test 2: Got unexpected dpi_x 6.00000000e+001,
expected 0.00000000e+000.
d2d1:d2d1:077c done (258) in 120s 13391B
See https://test.winehq.org/data/patterns.html#d2d1:d2d1
Note that this only happens in the 64-bit tests (including on
gitlab-debian-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=55318
Bug ID: 55318
Summary: ntdll:time - test_TimerResolution() fails on Windows
11
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:time - test_TimerResolution() fails on Windows 11:
time.c:284: Test failed: expected new timer resolution 5000, got 4882
time.c:284: Test failed: NtQueryTimerResolution() expected timer resolution
4882, got 5000
See https://test.winehq.org/data/patterns.html#ntdll:time
--
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=53247
Bug ID: 53247
Summary: user32:sysparams - test_dpi_context() fails on Windows
10 1909+
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 - test_dpi_context() fails on Windows 10 1909+:
sysparams.c:3813: Test failed: got 0
sysparams.c:3814: Test failed: wrong value -1
https://test.winehq.org/data/patterns.html#user32:sysparams
These traces could include a bit more information rather than leaving most of
it to the source line number.
--
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=55308
Bug ID: 55308
Summary: tools/winebuild/res16.c:156:5: runtime error: null
pointer passed as argument 1, which is declared to
never be null (UndefinedBehaviorSanitizer)
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: tools
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: Debian
Created attachment 74908
--> https://bugs.winehq.org/attachment.cgi?id=74908
build log
I've been using UndefinedBehaviorSanitizer at my day job and found it pretty
useful, so did some brief testing on it with Wine.
Not everything builds (notably loader/ and dlls/ntdll/unix/), but most other
stuff does.
For this issue, just recompiling tools/winebuild is enough to see the issue:
./configure && make -j12
cd tools/winebuild
make clean
make CFLAGS="-fsanitize=undefined" LDFLAGS="-fsanitize=undefined"
cd ../../dlls/avifile.dll16/
make clean && make
tools/winegcc/winegcc -o dlls/avifile.dll16/i386-windows/avifile.dll16
--wine-objdir . -b i686-w64-mingw32 -Wl,--wine-builtin -shared \
dlls/avifile.dll16/avifile.dll16.spec -m16 -Wb,--main-module,avifil32.dll \
dlls/avifile.dll16/i386-windows/main.o
dlls/avifil32/i386-windows/libavifil32.a \
dlls/winecrt0/i386-windows/libwinecrt0.a
dlls/ucrtbase/i386-windows/libucrtbase.a \
dlls/krnl386.exe16/i386-windows/libkernel.a
dlls/kernel32/i386-windows/libkernel32.a \
dlls/ntdll/i386-windows/libntdll.a -Wl,--disable-stdcall-fixup
tools/winebuild/res16.c:156:5: runtime error: null pointer passed as argument
1, which is declared to never be null
Seems to affect most win16 dlls, there are a total of 44 occurrences (build log
attached).
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54015
Bug ID: 54015
Summary: Accessing shared memory from Linux
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: berarma(a)hotmail.com
Distribution: ---
Some Windows games and applications share some internals through shared memory
with external tools. Shared memory is preferred over sockets because it adds no
overhead with no latency.
It's mostly used in driving and flying simulators to provide visual overlays,
data on additional displays, telemetry, rig movement, etc. from external tools.
There's also scientific apps using it for similar purposes or general
inter-process communication.
It's common to use tagged shared memory blocks that external tools can then
access using the already known tag.
Here's an example from a Python application for rFactor 2:
self._rf2_tele = mmap.mmap(0, ctypes.sizeof(rF2Telemetry),
f"$rFactor2SMMP_Telemetry${input_pid}")
self._rf2_scor = mmap.mmap(0, ctypes.sizeof(rF2Scoring),
f"$rFactor2SMMP_Scoring${input_pid}")
self._rf2_ext = mmap.mmap(0, ctypes.sizeof(rF2Extended),
f"$rFactor2SMMP_Extended${input_pid}")
self._rf2_ffb = mmap.mmap(0, ctypes.sizeof(rF2ForceFeedback),
"$rFactor2SMMP_ForceFeedback$")
Allowing these shared memory blocks to be accessed from Linux would allow us to
port some of these tools or even implement or own.
Then these tools could access resources or hardware that isn't available from
inside the Wine prefix. Some of these tools also fail to run on Wine.
Since I guess Wine is already using Linux shared memory mechanism to implement
Windows shared memory, the blocks are already available at /dev/shm but they
use generic names that can't be associated to the tag used on Windows.
Having these shared memory blocks created in the prefix directory with a name
containing the tag used on creation would allow us to use it from our native
applications. Or any other way to find them using the tags used on Windows.
Thanks for your attention.
--
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=55315
Bug ID: 55315
Summary: tools/wrc/parser.l:626:5: runtime error: null pointer
passed as argument 2, which is declared to never be
null (UndefinedBehaviorSanitizer)
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: tools
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: Debian
+++ This bug was initially created as a clone of Bug #55314 +++
For this issue, just recompiling tools/wrc is enough to see the issue:
./configure && make -j12
cd tools/wrc
make clean
make CFLAGS="-fsanitize=undefined" LDFLAGS="-fsanitize=undefined"
tools/wrc/wrc -u -o programs/winedbg/winedbg.res --nostdinc --po-dir=po
-Iprograms/winedbg -Iinclude -Iinclude/msvcrt \
-Ilibs/zydis/include -D_UCRT -D__WINESRC__ programs/winedbg/winedbg.rc
tools/wrc/parser.l:626:5: runtime error: null pointer passed as argument 2,
which is declared to never be null
--
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=55314
Bug ID: 55314
Summary: tools/wrc/genres.c:1078:31: runtime error: left shift
of 40664 by 16 places cannot be represented in type
'int' (UndefinedBehaviorSanitizer)
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: tools
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: Debian
For this issue, just recompiling tools/wmc is enough to see the issue:
./configure && make -j12
cd tools/widl
make clean
make CFLAGS="-fsanitize=undefined" LDFLAGS="-fsanitize=undefined"
tools/wrc/wrc -u -o dlls/fusion/version.res --nostdinc -Idlls/fusion -Iinclude
-Iinclude/msvcrt -D_UCRT -D__WINESRC__ \
dlls/fusion/version.rc
tools/wrc/genres.c:1078:31: runtime error: left shift of 50727 by 16 places
cannot be represented in type 'int'
tools/wrc/genres.c:1080:31: runtime error: left shift of 50727 by 16 places
cannot be represented in type 'int'
tools/wrc/wrc -u -o dlls/msvcr120/version.res --nostdinc -Idlls/msvcr120
-Idlls/msvcrt -Iinclude -Iinclude/msvcrt \
-D_MSVCR_VER=120 -D__WINESRC__ -D_CRTIMP= dlls/msvcr120/version.rc
tools/wrc/genres.c:1078:31: runtime error: left shift of 40664 by 16 places
cannot be represented in type 'int'
tools/wrc/wrc -u -o programs/ngen/version.res --nostdinc -Iprograms/ngen
-Iinclude -Iinclude/msvcrt -D_UCRT -D__WINESRC__ \
programs/ngen/version.rc
tools/wrc/genres.c:1078:31: runtime error: left shift of 50727 by 16 places
cannot be represented in type 'int'
tools/wrc/genres.c:1080:31: runtime error: left shift of 50727 by 16 places
cannot be represented in type 'int'
--
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=55313
Bug ID: 55313
Summary: tools/wmc/mcy.y:488:30: runtime error: left shift of 2
by 30 places cannot be represented in type 'int'
(UndefinedBehaviorSanitizer)
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: tools
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: Debian
For this issue, just recompiling tools/wmc is enough to see the issue:
./configure && make -j12
cd tools/widl
make clean
make CFLAGS="-fsanitize=undefined" LDFLAGS="-fsanitize=undefined"
tools/wmc/wmc -u -o dlls/kernelbase/winerror.res dlls/kernelbase/winerror.mc
--po-dir=po
tools/wmc/mcy.y:488:30: runtime error: left shift of 2 by 30 places cannot be
represented in type 'int'
tools/wmc/wmc -u -o dlls/mferror/mferror.res dlls/mferror/mferror.mc
--po-dir=po
tools/wmc/mcy.y:488:30: runtime error: left shift of 3 by 30 places cannot be
represented in type 'int'
--
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=55312
Bug ID: 55312
Summary: tools/widl/write_msft.c:1616:30: runtime error: left
shift of 1207959552 by 1 places cannot be represented
in type 'int' (UndefinedBehaviorSanitizer)
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: tools
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: Debian
Created attachment 74910
--> https://bugs.winehq.org/attachment.cgi?id=74910
build log
For this issue, just recompiling tools/widl is enough to see the issue:
./configure && make -j12
cd tools/widl
make clean
make CFLAGS="-fsanitize=undefined" LDFLAGS="-fsanitize=undefined"
tools/widl/widl -o dlls/atl/i386-windows/atl_lib_t.res -b i686-w64-mingw32
--nostdinc -Ldlls/\* -Idlls/atl -Iinclude \
-Iinclude/msvcrt -D_UCRT -D__WINESRC__ -D_ATL_VER=_ATL_VER_30
dlls/atl/atl_lib.idl
tools/widl/write_msft.c:1616:30: runtime error: left shift of 1476395008 by 1
places cannot be represented in type 'int'
There are 27 total occurrences.
--
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=55311
Bug ID: 55311
Summary: tools/widl/write_msft.c:1512:33: runtime error: left
shift of negative value -1
(UndefinedBehaviorSanitizer)
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: tools
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: Debian
For this issue, just recompiling tools/widl is enough to see the issue:
./configure && make -j12
cd tools/widl
make clean
make CFLAGS="-fsanitize=undefined" LDFLAGS="-fsanitize=undefined"
tools/widl/widl -o dlls/dhtmled.ocx/i386-windows/dhtmled_tlb_t.res -b
i686-w64-mingw32 --nostdinc -Ldlls/\* -Idlls/dhtmled.ocx -Iinclude \
-Iinclude/msvcrt -D_UCRT -D__WINESRC__ dlls/dhtmled.ocx/dhtmled_tlb.idl
tools/widl/write_msft.c:1512:33: runtime error: left shift of negative value -1
There are a total of 5 occurrences:
tools/widl/widl -o dlls/dhtmled.ocx/i386-windows/dhtmled_tlb_t.res -b
i686-w64-mingw32 --nostdinc -Ldlls/\* -Idlls/dhtmled.ocx -Iinclude \
-Iinclude/msvcrt -D_UCRT -D__WINESRC__ dlls/dhtmled.ocx/dhtmled_tlb.idl
tools/widl/widl -o dlls/mshtml.tlb/i386-windows/mshtml_tlb_t.res -b
i686-w64-mingw32 --nostdinc -Ldlls/\* -Idlls/mshtml.tlb -Iinclude \
-Iinclude/msvcrt -D_UCRT -D__WINESRC__ dlls/mshtml.tlb/mshtml_tlb.idl
tools/widl/widl -o dlls/msscript.ocx/i386-windows/msscript_t.res -b
i686-w64-mingw32 --nostdinc -Ldlls/\* -Idlls/msscript.ocx -Iinclude \
-Iinclude/msvcrt -D_UCRT -D__WINESRC__ dlls/msscript.ocx/msscript.idl
tools/widl/widl -o programs/cscript/i386-windows/ihost_l.res -b
i686-w64-mingw32 --nostdinc -Ldlls/\* -Iprograms/cscript \
-Iprograms/wscript -Iinclude -Iinclude/msvcrt -D_UCRT -D__WINESRC__
-DCSCRIPT_BUILD \
programs/wscript/ihost.idl
tools/widl/widl -o programs/wscript/i386-windows/ihost_l.res -b
i686-w64-mingw32 --nostdinc -Ldlls/\* -Iprograms/wscript -Iinclude \
-Iinclude/msvcrt -D_UCRT -D__WINESRC__ programs/wscript/ihost.idl
--
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=55310
Bug ID: 55310
Summary: tools/widl/hash.c:714:13: runtime error: store to
misaligned address 0xffda6583 for type 'unsigned int',
which requires 4 byte alignment
(UndefinedBehaviorSanitizer)
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: tools
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: Debian
Created attachment 74909
--> https://bugs.winehq.org/attachment.cgi?id=74909
build log
For this issue, just recompiling tools/widl is enough to see the issue:
./configure && make -j12
cd tools/widl
make clean
make CFLAGS="-fsanitize=undefined" LDFLAGS="-fsanitize=undefined"
tools/widl/widl -o include/windows.foundation.h -m32 --nostdinc -Ldlls/\*
-Iinclude -Iinclude -D__WINESRC__ \
include/windows.foundation.idl
tools/widl/hash.c:714:13: runtime error: store to misaligned address 0xffe6aac6
for type 'unsigned int', which requires 4 byte alignment
0xffe6aac6: note: pointer points here
00 00 00 00 00 00 00 00 00 00 8c ab e6 ff 00 e0 7a 56 20 40 7f 57 f8 aa e6
ff 00 e0 7a 56 30 00
^
tools/widl/hash.c:715:13: runtime error: store to misaligned address 0xffe6aaca
for type 'unsigned int', which requires 4 byte alignment
0xffe6aaca: note: pointer points here
00 00 00 00 00 00 8c ab e6 ff 00 e0 7a 56 20 40 7f 57 f8 aa e6 ff 00 e0 7a
56 30 00 00 00 8d 89
^
There are 62 total occurrences.
--
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=55309
Bug ID: 55309
Summary: tools/widl/expr.c:272:23: runtime error: negation of
-2147483648 cannot be represented in type 'int'; cast
to an unsigned type to negate this value to itself
(UndefinedBehaviorSanitizer)
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: tools
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: Debian
For this issue, just recompiling tools/widl is enough to see the issue:
./configure && make -j12
cd tools/widl
make clean
make CFLAGS="-fsanitize=undefined" LDFLAGS="-fsanitize=undefined"
tools/widl/widl -o include/d3d10_1.h -m32 --nostdinc -Ldlls/\* -Iinclude
-Iinclude -D__WINESRC__ \
include/d3d10_1.idl
tools/widl/expr.c:272:23: runtime error: negation of -2147483648 cannot be
represented in type 'int'; cast to an unsigned type to negate this value to
itself
Occurs for a few widl files:
tools/widl/widl -o include/d2d1.h -m32 --nostdinc -Ldlls/\* -Iinclude -Iinclude
-D__WINESRC__ include/d2d1.idl
tools/widl/widl -o include/d3d10.h -m32 --nostdinc -Ldlls/\* -Iinclude
-Iinclude -D__WINESRC__ include/d3d10.idl
tools/widl/widl -o include/d2d1effectauthor.h -m32 --nostdinc -Ldlls/\*
-Iinclude -Iinclude -D__WINESRC__ \
include/d2d1effectauthor.idl
tools/widl/widl -o include/d2d1_2.h -m32 --nostdinc -Ldlls/\* -Iinclude
-Iinclude -D__WINESRC__ \
include/d2d1_2.idl
tools/widl/widl -o include/d2d1_1.h -m32 --nostdinc -Ldlls/\* -Iinclude
-Iinclude -D__WINESRC__ \
include/d2d1_1.idl
tools/widl/widl -o include/d2d1_3.h -m32 --nostdinc -Ldlls/\* -Iinclude
-Iinclude -D__WINESRC__ \
include/d2d1_3.idl
--
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=52838
Bug ID: 52838
Summary: MachStudio Pro renders wrong
Product: Wine
Version: 7.6
Hardware: x86-64
OS: Windows
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d2d
Assignee: wine-bugs(a)winehq.org
Reporter: svyatpro(a)gmail.com
Any project is being rendered wrong in MachStudio Pro. The problem is in Wine's
D2D1.DLL. When using native Vista's d2d1.dll (7.0.6002.18107 809kb) this issue
does not appear.
Steps to repro:
1. Run MachStudio Pro
2. Open a project for example by this path \Program Files\StudioGPU\MachStudio
Pro\Data\assets\SGPU_MTL_BALL.mab
Uploaded two screenshots: Wine's d2d1.dll and native d2d1.dll from Vista.
Free GPU MachStudio Pro download link:
https://download.cnet.com/MachStudio-Pro/3000-6677_4-75498419.html
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30155
Bug #: 30155
Summary: secdrv.sys from SafeDisc v2.05.030 does not work
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntoskrnl
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: stefan(a)codeweavers.com
Classification: Unclassified
Created attachment 39336
--> http://bugs.winehq.org/attachment.cgi?id=39336
service,relay,winedevice,ntoskrnl log
SafeDisc 2.05.030 does not work out of the box. The user-visible symptom is
that the application exits with exit code 0 without any output. This affects
for example the Command and Conquer Red Alert 2 installer, which is safedisc
protected for some reason.
The problem seems to be related to the specific secdrv.sys version. If I take a
secdrv.sys from a newer safedisc version(e.g. 2.40.010 from the RA2 Yuri's
revenge expansion) and put it in C:\windows\system32\drivers, the installer
works.
ProtectId says:
Scanning -> D:\Setup\Setup.exe
File Type : 32-Bit Exe (Subsystem : Win GUI / 2), Size : 1308863 (013F8BFh)
Byte(s)
-> File has 733375 (0B30BFh) bytes of appended data starting at offset 08C800h
[File Heuristics] -> Flag : 00000000000000000100000000100111 (0x00004027)
[!] Safedisc v2.05.030 detected !
[i] Appended data contents....
[.] o: 0x0008C828 / t: <0x00000001> <0x00000000> <0x00000001> / s: 00194947
byte(s) -> ~de7bc4.tmp
[.] o: 0x000BC1D2 / t: <0x00000001> <0x00000000> <0x0000044C> / s: 00030208
byte(s) -> clcd32.dll
[.] o: 0x000C37F9 / t: <0x00000001> <0x00000000> <0x0000044C> / s: 00006784
byte(s) -> clcd16.dll
[.] o: 0x000C529D / t: <0x00000001> <0x00000000> <0x0000044D> / s: 00067584
byte(s) -> mcp.dll
[.] o: 0x000D5AC5 / t: <0x00000001> <0x00000000> <0x00000000> / s: 00327220
byte(s) -> ~df394b.tmp
[.] o: 0x00125920 / t: <0x00000001> <0x00000000> <0x00000002> / s: 00034304
byte(s) -> drvmgt.dll
[.] o: 0x0012DF47 / t: <0x00000001> <0x00000000> <0x00000002> / s: 00018768
byte(s) -> secdrv.sys
[.] o: 0x001328BF / t: <0x00000001> <0x00000000> <0x00000000> / s: 00053248
byte(s) -> ~ef7194.tmp
[CompilerDetect] -> Visual C++ 6.0
- Scan Took : 0.640 Second(s)
The md5sum of the broken secdrv.sys is XXX. The md5sum of the working 2.40.010
driver is f376a1580204e47f37a721e1cbc5582a.
I am attaching a +relay,+service,+winedevice+ntoskrnl log of a failed run of
the setup tool.
--
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=55305
Bug ID: 55305
Summary: advapi32:eventlog - test_autocreation() fails on the
Windows 10 2004 and 2009 VMs
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Created attachment 74901
--> https://bugs.winehq.org/attachment.cgi?id=74901
Minimal eventlog to reproduce the test_autocreation() failure
advapi32:eventlog - test_autocreation() fails on the Windows 10 2004 and 2009
VMs:
eventlog.c:1156: Test failed: Expected an eventlog file
See http://winetest.dolphin/data/patterns.html#advapi32:eventlog
This failure is systematic and specific to these two Windows configurations.
Also it happens even when running advapi32:eventlog on its own.
Commenting out parts of the test shows that the failure is caused by the final
CloseEventLog(handle) in test_clear(). See the attached patch to minimally
reproduce this failure.
This is similar to bug 54614: advapi32:eventlog causes the event log service to
crash which breaks test_autocreation():
Source : Service Control Manager
Event ID : 7031
The Windows Event Log service terminated unexpectedly. It has done this
1 time(s). The following corrective action will be taken in 60000
milliseconds: Restart the service.
--
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=55301
Bug ID: 55301
Summary: gdi32:font - test_bitmap_font_metrics(System) fails in
Wine for the Japanese and Chinese locales
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_bitmap_font_metrics(System) fails in Wine for the Japanese
and Chinese locales.
In the ja_JP locale:
font.c:986: Test failed: System(18): tm.tmWeight 700 != 400
In the zh_CN locale:
font.c:993: Test failed: System(16): tm.tmInternalLeading 0 != 3
See https://test.winehq.org/data/patterns.html#gdi32:font
This happens on both the TestBot's Debian 11 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=55303
Bug ID: 55303
Summary: gdi32:font - test_lang_names() fails in Wine for the
Japanese locale
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_lang_names() fails in Wine for the Japanese locale:
font.c:7268: Test failed: 2: (1) unexpected lfFaceName
L"\30d5\30a9\30f3\30c8\540d Cond (ja)"
font.c:7276: Test failed: 2: (1) unexpected elfStyle L"Regular"
font.c:7268: Test failed: 2: (0) unexpected lfFaceName L"Wine_Lang_Names"
font.c:7276: Test failed: 2: (0) unexpected elfStyle L"Regular"
font.c:7310: Test failed: 2: EnumFontFamiliesExW unexpected count 0.
font.c:7319: Test failed: 2: EnumFontFamiliesExW unexpected count 0.
See https://test.winehq.org/data/patterns.html#gdi32:font
This happens on both the TestBot's Debian 11 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=55302
Bug ID: 55302
Summary: gdi32:font fails in Wine for the Chinese locale
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 in Wine for the zh_CN locale:
test_GetCharABCWidths():
font.c:1238: Test failed: GetCharABCWidthsA 100 - 100 should have failed
font.c:1238: Test failed: GetCharABCWidthsA ffff - ffff should have failed
test_font_charset():
font.c:2703: Test failed: 0 vs 2: indices shouldn't match
test_bitmap_font_glyph_index():
font.c:6925: Test failed: expected a9, got 3f (Courier:0)
font.c:6925: Test failed: expected a9, got 3f (Small Fonts:0)
font.c:6870: Tests skipped: expected Fixedsys, got Noto Sans CJK SC
font.c:6925: Test failed: expected a9, got 3f (System:0)
See https://test.winehq.org/data/patterns.html#gdi32:font
This happens on both the TestBot's Debian 11 and Testing VMs.
There are other failures, see bug 55299 and bug 55301.
--
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=55300
Bug ID: 55300
Summary: gdi32:font - test_bitmap_font_metrics() fails in Wine
for the Arabic locale
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_bitmap_font_metrics() fails in Wine for the Arabic locale
(ar_MA):
font.c:995: Test failed: Small Fonts(11): tm.tmAveCharWidth 5 != 4
font.c:996: Test failed: Small Fonts(11): tm.tmFirstChar = 20
font.c:1001: Test failed: Small Fonts(11): tm.tmDefaultChar = 80
font.c:1002: Test failed: Small Fonts(11): tm.tmBreakChar = 20
font.c:1008: Test failed: Small Fonts(11): tm.tmMaxCharWidth 9 != 10
See See https://test.winehq.org/data/patterns.html#gdi32:font
This happens on both the TestBot's Debian 11 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=55297
Bug ID: 55297
Summary: dlls/ntdll/unix fails to build with gcc-10 and
AddressSanitizer
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: Debian
Building Wine with AddressSanitizer enabled fails in dlls/ntdll/unix with
pthread errors. To reproduce:
#!/bin/bash
export ASAN_OPTIONS=detect_leaks=0
export CFLAGS="-O0 -g -fsanitize=address"
export LDFLAGS="-fsanitize=address"
./configure
make
...
/usr/bin/ld: dlls/ntdll/unix/loader.o: in function `init_paths':
/home/austin/wine/dlls/ntdll/unix/loader.c:618: undefined reference to `dladdr'
/usr/bin/ld: dlls/ntdll/unix/loader.o: in function `dlopen_dll':
/home/austin/wine/dlls/ntdll/unix/loader.c:1166: undefined reference to
`dlerror'
/usr/bin/ld: /home/austin/wine/dlls/ntdll/unix/loader.c:1170: undefined
reference to `dlsym'
/usr/bin/ld: dlls/ntdll/unix/thread.o: in function `start_thread':
/home/austin/wine/dlls/ntdll/unix/thread.c:1102: undefined reference to
`pthread_setspecific'
--
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=51669
Bug ID: 51669
Summary: EverQuest d3d:wined3d acquires unexpected context
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: johnherschelfreeman2013(a)gmail.com
Distribution: ---
Created attachment 70543
--> https://bugs.winehq.org/attachment.cgi?id=70543
err wined3d_context_gl_reacquire
In game launcher and game client
--
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=53198
Bug ID: 53198
Summary: ws2_32:protocol - getaddrinfo() unexpectedly succeeds
for IPv6 on Windows 10 1507
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: winsock
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ws2_32:protocol - getaddrinfo() unexpectedly succeeds for IPv6 on Windows 10
1507:
protocol.c:2459: Test failed: Test 0: Got unexpected ret 0
protocol.c:2459: Test failed: Test 1: Got unexpected ret 0
protocol.c:2459: Test failed: Test 2: Got unexpected ret 0
protocol.c:2459: Test failed: Test 3: Got unexpected ret 0
protocol.c:2459: Test failed: Test 4: Got unexpected ret 0
protocol.c:2459: Test failed: Test 5: Got unexpected ret 0
protocol.c:2459: Test failed: Test 12: Got unexpected ret 0
protocol.c:2459: Test failed: Test 13: Got unexpected ret 0
protocol.c:2459: Test failed: Test 14: Got unexpected ret 0
protocol.c:2459: Test failed: Test 15: Got unexpected ret 0
protocol.c:2459: Test failed: Test 16: Got unexpected ret 0
protocol.c:2459: Test failed: Test 28: Got unexpected ret 0
protocol.c:2459: Test failed: Test 29: Got unexpected ret 0
https://test.winehq.org/data/patterns.html#ws2_32:protocol
This really looks like a Windows 10 1507 bug so it's tempting to add a
broken((hinttests[i].family == AF_UNSPEC && hinttests[i].sock_type != 999) &&
...).
But it's strange that there is no failure on index 6 for instance since it's
the same test after line 2455 (hint.ai_family = AF_INET6):
0: {AF_UNSPEC, SOCK_STREAM, IPPROTO_TCP, 0}, /* 0 */
6: {AF_INET, SOCK_STREAM, IPPROTO_TCP, 0},
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55270
Bug ID: 55270
Summary: NVIDIA OptiX SDK samples hang forever
Product: Wine
Version: 7.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: cybermax(a)dexter.no
Distribution: ---
Running NVIDA OptiX SDK samples hangs forever before drawing to screen. I have
bisected this to this particular patch:
https://gitlab.winehq.org/wine/wine/-/commit/18ae96e5fb3cbbd53f1a022ba81203…
This patch is from the https://gitlab.winehq.org/wine/wine/-/merge_requests/416
MR
Reverting this by removing XLockDisplay runs the samples again.
I am not sure why the need for a mutex + XLockDisplay is there, but i assume
the reasoning is perfectly fine - but maybe only IF one actually expect/get an
error? The OptiX samples hits the "ignored_error" thing, but seemingly just
stops without releasing the XDisplay again and thus just hang.
If interested in testing these OptiX samples, i have a pre-compiled set here:
https://github.com/SveSop/wine-nvoptix/pull/20#issuecomment-1079719794 (Read
installation instructions in that post - since the SDK hard-links binaries to
images and whatnot in the folder structure)
All of the samples in THAT particular archive do run if you use latest
"nvidia-libs" from here: https://github.com/SveSop/nvidia-libs/actions
Only nvcuda and nvoptix is needed - no need for DXVK/DXVK-NVAPI to run these
samples - but you DO need NVIDIA RTX 2xxx gpu, and with the aforementioned
revert of XLockDisplay it runs on wine-8.12 from GIT.
--
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=55222
Bug ID: 55222
Summary: Virtual Desktop does not work correctly under Wine
8.11
Product: Wine
Version: 8.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tst1(a)mixbox.pl
Distribution: ---
I use dual monitor (2 monitors).
Under Wine, I use Virtual Desktop, which covers up almost all of these two
monitors.
After updating Wine to 8.11 (under Manjaro Linux), regardless of the running
application, Wine desktop runs on only one monitor (in full screen mode).
You can then neither resize nor move the Wine desktop to the second monitor.
Downgrading Wine to my previous version: 8.8 is a workaround solution solving
the issue.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52826
Bug ID: 52826
Summary: All windows are grayed out. text is unreadable
Product: Wine
Version: 7.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mmikeinsantarosa(a)gmail.com
Distribution: ---
Created attachment 72213
--> https://bugs.winehq.org/attachment.cgi?id=72213
grayed out windows sample
cardfile.exe windows are grayed out. No text is readable. Bug has been present
since wine-6.6.
link to cardfile.exe and its help file on my google drive
https://drive.google.com/file/d/1uIJo1qtE1sQYQvgUsjiYHxBbU-ZhXehk/view?usp=…
--
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=52117
Bug ID: 52117
Summary: All windows are blacked out when running 16 bit
cardfile.exe
Product: Wine-staging
Version: 6.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mmikeinsantarosa(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 71147
--> https://bugs.winehq.org/attachment.cgi?id=71147
top window is unreadable due to being filled with black.
All windows are blacked out when running 16 bit cardfile.exe. The program runs
but text in any visible window is blacked out.
The cardfile.exe and its help can be downloaded from this link
https://drive.google.com/file/d/1uIJo1qtE1sQYQvgUsjiYHxBbU-ZhXehk/view?usp=…
--
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=55280
Bug ID: 55280
Summary: Wine should come with MSVBVM60.DLL
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: ry1tg3+RY1TN1(a)rokejulianlockhart.anonaddy.com
Distribution: ---
When I run VB6-based software with Wine, it states that the DLL is unavailable.
--
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=52576
Bug ID: 52576
Summary: Cardfile windows are grayed out
Product: Wine-staging
Version: 7.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mmikeinsantarosa(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 71902
--> https://bugs.winehq.org/attachment.cgi?id=71902
selected window grayed out
Program: cardfile.exe (16bit originally released in windows 3.1)
Symptom: selected windows are grayed out making any text unreadable.
History: this bug has been present in wine & wine-staging since release 6.6
The bug was not present in wine/wine-staging 6.5
--
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=44823
Bug ID: 44823
Summary: Steam doesn't close on exit. Will continue running in
background.
Product: Wine
Version: 3.4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: vblanton(a)gmail.com
Distribution: ---
Created attachment 60857
--> https://bugs.winehq.org/attachment.cgi?id=60857
Steam system information and version
Running the latest Steam client, I find that Steam doesn't actually close
entirely after I exit normally with Steam>Exit. I have to open System Monitor
and kill all steam and wine related processes. I can't open steam again until I
do so, and the Steam.exe and wineserver processes chew 17% of my CPU each in
the background until I do so.
--
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=55252
Bug ID: 55252
Summary: tightvnc viewer crashes on connection
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: mylazid(a)gmail.com
Distribution: ---
Created attachment 74859
--> https://bugs.winehq.org/attachment.cgi?id=74859
error occurs when connections
tightvnc viewer crashes on connection
--
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=42360
Bug ID: 42360
Summary: Terragen 4 fails to start
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: eneeen(a)gmail.com
Distribution: ---
Created attachment 57137
--> https://bugs.winehq.org/attachment.cgi?id=57137
tgd4_backlog
Using Kubuntu 16.10
I've attached backlog.
--
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=51406
Bug ID: 51406
Summary: riched32:editor fails in Wine on right-to-left locales
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: richedit
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
riched32:editor fails in Wine when run in the Arabic (EG and MA) and Hebrew
(IL) locales:
https://test.winehq.org/data/patterns.html#riched32:editor
editor.c:122: Test failed: [2] EM_GETLINECOUNT returned 2, expected 2
editor.c:122: Test failed: [5] EM_GETLINECOUNT returned 3, expected 3
editor.c:122: Test failed: [6] EM_GETLINECOUNT returned 4, expected 4
editor.c:122: Test failed: [14] EM_GETLINECOUNT returned 3, expected 3
editor.c:122: Test failed: [15] EM_GETLINECOUNT returned 4, expected 4
editor.c:455: Test failed: 1: expected_bytes_written=2
editor.c:455: Test failed: 2: expected_bytes_written=4
editor.c:455: Test failed: 3: expected_bytes_written=5
editor.c:455: Test failed: 4: expected_bytes_written=3
editor.c:876: Test failed: EM_POSFROMCHAR reports x=1, expected 8
editor.c:902: Test failed: EM_POSFROMCHAR reports x=1, expected 8
In both cases the failure are the same. Also the test succeeds in the
corresponding locales on Windows 2004.
The test on line 122 fails because Wine returns the same values in RTL locales
as in LTR ones.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.