https://bugs.winehq.org/show_bug.cgi?id=55100
Bug ID: 55100
Summary: Final Fantasy XIV: Backspace stops working after
backspacing Japanese composition string
Product: Wine
Version: 8.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: imm32
Assignee: wine-bugs(a)winehq.org
Reporter: achurch+wine(a)achurch.org
Distribution: ---
Created attachment 74666
--> https://bugs.winehq.org/attachment.cgi?id=74666
Possible fix
Environment: Linux, LANG=ja_JP.UTF-8, ATOK X3 (XIM)
In Final Fantasy XIV using Japanese input, after backspacing the last character
in a pending composition string (with the fix for bug 55055 in
https://gitlab.winehq.org/wine/wine/-/commit/e5646191723fa4b5e4cb38187e1611…
applied), the game no longer accepts backspace input in the text field.
Specifically, given the following sequence:
1) Activate a text input field (such as the screenshot folder path entry field
in Settings -> Other Settings from the title screen).
2) Press backspace in the input field and observe that the last character of
the string is deleted.
3) Activate the IME.
4) Press the "A" key, giving the composition string "あ", which is displayed at
the end of the string.
5) Press backspace, leaving an empty composition string.
Pressing backspace again should delete the character at the end of the string
as in step 2, but instead does nothing. (Backspace also does not work after
turning on the IME and before any input, as between steps 3 and 4, but does
work correctly immediately after confirming a conversion.)
Sending WM_IME_ENDCOMPOSITION in ImeToAsciiEx() when dwCompStrLen is zero, as
in the attached patch, seems to fix the bug, so FFXIV may be expecting an
explicit ENDCOMPOSITION or similar message to switch from a "waiting for
composition" state to "normal text input".
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=38890
Bug ID: 38890
Summary: Terraria - terraria.exe crashes on startup
Product: Wine
Version: 1.7.44
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: trojangoat(a)gmail.com
Distribution: ---
Created attachment 51828
--> https://bugs.winehq.org/attachment.cgi?id=51828
Backtrace of startup issue
Terraria 1.3.0.3 has been working flawlessly until external updates applied
today. Not sure exactly what is causing this 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=39930
Bug ID: 39930
Summary: HtmlHelp() shows blank page when '\\' is used as path
separator after '::'
Product: Wine
Version: 1.9.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: hhctrl.ocx
Assignee: wine-bugs(a)winehq.org
Reporter: foka(a)debian.org
Distribution: ---
Despite the fact that Microsoft documentation clearly states that
Anything after the double colon (::) must use forward slashes (/),
in accordance with URL standards.
(see https://support.microsoft.com/en-us/kb/235226), Windows developers tend to
forget(?) that rule and use backslashes (\) after the double colon.
For example, running UFile 2013 under Wine, opening the tutorial comes up with
a blank window, and the trace/fixme messages are logged:
trace:htmlhelp:HtmlHelpW (0x1006e,
L"ubxkbE.chm::\\tutorial/pages/1intro.htm>DT_HTML_TUT",
command=HH_DISPLAY_TOPIC, data=0)
trace:htmlhelp:NavigateToChm 0x208ba0 L"C:\\Program Files\\UFile
2013\\ubxkbE.chm" L"\\tutorial/pages/1intro.htm"
trace:htmlhelp:AppendFullPathURL L"C:\\Program Files\\UFile
2013\\ubxkbE.chm" 0x31dc98 L"\\tutorial/pages/1intro.htm"
trace:htmlhelp:navigate_url L"mk:@MSITStore:C:\\Program Files\\UFile
2013\\ubxkbE.chm::/\\tutorial/pages/1intro.htm"
fixme:ieframe:handle_navigation_error Navigate to error page
But of course, as a retail product, UFile 2013's tutorial of course shows
correctly in Windows.
Apparently, Microsoft knows how often developers get confused by '/' and '\',
and silently accepts such erroneous backslashes so that the relevant HTML Help
can be displayed.
The current Wine implementation of HTML Help, however, does not account for
such developer errors, leading to such blank HTML Help windows in (slightly)
buggy programs like UFile 2013.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53897
Bug ID: 53897
Summary: Programmer's File Editor MDI windows initially open
with doubled-up scroll bars
Product: Wine
Version: 7.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: wine_bugzilla(a)sctb.ch
Distribution: ---
Created attachment 73438
--> https://bugs.winehq.org/attachment.cgi?id=73438
Screenshot of doubled-up scroll bars.
I've been using Programmer's File Editor (PFE), a text editor from 1999, with
WINE, since the beginning of time.
There has always been a problem that when the editor starts, the scroll bars
(vertical and horizontal) are doubled up. It's an MDI interface, which I think
is the problem.
Clicking on a scrollbar, tiling the windows, etc - anything which makes them do
something - returns the scrollbars to the normal state.
Screenshot 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=54122
Bug ID: 54122
Summary: Call of Juarez - Bound in Blood in-menu videos don't
work
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: VladimirVSC(a)yandex.ru
Distribution: ---
Created attachment 73655
--> https://bugs.winehq.org/attachment.cgi?id=73655
The output of missing videos
The video-animated background into the main menu doesn't work. The same for 7.0
and 8.0-rc1. The output 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=54031
Bug ID: 54031
Summary: user32:msg - test_SendMessage_other_thread() broken by
WM_WINDOWPOSCHANGING on Windows dual-monitor configs
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_SendMessage_other_thread() sometimes gets an unexpected
WM_WINDOWPOSCHANGING message:
msg.c:19053: Test failed: wrong status 00480048
msg.c:19091: Test failed: SendMessage from other thread 5: 0: the msg sequence
is not complete: expected 0000 - actual 0046
msg.c:19091: Failed sequence SendMessage from other thread 5:
msg.c:19091: 0: expected: nothing - actual: MsgCheckProc: 006F025C
WM_WINDOWPOSCHANGING wp 00000000 lp 0022fc40 after 00000000 x 100 y 100 cx 200
cy 200 flags SWP_NOACTIVATE|SWP_NOZORDER (flags 19)
msg.c:19091: 1: expected: nothing - actual: MsgCheckProc: 006F025C 0024 wp
00000000 lp 0022f700 (flags 39)
msg.c:19059: Failed sequence SendMessage from other thread 1:
msg.c:19059: 0: expected: msg 0402 - actual: MsgCheckProc: 007102CA 0402 wp
00000000 lp 00000000 (flags 19)
msg.c:19059: 1: expected: msg 0400 - actual: MsgCheckProc: 007102CA 0400 wp
00000000 lp 00000000 (flags 19)
msg.c:19079: Failed sequence SendMessage from other thread 3:
msg.c:19079: 0: expected: msg 0403 - actual: MsgCheckProc: 007102CA 0403 wp
00000000 lp 00000000 (flags 19)
msg.c:19079: 1: expected: msg 0401 - actual: MsgCheckProc: 007102CA 0401 wp
00000000 lp 00000000 (flags 19)
[53435] msg.c:19087: Test failed: wrong status 00400040
msg.c:19091: Failed sequence SendMessage from other thread 5:
msg.c:18487: Failed sequence SetFocus on a desktop window:
msg.c:18497: Failed sequence SetFocus on another thread window:
msg.c:18517: Failed sequence SetActiveWindow on a desktop window:
msg.c:18527: Failed sequence SetActiveWindow on another thread window:
msg.c:18592: Failed sequence SetFocus on a child window:
msg.c:18592: 0: expected: hook 0009 - actual: CBT: hook 9 (HCBT_SETFOCUS) wp
005e0252 lp 002f0278
msg.c:12896: QS_RAWINPUT not supported on this platform
msg.c:12921: Test failed: wrong qstatus 00000000
See https://test.winehq.org/data/patterns.html#user32:msg
This seems to only happen on dual-monitor configurations, most frequently on
w1064-2qxl but also regularly on w7u-2qxl.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52571
Bug ID: 52571
Summary: batch token parsing regression
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: dragonwarriorxtreme(a)gmail.com
Distribution: ---
This is easily demonstrated with vcvars script batch files in Visual Studio
2015, on amd64.
>)
>)
>)
>)
>)
>Can't recognize 'x86' as an internal or external command, or batch script.
>Can't recognize '\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.1 Tools\x64\;C:\windows\system32;C:\win
dows;C:\windows\system32\wbem;C:\windows\system32\WindowsPowershell\v1.0' as an
internal or external
command, or batch script.
>Can't recognize 'x86' as an internal or external command, or batch script.
>Can't recognize '\Windows Kits\NETFXSDK\4.6.1\include\um;' as an internal or external command, or bat
ch script.
>Can't recognize 'x86' as an internal or external command, or batch script.
>Can't recognize '\Windows Kits\NETFXSDK\4.6.1\lib\um\x86;' as an internal or external command, or bat
ch script.
>Can't recognize 'x86' as an internal or external command, or batch script.
>Can't recognize '\Microsoft Visual Studio 14.0\Team Tools\Performance Tools\x64;C:\Program Files ' as
an internal or external command, or batch script.
>Can't recognize 'x86' as an internal or external command, or batch script.
... etc ...
1. Install Visual Studio 2015 (latest Wine-git works around ncrypt limitations)
or the v140/v141 build tools using 2017 (already works).
What I did personally (was attempting to compile x86 programs on an x64 install
before I hit this bug):
2. cd C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\amd64_x86
3. wine cmd /K vcvarsamd64_x86.bat
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55031
Bug ID: 55031
Summary: experimental wow64 mode: crashes in some 3d graphics
code
Product: Wine
Version: 8.10
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 74591
--> https://bugs.winehq.org/attachment.cgi?id=74591
wine.crash.log
When I'm trying to run Spellforce 2 with experimental wow64 wine mode, it
crashes. When I'm running it using normal multilib setup, everything runs fine,
at least until main menu, didn't check again further.
Same happens when I'm trying to run Torchlight 2 from Steam. Demo available on:
https://store.steampowered.com/app/200710/Torchlight_II/
Crashing wine build options: ./configure --with-mingw
--enable-archs='i386,x86_64' --prefix=/tmp/wineinstall
Suspicious log lines just before crash:
0114:fixme:opengl:wow64_map_buffer GL_MAP_PERSISTENT_BIT not supported!
wine: Unhandled page fault on write access to 5BFFF000 at address 6AB23144
(thread 0114), starting debugger...
OS: Gentoo Linux amd64 (64bit)
Graphics: X11
Videocard information:
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: Quadro K1000M/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 470.182.03
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55246
Bug ID: 55246
Summary: ntdll:om - The 64-bit test_object_types() crashes on
Windows 8+
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:om - The 64-bit test_object_types() crashes on Windows 8+:
om.c:2325: this is the last test seen before the exception
1c98:om: unhandled exception c0000005 at 00007FFFC32A60AB
See https://test.winehq.org/data/patterns.html#ntdll:om
Where c0000005 == STATUS_ACCESS_VIOLATION
This started on 2023-07-10 which corresponds to the GitLab CI switch to Debian
12 for builds which means it is caused by the commit below:
commit 5799e89f15b5584f186dcc2fd24b98e0a7bd6c10
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Mon Jul 10 17:18:49 2023 +0200
gitlab: Upgrade the Debian image to bookworm.
Note that, to this day, the 64-bit binaries produced by the TestBot still run
successfully on Windows because they are built on Debian 11. But the nightly
WineTest runs fail because they use the official WineTest binaries produced by
the GitLab CI which uses Debian 12.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54331
Bug ID: 54331
Summary: Game "Antecrypt": Black screen after launch
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: stabilergriller(a)gmail.com
Distribution: ---
Created attachment 73894
--> https://bugs.winehq.org/attachment.cgi?id=73894
Output when running "wine beam.exe"
This shooting game from https://punkcake.itch.io/antecrypt just opens up a
window which is completely black.
I confirm that this game runs on Windows 10.
My set up:
OS: Arch 64-Bit
GPU: Intel HD Graphics 610
Mesa: 22.3.3
Kernel version: 6.1.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.