https://bugs.winehq.org/show_bug.cgi?id=45461
Bug ID: 45461
Summary: OnScreenKeyboard Portable: App displays splash screen
but does not start
Product: Wine
Version: 3.12
Hardware: x86-64
URL: https://portableapps.com/apps/accessibility/on-screen_
keyboard_portable
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tobbi.bugs(a)googlemail.com
Created attachment 61801
--> https://bugs.winehq.org/attachment.cgi?id=61801
log
After installing (extracting) OnScreenKeyboard Portable and tryin to run it, it
does show the splash screen but does not start the actual program.
$ openssl sha256 On-ScreenKeyboardPortable_2.0.paf.exe
SHA256(On-ScreenKeyboardPortable_2.0.paf.exe)=
12c4943e1d7a65a12f7c58ac5aac3430b98c5158f18a94c51c26036770af19df
--
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=55149
Bug ID: 55149
Summary: Nancy Drew: Danger by Design exits on game start
Product: Wine
Version: 8.0.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tiger12506(a)gmail.com
Distribution: ---
Created attachment 74715
--> https://bugs.winehq.org/attachment.cgi?id=74715
warn+all,+seh,+ddraw
Nancy Drew: Danger By Design is 2 disc cd game. I have ISOs created from
original discs that I am installing from. Setup.exe works fine -- I choose to
change the install location to C:\ND\DangerbyDesign\ because previous attempts
to run game from the default location result in it looking for a CIFTree file
in the C:\ND\DangerbyDesign directory. That's not the issue.
When installed correctly, the game appears to start, the screen goes black,
resolution changes to the game's chosen 640x480, and then the game quits
(leaving my linux desktop resolution in 640x480 mode). This is the issue.
I assume this is a crash, but I either haven't found, or don't understand the
outputs of the WINEDEBUG logs well enough to diagnose the issue. Any way that I
can help you help me would be appreciated.
--
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=46820
Bug ID: 46820
Summary: 20XX (Game) needs native d3dcompiler_43.dll
Product: Wine
Version: 4.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: patoplc(a)live.com
Distribution: ---
The game 20XX won't start unless the native d3dcompiler_43.dll is provided.
--
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=56365
Bug ID: 56365
Summary: ntdll-Syscall_Emulation patchset causing xdelta3
process to crash/fail
Product: Wine-staging
Version: 9.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: madbyte(a)tuta.io
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 76104
--> https://bugs.winehq.org/attachment.cgi?id=76104
log winedebug_seh wine-staging-9.2
Me and a bunch of other users encounter an issue while using a delta patcher
used to downpatch a specific game to an earlier game version.
The delta patcher utilizes xdelta3.
I found that the xdelta3 process seemingly fails at a random file while
patching the game data.
I started building wine-staging from source myself and after some testing and
excluding seemingly relevant patchsets I found that excluding the patch
'ntdll-Syscall_Emulation' will result in the patcher finishing it's job without
issues.
The issue using vanilla wine-staging builds seemed to not be consistent between
distros as well:
Tests always failed on e.g Pop!_Os, CachyOS, EndeavourOS, Garuda, but on e.g
Fedora 39, Mint 21.3, Manjaro, Ubuntu 23.10 the patching worked every time,
even with the ntdll-Syscall_Emulation patchset enabled. I guessed it might be
because of some kernel option/feature enabled/disabled by default on some
distros but didn't want to built kernels from source myself to test this.
In case it helps, here is the patcher src snippet from where the xdelta3
process is invoked:
https://dev.sp-tarkov.com/waffle.lord/Patcher/src/branch/main/Patcher/Patch…
(the error log of the patcher itself shows the message seen on line 113,
"something went wrong during the xdelta3 process")
I've attached a log showing a failed attempt with wine-staging-9.2 including
said patchset.
imho the relevant part starts at line 14726 in the file:
0748:trace:seh:sigsys_handler SIGSYS, rax 0xffff, rip 0x600000000005.
0748:trace:seh:install_bpf Seccomp filters already installed.
0748:fixme:ver:GetCurrentPackageId (000000000063FEB0 0000000000000000): stub
02c4:trace:seh:dispatch_exception code=e0434352 flags=1 addr=00006FFFFFC135A7
ip=6fffffc135a7
--
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=42107
Bug ID: 42107
Summary: app kpg91d crashes when setting up serial port
selection
Product: Wine
Version: 1.6.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kl7ut(a)ymail.com
Distribution: ---
Created attachment 56627
--> https://bugs.winehq.org/attachment.cgi?id=56627
backtrace from Wine kpg91d crash
Kenwood Radio programming software kpg91d crashes when accessing settings,
communications port dialogue.
--
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=55955
Bug ID: 55955
Summary: some part of the software is black, if I click a line
it appears, but only a line, never more than a line
Product: Wine
Version: 8.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: gerard.labadie(a)sysgroup.fr
Distribution: ---
Created attachment 75543
--> https://bugs.winehq.org/attachment.cgi?id=75543
Display of Captvty 3 on Windows
The resolution of the bug
https://bugs.winehq.org/show_bug.cgi?id=55742
allows to launch successfully Captvty V3, but part of the window is black and
impossible to read
I have attached the file Captvty-3-display-ok, when running on Windows which
shows a normal display
and the file Captvty-linux which shows that the resume of the replay is Ok, but
not the lines with the names of the replays.
reproducer
have wine 8.20 or after, the latest winetricks
create a directory .captvty_V3
download the zip from v3.captvty.fr
unzip it to .captvty_V3
export WINEARCH=win64
export WINPREFIX=~/.captvty_V3
wineboot -u
winetricks -q dotnet48 corefonts gdiplus fontsmooth=rgb vlc win7
mkdir temp
cd temp
cabextract ~/.cache/winetricks/win7sp1/windows6.1-KB976932-X64.exe
cp -rf
./x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2/comctl32.dll
~/.wine_captvty_V3/drive_c/windows/syswow64/comctl32.dll
cd ~
rm -rf temp
launch it with
wine .captvty_V3/Captvty.exe
I noticed from the command line the messages
fixme:uxtheme:BeginBufferedPaint painting parameters are ignored
and
0024:fixme:uxtheme:AllowDarkModeForWindow 00030048 1: stub
using winecfg I tried various options for comctl32, any option with "native"
works (with the black display), any other option crashes the sofware.
in https://forum.winehq.org/viewtopic.php?t=38088
somebody commented
I don't know how to fix the black display, but I strongly believe this might be
due to using the native comctl32 (which is not really a good thing).
I think it might be a good idea to open a bugreport about the application not
being able to load builtin comctl32, maybe one of the developers has an idea
how to fix this, and maybe this "black display" issue might be solved then as
well
--
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.