http://bugs.winehq.org/show_bug.cgi?id=13340
Summary: dicom image viewer aborts because
IMultiLanguage2_GetCharsetInfo doesn't like "ISO8859-1"
Product: Wine
Version: CVS/GIT
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
I had an MRI recently, and got a copy on cd-rom. The viewer app
crashed quickly on Wine.
trace:mlang:fnIMultiLanguage2_GetCharsetInfo 0x19dce8 L"ISO8859-1" 0x32f5b4
...
0009:Call KERNEL32.lstrcmpiW(01031d58 L"ISO8859-1",0032f524 L"iso-8859-1")
ret=7d52ed97
...
0009:Call oleaut32.SysAllocString(01577b00 L"System does not support the
specified encoding.\r\n") ret=69bf1378
...
wine: Unhandled exception 0x80000003 at address 0x7b83d7c1 (thread 0009),
starting debugger...
Backtrace:
=>1 0x7b83d7c1 DebugBreak+0x3() [wine-git/include/winternl.h:1828] in kernel32
2 0x7bc54140 call_entry_point+0x20() in ntdll
3 0x7bc55118 relay_call_from_32+0x1a1(descr=0x7b8b416c, idx=?,
stack=0x32f8fc) [wine-git/dlls/ntdll/relay.c:372] in ntdll
4 0x7b8273c1 in kernel32 (+0x73c1)
5 0x69b20265 in msxml4 (+0x10265)
6 0x004b8a53 in efilmlt (+0xb8a53)
Looks like Windows is more forgiving about how callers
identify charsets. We were only accepting names
like "iso-8859-1", but Windows accepts "ISO8859-1".
I have test that passes on WinXP, and a patch that fixes both the
test and the real app. Will send to wine-patches.
--
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=55210
Bug ID: 55210
Summary: Hatching printed with wrong stripes direction in
Framemaker 8
Product: Wine
Version: 8.12
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wineps.drv
Assignee: wine-bugs(a)winehq.org
Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de
Distribution: ---
When printing a hatching in Framemaker 8 the stripes are printed in
the wrong direction (from left to right instead of from right
to left and vice versa).
Attached are two FrameMaker documents each with a hatching in different
directions and the generated postscript files. The Postscript files differ
only in one (relevant) line - the /DataSource Statement created by ps.c.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55075
Bug ID: 55075
Summary: Araxis Merge 2023.5877: Application will not start
Product: Wine
Version: 8.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: djgredler(a)gmail.com
Distribution: ---
Araxis Merge 2023.5877 will not start after installation.
It looks like some Windows UWP libs (api-ms-win-core-com-l2-1-1.dll) are
missing: https://learn.microsoft.com/en-us/uwp/win32-and-com/win32-apis
The Araxis Merge installer is available here:
https://www.araxis.com/download/Merge2023.5877-x64.msi (SHA1
956406d574f21155dce99872ac0bff3f9f2b96e6)
Setup steps:
winecfg -v win10
wine Downloads/Merge2023.5877-x64.msi
wine "C:/Program Files/Araxis/Araxis Merge/Merge.exe"
Output from running application (immediate crash):
0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
00d4:err:module:import_dll Library api-ms-win-core-com-l2-1-1.dll (which is
needed by L"C:\\Program Files\\Araxis\\Araxis Merge\\Merge.exe") not found
00d4:err:module:LdrInitializeThunk Importing dlls for L"C:\\Program
Files\\Araxis\\Araxis Merge\\Merge.exe" failed, status c0000135
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55045
Bug ID: 55045
Summary: NFS Most Wanted has missing graphics with WineD3D in
WoW64 mode
Product: Wine
Version: 8.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: aidas957(a)gmail.com
Distribution: ArchLinux
Created attachment 74608
--> https://bugs.winehq.org/attachment.cgi?id=74608
NFS Most Wanted graphics corruption screenshot
Hello,
as you have seen in the title, Need for Speed Most Wanted has missing graphics
when using WineD3D together with the new WoW64 mode (the old WoW64 mode works
fine as expected)
The first thing you'll notice is that the intro video is a black screen with a
semi-broken cursor
After that the start screen is completely black with some flickering (and then
once the main menu loads the 3D scene looks fine but the 2D menu interface is
missing completely except for some weird flickers)
If I load the game in the old WoW64 mode, the issues disappear and the game
looks correct
Now for some system information:
Kernel: 6.3.6-arch1
Graphics driver: Mesa 23.1.2 (with radeonsi driver being used)
GPU: AMD Renoir (the GPU in my Ryzen 5 4600H)
Window manager: KWin 5.27.5 (Wayland)
I couldn't upload a log and a trace to the Bugzilla attachments due to file
size limits, so here they are:
WineD3D WoW64 apitrace (done from the Linux side):
https://drive.google.com/file/d/1JkRbuoq9QLeQ8EsLvIVRnVvn4Ub1PthI/view
Huge Wine log (with +d3d,+d3d9,-ver,-d3dx):
https://drive.google.com/file/d/1731nk11aUqVrJHw42TbulQ9WkvmT7rTz/view
Note: I had to apply this patch
(https://gitlab.winehq.org/wine/wine/-/commit/13b9d7da6446ba6386be6c586c7d15…)
to prevent the game from crashing (because WoW64 doesn't support the
PERSISTENT_BIT flag yet)
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55065
Bug ID: 55065
Summary: user32:monitor - check_preferred_mode() fails on the
TestBot's debiant VM
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
user32:monitor - check_preferred_mode() fails on the TestBot's debiant VM:
monitor.c:1699: Tests skipped: Current display mode is already 1024x768,
skipping test.
monitor.c:1788: Test marked todo: Expected 0, got 50
monitor.c:1789: Test marked todo: Expected adapter device path, got empty
string
monitor.c:1729: Test failed: got -2.
monitor.c:1788: Test marked todo: Expected 0, got 50
monitor.c:1789: Test marked todo: Expected adapter device path, got empty
string
monitor.c:1699: Tests skipped: Current display mode is already 1024x768,
skipping test.
monitor.c:1788: Test marked todo: Expected 0, got 50
monitor.c:1789: Test marked todo: Expected adapter device path, got empty
string
monitor.c:1729: Test failed: got -2.
monitor.c:1788: Test marked todo: Expected 0, got 50
monitor.c:1789: Test marked todo: Expected adapter device path, got empty
string
See: https://test.winehq.org/data/patterns.html#user32:monitor
The failures started with the commit below which introduced
check_preferred_mode():
commit 24019f0d385c653d58be50f7941256e4e1c8b68a
Author: Paul Gofman <pgofman(a)codeweavers.com>
Date: Wed Apr 19 18:57:04 2023 -0600
win32u: Partially implement
NtUserDisplayConfigGetDeviceInfo(DISPLAYCONFIG_DEVICE_INFO_GET_TARGET_PREFERRED_MODE).
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54037
Bug ID: 54037
Summary: user32:msg - test_SendMessage_other_thread() sometimes
gets a todo success (GitLab CI)
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
user32:msg - test_SendMessage_other_thread() sometimes gets a todo success:
msg.c:19067: Test succeeded inside todo block: WaitForSingleObject failed,
ret:0
msg.c:19091: Test succeeded inside todo block: wrong status 00000000
See https://test.winehq.org/data/patterns.html#user32:msg
This happens about once a month on the Debian VMs in the TestBot nightly
WineTest runs, but is also known to impact the GitLab CI (e.g. MR!1596 MR!1519
).
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53175
Bug ID: 53175
Summary: Roon no longer works under wine staging, help needed,
thanks.
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: rustytone(a)gmx.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 72621
--> https://bugs.winehq.org/attachment.cgi?id=72621
backtrace of the roon application - failed start, get it every time i launch.
hello sorry if this in the wrong section,
I have roon installed using wine-staging, the wine (non staging) doesn't seem
to work well with the roon windows application so decided to go with staging
release.
it was working correctly until 2 days ago, there was an update to wine-staging
and an update to the roon application as well.
hopefully the backtrace is helpful and I have included it,
running arch, latest updates, latest kernel, latest wine-staging etc.
any more information you need I will be happy to assist.
sorry again if this in the wrong section.
thank you - antonio.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49527
Bug ID: 49527
Summary: Printing font Chilanka crashes Notepad and Word
Product: Wine
Version: 5.12
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wineps.drv
Assignee: wine-bugs(a)winehq.org
Reporter: bernhardu(a)mailbox.org
Distribution: ---
Created attachment 67657
--> https://bugs.winehq.org/attachment.cgi?id=67657
Avoid crash in get_glyf_pos in wineps.drv with font Chilanka.
Function get_glyf_pos accesses unconditionally the memory pointed to by
".data".
Unfortunately with this font we end up here with a null pointer.
123 *start = GET_BE_WORD(((WORD*)t42->tables[t42->loca_tab].data) + index);
I could observe this with following font:
fonts-smc-chilanka_1.400-1_all.deb from Ubuntu focal (20.04LTS).
https://packages.ubuntu.com/focal/fonts-smc-chilankahttp://de.archive.ubuntu.com/ubuntu/pool/main/f/fonts-smc-chilanka/fonts-sm…
To reproduce just enter "Test" and select font "Chilanka" in either Notepad
or Word. Then attempt to print.
Attached path on top of 5.12 avoids the crash, but does still not
produce the expected output, maybe related to 42739.
But avoiding the crash separately might still be desired?
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53905
Bug ID: 53905
Summary: widl: support MIDL 3.0 and WinMD output
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tools
Assignee: wine-bugs(a)winehq.org
Reporter: alvin(a)alvinhc.com
C++/WinRT (cppwinrt):
https://github.com/microsoft/cppwinrt
It is currently impossible to build the custom components in the cppwinrt test
suite with mingw-w64. For this to work, widl needs to:
- understand MIDL 3.0 syntax,
- generate the ABI header (not required if only using C++/WinRT projection),
- produce .winmd metadata of the component,
- read existing system .winmd metadata (not sure if actually needed).
The MIDL command line for this:
midl.exe /metadata_dir C:\Windows\System32\WinMetadata /winrt /winmd
"D:\a\cppwinrt\cppwinrt\_build\x64\Debug\test_component.winmd" /h
"D:\a\cppwinrt\cppwinrt\_build\x64\Debug\test_component.h" /ns_prefix /nomidl
test_component.idl
## MIDL 3.0
https://learn.microsoft.com/en-us/uwp/midl-3/intro
What I can tell is missing widl so far:
- MIDL 3.0 uses different basic type names (e.g. Int32, String)
- Attribute types, and using custom attributes
Example file:
https://github.com/microsoft/cppwinrt/blob/5ca626adae21be363399b44d2b6a9ab3…
> widl --winrt -h -H out/test_component.h --ns_prefix test_component.idl
test_component.idl:5: error: syntax error, unexpected aIDENTIFIER,
expecting ',' or ']'
(widl version 7.7 from mingw-w64)
## WinMD metadata
https://learn.microsoft.com/en-us/uwp/winrt-cref/winmd-files
These are CLR (think .NET and ECMA 335) assemblies used as a replacement for
the old typelib files.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.