https://bugs.winehq.org/show_bug.cgi?id=52115
Bug ID: 52115
Summary: Horizon Zero Dawn crashes during loading
Product: vkd3d
Version: 1.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: vkd3d
Assignee: wine-bugs(a)winehq.org
Reporter: berillions(a)gmail.com
Distribution: ---
Hello,
I tried this game from GoG with vkd3d-git and it crashes during the 1st loading
(see https://youtu.be/3qpdE9FUBQg) -
The game works with vkd3d-proton without issue (https://youtu.be/MA3ehphVWsg)
I attach the WINEDEBUG=+vkd3d VKD3D_DEBUG="trace" log
--
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=57097
Bug ID: 57097
Summary: Keyboard inputs for special characters on non-english
keyboards are switched in winewayland
Product: Wine
Version: 9.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winewayland
Assignee: wine-bugs(a)winehq.org
Reporter: sutupud(a)yahoo.com
Distribution: ---
I noticed that if I use a german keyboard layout, the key mapping seems to be
off. I'm using kwin_wayland (but also tested on sway, same result).
The regular lower keys are ok, but example, ö produces ü, # produces ä, etc.
Looking at dlls/winewayland.drv/wayland_keyboard.c, I saw that there are
different lookup tables for different languages (scan2vk_qwerty,
scan2vk_azerty. scan2vk_qwertz, ...), so my first quess was that something
might be switched there.
But that doesn't really seem the case, changing it to always use
`scan2vk_qwertz ` regardless of `lang` makes it work.
I don't really have a very good understanding of how this is supposed to work,
but does the appliaction really need to do such a translation? Isn't that
already handled by the layout being passed in? At least that would explain why
it works when doing no such lookup at all.
--
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=56614
Bug ID: 56614
Summary: Videos are not player in The Signifier (GOG)
Product: Wine
Version: 9.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mfplat
Assignee: wine-bugs(a)winehq.org
Reporter: titan.costa(a)gmail.com
Distribution: ---
Created attachment 76371
--> https://bugs.winehq.org/attachment.cgi?id=76371
console log
Videos are not played. Observable during menu and on the computer at the
beginning. Console output attached.
wine-9.7-100-g7641124d07a
--
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=57316
Bug ID: 57316
Summary: PowerPoint 2000 now crashes when loading most .ppt
files
Product: Wine
Version: 9.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jpleonard12(a)gmail.com
Distribution: ---
Created attachment 77268
--> https://bugs.winehq.org/attachment.cgi?id=77268
Power point file created with PowerPoint 2000 on Wine v9.19
In Wine v9.19, PowerPoint 2000 now crashes when loading most .ppt files. The
console log only reports a couple lines relating to the crash:
0024:fixme:hlink:HlinkQueryCreateFromData 01B5A148
double free or corruption (!prev)
0024:err:seh:NtRaiseException Exception frame is not in stack limits => unable
to dispatch exception.
This error did not exist in Wine v9.18 or earlier. The application starts up
normally, and a new .ppt file can be created, and saved. But it will crash when
trying to open it again. An example file is attached.
Some older PowerPoint 2000 files created on Windows systems seem to open, but
this behavior does not appear to be consistent. Perhaps it is something in the
content of the file that is causing the error.
--
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=47686
Bug ID: 47686
Summary: No Man's Sky - crash when moving fast through
asteroids / space
Product: Wine
Version: 4.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winevulkan
Assignee: wine-bugs(a)winehq.org
Reporter: winebugz(a)kbrm.net
Distribution: ---
Created attachment 65143
--> https://bugs.winehq.org/attachment.cgi?id=65143
First crash backtrace
WINE : wine-4.14 (Staging)
OPSYS: Debian 9.9
GPU : Nvidia GTX 670
VDRV : nvidia-driver 430.40-1 (experimental repo)
DLL-OVERRIDE: vulkan-1 (built-in) /* game won't even start to menu without this
*/
Replicate:
Get in ship
Get above atmosphere
Target "Signal Source / Coordiates"
Engage Pulse Engines
1-3 minutes into flight - NMS crashes with:
Unhandled exception: page fault on write access to [HEX ADDRESS] in 64-bit
code ([HEX ADDRESS]).
Attaching three (3) backtraces and console 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=57431
Bug ID: 57431
Summary: Links 2003 Crashes
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dwg(a)australiamail.com
Distribution: ---
Environment
Linux Mint 21.3 Wine Version: 9.21 Links version: 2003 1.07
Links requires WMP9 to be installed.
I am seeing a crash on approximately 40% of the courses in my test subset,
usually accompanied by some incorrect rendering of what are water textures,
i.e. water with reflections.
The address is consistent I am repeatedly seeing the Address 69defc in the
dumps
The crashes are repeatable but not always in exactly the same place during the
game. Crashes are seen on two different machines across 3 different GPUs
Initial crash screen shows:
Appname: linksmmiii.exe AppVer: 22.10.2.41 Modename: linksmmiii.exe
ModVer: 22.10.2.41 Offset: 0029defc
Exception Information:
Code: 0xc0000005 Flags:0x00000000
Record 0x0000000000000000 Address: 0x000000000069defc
Followed by System info and modules listing.
I can stop the crashes by using some Wrapper programs, specifically dgVooDoo
seems to be the best, but that does seem to lead to other issues like video
performance.
--
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=52240
Bug ID: 52240
Summary: VODKALIBUR Mod Tool Crashes on Starup
Product: Wine
Version: 6.23
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: nekoNexus(a)protonmail.ch
Distribution: ---
Created attachment 71349
--> https://bugs.winehq.org/attachment.cgi?id=71349
Staging6.23_Logs_and_dotnet_prefix_backtrace
(The mod-tool is meant for SoulCalibur VI)
In a clean Wine Staging 6.23 prefix, the program crashes on startup without
displaying anything.
Running the program with dotnet48 gets the program to display a splash-screen
before throwing an exception error and dropping 3 .dll files in the app's
directory.
SHA256:
4ddbc85ed075aaf3943319945d0dc7d43b7be4e244674f4df8f47c6d18b6dbe3
Download:
https://cdn.discordapp.com/attachments/651396632167841812/90621213743162163…
(Releases are typically obtained with in-app updates or via the developer's
Discord server - this is a direct link to the last WPF build that was released
via a direct Discord attachment at the time of writing)
--
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=48006
Bug ID: 48006
Summary: Final Fantasy XIV Launcher stuck on splash screen
Product: Wine
Version: 4.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ieframe
Assignee: wine-bugs(a)winehq.org
Reporter: winehq.eloelo(a)spamgourmet.com
Distribution: ---
Created attachment 65534
--> https://bugs.winehq.org/attachment.cgi?id=65534
wine output
The FFXIV launcher has been updated and is now frozen on the splash screen.
(Just a big "Final Fantasy XIV Online" logo).
For now there is a workaround: Set Browser to 1 in FFXIV_BOOT.CFG.
This browser type isn't supposed to last forever, so this is just a temporary
workaround.
--
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=57020
Bug ID: 57020
Summary: Anritsu Software Toolbox doesn't install properly
Product: Wine
Version: 9.14
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
Download:
https://dl.cdn-anritsu.com/en-us/test-measurement/files/Software/Drivers-So…
To test
- Run the installer in clean WINEPREFIX
- Uncheck "Check for Updates"
- Select all components (default)
- When it asks something about the "NI VISA" runtime, select "Yes"
In the install folder (default .wine/drive_c/Program Files (x86)/Anritsu) there
hsould be folders like "Line Sweep Tools" and other. On Wine, those are
missing.
The problem can be worked around by using "winetricks -q dotnet35" before
attempting the install.
Not sure why it can't use wine-mono.
Another way to possibly test: You can unpack the installer exe with 7-zip, then
the $TEMP folder contains the installers, e.g. LST_V1.71_Installer.exe
If you run those, they will complain about missing .NET 3.5 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.
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.