https://bugs.winehq.org/show_bug.cgi?id=38270
Bug ID: 38270
Summary: unimplemented function msctf.dll.TF_CreateCicLoadMutex
called by ctfmon.exe
Product: Wine
Version: 1.3.26
Hardware: x86
OS: Linux
Status: NEW
Keywords: download
Severity: enhancement
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: ---
If you have xpsp3 from winetricks, you can get the files needed:
$ cabextract -F i386/ctfmon.ex_
~/.cache/winetricks/xpsp3/WindowsXP-KB936929-SP3-x86-ENU.exe
$ cabextract -F i386/msutb.dl_
~/.cache/winetricks/xpsp3/WindowsXP-KB936929-SP3-x86-ENU.exe
$ cd i386
$ cabextract *
$ wine ctfmon.exe
fixme:msctf:TF_InitMlngInfo stub
wine: Call from 0x7b83962c to unimplemented function
msctf.dll.TF_CreateCicLoadMutex, aborting
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52813
Bug ID: 52813
Summary: ArmA II: Operation Arrowhead crashes after splash
screen
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: desperategame(a)gmail.com
Distribution: ---
Created attachment 72192
--> https://bugs.winehq.org/attachment.cgi?id=72192
ArmA2OA.exe archlinux journald systemd-coredump
Arma 2 and ArmA II: Operation Arrowhead crashes after showing splash screen
before main menu should show.
it happens on:
- Gentoo mixed unstable ~amd64, updated after ~ in between 2022.01.01 -
2022.04.01, wine-vanilla and wine-staging, nine and without nine, 6.0.2 - 7.6
- Arch installed 12.04.2022, wine-nine
this is not in:
- Mint, old non-updated, without nine
it wasn't there before on:
- Gentoo mixed unstable ~amd64, before ~ in between 2022.01.01 - 2022.04.01,
wine-vanilla and wine-staging, nine and without nine, maybe 6.? - 7.3
Video:
- Radeon HD 5000 M, r600
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54067
Bug ID: 54067
Summary: Ultrakill demo: cursor behaves erratically
Product: Wine
Version: 7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: dinput
Assignee: wine-bugs(a)winehq.org
Reporter: matheus.venturini(a)acad.ufsm.br
Distribution: ---
How to reproduce:
1. Install the Ultrakill demo for Windows
2. Complete the tutorial
3. In the first level, walk up to the weapon vending machine and press the left
mouse button
When interacting with the vending machine in the game, an interface should be
displayed where you can interact with buttons to choose the weapon you want to
buy. This is different from the rest of the game in that a cursor is visible
and it is used to select things rather than being used to aim. On Wine the
vending machine interface will not appear, and pressing the left mouse button
thereafter will cause the aim to go down, perpendicular to the ground. You
can't shoot afterwards, so it's impossible to progress.
This happens on a fresh prefix. I tested it on two machines and it happened in
both, one running Zorin OS 16 and another running Lubuntu 22.04.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54218
Bug ID: 54218
Summary: RTLD_SELF use breaks musl build since 8.0-rc1
Product: Wine
Version: 8.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: alice(a)ayaya.dev
Distribution: ---
the winecrt0 rework in bef09697227c29f53bb0ad95232399cbba5c9c6b makes use of
dlinfo(RTLD_SELF, .. , which breaks the build on musl libc as it does not
implement the RTLD_SELF handle.
example error:
/home/demon/src/aports/community/wine/src/wine-8.0-rc2/dlls/winecrt0/dll_soinit.c:
In function '__wine_init_so_dll':
/home/demon/src/aports/community/wine/src/wine-8.0-rc2/dlls/winecrt0/dll_soinit.c:95:17:
error: 'RTLD_SELF' undeclared (first use in this function); did you mean
'RTLD_NEXT'?
95 | if (dlinfo( RTLD_SELF, RTLD_DI_LINKMAP, &map )) return;
| ^~~~~~~~~
| RTLD_NEXT
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53536
Bug ID: 53536
Summary: ntdll:rtl - The 32-bit RtlUlonglongByteSwap() breaks
test_RtlDecompressBuffer() on Windows
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 - The 32-bit RtlUlonglongByteSwap() breaks test_RtlDecompressBuffer()
on Windows:
rtl.c:2790: Running test 0 (compressed_size=6, uncompressed_size=4,
status=0x00000000)
rtl.c:2790: Running test 1 (compressed_size=10, uncompressed_size=8,
status=0x00000000)
rtl.c:2790: this is the last test seen before the exception
170c:rtl: unhandled exception c0000005 at 005542C0
https://test.winehq.org/data/patterns.html#ntdll:rtl
The crash is specific to the 32-bit build.
Strangely the crashes started on 2022-07-26 despite there being no changes to
this test or to the test configurations. Also, the crash still happens when
testing older Wine versions.
Anyway, the crash still happens even when only keeping these two tests:
test_RtlUlonglongByteSwap();
test_RtlDecompressBuffer();
The Windows headers claims that RtlUlonglongByteSwap() is a FASTCALL API but
not so in Wine:
winternl.h: NTSYSAPI ULONGLONG __cdecl RtlUlonglongByteSwap(ULONGLONG);
rtl.c: static ULONGLONG (WINAPIV *pRtlUlonglongByteSwap)(ULONGLONG
source);
Replacing WINAPIV with WINAPI in rtl.c fixes the crash but it's probably not
the correct fix.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53382
Bug ID: 53382
Summary: Slow rendering when connected to external monitor
Product: Wine
Version: 7.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: allencch(a)hotmail.com
Distribution: ---
Created attachment 72769
--> https://bugs.winehq.org/attachment.cgi?id=72769
Slow winecfg GIF
When connected with an external monitor through HDMI, winecfg and explorer are
extremely slow rendering.
If enabled "Emulate a virtual desktop", rendering will become normal. Without
connecting on external monitor, the rendering is normal as well.
There is an error message shown in console when the rendering is slow comparing
to the normal rendering,
0068:fixme:xrandr:xrandr10_get_current_mode Non-primary adapters are
unsupported.
OS: Arch 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=54180
Bug ID: 54180
Summary: Petz 4: Recent wine releases (after 6.0) corrupt .pet
files upon startup of game
Product: Wine
Version: 7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: coreyjosesilva(a)gmail.com
Distribution: ---
Dogz 4, Catz 4, Dogz 5, Catz 5 all share this issue. The .pet files are the way
to save "pets" in the game. The files are corrupted in recent wine releases.
This essentially makes the game unplayable.
I confirmed petz 4 works on wine 6.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=54045
Bug ID: 54045
Summary: ntdll:rtl - test_RtlIpv6StringToAddress() 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:rtl - test_RtlIpv6StringToAddress() fails on Windows 11:
rtl.c:2061: Test failed: [::0:0:0:0:0:0:0] terminator = 0052F925, expected
0052F923
rtl.c:2061: Test failed: [::0:a:b:c:d:e:f] terminator = 0052F935, expected
0052F933
rtl.c:2067: Test failed: [::0:a:b:c:d:e:f] ip = 0:0:a00:b00:c00:d00:e00:f00,
expected 0:0:0:a00:b00:c00:d00:e00
rtl.c:2293: Test failed: [::0:0:0:0:0:0:0] res = 0x00000000, expected
0xc000000d
rtl.c:2293: Test failed: [::0:a:b:c:d:e:f] res = 0x00000000, expected
0xc000000d
See https://test.winehq.org/data/patterns.html#ntdll:rtl
Note that the 32-bit version crashes too due to bug 53536.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53671
Bug ID: 53671
Summary: No objects are being rendered in any DX10/11 apps with
older GPU drivers
Product: Wine
Version: 7.17
Hardware: x86-64
OS: Windows
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: svyatpro(a)gmail.com
There is a regression after a patch 5ce7adaace3637ff6f8a33264b62c69bf2e53967
I have AMD graphics with outdated driver for Windows XP.
Stating from the patch above it broke WineD3D10/11 compatibility.
This BUG appeared with WineD3D 6.13 and above.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52994
Bug ID: 52994
Summary: mstask:task_trigger - test_GetNextRunTime() fails in
Wine on date change
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: mstask
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
Created attachment 72360
--> https://bugs.winehq.org/attachment.cgi?id=72360
Make the failure 100% reproducible
mstask:task_trigger - test_GetNextRunTime() fails in Wine on date change:
task_trigger.c:434: old: 5/5/2022 wday 0 23:58:00.000
task_trigger.c:443: new: 6/5/2022 wday 5 0:03:00.000
task_trigger.c:533: Test failed: got 0x41307
task_trigger.c:534: Test failed: got 0/0/0 wday 0 0:00:00
https://test.winehq.org/data/patterns.html#mstask:task_trigger
What seems to be happening is that ITask_GetNextRunTime() returns
SCHED_S_TASK_NO_VALID_TRIGGERS for TASK_TIME_TRIGGER_ONCE tasks where the
trigger is on the next day.
So I suspect the bug is in the ITask_GetNextRunTime() implementation rather
than in the test itself.
Note: Initially I was a bit alarmed by the week day change in the traces. But
in fact trigger_add_ms() just sets it to 0 so that's what we get on the "old:"
line. Then FileTimeToSystemTime() fully initializes it so we get the correct
value on the "new:" line. That's why it changes in surprising ways.
Luckily the test and Itask_GetNextRunTime() implementation were both added in
the commit below and I was also able to confirm that the failure was already
present:
commit ac322334fa4d6740e89c6f19361a66f063103a46
Author: Dmitry Timoshkov <dmitry(a)baikal.ru>
AuthorDate: Mon May 21 18:17:47 2018 +0800
mstask: Implement ITask::GetNextRunTime() for ONCE trigger type.
Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.