December 2022 - Wine-Bugs - list.winehq.org

[Bug 54244] New: cardfile windows are grayed out

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54244 Bug ID: 54244 Summary: cardfile windows are grayed out Product: Wine-staging Version: 8.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mmikeinsantarosa(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 73797 --> https://bugs.winehq.org/attachment.cgi?id=73797 grayed out window example All cardfile.exe windows are grayed out. Here is a link to my goolge drive for cardfile.exe for testing https://drive.google.com/file/d/1uIJo1qtE1sQYQvgUsjiYHxBbU-ZhXehk/view?usp=… This bug has been present since wine-staging-6.6 -- 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.

Dec. 31, 2022

[Bug 54243] Warcraft 2 BNE: Fails CD check in wine versions >6.0.X

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54243 Matthew Ogilvie <mmogilvi2+wine(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Gentoo Regression SHA1| |50903a15046354e405564aff643 | |0ee505c01100a -- 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.

Dec. 31, 2022

[Bug 12209] Microsoft Office Compatibility Pack for Office 2007 File Formats does not work for PowerPoint or Excel 2003

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=12209 evelyn <evelyncillerico1(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |evelyncillerico1(a)gmail.com -- 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.

Dec. 31, 2022

[Bug 54243] New: Warcraft 2 BNE: Fails CD check in wine versions >6.0.X

by WineHQ Bugzilla

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.

Dec. 31, 2022

[Bug 53382] Slow rendering when connected to external monitor

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53382 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression Ever confirmed|0 |1 Version|7.13 |6.11 Status|UNCONFIRMED |NEW Component|-unknown |winex11.drv --- Comment #8 from Zeb Figura <z.figura12(a)gmail.com> --- Confirmed status doesn't really matter, but sure. -- 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.

Dec. 31, 2022

[Bug 54049] ddraw:ddraw2 test_texture_wrong_caps test triggers use after free bug

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54049 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |1a9c1d593b5ac5aee7450ba510f | |46c2a153741f7 Resolution|--- |FIXED CC| |z.figura12(a)gmail.com Status|NEW |RESOLVED Keywords| |source, testcase Version|unspecified |8.0-rc1 --- Comment #1 from Zeb Figura <z.figura12(a)gmail.com> --- Should be fixed by <https://source.winehq.org/git/wine.git/commitdiff/1a9c1d593b5ac5aee7450ba51…>. -- 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.

Dec. 31, 2022

[Bug 52974] MuLab 9: context menu loses focus instantly

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52974 OldCastle <oldcastlehq(a)protonmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL|https://www.mutools.com/mul |https://www.mutools.com/mul |ab/app/mulab-app-9-0-37-win |ab/app/mulab-app-9-0-59-win |64.zip |64.zip Version|7.17 |7.22 -- 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.

Dec. 31, 2022

[Bug 51179] Boss ES-5 editor: page fault on read access to 0x00000000 in 32-bit code

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51179 michael <zhangys_0217(a)sina.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zhangys_0217(a)sina.com -- 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.

Dec. 31, 2022

[Bug 54237] Metatrader 5 - Indicators with dashed style are not correctly drawn on the charts

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54237 --- Comment #2 from blueprint.trading(a)gmail.com --- Another element to consider and that I have noted is that if you set the maximum zoom in the chart then the curved dashed lines will be displayed correctly. But as soon as we sets up a lower zoom value, the problem will return evident. -- 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.

Dec. 31, 2022

[Bug 51420] Running any program in Wine causes 100% cpu usage in Xorg

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51420 NSLW <lukasz.wojnilowicz(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lukasz.wojnilowicz(a)gmail.co | |m -- 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.

Dec. 31, 2022