https://bugs.winehq.org/show_bug.cgi?id=54906
Bug ID: 54906
Summary: Menu items with icons are drawn with black squares if
Wine is running in Vista+ mode
Product: Wine
Version: 8.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: george.hazan(a)gmail.com
Distribution: ---
The following construction fails in the all 8.x versions of Wine (currently I
upgraded to version 8.7 devel) and works Ok in Wine 7.1:
MENUITEMINFO mii = {};
mii.cbSize = sizeof(mii);
mii.fMask = MIIM_STRING | MIIM_STATE;
if (pimi->iconId != -1) {
mii.fMask |= MIIM_BITMAP;
if (IsWinVerVistaPlus() && IsThemeActive()) {
if (pimi->hBmp == nullptr)
pimi->hBmp = ConvertIconToBitmap(pimi->parent->m_hMenuIcons,
pimi->iconId);
mii.hbmpItem = pimi->hBmp;
}
else mii.hbmpItem = HBMMENU_CALLBACK;
}
InsertMenuItemW(hMenu, uItem, TRUE, &mii);
I.e. if I run command 'winecfg -v win2003', then everything is Ok with icons,
otherwise I see black squares instead of icons. This code works Ok under all
versions of Windows, from XP to Windows 11, the problem is specific to Wine 8.x
under Linux (I use Kubuntu 23.04).
To see the problem you can download my open source messenger Miranda NG from
https://miranda-ng.org/downloads, just download a ZIP, run it and open main or
tray icon menu. The full source code is avalable here:
https://github.com/miranda-ng/miranda-ng, you need module menu_utils.cpp inside
mir_app, InsertMenuItemWithSeparators or BuildRecursiveMenu functions.
WMBR, George Hazan.
--
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=32515
Bug #: 32515
Summary: Warhammer 40,000: Space Marine (Steam) fails to start
Product: Wine
Version: 1.5.20
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gyebro69(a)gmail.com
Classification: Unclassified
Created attachment 42894
--> http://bugs.winehq.org/attachment.cgi?id=42894
plain terminal output
On startup the game shows a black screen for a few seconds and audio from the
intro video can be heard for 0.5-1 second, then the game's own bug reporting
tool (Bugsplat) is popping up: "A problem has been encountered and the program
needs to close". No backtrace from Wine is generated.
A demo version is available on Steam, but I couldn't test it as I have the full
version.
http://store.steampowered.com/app/55150/
Steam installs MSVC++ 2005 runtime libraries and various DirectX components the
first time you start the game. Disabling gameoverlayrenderer in winecfg doesn't
help. I tested this bug with Wine 1.2.3, 1.4.1, 1.5.20.
Fedora 17 x86
Nvidia 250 / driver 304.64
X.Org X Server 1.12.4
Alsa 1.0.26
--
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=48525
Bug ID: 48525
Summary: 0009:err:gdi:alloc_gdi_handle out of GDI object
handles, expect a crash
Product: Wine
Version: 4.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdiplus
Assignee: wine-bugs(a)winehq.org
Reporter: cagnulein(a)gmail.com
Distribution: ---
On a commercial application written on .NET 2.0 i have a crash that occurs
randomly every few days.
I put the +seh debug here. I have 2 questions:
1) my +seh log file is full of
0048:trace:seh:__regs_RtlUnwind handler at 0x7bc82da0 returned 1
0048:trace:seh:raise_exception code=40010006 flags=0 addr=0x7b43e223
ip=7b43e223 tid=0048
0048:trace:seh:raise_exception info[0]=00000041
0048:trace:seh:raise_exception info[1]=0d061dd8
0048:trace:seh:raise_exception eax=7b42a5c1 ebx=00000004 ecx=0733ef20
edx=0733efd0 esi=00000041 edi=40010006
0048:trace:seh:raise_exception ebp=0733ef78 esp=0733eef4 cs=300023 ds=002b
es=f7d7002b fs=006b gs=73c0063 flags=00000212
0048:trace:seh:call_stack_handlers calling handler at 0x7b48ad80 code=40010006
flags=0
0048:trace:seh:__regs_RtlUnwind code=40010006 flags=2
0048:trace:seh:__regs_RtlUnwind eax=00000000 ebx=7b48ace0 ecx=0733ef0c
edx=0733efd8 esi=0733efd8 edi=7b48ace0
0048:trace:seh:__regs_RtlUnwind ebp=0733eac8 esp=0733eaa8 eip=7b48ad3d cs=0023
ds=002b fs=006b gs=0063 flags=00000202
0048:trace:seh:__regs_RtlUnwind calling handler at 0x7bc82da0 code=40010006
flags=2
it's a problem of my application? Of wine gdiplus implementation?
2) In the meanwhile i'm trying with "winetricks gdiplus": what you think about
this +seh trace?
0048:trace:seh:call_stack_handlers calling handler at 0x7b48ad80 code=40010006
flags=0
0048:trace:seh:__regs_RtlUnwind code=40010006 flags=2
0048:trace:seh:__regs_RtlUnwind eax=00000000 ebx=7b48ace0 ecx=0733ef0c
edx=0733efd8 esi=0733efd8 edi=7b48ace0
0048:trace:seh:__regs_RtlUnwind ebp=0733eac8 esp=0733eaa8 eip=7b48ad3d cs=0023
ds=002b fs=006b gs=0063 flags=00000202
0048:trace:seh:__regs_RtlUnwind calling handler at 0x7bc82da0 code=40010006
flags=2
0048:trace:seh:__regs_RtlUnwind handler at 0x7bc82da0 returned 1
0048:trace:seh:raise_exception code=40010006 flags=0 addr=0x7b43e223
ip=7b43e223 tid=0048
0048:trace:seh:raise_exception info[0]=00000041
0048:trace:seh:raise_exception info[1]=0d061dd8
0048:trace:seh:raise_exception eax=7b42a5c1 ebx=00000004 ecx=0733ef20
edx=0733efd0 esi=00000041 edi=40010006
0048:trace:seh:raise_exception ebp=0733ef78 esp=0733eef4 cs=300023 ds=002b
es=f7d7002b fs=006b gs=73c0063 flags=00000212
0048:trace:seh:call_stack_handlers calling handler at 0x7b48ad80 code=40010006
flags=0
0048:trace:seh:__regs_RtlUnwind code=40010006 flags=2
0048:trace:seh:__regs_RtlUnwind eax=00000000 ebx=7b48ace0 ecx=0733ef0c
edx=0733efd8 esi=0733efd8 edi=7b48ace0
0048:trace:seh:__regs_RtlUnwind ebp=0733eac8 esp=0733eaa8 eip=7b48ad3d cs=0023
ds=002b fs=006b gs=0063 flags=00000202
0048:trace:seh:__regs_RtlUnwind calling handler at 0x7bc82da0 code=40010006
flags=2
0048:trace:seh:__regs_RtlUnwind handler at 0x7bc82da0 returned 1
0048:trace:seh:raise_exception code=40010006 flags=0 addr=0x7b43e223
ip=7b43e223 tid=0048
0048:trace:seh:raise_exception info[0]=0000003e
0048:trace:seh:raise_exception info[1]=0d0719e8
0048:trace:seh:raise_exception eax=7b42a5c1 ebx=00000004 ecx=0733ef50
edx=0733f000 esi=0000003e edi=40010006
0048:trace:seh:raise_exception ebp=0733efa8 esp=0733ef24 cs=0023 ds=34002b
es=733002b fs=7dd9006b gs=7330063 flags=00000216
0048:trace:seh:call_stack_handlers calling handler at 0x7b48ad80 code=40010006
flags=0
0048:trace:seh:__regs_RtlUnwind code=40010006 flags=2
0048:trace:seh:__regs_RtlUnwind eax=00000000 ebx=7b48ace0 ecx=0733ef3c
edx=0733f008 esi=0733f008 edi=7b48ace0
0048:trace:seh:__regs_RtlUnwind ebp=0733eaf8 esp=0733ead8 eip=7b48ad3d cs=0023
ds=002b fs=006b gs=0063 flags=00000202
0048:trace:seh:__regs_RtlUnwind calling handler at 0x7bc82da0 code=40010006
flags=2
0048:trace:seh:__regs_RtlUnwind handler at 0x7bc82da0 returned 1
0009:trace:seh:raise_exception code=40010006 flags=0 addr=0x7b43e223
ip=7b43e223 tid=0009
0009:trace:seh:raise_exception info[0]=00000046
0009:trace:seh:raise_exception info[1]=0d068440
0009:trace:seh:raise_exception eax=7b42a5c1 ebx=00000004 ecx=0032e720
edx=0032e7d0 esi=00000046 edi=40010006
0009:trace:seh:raise_exception ebp=0032e778 esp=0032e6f4 cs=0023 ds=34002b
es=002b fs=006b gs=0063 flags=00000212
0009:trace:seh:call_stack_handlers calling handler at 0x7b48ad80 code=40010006
flags=0
0009:trace:seh:__regs_RtlUnwind code=40010006 flags=2
0009:trace:seh:__regs_RtlUnwind eax=00000000 ebx=7b48ace0 ecx=0032e70c
edx=0032e7d8 esi=0032e7d8 edi=7b48ace0
0009:trace:seh:__regs_RtlUnwind ebp=0032e2c8 esp=0032e2a8 eip=7b48ad3d cs=0023
ds=002b fs=006b gs=0063 flags=00000202
0009:trace:seh:__regs_RtlUnwind calling handler at 0x7bc82da0 code=40010006
flags=2
0009:trace:seh:__regs_RtlUnwind handler at 0x7bc82da0 returned 1
0009:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash
Fatal,Program[1:MainThread]: System.Runtime.InteropServices.SEHException:
External component has thrown an exception.
at System.Drawing.SafeNativeMethods.SelectObject(HandleRef hdc, HandleRef
obj)
at System.Drawing.BufferedGraphicsContext.DisposeDC()
at System.Drawing.BufferedGraphicsContext.ReleaseBuffer(BufferedGraphics
buffer)
at System.Drawing.BufferedGraphics.Dispose(Boolean disposing)
at System.Drawing.BufferedGraphics.Dispose()
at System.Windows.Forms.Control.WmPaint(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Label.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr
wparam, IntPtr lparam)
I can't share the application because it's not free, but if you need more
information i will try to get them.
Thanks in advance
--
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=55662
Bug ID: 55662
Summary: Different behaviour of "set" command
Product: Wine
Version: 8.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: ch.panel(a)free.fr
Distribution: ---
behavior of these commands are different in wine and windows in a batch file
set test=A
set /P test="type A or B (%test%) :"
echo "%test%"
pause
if the user type nothing the result is :
"A" on windows
"" on wine
--
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=52131
Bug ID: 52131
Summary: wine-mono + RMS Express: HF Channel Selection Browser
crashes
Product: Wine
Version: 6.22
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mscoree
Assignee: wine-bugs(a)winehq.org
Reporter: eric.wheez(a)gmail.com
Distribution: ---
wine-mono + RMS Express: HF Channel Selection Browser crashes when updating
from the internet (crashes soon after the "Update from Internet" button is
pushed - after downloading data, during "STANDBY - Updating RMS channels
propagation indices for" [callsignhere]). Crash happens with wine-mono, but
does not happen with dotnet46.
A very similar-looking crash also happens when pushing the "SFI" (solar flux
index) button in the HF Channel Selection Browser (which also crashes during
"STANDBY - Updating RMS channels propagation indices for" [callsignhere]). This
crash could be the same crash as the "Update from Internet" crash.
Notes:
Madewokherd (Esme) has been incredibly gracious (already fixing three other
errors in wine-mono + RMS Express) that I didn't want to be annoying by posting
another RMS Express error on their github page, so I thought maybe this would
be the best place to post. The other bugs that Esme fixed (thank you!!) and
their terminal logs (for comparison) can be found here:
https://github.com/madewokherd/wine-mono/issues/116 &
https://github.com/madewokherd/wine-mono/issues/122
System specs:
- Program: RMS Express.exe (Winlink Express) v1.5.42.0 (latest as of
11/28/2021 - downloaded from https://downloads.winlink.org/User%20Programs/ ).
Note: This program requires a free user account to use. User accounts can be
created for free using the in-program prompts on first-run.
- Winetricks packages: winetricks -q dotnet46 win7 sound=alsa
- Wine version: wine-devel 6.22
- wine-mono version: Nov 26, 2021 nightly (PR #126 / commit 6831b18 - msi
downloaded from
https://github.com/madewokherd/wine-mono/actions/runs/1496716432 )
- OS: x86 Debian 10 Linux (on VMWare Workstation 16 on a Windows laptop)
Logs:
I've logged quite a bit of behavior and attached those below.
- For larger logs, I've included truncated versions and 'interesting' parts.
- The crash 'backtrace' from the wine/wine-mono "Program Error" window is
included.
- Logs also include both the program running idly in wine-mono (without
pushing the "Update from Internet" button) and the program crash in wine-mono.
- Different logs were made using by running wine-mono's built-in functions:
WINE_MONO_TRACE=x, WINE_MONO_TRACE=program, and WINE_MONO_TRACE=wrapper. (No
suspicious WINE_MONO_TRACE=x exceptions pop up during the crash though).
- I've also logged normal behavior on Windows using "Improved dotNET Tracer"
(by Kao / Kurapica), which shows which program VB.NET methods are supposed to
be being used when the crash happens (it also doesn't expose any .NET
Windows/Winlink code internals, just program method names near the crash).
- Some pictures are also included for reference.
Let me know what you think or if I can submit any other logs. And thank you
for reading/considering it!
--
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=55818
Bug ID: 55818
Summary: 32-bit game Dark Age of Camelot slow memory leak leads
to crash since WINE 7.4
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: tmwine(a)pertho.net
Distribution: ---
I've bisected a bug relating to a possible memory leak in wined3d. I've been
playing an old game (Dark Age of Camelot) for years now on free servers, but I
noticed there is a slow memory leak as it runs. I ran 'top' and watched the RES
memory creep up to 1.0 GB and then hit about 1.2-1.3 GB before the game
crashes.
On WINE 8 this issue seems to persist as well. So I went back and bisected the
bug and it occurs between WINE 7.3 and 7.4. In 7.3, I don't get the memory leak
and the game plays for hours, but in 7.4 I get the memory leak.
I've narrowed it down to this commit:
https://gitlab.winehq.org/wine/wine/-/commit/ee12556960e30fc22f276d2de2833e…
It might have to do with the code change in the function
wined3d_context_gl_destroy_bo that introduced this.
Happy to try any patches to test with against latest WINE 8.x tree.
Thanks,
Tom
--
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=54735
Bug ID: 54735
Summary: AOL (America Online) Desktop Beta fails when
installing .net 2.8
Product: Wine
Version: 8.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maiktapwagner(a)aol.com
Distribution: ---
Created attachment 74239
--> https://bugs.winehq.org/attachment.cgi?id=74239
Backtrace (wine 8.4 on Slackware64/Multilib)
https://beta.aol.com/projects/desktop/windows
sha256sum Install_AOL_Desktop.exe
13cd19996e183e927ce0710f367d586474dcca308f593e2551b67334a0315b4d
Install_AOL_Desktop.exe
Installer starts up okay but eventually crashes when installing .net 4.8 which
is required for AOL Desktop Gold Beta.
--
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=44962
Bug ID: 44962
Summary: Smart Guard no run
Product: Wine-staging
Version: 3.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: terapy-session(a)bk.ru
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 61074
--> https://bugs.winehq.org/attachment.cgi?id=61074
averia petch, l2.exe log
Smart Guard does not work and cannot work around it.
Checked on different servers, but I give a log from the server Averia.ws
--
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=54788
Bug ID: 54788
Summary: AOL 5.0 Installation fails
Product: Wine
Version: 8.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maiktapwagner(a)aol.com
Distribution: ---
Created attachment 74281
--> https://bugs.winehq.org/attachment.cgi?id=74281
Backtrace (wine 8.5 on Slackware64/Multilib)
Download is at:
http://www.oldversion.com/windows/download/america-online-5-0
bash-5.1$ sha1sum aol50.exe
cacd3d5b93e7f2d6004812707148364a47db6db6 aol50.exe
Backtrace is attached. Console output to follow shortly.
--
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=55798
Bug ID: 55798
Summary: Unreal Engine 5.2: Wine minidumps take hours to load
into a debugger
Product: Wine
Version: 8.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: dbghelp
Assignee: wine-bugs(a)winehq.org
Reporter: aiden.deloryn(a)tensorworks.com.au
Distribution: ---
=== Overview ===
When attempting to load a Wine generated minidump from an Unreal Engine
application using a debugger (such as Visual Studio or VS Code), it takes a
number of hours for the file to load. If left uninterrupted during this time,
the process does eventually complete and all of the expected debug data becomes
visible within the IDE. This behaviour has only been observed for minidumps of
type MiniDumpNormal. When working with a Wine generated minidump of type
MiniDumpWithFullMemory, the debugger is able to load the file within a few
seconds.
=== Steps to Reproduce ===
1. Build this minimal sample application
https://github.com/TensorWorks/BuggyFirstPersonDemo.git on a Windows machine
with Unreal Engine 5.2.1 using the following command:
C:\<UE_INSTALL_DIR>\Engine\Build\BatchFiles\RunUAT.bat BuildCookRun -utf8output
-clientconfig=DebugGame
-project="C:\<PATH_TO_PROJECT_DIR>\BuggyFirstPersonDemo.uproject" -noP4 -cook
-build -stage -prereqs -pak -archive
-archivedirectory="C:\<PATH_TO_PROJECT_DIR>\GameBuilds" -platform=Win64
2. Copy the build directory (C:\<PATH_TO_PROJECT_DIR>\GameBuilds) to a Linux
machine and run the application using Wine (DXVK required):
wine
./GameBuilds/Windows/BuggyFirstPersonDemo/Binaries/Win64/BuggyFirstPersonDemo-Win64-DebugGame.exe
-windowed -ResX=800 -ResY=600
3. Trigger a crash by picking up the gun and shooting the large white cube.
Note: hold down the right mouse button to aim/look, and press the left mouse
button to shoot.
4. Copy the crash dump from
./GameBuilds/Windows/BuggyFirstPersonDemo/Saved/Crashes/<CRASH_ID>/UEMinidump.dmp
to a Windows machine and attempt to load it using Visual Studio or VS Code (for
VS Code you will need the C/C++ extension from Microsoft installed).
=== Actual Results ===
The minidump takes hours to load into Visual Studio and VS Code.
MemoryListStream contains over 950,000 memory ranges (see additional
information below).
=== Expected Results ===
The minidump takes less than a minute to load into Visual Studio and VS Code,
which is true for full memory minidumps generated under Wine and any minidump
generated under Windows.
=== Build Date & Hardware ===
wine-8.14 on Ubuntu 22.04.3 LTS x86-64
=== Additional Builds and Platforms ===
Also reproducible on wine-8.17 and wine-8.0.2
=== Additional Information ===
When analysing and comparing minidumps generated under Wine versus those
generated under Windows using the Microsoft Crash Dump File Checker tool
“DumpChk”
(https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/dumpchk),
a significant discrepancy can be observed in the normal minidump generated
under Wine. In particular, the number of memory ranges in MemoryListStream is
substantially higher, as can be seen in the excerpts below. Note that full
memory minidumps have also been included from both Windows and Wine for
additional context and comparison.
Windows - MiniDumpNormal:
Stream 3: type MemoryListStream (5), size 00000804, RVA 0006FF09
128 memory ranges
[OMITTED]
Total memory: 463cc
Wine - MiniDumpNormal:
Stream 4: type MemoryListStream (5), size 00EA0FF4, RVA 0002986B
958719 memory ranges
[OMITTED]
Total memory: 15bd62e
Windows - MiniDumpWithFullMemory:
Stream 5: type Memory64ListStream (9), size 0000EAC0, RVA 000C8D45
3755 memory ranges
[OMITTED]
Total memory: a74c1000
Wine - MiniDumpWithFullMemory:
Stream 7: type Memory64ListStream (9), size 0000E260, RVA 0006ADFB
3621 memory ranges
[OMITTED]
Total memory: 7ab14000
Note: You can generate a full memory minidump using the provided sample
application by specifying the -fullcrashdumpalways flag. For example:
wine
./GameBuilds/Windows/BuggyFirstPersonDemo/Binaries/Win64/BuggyFirstPersonDemo-Win64-DebugGame.exe
-windowed -ResX=800 -ResY=600 -fullcrashdumpalways
--
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.