https://bugs.winehq.org/show_bug.cgi?id=55960
Bug ID: 55960
Summary: user32: 512 is not enough for LB_ADDSTRING
Product: Wine
Version: 8.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: galtgendo(a)o2.pl
Distribution: ---
So, as noted in bug 54034, while dealing with some out-of-memory crashes, I ran
into an odd one, one that could be triggered even shortly after reload and
acting more like a buffer overflow bug.
Namely, if a certain string that was about to be displayed on the screen was
above 530 chars (but it had newline embedded), the game crashed, but didn't if
the string was manually truncated.
It left me grasping at straws, as my (quite lacking) gdb skills didn't lets me
see where the crash occurred.
So, I was left waiting for some burst of inspiration.
It came today.
For some reason, this felt like I had been hitting some internal limit. I
suspected wine code.
After trying a few debug channel combinations, I eventually tested 'msg'.
The strings were printed using ID3DXFontImpl_DrawTextA.
In the log, I've noted LB_ADDSTRING and - after looking at that code - took a
stab in the dark.
I've set the buffer size for that message in both WINPROC_CallProcAtoW and
WINPROC_CallProcWtoA to 1536 (yes, likely excessively large). Making this
change has fixed the crash.
I'm marking it wine 8.21, but I expect this has been around as long as wine has
been using too small buffer.
--
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=55511
Bug ID: 55511
Summary: Wine repeatedly prints err:system:update_display_cache
Failed to read display config.
Product: Wine
Version: 8.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: win32u
Assignee: wine-bugs(a)winehq.org
Reporter: m101010a(a)gmail.com
Distribution: ---
In sysparams.c the read_display_adapter_settings function uses the global
variable config_key, but does not actually initialize it. This causes the
function to fail, and that failure eventually trickles down to
update_display_cache. I haven't seen any functionality break because of it, but
the messages are annoying and could be trivially fixed by initializing
config_key before it is 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=55014
Bug ID: 55014
Summary: kernel32:comm crashes in WoW64 mode on Linux
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
kernel32:comm crashes in WoW64 mode on Linux:
comm.c:708: Found Com port COM1. Connected devices may disturb results
Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit
code (0x007f47b448083c).
[...]
=>0 0x007f47b448083c wait_for_event+0x1c(arg=<internal error>)
[/home/winetest/tools/testbot/var/wine-wow64/../wine/dlls/ntdll/unix/serial.c:945]
in ntdll.so (0000000000000000)
0x007f47b448083c wait_for_event+0x1c
[/home/winetest/tools/testbot/var/wine-wow64/../wine/dlls/ntdll/unix/serial.c:945]
in ntdll.so: mov (%rdi), %rdi
945 if (!server_get_unix_fd( commio->hDevice, FILE_READ_DATA |
FILE_WRITE_DATA, &fd, &needs_close, NULL, NULL ))
See https://test.winehq.org/data/patterns.html#kernel32:comm
The failure seems to only happen on the TestBot VMs, maybe because of QEmu,
particularly because it does not set the baud rate correctly.
A bisect shows that this failure started with the commit below:
commit b337c5b1a1757b2abbc90a7c6955d64242861ab9
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Fri Jun 2 09:35:29 2023 +0200
ntdll: Use the default ABI for all functions on the Unix 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=54616
Bug ID: 54616
Summary: Wine 8.0+, Memory Access Violation in Libaes.dll,
Texecom Wintex
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: zestier-bib.0a(a)icloud.com
Distribution: ---
Created attachment 74142
--> https://bugs.winehq.org/attachment.cgi?id=74142
Error from console when Program is run.
When attempting to run running Texecom Wintex in Wine 8.0 or above, there is a
Memory Access Violation/Buffer Overrun error c0000005 in libaes.dll.
Downgrading to Wine 7.0.1 with no other changes allows the program to run
normally.
The environment has C++ Redistributable 2010 installed as required.
There is no GUI errors shown when the issue is present. The attached .txt file
contains the error that is printed when the program is run via the console.
libaes.dll seems to be specific to this program.
The program can be downloaded from here:
https://texecom-live.s3.eu-west-2.amazonaws.com/wp-content/uploads/2022/08/…
(no account required)
or https://www.texe.com/help-and-support/product-support/ (free account
required)
No accounts or hardware is needed to run the software.
See also: My forum post:
https://forum.winehq.org/viewtopic.php?p=139794#p139794
If I can provide any more information, please let me know.
--
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=40236
Bug ID: 40236
Summary: winetricks ie6: buttons are missing
Product: Wine
Version: 1.9.4
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Regression SHA1: 6e638d824b80e8a02cb830cd6bc25a7ef8507849
Distribution: Fedora
Created attachment 53780
--> https://bugs.winehq.org/attachment.cgi?id=53780
screenshot
Regression, introduced by:
commit 6e638d824b80e8a02cb830cd6bc25a7ef8507849
Author: Dmitry Timoshkov <dmitry(a)baikal.ru>
Date: Mon Mar 23 10:20:59 2015 +0800
shell32: Update version information to match XP values.
To reproduce:
$ rm -rf ~/.wine
$ winetricks -q ie6
$ cd ~/.wine/drive_c/Program\ Files/Internet\ Explorer/
$ wine "C:\\program files\\internet explorer\\iexplore.exe"
see screenshot.
--
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=53114
Bug ID: 53114
Summary: Crash of applications and games when out of focus
Product: Wine-staging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ryu.ketsueki(a)outlook.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
I don't know why this happens but every wine application I could test, they
need to stay on focus in the current virtual desktop (from the Desktop
Environment, not Wine's virtual desktop) or else they will simply close on
their own. I can't track to a specific cause because even with a completely new
prefix with no "helpers", Lutris and even Valve's own Proton, this happens. So
far I got the exact same result with The Sims 4, StarCraft 2 and Sonic After
the Sequel. All those games will close if I change to another virtual desktop,
let's say, desktop 2, if the apps themselves are on desktop 1. It also happened
with the releases but it persists with Staging as well. I don't know how to
backtrace this, as launching them through CLI didn't return anything useful and
I'm not sure if wine itself is what is crashing or the applications. I didn't
get the classic crash window either. They simply close.
--
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=49177
Bug ID: 49177
Summary: Naruto Online
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kacper.cholody(a)onet.pl
Distribution: ---
Created attachment 67194
--> https://bugs.winehq.org/attachment.cgi?id=67194
dont know
When i run an application its showing a bug. I cant run 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=45268
Bug ID: 45268
Summary: Logicly 1.9 (Adobe AIR app) windows do not resize
correctly when screen resolution is set to non-default
value
Product: Wine
Version: 3.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de
Distribution: ---
Created attachment 61511
--> https://bugs.winehq.org/attachment.cgi?id=61511
Start log for logicly 1.8
Logicly 1.9 (Adobe AIR application) installs and works perfect when the screen
resolution is left at the default (96 dpi). When changing the screen resolution
to a higher value (which is necessary for newer displays) Logicly shows its
windows minimized. This prevents installing because (i.e.) the License accept
dialog can not be confirmed.
To reproduce
- Download logicly 1.9 (see download link)
- change the screen resolution with winecfg to (i.e.) 168 dpi
- Install Logicly by calling the installer, start it after installation
The shown windows are minimized and not resizable.
When installing with the default screen resolution and running Logicly later,
its windows are minimized and can be resized. so the app is usable in
principle.
It may be of interest, that the previous release (Logicly 1.8) does not have
this problem (download from http://logic.ly/updates/Logicly-1.8.0.exe).
The log files from the start of both releases are 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.