https://bugs.winehq.org/show_bug.cgi?id=38201
Bug ID: 38201
Summary: Newly displayed dialogs have inactive-looking
decorations although are actually active
Product: Wine
Version: 1.7.38
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: b7.10110111(a)gmail.com
Distribution: ---
Created attachment 50980
--> https://bugs.winehq.org/attachment.cgi?id=50980
Screenshot of Windows (left) and Wine (right) MessageBox
If I uncheck "Allow the window manager to decorate the windows" in Graphics tab
of winecfg, or just set wine to show all its windows in a virtual desktop or
launch the apps like `wine explorer /desktop=a,1152x864 appname.exe`, their
windows often look as inactive (gray title bar) while they are actually active.
This is visible in particular in winecfg dialog, Mono/Gecko downloaders dialogs
on wine prefix update, as well as with a simple program like this:
#include <windows.h>
int main() { MessageBox(0,"Hello","Message",MB_OK); }
I've tested the code above in Wine and Windows XP, and in Windows it has
correct active title (blue-lightBlue gradient), while in wine it has inactive
title (gray-lightGray gradient).
If I make any other window active, then switch back to this one, it'll then
show the correct title colors.
The attachment compares Windows' MessageBox with that of Wine, both untouched
at the moment of screenshooting.
--
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=41215
Bug ID: 41215
Summary: Necromancer's Dos Navigator (NDN) fails to run
Product: Wine
Version: 1.9.17
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ddascalescu+wine(a)gmail.com
Distribution: ---
I'm trying to run the W32 version of NDN from http://ndn.muxe.com/download/
because the GNU version fails pretty miserably on current *nixes. The W32
version works great on Windows 7 in XP compatibility mode, but when I run it in
Wine, I get the exact error I get in Windows 7 without XP compatibility turned
on:
$ wine ndn.exe
fixme:process:SetProcessShutdownParameters (00000280, 00000001): partial stub.
Not enough memory available for Necromancer's Dos Navigator .
Please check if at least 400kb memory is available...
$ wineconsole ndn.exe
fixme:process:SetProcessShutdownParameters (00000280, 00000001): partial stub.
dosbbox doesn't work because the program must be run in Win32.
--
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=3599
bignintyfan(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bignintyfan(a)gmail.com
--- Comment #28 from bignintyfan(a)gmail.com ---
I just tried this myself with vanilla Wine 4.18 staging and in a new Wine
prefix. The page printed successfully to a network printer. I think this issue
can be closed.
--
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=47380
Bug ID: 47380
Summary: GT Legends: Slow graphics and 100% CPU usage
Product: Wine
Version: 4.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: timschumi(a)gmx.de
Distribution: ---
GT Legends does have a significant graphics slowdown when running in wine,
while a single CPU thread is locked at 100%.
When looking at the process in a profiler, most of the time is spent in the
function wined3d_cs_mt_finish() (and I guess the wined3d_pause() function
within, which doesn't show up in a profiler due to being inline).
This seems to be a regression as well, since there are videos (for Wine 1.9.10,
[1]) and AppDB entries (latest entry for Wine 1.7.0, [2]) that claim that the
game was running fine on earlier releases of Wine, but I wasn't able to find
the exact commit that introduced the regression so far.
Patches from wine-staging don't help either. Please let me know what type of
logs would be the most suitable ones to debug this, since a normal +d3d log
seems impractical with over 13MB in size.
[1] https://www.youtube.com/watch?v=L80NsdNcVgI
[2] https://appdb.winehq.org/objectManager.php?sClass=version&iId=28706
--
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=47733
Bug ID: 47733
Summary: Project Reality BF2 PRLauncher.exe doesn't start with
Wine-Mono.
Product: Wine
Version: 4.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: apq49584(a)tuofs.com
Distribution: ---
Created attachment 65209
--> https://bugs.winehq.org/attachment.cgi?id=65209
What you see if it works (obtained wth native dotNetFx40_Client)
Debian 10 buster with winehq packaged wine-devel and libfaudio from OBS.
wine-mono-4.9.2.msi downloaded and installed by wine on first run.
Download link:
https://www.realitymod.com/downloads
$ wine start PRLauncher.exe
The entry point method could not be loaded due to Could not load file or
assembly 'PresentationFramework, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35' or one of its dependencies.
(The PRLauncher.exe does work if wine-mono is removed and
dotNetFx40_Client_x86_x64.exe is installed with wine uninstaller.
This is again just background information and was NOT done for the bug report.)
I am reporting the bugs with PRBF2.exe and PRLauncher.exe seperately, because
they happen in very different parts of wine and can be tested for
independently.
--
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=47814
Bug ID: 47814
Summary: Continuous message closing down Sims 4
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sophiepark139(a)yahoo.com
Distribution: ---
It closes down my sims 4 game without saving and says it is a, “serious”
problem. I have to remember to keep saving...it’s really irritating. Please
tell me how to stop it, I looked but it doesn’t give me an option to not do
that again (closing down my game). I haven’t got an attachment since when my
game closes the message pops up and then goes again, hardly giving me time to
read 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=47769
Bug ID: 47769
Summary: Royal Quest: fails to start with LdrInitializeThunk
"gaxomofy.dll" failed to initialize, aborting
Product: Wine
Version: 4.16
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: spoon0042(a)hotmail.com
Distribution: ---
wine 4.16 clicking "play" in the launcher nothing happens other than this
error:
006c:err:module:LdrInitializeThunk "gaxomofy.dll" failed to initialize,
aborting
006c:err:module:LdrInitializeThunk Initializing dlls for L"C:\\Program
Files\\1C\\Royal Quest\\rqmain.exe" failed, status c0000005
regression test flags this:
58139dcb125390b9a2bcd79869d571337d8ab3d8 is the first bad commit
commit 58139dcb125390b9a2bcd79869d571337d8ab3d8
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Thu Sep 12 20:00:48 2019 +0200
ntdll: Handle invalid %gs fault in signal handler on i386.
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
:040000 040000 548954322ce3d9671b57c059b76b4ce117f5862a
4e9d605e406359211a8e1bdf9af87f4484c9aa62 M dlls
also 'file' says dll is UPX compressed which may be relevant
--
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=35420
Bug ID: 35420
Summary: Stronghold Kingdoms crashes due to ID3DXFont
PreloadCharacters being a stub.
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: leslie_alistair(a)hotmail.com
CC: wine-bugs(a)winehq.org
Classification: Unclassified
Use patch from http://bugs.winehq.org/show_bug.cgi?id=23934 to work around
update issue.
winetricks dotnet2
Install Stronghold Kingdoms
Uncheck "Installed DirectX runtime"
Run Stronghold Kingdoms
Now a exception dialogs appears, which is caused by the following stub
fixme:d3dx:ID3DXFontImpl_PreloadCharacters iface 0x6132088, first 0, last 255
stub
workaround.
winetricks d3dx9_36
--
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=8848
Michael Stefaniuc <mstefani(a)winehq.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |4.0.x
--
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.