https://bugs.winehq.org/show_bug.cgi?id=53939
Bug ID: 53939
Summary: TextOut will output ASCII control character(0~31) as
tofu cause crash
Product: Wine
Version: 7.12
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: 399989567(a)qq.com
Distribution: ---
TextOut will output ASCII control character(0~31) as tofu cause crash
build a string on windows
> static WCHAR str[] = {0x1c,0x30,0x31,0x32,0}
use TextOut(hdc,x,y,str,wcslen(str)) to output this str
on windows: output is "012"
on wine : output is "?012"
The reason is that this API does not filter ASCII control characters, and
treats the control characters as an ordinary character to output.
by the way if we fillter the control character we alse need fix the API
:GetTextExtentExPointW
Because my program uses control characters, there will be problems when
calculating the length, resulting in a crash. If I filter out the control
characters in the code myself, it will not crash. And in principle, the focus
should be on whether control characters should be output
--
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=55411
Bug ID: 55411
Summary: Stack overflow when running Battle For Middle Earth
2.22 Launcher
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: danielginovker(a)gmail.com
Distribution: ---
Created attachment 74971
--> https://bugs.winehq.org/attachment.cgi?id=74971
Logs when running Restarter.exe
Hello beautiful Wine developers,
Battle for Middle Earth is an old game with custom launchers being used to make
it compatible and playable on modern Windows PCs.
When running recent versions of the launcher (cd "~/.wine/drive_c/Patch 2.22
Launcher" ; wine Restarter.exe) after installing it in a fresh wine prefix, it
gets stuck and outputs "virtual_setup_exception stack overflow"
The launcher is downloadable on Moddb (this is the official place to find the
Patch 2.22 launcher .exe):
https://www.moddb.com/mods/battle-for-middle-earth-patch-222/downloads/patc…
The source code for the launcher is also available on Github:
https://github.com/Ravo92/Patch-2.22-Launcher
--
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=45329
Bug ID: 45329
Summary: Fresh steam install will not install games -- error:
"content servers unreachable"
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alasky(a)codeweavers.com
Distribution: ---
Created attachment 61617
--> https://bugs.winehq.org/attachment.cgi?id=61617
Steam error dialogue box
Ubuntu 18.04
Wine tip (most recent commit is
83f845dfa1bb4a6ec6e8b7f65e9469dc9a8a7787)
When attempting to install a game on a fresh Steam install, an error comes up
that says "content servers unreachable." The servers are not down and I am
able to install games correctly on my steam account not using wine. This issue
seems to be caused by an update on Steam's side.
--
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=54761
Bug ID: 54761
Summary: D3D12CreateDevice no longer in ABI of
libvkd3d-utils.so.1
Product: vkd3d
Version: 1.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: vkd3d
Assignee: wine-bugs(a)winehq.org
Reporter: smcv(a)collabora.com
Distribution: ---
While looking at updating Debian's vkd3d package from 1.2 to 1.7, I noticed
that `D3D12CreateDevice@VKD3D_1_0` disappeared from the ABI of
libvkd3d-utils.so.1. Was this intentional?
(D3D12CreateDeviceVKD3D@VKD3D_1_0 is still there, but if I'm understanding the
intention of this library correctly, D3D12CreateDevice@VKD3D_1_0 should have
continued to be present for backwards compat with older library binaries.)
--
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=55474
Bug ID: 55474
Summary: Lunar Client do not work since its last update (3.0.0)
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: brandowlucas(a)gmail.com
Distribution: ---
Created attachment 75034
--> https://bugs.winehq.org/attachment.cgi?id=75034
log lunar wine
As said in the title, since lunar client updated its launcher it freezes in a
infinite loading.
--
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=55373
Bug ID: 55373
Summary: Running native application inside a windows one, shows
a terminal
Product: Wine
Version: 8.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: cagnulein(a)gmail.com
Distribution: ---
Since Wine4 i'm using this
https://wiki.winehq.org/FAQ#How_do_I_launch_native_applications_from_a_Wind…
to run my native application inside a Windows applications.
Starting from Wine 8, every time I run a native application from a Windows one,
a terminal window popups. How can I prevent this returning to the default
behaviour?
Thanks
--
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=54784
Bug ID: 54784
Summary: mIRC 7.72 crashes after restoring from application
tray
Product: Wine
Version: 8.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dragone2(a)risposteinformatiche.it
Distribution: ---
Created attachment 74279
--> https://bugs.winehq.org/attachment.cgi?id=74279
Unhandled exception: page fault on read access - mIRC - Wine-staging 8.5
mIRC was running for about 4-5 hours before the crash.
It was reduced on the tray and its icon was blinking to notify that there were
new messages / activities in channels or private messages.
I clicked on it to restore the window and see the messages and wine gave me
this backtrace (see the attachment).
I was forced to quit mIRC and restart it again.
This rarely happens, so it's not a real problem for me, but I don't know if it
could help you fix this.
Other infos:
- Executable path: D:\mIRC\mirc.exe
- mIRC Version: 7.72 (the latest one).
- mIRC running in portable mode from a specific drive (on Wine, D:\) formatted
in NTFS.
- mIRC was running using some custom scripts. But this crash never happen on
Windows.
- Distro: Linux Mint 21.1 with latest updates.
- Kernel: 5.15.0-69-generic
- Wine infos:
Wine build: wine-8.5 (Staging)
Platform: i386 (WOW64)
Version: Windows 10
- Drive Z: is a drive formatted in BTRFS.
- CPU: Intel Core i7-6700
- RAM: 32 GB, when the crash occurred I was using less than 8 GB.
--
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=52676
Bug ID: 52676
Summary: enigma protected software fails to work properly
Product: Wine
Version: 7.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: galtgendo(a)o2.pl
CC: dark.shadow4(a)web.de
Distribution: ---
Created attachment 72003
--> https://bugs.winehq.org/attachment.cgi?id=72003
backtrace of the crash (note the garbage)
As I've said in bug 49052, the trial that's supposed to work just crashes
without displaying anything.
Attaching console output.
I've got one other trial that's also enigma protected - that one starts, but
enters an infinite loop without displaying anything. That one is using an
engine that's known to work here, so I suspect enigma being the reason of the
failure.
--
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=4045
Bloody Iron <bloodyiron(a)lanified.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bloodyiron(a)lanified.com
--- Comment #22 from Bloody Iron <bloodyiron(a)lanified.com> ---
DPI issues are persisting, and this also is present in Wayland.
Latest example for me is Ubuntu 22.04 on a Microsoft Surface Pro 9, which runs
a display of 2880x1920 (3:2) and I believe it was a regular DPI of 271, up from
the normal 96. But in testing 192 seems to be a good number-ish.
In my case installing Mono the install dialogue is so small it's next to
impossible to read.
--
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.