https://bugs.winehq.org/show_bug.cgi?id=57420
Bug ID: 57420
Summary: Incorrect (broken) Japanese Font Substitution for
Tahoma via FontLink
Product: Wine
Version: 9.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: win32u
Assignee: wine-bugs(a)winehq.org
Reporter: rikul(a)inbox.ru
Distribution: ---
Created attachment 77410
--> https://bugs.winehq.org/attachment.cgi?id=77410
Left->FontLink,Right->FontSubstitutes
When configuring the Tahoma font to use a Japanese fallback font via FontLink,
issues arise with proper font substitution in Notepad++ and other applications.
Here’s a summary of the issue:
1. A FontLink -> SystemLink registry key is added for Tahoma, which includes
VL-Gothic-Regular.ttf,VL Gothic among other fonts.
2. The system locale is set to ja_JP.UTF-8.
3. Notepad++ (and other applications) is launched.
Expected Behavior: The Japanese font should display correctly throughout the
application interface.
Actual Behavior:
- In some parts in Notepad++ where using Tahoma font (e.g., menus), the
Japanese font does not display correctly, though in other areas, like the
settings window, it does.
- We have verified this behavior in other applications, and the same issue is
consistently observed.
- Without linking to VL Gothic, the Japanese text in menus becomes completely
unreadable. VL Gothic is used here as an example for a readable fallback font.
Workaround: Adding a FontSubstitutes registry entry that maps Tahoma to VL
Gothic Regular resolves the issue, and the correct font appears throughout the
interface.
Problem with the Workaround: This approach is not ideal because changing the
system locale does not automatically update the FontSubstitutes entry. As a
result, VL Gothic Regular remains set for Tahoma, which is undesirable in an
English locale, for example.
Additional Information:
- Attached are screenshots showing correct and incorrect font rendering.
- Tested on Wine 9.0 as well as the main branch, with consistent behavior in
both versions.
--
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=57429
Bug ID: 57429
Summary: Wine fails to open a terminal window if a terminal
application is invoked from the file manager
Product: Wine
Version: 9.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tobi17spam(a)gmx.de
Distribution: ---
This is on Linux Mint. If Wine is invoked from the file manager (using an open
action), on a windows terminal exe, it doesn't open a terminal on its own (like
Windows would in such a situation). When run from an existing terminal, the
executable is run as it should.
--
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=48641
Bug ID: 48641
Summary: skse64 is broken with the ntdll-ForceBottomUpAlloc
patchset
Product: Wine-staging
Version: 5.0-rc3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: qsniyg(a)mail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
While SKSE64 now works properly under wine, it hangs (then fails to launch)
when the ntdll-ForceBottomUpAlloc patchset is enabled. Building wine-staging
without that specific patchset works fine.
This is similar to how it was in earlier wine versions, before a better version
of the F4SE patches (https://github.com/hdmap/wine-hackery/tree/master/f4se)
were mainlined.
--
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=57099
Bug ID: 57099
Summary: Frosty Mod Manager opens up but apply nor launch the
game.
Product: Wine
Version: 9.13
Hardware: arm
OS: MacOS
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tanvir.maht(a)outlook.com
Frosty Mod Manager can be opened but you can’t apply mods and then launch the
game.
--
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=54114
Bug ID: 54114
Summary: Cyberworld Browser: "Could not resolve
'intro_default.url'"
Product: Wine
Version: 7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ieframe
Assignee: wine-bugs(a)winehq.org
Reporter: doomtay(a)gmail.com
Distribution: ---
Created attachment 73649
--> https://bugs.winehq.org/attachment.cgi?id=73649
Example files
https://web.archive.org/web/20020808051830id_/http://www.cyberworldcorp.com…
Cyberworld Browser Installer
When opening up "intro.borg" in the sample zip, I expect both the large web
panel and side panel to change. Instead, I get a black screen and the message
"Could not resolve 'intro_default.url'" at the bottom
--
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=30615
Bug #: 30615
Summary: Audition CS6 (5.0) - strange UI graphics
Product: Wine
Version: 1.5.3
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jan(a)lugfl.de
Classification: Unclassified
Created attachment 40072
--> http://bugs.winehq.org/attachment.cgi?id=40072
Audition CS6 Mixer screenshot
The UI looks very strange. Results with native and buildin gdiplus looks
identical.
see attached screenshot.
A log of the console output is attached too.
--
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=43670
Bug ID: 43670
Summary: MsPaint from Win7 does not start
Product: Wine
Version: 2.16
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
First you need a 32bit copy of mspaint from a win7 machine. You'll also need
"winetricks mfc42".
Program fails with a messagebox: "Failed to create empty document"
--
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=54511
Bug ID: 54511
Summary: Cygwin installer hangs during postprocessing step
Product: Wine
Version: 8.1
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
Install seems to go fine, but in the end it hangs when running
C:\cygwin64\bin\dash.exe "/etc/postinstall/0p_000_autorebase.dash"
Both wineserver and dash.exe use about half a cpu core each, but nothing seems
to happen. Comparing it to windows, that step should be fast.
Cygwin used to install fine, but even when downgrading wine I can't seem to get
it to work, it all shows the same issue. So it's probably not a Wine
regression.
--
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=57359
Bug ID: 57359
Summary: Multiple games failed to launch in DX12 mode (SILENT
HILL 2 (2024), Sumerian Six)
Product: vkd3d
Version: 1.13
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: vkd3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: gmascellani(a)codeweavers.com
Regression SHA1: 080f25c5839f8fe3ee8b082143cfff66b2497eb5
Distribution: ---
Spamming with 'err:shader_dst_param_io_normalise
../vkd3d/libs/vkd3d-shader/ir.c:1663: Unreachable code reached.'
--
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=52159
Bug ID: 52159
Summary: 64-bit cygwin gdb.exe and python3.8.exe fail to run
Product: Wine
Version: 6.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: bernhardu(a)mailbox.org
Distribution: ---
Created attachment 71205
--> https://bugs.winehq.org/attachment.cgi?id=71205
details.txt
This issue can be seen if the workarounds for bug #47808 got applied first.
Both gdb.exe and python3.8.exe fail in the python initialisation.
As far as I see it python allocates 8 bytes for a sem_t structure.
This uninitialized struct is given to sem_init which checks if this
is a previously initialized semaphore by checking
with verifyable_object_isvalid. This check happens inside
a __try/__endtry [2] [3].
That way we end up in RtlUnwindEx, which inspects
NtCurrentTeb()->Tib.ExceptionList.
Unfortunately this list finally contains a pointer to the initial stack,
which cygwin deallocated before [1].
See details.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.