wine-bugs September 2023

wine-bugs@winehq.org

1 participants
2497 discussions

[Bug 53114] New: Crash of applications and games when out of focus
by WineHQ Bugzilla 17 Dec '23

17 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=53114 Bug ID: 53114 Summary: Crash of applications and games when out of focus Product: Wine-staging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ryu.ketsueki(a)outlook.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- I don't know why this happens but every wine application I could test, they need to stay on focus in the current virtual desktop (from the Desktop Environment, not Wine's virtual desktop) or else they will simply close on their own. I can't track to a specific cause because even with a completely new prefix with no "helpers", Lutris and even Valve's own Proton, this happens. So far I got the exact same result with The Sims 4, StarCraft 2 and Sonic After the Sequel. All those games will close if I change to another virtual desktop, let's say, desktop 2, if the apps themselves are on desktop 1. It also happened with the releases but it persists with Staging as well. I don't know how to backtrace this, as launching them through CLI didn't return anything useful and I'm not sure if wine itself is what is crashing or the applications. I didn't get the classic crash window either. They simply close. -- 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 29

[Bug 40712] New: blueMSX hangs at start
by wine-bugs＠winehq.org 16 Dec '23

16 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=40712 Bug ID: 40712 Summary: blueMSX hangs at start Product: Wine Version: 1.9.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jeremielapuree(a)yahoo.fr Distribution: --- Lauching the msx emulator blueMSX makes it hang: here is the short console output wine blueMSX.exe err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:dwmapi:DwmIsCompositionEnabled 0x6d88c758 fixme:iphlpapi:NotifyIpInterfaceChange (family 0, callback 0x69e94b5e, context 0x8bd300, init_notify 0, handle 0x127e1b0): stub err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:iphlpapi:NotifyIpInterfaceChange (family 0, callback 0x6a0a6836, context 0x93dd98, init_notify 0, handle 0x124e7a4): stub wine: configuration in '/home/david/.wine' has been updated. fixme:win:EnumDisplayDevicesW ((null),0,0x33ec64,0x00000000), stub! fixme:aspi:SendASPI32Command ASPI: Partially implemented SC_HA_INQUIRY for adapter 0. err:aspi:SCSI_OpenDevice Failed to open device /dev/sg0: Permission non accordée fixme:aspi:SendASPI32Command ASPI: Partially implemented SC_HA_INQUIRY for adapter 1. fixme:aspi:SendASPI32Command ASPI: Partially implemented SC_HA_INQUIRY for adapter 2. err:aspi:SCSI_OpenDevice Failed to open device /dev/sg2: Permission non accordée fixme:win:EnumDisplayDevicesW ((null),0,0x33ea54,0x00000000), stub! fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet fixme:d3d:wined3d_surface_blt Can't handle WINED3D_BLT_DO_NOT_WAIT flag. -- 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 15

[Bug 49177] New: Naruto Online
by WineHQ Bugzilla 16 Dec '23

16 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=49177 Bug ID: 49177 Summary: Naruto Online Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kacper.cholody(a)onet.pl Distribution: --- Created attachment 67194 --> https://bugs.winehq.org/attachment.cgi?id=67194 dont know When i run an application its showing a bug. I cant run game -- 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 3

[Bug 45268] New: Logicly 1.9 (Adobe AIR app) windows do not resize correctly when screen resolution is set to non-default value
by wine-bugs＠winehq.org 16 Dec '23

16 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=45268 Bug ID: 45268 Summary: Logicly 1.9 (Adobe AIR app) windows do not resize correctly when screen resolution is set to non-default value Product: Wine Version: 3.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- Created attachment 61511 --> https://bugs.winehq.org/attachment.cgi?id=61511 Start log for logicly 1.8 Logicly 1.9 (Adobe AIR application) installs and works perfect when the screen resolution is left at the default (96 dpi). When changing the screen resolution to a higher value (which is necessary for newer displays) Logicly shows its windows minimized. This prevents installing because (i.e.) the License accept dialog can not be confirmed. To reproduce - Download logicly 1.9 (see download link) - change the screen resolution with winecfg to (i.e.) 168 dpi - Install Logicly by calling the installer, start it after installation The shown windows are minimized and not resizable. When installing with the default screen resolution and running Logicly later, its windows are minimized and can be resized. so the app is usable in principle. It may be of interest, that the previous release (Logicly 1.8) does not have this problem (download from http://logic.ly/updates/Logicly-1.8.0.exe). The log files from the start of both releases are 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.

2 12

[Bug 34132] New: EaDesigner 1.01 Page Fault crash on launch
by wine-bugs＠winehq.org 16 Dec '23

16 Dec '23

http://bugs.winehq.org/show_bug.cgi?id=34132 Bug #: 34132 Summary: EaDesigner 1.01 Page Fault crash on launch Product: Wine Version: 1.6 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: loader AssignedTo: wine-bugs(a)winehq.org ReportedBy: kc-winebugs(a)chadwicks.me.uk Classification: Unclassified Created attachment 45398 --> http://bugs.winehq.org/attachment.cgi?id=45398 Backtrace In a clean WINEPREFIX and all wine dependencies handled EAdesigner 1.01 which now has libgc-1.dll added and only the exe having been changed (http://cdn.energymicro.com/dl/packages/energyAwareDesigner_pkg_1.01.zip) crashes immediately with page fault sha1-488fee6ec74b56a1dfa8bb534653db6eecdab874 EAdesigner 1.00 works fine (http://cdn.energymicro.com/dl/packages/energyAwareDesigner_pkg_1.00.zip) -- 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 6

[Bug 54243] New: Warcraft 2 BNE: Fails CD check in wine versions >6.0.X
by WineHQ Bugzilla 16 Dec '23

16 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=54243 Bug ID: 54243 Summary: Warcraft 2 BNE: Fails CD check in wine versions >6.0.X Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: mmogilvi2+wine(a)gmail.com Distribution: --- SYMPTOM: Starting with wine versions mid-6.X and including all 7.X through at least 7.22, the game "Warcraft 2: Battle.net Edition" always fails a CD check and pops up an error dialog: "Warcraft II Battle.net Edition is unable to read a required file. Your Warcraft II Battle.net Edition CD may not be in the CDROM drive. Please ensure that the disk in in the CDROM drive and press OK. To leave the program, press Exit." ---- BACKGROUND: Wine had long been able to run "Warcraft 2: Battle.net Edition", up through wine version 6.0.2 and some early 6.X versions. As described in the howto of the application DB https://appdb.winehq.org/objectManager.php?sClass=version&iId=592 (and other places), in my setup I have long used an .iso of my original CD, with symlinks for "d::" (linked to the iso) and "d:" (linked to the directory where the .iso is loop-mounted). (I actually use some wrapper scripts to temporarily mount it only when needed, etc...) I unsuccessfully asked about this in the wine forum last July https://forum.winehq.org/viewtopic.php?f=8&t=36787&sid=e1b75b6a5ffa1534a042… and am finally digging deeper into it on my own. There are also some tangential mentions in my recent Gentoo Linux forum post: https://forums.gentoo.org/viewtopic-p-8766703.html ---- ANALYSIS: I have managed to git bisect this bug to commit 50903a15046354e405564aff6430ee505c01100a "kernelbase: Reimplement GetVolumeInformation on top of GetVolumeInformationByHandle" (although I needed to cherry-pick an unrelated "sincos()" build fix at each step...). Digging deeper, the following sequence of events leads to the bug: 1. The game calls GetVolumeInformationW() with root=L"D:\\". - The game only wants file system flags and FS type name. - Wine proceeds to: 2. NtOpenFile() the root (I haven't traced into this much)... 3. GetVolumeInformationByHandleW() 4. NtQueryVolumeInformationFile() with info_class=FileFsAttributeInformation 5. get_mountmgr_fs_info(), which determines unix_name="/archive/wineData/warcraftII-BNE-2001.iso" and letter=25 (Z:). - BUG: letter=25 definitely indicates a bug. The game is asking about D:, not Z:. - MAYBE BUG: Not sure whether mapping "D:\\"'s handle to the .iso rather than the loop mount point directory is a bug or not. - FYI: I'll note that NtQueryVolumeInformationFile()'s documentation says that if the handle "represents a direct device open, only FileFsDeviceInformation can be specified..." in the remarks (i.e., not the info_class being asked for here). There doesn't seem to be any attempt to enforce this in wine. See https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/ntifs/nf-nti… 6. Since wine now thinks the game is asking about "Z:", it returns file system type "NTFS" and associated flags, rather than the correct "CDFS" (and flags). 7. Presumably the game sees the "NTFS" and/or flags, decides this isn't a CD at all, and after some more searching, ultimately pops up the error dialog. ---- POTENTIAL FIXES: I'm not sure the best way to fix this. Some possibilities include: A. Somehow ensure the handle that GetVolumeInformation() opens gets mapped to the mounted directory, instead of the .iso file? - This would seem to make sense, but I'm not sure. B. Add more logic to find_dos_device() to notice if path is a file (or device) that is pointed at by one of the double-colon symlinks? - It might need similar caching as get_drives_info(), etc? This would be just a little involved, but might be the best "smallish scale" fix. C. Just revert commit 50903a15046354e405564aff6430ee505c01100a? But that might leave GetVolumeInformationByHandle() broken, and it does seem cleaner to only do all the device/FS superblock parsing and determination in one place... D. Do a more thorough audit / cleanup of how different ways of representing and mapping between unix names, NT names, devices, mount points, symlinks, fallback logic, etc all interact with each other? My initial vague impression is that a lot of this logic is a bit haphazard and only "mostly" works, rather than being robustly designed to always work. - Very involved and time consuming, and well beyond anything I currently have any interest in attempting myself. ---- WORKAROUND: A quick end-user workaround that seems to work is to change the "d::" symlink to point to the correct /dev/loop0 or loop1, or 2...., that just happens to match whatever free loop device that "mount" dynamically picks to use. - I think this only works because these days /dev is usually mounted as a separate file system, and in wine there is find_dos_device() logic to stops looking if the st_dev changes and then later stuff falls back on doing something else... - Even disregarding that, it seems a bit ugly and fragile to assume a particular loop device, especially if you have other things you sometimes loop mount... (Although maybe my wrapper script could dynamically update the symlink based on parsing /proc/mounts after things are mounted...) -- 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 11

[Bug 23921] New: LBA2 doesnt refresh its screen
by wine-bugs＠winehq.org 15 Dec '23

15 Dec '23

http://bugs.winehq.org/show_bug.cgi?id=23921 Summary: LBA2 doesnt refresh its screen Product: Wine Version: 1.3.0 Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: vleon1(a)gmail.com Little big adventure 2 rarely refresh its screen, rendering the game unplayable. the bug didnt exist in the 1.2 branch. You can hear the games music from the next screen (for example from the ingame) while having a picture of the games menu. -- 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 19

[Bug 55561] New: kernel32:virtual - The 32-bit test_write_watch() fails in the new WoW mode
by WineHQ Bugzilla 15 Dec '23

15 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=55561 Bug ID: 55561 Summary: kernel32:virtual - The 32-bit test_write_watch() fails in the new WoW mode Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- kernel32:virtual - The 32-bit test_write_watch() fails in the new WoW mode: virtual.c:2099: Test failed: VirtualAlloc succeeded See https://test.winehq.org/data/patterns.html#kernel32:virtual A bisect shows that this started with the commit below: commit f6dbcccab9e33f05b4df9ba3824a849b172b97c3 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Mon Aug 28 13:47:14 2023 +0200 wow64: Send cross-process notifications. -- 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 3

[Bug 45123] New: gdiplus/ graphicspath test crashes under clang-5.0.1 but not gcc-7.3.0
by wine-bugs＠winehq.org 15 Dec '23

15 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=45123 Bug ID: 45123 Summary: gdiplus/graphicspath test crashes under clang-5.0.1 but not gcc-7.3.0 Product: Wine Version: 3.7 Hardware: x86 URL: https://test.winehq.org/data/8dca6c35e11a104385242ed83 46ee05707b78ef7/linux_ae-gentoo-dbg-clang/gdiplus:grap hicspath.html OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com CC: madewokherd(a)gmail.com Distribution: Gentoo Backtrace: =>0 0x7eca42d9 widen_joint+0x139(p1=<is not available>, p2=<is not available>, p3=<is not available>, pen=<is not available>, last_point=<has been optimized away by compiler>) [/var/lib/jenkins/home/workspace/wine-clang/dlls/gdiplus/graphicspath.c:1849] in gdiplus (0x0033fc38) 1 0x7eca2ac1 GdipWidenPath+0x3a0(path=<is not available>, pen=<is not available>, matrix=<is not available>, flatness=<is not available>) [/var/lib/jenkins/home/workspace/wine-clang/dlls/gdiplus/graphicspath.c:2029] in gdiplus (0x0033fca8) 2 0x7ed36262 func_graphicspath+0x3331() in gdiplus_test (0x0033fe08) 3 0x7ed74968 main+0x457() in gdiplus_test (0x0033fea8) 4 0x7ed74caa in gdiplus_test (+0x8fca9) (0x0033fee0) 5 0x7b45df9c call_process_entry+0xb() in kernel32 (0x0033fef8) 6 0x7b45e0f3 start_process+0x122(entry=0x7ed74f7a, peb=<is not available>) [/var/lib/jenkins/home/workspace/wine-clang/dlls/kernel32/process.c:1099] in kernel32 (0x0033ffdc) 7 0x7b45dfaa start_process_wrapper+0x9() in kernel32 (0x0033ffec) 0x7eca42d9 widen_joint+0x139 [/var/lib/jenkins/home/workspace/wine-clang/dlls/gdiplus/graphicspath.c:1849] in gdiplus: divps %xmm5,%xmm0 1849 float dx0 = distance * (p2->X - p1->X) / length_0; -- 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 10

[Bug 27916] New: Ferro CCTV: Fails to start
by wine-bugs＠winehq.org 15 Dec '23

15 Dec '23

http://bugs.winehq.org/show_bug.cgi?id=27916 Summary: Ferro CCTV: Fails to start Product: Wine Version: 1.3.25 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: lukasz.wojnilowicz(a)gmail.com Created an attachment (id=35713) --> (http://bugs.winehq.org/attachment.cgi?id=35713) Error message Steps to reproduce: 1) remove ~/.wine 2) winetricks wmp9 3) install Ferro CCTV 4) wine FerroCCTV.exe Behaviour: Error message (see attachment). Expected behaviour: No error message. -- 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 12

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs September 2023