https://bugs.winehq.org/show_bug.cgi?id=55536
Bug ID: 55536
Summary: Aldec Active-HDL student edition: crashes when trying
to open a file
Product: Wine
Version: 8.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: remilabelle(a)outlook.com
Distribution: ---
Created attachment 75094
--> https://bugs.winehq.org/attachment.cgi?id=75094
backtrace
Unhandled exception: unimplemented function
SHELL32.dll.SHSetTemporaryPropertyForItem called in 64-bit code
(0x00000170030088) when trying to open a file (or workspace) in Active-HDL
student edition version 13.0.376.8320 Windows64.
--
Do not reply to this email, post in Bugzilla using the
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=55591
Bug ID: 55591
Summary: Castlevania: Lords of Shadow 2 has rendering glitches
Product: Wine
Version: 7.2
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: z.figura12(a)gmail.com
Regression SHA1: 1b1b03055db8bf03c6783d4fcb19abf670d53338
Distribution: ---
Created attachment 75118
--> https://bugs.winehq.org/attachment.cgi?id=75118
example
Doesn't matter what graphics settings are used.
--
Do not reply to this email, post in Bugzilla using the
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.
https://bugs.winehq.org/show_bug.cgi?id=41977
Bug ID: 41977
Summary: Gunner3 always crashes due to wine having a different
allocation scheme than windows
Product: Wine
Version: 1.9.24
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ArchLinux
Created attachment 56382
--> https://bugs.winehq.org/attachment.cgi?id=56382
Hack to get the game working, patch for the exe
Gunner 3 always crashes when selecting a level. According to my debugging, it's
because the game allocates memory with RtlAllocateHeap and then accesses the
area before that, aka undefined behavior. But note that it works just fine on
all windows versions and ReactOS.
It's probably WONTFIX, but since it works on windows I'll provide a hack (and
maybe a patch) for usage on linux.
Attached an patch for the gunner3.exe, make sure it has the MD5
4481bc4382bb00353edf0635516d904d.
--
Do not reply 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=29255
Bug #: 29255
Summary: Microsoft Office 2003, 2007 & 2010 applications do not
print OTF
Product: Wine
Version: 1.3.34
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gunwald(a)gmx.de
Classification: Unclassified
Created attachment 37835
--> http://bugs.winehq.org/attachment.cgi?id=37835
Document showing that OTF printing does not work
All Microsoft Office applications form 2003 to 2010 are not able to print
documents using any OTF (Open Type Font). Printing a Document using any OTF
leads in a completely blank page.
I think, this is an important bug, because printing is a main function of any
office application.
This bug may be related to bug 25515
(http://bugs.winehq.org/show_bug.cgi?id=25515).
I did attach an document to demonstrate the bug.
--
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.