https://bugs.winehq.org/show_bug.cgi?id=51745
Bug ID: 51745
Summary: Xbox Controller no longer recognised
Product: Wine
Version: 6.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: xinput
Assignee: wine-bugs(a)winehq.org
Reporter: lemonzest(a)gmail.com
Distribution: ---
Created attachment 70631
--> https://bugs.winehq.org/attachment.cgi?id=70631
XinputTest.exe Test Program for Xinput Controllers
Hi
I just updated to WineHQ-Devel 6.17 and Xinput/Xbox controllers (Not sure about
others as don't own any) are no longer detected in games
I have tried Dragon's Dogma, Dead Cells and a couple of others and they no
longer react to Gamepad inputs and XinputTest.exe says its disconnected.
rolling back to WineHQ-Devel 6.16 all is working.
I am on Fedora 34 with a PDP Afterglow XBox One Controller which in many
previous versions worked correctly.
--
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=51521
Bug ID: 51521
Summary: Installer of Tencent meeting crashes when using enter
key in the license agreement screen.
Product: Wine
Version: 6.13
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: richedit
Assignee: wine-bugs(a)winehq.org
Reporter: jactry92(a)gmail.com
Distribution: ---
Created attachment 70361
--> https://bugs.winehq.org/attachment.cgi?id=70361
a +richedit log.
Steps to reproduce:
1. `wine TencentMeeting_0300000000_2.15.4.400.publish.exe`.
2. Pass the 'return' key for selecting a language.
3. Pass the 'return' key in the license agreement screen.
Then it will crash.
Wine version: wine-6.13-114-ga5f787ac445
MD5: 13359c85cb244a587e703111c80080ec
TencentMeeting_0300000000_2.15.4.400.publish.exe
--
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=51479
Bug ID: 51479
Summary: Сreating a prefix gives "wine: Unhandled page fault on
write access ..."
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lvb.crd(a)protonmail.com
CC: rbernon(a)codeweavers.com
Regression SHA1: b065daa600e858823944f996144ed233065da7fd
Distribution: ArchLinux
When closing winecfg after creating a prefix (I mean run winecfg without
prefix), now every time this message appears in the terminal:
wine: Unhandled page fault on write access to 0000000000000000 at address
00007F6E5819F9BB (thread 00d0), starting debugger...
Not sure if this is causing any negative consequences, and I have not found any
similar descriptions among the recent issues.
Bisecting tests indicate that it started after this patch series:
https://github.com/wine-mirror/wine/commits/f24c8c75fe11fc4b928d3ec45e71ea7…
Specific commit:
b065daa600e858823944f996144ed233065da7fd bad
e3b28631485a010219928a888fcc543a5bb3c61d good
I am using the build environment that Archlinux provides. If possible please
let me know if someone can reproduce this. Thanks.
--
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=51296
Bug ID: 51296
Summary: Cogmind: Mouse cursor is a black square
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: jan.steffens(a)gmail.com
CC: z.figura12(a)gmail.com
Regression SHA1: db2b266c57b73e1a16785213ce923b749c84400e
Distribution: ArchLinux
Cogmind (a 2D SDL 1.2 game) sets a custom, monochrome mouse cursor. Since Wine
6.10, this cursor is broken and displays as a black square.
Cogmind Beta 10.2
Wine 6.9 (good), 6.10 (bad), 6.11 (bad)
GNOME 40.2 (no difference between Xorg and Wayland)
Arch Linux
db2b266c57b73e1a16785213ce923b749c84400e (user32: Handle monochrome icons in
CreateIcon() and CreateCursor() instead of CreateIconIndirect().) is the first
bad commit.
--
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=51766
Bug ID: 51766
Summary: ^C in gdb mode makes debugger quit
Product: Wine
Version: 6.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winedbg
Assignee: wine-bugs(a)winehq.org
Reporter: hi-angel(a)yandex.ru
Distribution: ---
# Steps to reproduce
1. Run `winedbg --gdb notepad.exe`
2. Once you're dropped in gdb prompt, press ^C (Ctrl+c)
## Expected
Prompt gets redrawn a line below
## Actual
You are dropped out of winedbg into the terminal.
--
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=51380
Bug ID: 51380
Summary: The segment register tests fail in the wow32
ntdll:exception build
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The segment register tests fail in the wow32 ntdll:exception build:
https://test.winehq.org/data/patterns.html#ntdll:exception
exception.c:1233: Test failed: wrong ds 0000 / 002b
exception.c:1234: Test failed: wrong es 0000 / 002b
exception.c:1235: Test failed: wrong gs 0000 / 002b
exception.c:1233: Test failed: wrong ds 0000 / 002b
exception.c:1234: Test failed: wrong es 0000 / 002b
exception.c:1235: Test failed: wrong gs 0000 / 002b
Note that these failures don't happen in a pure 32-bit prefix or when running
the 64-bit tests.
These tests were introduced by this commit:
commit 03fe2b36cdcd6d5b431af2bc02aeeb67219c1a51
Author: Alexandre Julliard <julliard(a)winehq.org>
AuthorDate: Tue Jun 22 12:43:09 2021 +0200
ntdll/tests: Add more tests for segment registers in 64-bit mode.
Signed-off-by: Alexandre Julliard <julliard(a)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=50906
Bug ID: 50906
Summary: Her Story hangs/crashes in video clips
Product: Wine
Version: 6.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sa(a)whiz.se
Distribution: ---
Created attachment 69715
--> https://bugs.winehq.org/attachment.cgi?id=69715
Video played to the end
Hi,
The game Her Story (the GOG version in my tests) either hangs or crashes on
playing videos.
There are two issues:
1, Letting a video play through to the end results in a hang and these errors:
01c4:err:quartz:DSoundRender_SendSampleData 0
01c4:err:ntdll:RtlpWaitForCriticalSection section 016F24E8
"dlls/quartz/filtergraph.c: filter_graph.cs" wait timed out in thread 01c4,
blocked by 0024, retrying (60 sec)
This is not 100% reproducible, the attached playthrough.log for this issue
contains one successful playthrough before the hang.
2. Seeking in a video results in a crash. Seems to happen every time.
0194:err:ntdll:RtlpWaitForCriticalSection section 016F1CC8
"dlls/winegstreamer/quartz_parser.c: pin.flushing_cs" wait timed out in thread
0194, blocked by 0024, retrying (60 sec)
0198:fixme:dbghelp:validate_addr64 Unsupported address fffffffff7f70000
[...]
0198:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr
0x7bc46b15
To reproduce this, click on the video once for the seek bar to appear and skip
forwards/backwards.
This is the seek_backwards.log
Logs are attached captured with +quartz,+gstreamer
Video files are H264 with MP3 audio in an AVI container.
Interestingly removing the audio track from the video files gets rid of both
issues.
(The first video file used by the game is D305.avi, unless it's random?)
--
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=29934
Bug #: 29934
Summary: Weird Worlds: Launcher no longer launches the game
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: samurai_no_densetsu(a)yahoo.es
Classification: Unclassified
Weird Worlds's launcher no longer works as expected. Since this is a
regression, I did a regression test but it was unsuccessful.
The launcher works fine from wine-1.0 to wine-1.3.25, including the stable
version wine-1.2.3. So I tried to bisect 1.3.25 against 1.4-rc4.
When I was doing the bisection learned that between wine-1.3.27 and wine-1.3.33
(both included) the launcher didn't even appear, and manually had to skip all
that range, and within wine-1.3.34 to wine-1.4-rc4 the menu launcher is there
but no longer launches the game. Can't provide a regression id as the issue
clearly raised between wine-1.3.27 and wine-1.3.33, versions in which the
launcher does not start so is virtually impossible to test.
Didn't noticed earlier as the game can be launched from scripts or commandline
this way: wine weird.exe -skiplauncher -game default
Luckyly there's a demo showing the same behaviour here:
http://www.shrapnelgames.com/Demos/DD_WW_win.html
I wish I could add more info, but that's all I have right now.
--
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=51539
Bug ID: 51539
Summary: "server: Get the process entry point from the exe
image info" breaks running if exe is loaded at a
non-default address
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: martin(a)martin.st
CC: jacek(a)codeweavers.com, julliard(a)winehq.org
Regression SHA1: a3c92a02cc7014cfdb1f90f1d070037868067097
Distribution: ---
Since "server: Get the process entry point from the exe image info",
a3c92a02cc7014cfdb1f90f1d070037868067097, starting a process fails if the exe
image ends up loaded at a non-default address.
This can be easily triggered e.g. with this patch:
---8<---
diff --git a/dlls/ntdll/unix/virtual.c b/dlls/ntdll/unix/virtual.c
index 8ceba611875..2515d73ee9e 100644
--- a/dlls/ntdll/unix/virtual.c
+++ b/dlls/ntdll/unix/virtual.c
@@ -2405,8 +2405,10 @@ static NTSTATUS virtual_map_image( HANDLE mapping,
ACCESS_MASK access, void **ad
base = wine_server_get_ptr( image_info->base );
if ((ULONG_PTR)base != image_info->base) base = NULL;
+#if 0
if ((char *)base >= (char *)address_space_start) /* make sure the DOS
area remains free */
status = map_view( &view, base, size, alloc_type & MEM_TOP_DOWN,
vprot, zero_bits_64 );
+#endif
if (status) status = map_view( &view, NULL, size, alloc_type &
MEM_TOP_DOWN, vprot, zero_bits_64 );
if (status) goto done;
---8<---
This seems to happen a lot on 32 bit arm builds (on Ubuntu 20.04), when the
expected low addresses used as default load address of 0x400000 conflicts with
e.g. /home/martin/wine32/share/wine/nls/sortdefault.nls which is mapped at
0x00230000-0x00564000.
--
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=51409
Bug ID: 51409
Summary: Trails to Azure main menu crash after video playback
after wine 6.1
Product: Wine
Version: 6.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: quartz
Assignee: wine-bugs(a)winehq.org
Reporter: billfleming11(a)gmail.com
Distribution: ---
Created attachment 70265
--> https://bugs.winehq.org/attachment.cgi?id=70265
Good vs Bad Crash logs
In Trails To Azure (and Trails from Zero) both games were working fine in Wine
5.XX and 6.1 but not in future wine releases. (using Geofront translation patch
with dinput8 dll)
These games play a video on startup, then have a typical "Press Start" screen
to get to the main menu.
After doing a bisect wine-6.1-249-g5bff63621ee is the last working release.
Bisect bad commit:
https://source.winehq.org/git/wine.git/commit/897800fd449ae0ea5da00206bd348…https://bugs.winehq.org/show_bug.cgi?id=50667#c1 (reference for getting logs
and bug from same commit)
Starting in wine-6.1-250-g897800fd449 (for several dozen versions) the game
will crash immediately before the video starts playing. All future wine
versions (6.2 to present) that succeed in playing the video crash at the menu
screen immediately afterwords as soon as input is received at the "PRESS START"
screen.
However the video does appear to play correctly in these newer releases.
If the video is removed or disabled (in the game settings) the game will still
crash in the newer wine versions when pressing start at the main menu. You have
to let the short (7 second) video play then press a button at the screen in the
working wine 6.1 version.
See attached logs.
--
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.