January 2023 - Wine-bugs - list.winehq.org

[Bug 53456] New: kernel32:debugger - load_blackbox() sometimes fails for crash_and_debug() on Windows
by WineHQ Bugzilla 22 Mar '23

22 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=53456 Bug ID: 53456 Summary: kernel32:debugger - load_blackbox() sometimes fails for crash_and_debug() on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:debugger - load_blackbox() sometimes fails for crash_and_debug() on Windows: debugger.c:155: Test failed: unable to open 'C:\Users\winetest\AppData\Local\Temp\wt39FA.tmp' debugger.c:155: Test failed: failed to open: C:\Users\winetest\AppData\Local\Temp\wt39FA.tmp debugger.c:676: Test failed: the child and debugged pids don't match: 4840 != 1472 https://test.winehq.org/data/patterns.html#kernel32:debugger This happens on Window 8 to Windows 10 21H1 in both 32- and 64-bit tests but the failure rate appears to be below 2%. -- 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.

1 5

[Bug 54304] New: user32:input - test_GetRawInputBuffer() sometimes gets unexpected GetRawInputData() success in Wine
by WineHQ Bugzilla 21 Mar '23

21 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54304 Bug ID: 54304 Summary: user32:input - test_GetRawInputBuffer() sometimes gets unexpected GetRawInputData() success in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- user32:input - test_GetRawInputBuffer() sometimes gets unexpected GetRawInputData() success in Wine. This results in a group of 3 failures: input.c:2287: Test failed: GetRawInputData succeeded input.c:2288: Test failed: GetRawInputData returned deadbeef input.c:2421: Test failed: Spurious WM_INPUT messages See https://test.winehq.org/data/patterns.html#user32:input The first known instance goes back to 2022-08-29 and there has been roughly 2 failures per month since then with a two months gap (October & November). That makes it hard to know when this failure really appeared. Note that the 'spurious WM_INPUT messages' failure also appears on Windows. See bug 54053. -- 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.

1 2

[Bug 52982] New: PotPlayer: Crashes and hangs
by WineHQ Bugzilla 21 Mar '23

21 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=52982 Bug ID: 52982 Summary: PotPlayer: Crashes and hangs Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bq74stlxvkpb(a)opayq.com Distribution: --- Created attachment 72350 --> https://bugs.winehq.org/attachment.cgi?id=72350 Terminal output when the application hangs PotPlayer crashes or hangs shortly after starting, or starting to play a video file. Default configuration (just with Windows 10 set). I'm trying to add a printscreen as a second attachment, but it seems I cannot have more than one attachment? Well, I can add it as a link, I guess: https://imgur.com/zedUjNf (other applications work correctly with these settings and all of those drive paths are accessible) I can't quite use a non-stable version, because this is my work laptop and my work needs for wine to work correctly at all times. It would be nice if I could watch videos through PotPlayer while on breaks, though! :) https://t1.daumcdn.net/potplayer/PotPlayer/Version/Latest/PotPlayerSetup64.… I've managed to get PotPlayer working for a bit, even playing videos without a hitch, but I have no idea why - upon closing it and relaunching, I was met with a hang (I'm going to place that in the attachment). Furthermore, the logging mini-application that is supposed to gather the logs for the crash also... crashed/hanged. Dammit! :D It's been like this for over 10 minutes: https://imgur.com/HEMRh2l I've decided to use the newest hang as the attachment. I don't know how to connect this bug to the App database other than to just post a link here: https://appdb.winehq.org/objectManager.php?sClass=application&iId=14890 PotPlayer version: 220420 (1.7.21632) O.S: Linux Mint 20.3 Una with Cinnamon -- 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.

1 8

[Bug 51877] New: improve POSIX compatibility for wine-staging's patches/gitapply.sh
by WineHQ Bugzilla 21 Mar '23

21 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=51877 Bug ID: 51877 Summary: improve POSIX compatibility for wine-staging's patches/gitapply.sh Product: Wine-staging Version: 6.19 Hardware: x86-64 OS: other Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: damjan.jov(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Created attachment 70802 --> https://bugs.winehq.org/attachment.cgi?id=70802 Makes patches/gitapply.sh more POSIX compatible wine-staging's patches/patchinstall.sh can apply patches using Git commands, or CLI tools. It prefers Git commands, but when it detects that some parent directory is a Git repository, it passes --nogit to patches/gitapply.sh, which then starts using CLI tools which use various Linuxisms. On FreeBSD, the Git commands work, but since the Ports tree can itself be a Git repository, and Wine extracts under it (by default), they cannot always be used, falling back to CLI tools with Linuxisms that break. This patch makes patches/gitapply.sh more POSIX compatible, and gets it working on FreeBSD. -- 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.

1 18

[Bug 36866] New: ACDSee v17.0 failed to start, and process become "zombie" at end
by wine-bugs＠winehq.org 20 Mar '23

20 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=36866 Bug ID: 36866 Summary: ACDSee v17.0 failed to start, and process become "zombie" at end Product: Wine Version: 1.7.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: penghao(a)linuxdeepin.com Created attachment 48960 --> https://bugs.winehq.org/attachment.cgi?id=48960 +tid,+seh log Deepin 2014 Linux phcole 3.13.0-30-generic #55-Ubuntu SMP Fri Jul 4 21:43:42 UTC 2014 i686 i686 i686 GNU/Linux wine-1.7.21-67-g5acf151 download ACDSee 17 from: http://dl.acdsystems.com.s3.amazonaws.com/acdsee/en/acdsee.exe after install ACDSee, start from: ~/.wine/drive_c/Program Files/ACD Systems/ACDSee/17.0/ with: wine ACDSee.exe the program failed to start, and then turn to "zombie" process in the gnome-system-monitor. last output is: err:seh:setup_exception_record stack overflow 992 bytes in thread 0009 eip 7e8310dc esp 00230f50 stack 0x230000-0x231000-0x330000 As Anastasius Focht metioned that it was a "recursion with SHGetDesktopFolder" in: https://bugs.winehq.org/show_bug.cgi?id=36790 -- 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.

2 7

[Bug 45888] New: Tag&Rename stackoverflows on startup unless Windows version is XP
by wine-bugs＠winehq.org 19 Mar '23

19 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=45888 Bug ID: 45888 Summary: Tag&Rename stackoverflows on startup unless Windows version is XP Product: Wine Version: 3.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ronan(a)jouchet.fr Distribution: --- Created attachment 62397 --> https://bugs.winehq.org/attachment.cgi?id=62397 Tag&Rename StackOverflow debug info (logs, strace, winedbg) This is a followup of forum thread "Help debug stack overflow on Tag&Rename that used to work": https://forum.winehq.org/viewtopic.php?f=8&t=31184 --- I reinstalled my distro (Arch Linux) for reasons unrelated to Wine. After the reinstall, some Windows programs (Picasa 3, winecfg, wine regedit, wine control) that used to run fine in Wine 3.16 before the reinstall still work in freshly-reinstalled Wine 3.16, but one (Tag & Rename v3.9.15, https://appdb.winehq.org/objectManager.php?sClass=version&iId=32380 ) doesn't, and crashes with error err:seh:setup_exception_record stack overflow . See attachment for detailed crashlog and system information. I tried, without success, - To remove the existing ~/.wine prefix and get a fresh new one (as you'll see in the attachment). - To install wine_gecko (2.47-1) and wine-mono (4.7.3-1). - To install various 32bit libs recommended by Arch's wiki: https://wiki.archlinux.org/index.php/Wine#Installation . - To create a 32bit prefix and run from it. - To strace my run, but there's lots and I don't know what's (a)normal. Attached is a (partial/truncated) strace output. Forum user Bob Wya suggested that could be bug 45199 - "Many applications and games fail to start/crash after compiling wine with gcc 8.1.0 and -O2 (GOT/PIC register load code now emitted at function entry, missing hotpatch signatures)", but I recompiled wine with -O0, and it didn't help. In the end, forum user DarkShadow44 suggested I try setting Windows version to XP, and it worked. After wiping my wineprefix and running winecfg to set Windows version to XP, Tag&Rename works fine. I'm available to get debug info as necessary. Thanks for the wine :) . -- 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.

2 9

[Bug 26058] New: Thief: Deadly Shadows - Some texture problems & very many messages 'Texture wrapping not yet supported'
by wine-bugs＠winehq.org 19 Mar '23

19 Mar '23

http://bugs.winehq.org/show_bug.cgi?id=26058 Summary: Thief: Deadly Shadows - Some texture problems & very many messages 'Texture wrapping not yet supported' Product: Wine Version: unspecified Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fcsadcfgbh(a)mail.ru Created an attachment (id=33227) --> (http://bugs.winehq.org/attachment.cgi?id=33227) Look at the tree & at player's figure * There are very many messages like this 'fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.' in console while playing Thief: Deadly shadows * There are problems with textures of trees. Maybe there are also problems with textures of people - I don't know if they must be so as they are. See attached screenshot of game Wine version: git from 10 february 2011 OS: Debian Squeeze Videocard: Notebook with Nvidia GeForce 8200M with latest drivers (NVIDIA-Linux-x86_64-260.19.36.run) from www.nvidia.com -- 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.

2 11

[Bug 24159] New: sigcheck -a outputs garbage in comments for WoW.exe
by wine-bugs＠winehq.org 18 Mar '23

18 Mar '23

http://bugs.winehq.org/show_bug.cgi?id=24159 Summary: sigcheck -a outputs garbage in comments for WoW.exe Product: Wine Version: 1.3.1 Platform: x86 URL: http://technet.microsoft.com/en-us/sysinternals/bb8974 41.aspx OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: adys.wh(a)gmail.com Created an attachment (id=30403) --> (http://bugs.winehq.org/attachment.cgi?id=30403) WINEDEBUG=+ver wine sigcheck wow.exe Download sigcheck (url) and run it on WoW.exe with wine sigcheck -a wow.exe. Comments (the last line) is supposed to be empty. Instead, I get "NCompanyName" (two invisible bytes between N and Company). -- 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.

2 8

[Bug 31783] New: Add VMs with a virtual smart card reader
by wine-bugs＠winehq.org 18 Mar '23

18 Mar '23

http://bugs.winehq.org/show_bug.cgi?id=31783 Bug #: 31783 Summary: Add VMs with a virtual smart card reader Product: Wine-Testbot Version: unspecified Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com Classification: Unclassified Bruno Jesus reported that having at least some VMs with a virtual smart card reader would be useful in getting smartcard support in Wine. * One way would be through Windows software that provides a virtual smartcard device. If you know of such software please provide pointers below. * Another option would be to do it through QEmu/Libvirt's support for smartcard devices. However this seems to require plugging in a real smartcard reader into the host... Given that smartcard readers can often plug into a USB port this may be possible, but again with a rack-mounted server it may not. * QEmu/Libvirt also supports a 'host-certificate' mode for the smartcard reader. It's not clear if that negates the need for a real smartcard reader. -- 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.

2 11

[Bug 49729] New: Test the macOS build
by WineHQ Bugzilla 18 Mar '23

18 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=49729 Bug ID: 49729 Summary: Test the macOS build Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Running the tests on macOS requires being able to run macOS in a LibVirt VM which is tricky. But just testing the macOS Wine build can be achieved in the Linux VM and is thus a much easier goal to achieve and may be enough to make sure that patches don't break the macOS build. The following Docker containers provide a blueprint for how to set up such an environment: * OSXCross provides the cross-compilation tools https://github.com/tpoechtrager/osxcross * PhoenicisOrg provides an OSXCross-based container for building macOS Wine https://github.com/PhoenicisOrg/phoenicis-winebuild/blob/master/environment… -- 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.

1 5