https://bugs.winehq.org/show_bug.cgi?id=55414
Bug ID: 55414
Summary: Ultimate Spider-Man: Widescreen Fix shifts HUD too
much to the right
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tinozzo123(a)tutanota.com
Distribution: ---
Created attachment 74975
--> https://bugs.winehq.org/attachment.cgi?id=74975
Logs taken from fresh prefix, with `WINEDEBUG=warn+all`
The game Ultimate Spider-Man works well in Wine (I played it from start to
finish).
I also played with the Widescreen Fix, which works except for one thing.
The mod offers the option (enabled by default) to fix the HUD (without it, the
HUD would be stretched). That is the problematic part under Wine, because with
it the HUD is shifted too much to the right, rendering the mod unusable.
It works no problem with it disabled (which is how I played).
So, to reproduce:
- Install Ultimate Spider-Man
- Install the mod:
https://github.com/ThirteenAG/WidescreenFixesPack/releases/tag/usm
- Set `WINEDLLOVERRIDES` for `dsound`
- Make sure that in the mod settings, `FixHUD` is set to `1` (it's the default)
- Launch the game, you should see the problem right in the main menu.
Source code of the mod:
https://github.com/ThirteenAG/WidescreenFixesPack/tree/master/source/Ultima…
Images of the issue (made an issue on GitHub in case the issue wasn't on from
Wine's side): https://github.com/ThirteenAG/WidescreenFixesPack/issues/1309
--
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=55287
Bug ID: 55287
Summary: msvcrt:file - The 32-bit test_pipes() fails in the new
WoW mode
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: msvcrt
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
msvcrt:file - The 32-bit test_pipes() fails in the new WoW mode:
file.c:2343: Test failed: i 0, expected to write 'Hello world' wrote -1
file.c:2343: Test failed: i 1, expected to write 'Hello world' wrote -1
file.c:2343: Test failed: i 2, expected to write 'Hello world' wrote -1
file.c:2350: Test failed: unable to close 4: 9
01cc:file: 5 tests executed (0 marked as todo, 0 as flaky, 4 failures), 0
skipped.
file.c:2383: Test failed: i 0, got 0
file.c:2386: Test failed: expected to read 'Hello world', got ''
file.c:2383: Test failed: i 1, got 0
file.c:2386: Test failed: expected to read 'Hello world', got ''
file.c:2383: Test failed: i 2, got 0
file.c:2386: Test failed: expected to read 'Hello world', got ''
file.c:2343: Test failed: i 0, expected to write 'Hello world' wrote -1
file.c:2343: Test failed: i 1, expected to write 'Hello world' wrote -1
file.c:2343: Test failed: i 2, expected to write 'Hello world' wrote -1
file.c:2350: Test failed: unable to close 4: 9
076c:file: 5 tests executed (0 marked as todo, 0 as flaky, 4 failures), 0
skipped.
file.c:2419: Test failed: fread() returned 0: ferror=0
file.c:2422: Test failed: got '' expected 'Hello worldHello worldHello world'
See https://test.winehq.org/data/patterns.html#msvcrt:file
--
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=55402
Bug ID: 55402
Summary: CMD '!var!' not working in 'if' statement
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: mr.dmitry.sokolov(a)gmail.com
Distribution: ---
The command not working
set var=qwe
if "!var!"=="" ...
ACTUAL
The script (attached) produces wrong output
EXPECTED
See the output in .exp file (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.
https://bugs.winehq.org/show_bug.cgi?id=46107
Bug ID: 46107
Summary: Altium Designer 18 page faults when launched
Product: Wine
Version: 3.19
Hardware: x86
URL: https://s3.amazonaws.com/altium-release-manager/Altium
_Designer_18/OfflineSetup_Altium_Designer_Public_18_1_
9.zip
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jhansonxi(a)gmail.com
Distribution: Ubuntu
Created attachment 62738
--> https://bugs.winehq.org/attachment.cgi?id=62738
Backtrace of Altium Designer 18.1.9 on wine-staging 3.19 on xubuntu 16.04
x86-64
Altium Designer 18 is a major rewrite of the EDA/PCB CAD suite and is 64-bit
with some legacy 32-bit components (previous versions were 32-bit only). It
appears to still be a mix of NET Framework and Delphi components.
It has both online and offline installers (URL link is to offline installer,
2.1GB). It requires a registration code to use the app but this is prompted
after launch. The offline installer works without problems but includes NET
Framework 2.6.1 which doesn't install properly (as per NET Framework Setup
Verification Tool) so winetricks is needed:
winetricks -q corefonts dotnet461
Upon execution the app (X2.EXE) page faults after the splash screen. Occurs
with both dev and staging.
Wine packages:
wine-devel | 3.19.0~xenial | https://dl.winehq.org/wine-builds/ubuntu
xenial/main amd64 Packages
wine-staging | 3.19.0~xenial | https://dl.winehq.org/wine-builds/ubuntu
xenial/main amd64 Packages
winetricks list:
Using winetricks 20180815-next - sha256sum:
cff80fa6dbd02b43972d13fc82e4af9bddd968623c0b18620679816968a07f80 with wine-3.19
(Staging) and WINEARCH=win64
andale
arial
comicsans
courier
georgia
impact
times
trebuchet
verdana
webdings
corefonts
w_workaround_wine_bug-34803
remove_mono
w_workaround_wine_bug-34803
remove_mono
w_workaround_wine_bug-34803
remove_mono
w_workaround_wine_bug-42701
w_workaround_wine_bug-34803
remove_mono
winxp
dotnet40
dotnet45
w_workaround_wine_bug-38959
dotnet46
dotnet461
Third-party components (identified by file name and hex dumps):
TeighaX
SQLite
DirectX 9
zlib
Professional Software Development FastMM
FFmpeg
LAME
7-Zip
LZ4
DevExpress
Chromium Embedded Framework
--
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=39876
Bug ID: 39876
Summary: Humanity Asset crashes on start with built-in d3dx
Product: Wine
Version: 1.9.0
Hardware: x86
URL: http://www.moddb.com/games/humanity-asset/downloads/hu
manity-asset-demo#
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
Distribution: ---
Created attachment 53243
--> https://bugs.winehq.org/attachment.cgi?id=53243
+d3dx log
The demo comes bundled with native d3dx9_38.dll, if you set it to 'built-in' in
winecfg, then the game crashes while loading to the main menu.
HumanityAssetDemo.2.rar
sha1: 619538846bc8c8a6d8d319378708582ef41be1c4
--
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=25988
Summary: Mr. Smoozles Goes Nutso: problems playing sound
Product: Wine
Version: 1.3.12
Platform: x86
URL: http://www.juniper-games.com/smoozles/Nutsosetup.exe
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gyebro69(a)gmail.com
Created an attachment (id=33126)
--> (http://bugs.winehq.org/attachment.cgi?id=33126)
terminal output (only built-in dlls)
The game is a nice, freeware adventure puzzle game.
Neither sound nor music is playing in the game with a clean Wine install.
After installing the directmusic components via winetricks and starting
Timidity as a separate process music is playing fine in the menu and in some of
the scenes.
However there are still problems playing sound effects during gameplay: it is
most noticeable in the first scene where a simple sound effect is intended to
play (sounds like a shooting sound).
The game becomes almost unplayable because of a strange lagging issue: the game
barely responds to keyboard events while the sound is playing.
Once you manage to make it past the first scene, gameplay seems to be back to
normal in the second scene. It seems that the lagging issue has something to do
with the looping sound effect during the first scene.
The first log is showing the output without native directmusic dlls.
--
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=44276
Bug ID: 44276
Summary: Poor resolution change handling with Shadow of
Memories demo
Product: Wine
Version: 2.21
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jhansonxi(a)gmail.com
Distribution: Ubuntu
Created attachment 60099
--> https://bugs.winehq.org/attachment.cgi?id=60099
Log from successful demo gameplay start
When game starts (fresh boot) it shows only the upper-left quadrant of the logo
screens. It then changes resolution and shows the intro video the size of a
postage stamp (often loses focus and an alt-tab is needed to see it). It then
shows only the upper-left quadrant of the main menu. It's possible to pan
around and see all of it but the button graphics don't align with the buttons
so they're hard to target with the pointer.
At the main menu, if the game is started it often freezes at the "Prologue"
screen.
Alt-tabbing during these various stages can trigger some odd effects (at least
with the Nvidia proprietary driver). The game will crash, the screen gets left
at a low resolution, etc. Eventually the behavior changes - the game launches
the opening screens correctly sized but with the Xfce desktop panel still
visible. The game will then be startable (won't freeze at the "Prologue"
screen). It still seems to freeze further along, normally after the tea house
scene when control is returned to the player. The behavior is persistent until
the system is rebooted.
The CD version of the game acts the same except it never seems to get past
"Prologue".
Some of this may be related to bug #44275.
Install notes (demo download link on same page):
https://appdb.winehq.org/objectManager.php?sClass=version&iId=31628#notes
System tested:
Xubuntu 17.04 x86, Intel Pentium D 3.46GHz, GeForce 8600 GT with Nvidia
340.102 driver.
wine-staging 2.21.0~zesty from dl.winehq.org
--
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=55241
Bug ID: 55241
Summary: The 64-bit winmm:capture & winmm:wave crash on Windows
8
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: winmm&mci
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
The 64-bit winmm:capture & winmm:wave crash on Windows 8:
capture.c:171: this is the last test seen before the exception
07d0:capture: unhandled exception c0000005 at 00007FFDC66DCF38
wave.c:686: this is the last test seen before the exception
0b14:wave: unhandled exception c0000005 at 00007FFDC66DCF38
See https://test.winehq.org/data/patterns.html#winmm:capturehttps://test.winehq.org/data/patterns.html#winmm:wave
This started with the GitLab CI's switch to Debian 12 (bookworm) for the build
system:
* The winmm_test.exe binary produced by the TestBot's Debian 11-based build VM
produces no failures when run on Windows while GitLab CI's binary for the same
Wine version produces this set of failures.
* And the TestBot runs the official WineTest builds on its Windows VMs which is
why the failures appeared on 2023-07-10 which corresponds to this commit:
commit 5799e89f15b5584f186dcc2fd24b98e0a7bd6c10
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Mon Jul 10 17:18:49 2023 +0200
gitlab: Upgrade the Debian image to bookworm.
Now the question is whether the new build environment revealed a preexisting
bug in Wine, or if the new build environment itself is broken, or if the bug is
elsewhere such as in the MinGW compiler. This is also likely the same issue as
bug 55240.
--
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=54744
Bug ID: 54744
Summary: explorerframe:taskbarlist - test_ITaskbarList()
sometimes gets E_NOTIMPL on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: explorerframe
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
explorerframe:taskbarlist - test_ITaskbarList() sometimes gets E_NOTIMPL on
Windows:
taskbarlist.c:61: Test failed: Got hr 0x80004001.
taskbarlist.c:66: Test failed: Got hr 0x80004001.
See https://test.winehq.org/data/patterns.html#explorerframe:taskbarlist
Where 0x80004001 == E_NOTIMPL
On average this happens about once every other month on recent Windows 10
versions:
* 2022-08-31 on w1064-tsign-64 (21h2)
* 2022-11-14 on w1064-tsign-32 (21h2)
* 2023-01-10 on fgtb-w10pro64-rx550-64 (22h2)
* 2023-02-06 on w10pro64-rx550-64 (22h2)
* 2023-03-27 on w10pro64-ar-64 (21h1)
--
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=54069
Bug ID: 54069
Summary: ddraw:ddraw7 - test_texture_wrong_caps() sometimes
fails on Windows 8+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ddraw:ddraw7 - test_texture_wrong_caps() sometimes fails on Windows 8+.
ddraw7.c:18954: Test failed: Got unexpected color 0x00000040.
and
ddraw7.c:18972: Test failed: Got unexpected color 0x00ff00ff.
See https://test.winehq.org/data/patterns.html#ddraw:ddraw7
Notes:
* There is no evidence of this happening on Windows 11.
* This seems to only happen with Microsoft's "Microsoft Basic Display Adapter"
driver: the "-1qxl" and "-2qxl" (dual-monitor) configuration use the "Red Hat
QXL controller" driver and are are not affected. Neither are the AMD / NVIDIA
PCI passthrough configurations.
* The 0x00000040 result mostly happens on Windows 8 to Windows 10 1607 but it
also happened a couple of times on Windows 10 21H2. Meanwhile the 0x00ff00ff
result seems to only happen on Windows 10 2004+.
* ddraw:ddraw1, ddraw:ddraw2 and ddraw:ddraw4 have a similar test function but
don't have this failure.
--
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.