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

[Bug 53337] Ice Cream Calculator: unusually slow scrolling

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53337 Zhiyi Zhang <zzhang(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #3 from Zhiyi Zhang <zzhang(a)codeweavers.com> --- Confirmed with wine-7.16. I am looking into this. -- 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.

Aug. 31, 2022

[Bug 53613] New: Visual novel RE:D Cherish! logo video and opening movie does not play

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53613 Bug ID: 53613 Summary: Visual novel RE:D Cherish! logo video and opening movie does not play Product: Wine Version: 7.15 Hardware: x86-64 URL: http://crystalia.amusecraft.com/red/download.html#Tria l OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: myatmin7800(a)gmail.com Distribution: --- Created attachment 73010 --> https://bugs.winehq.org/attachment.cgi?id=73010 Application log using wine-devel 7.15 At wine-devel 7.15 You can download trial game at the game's offical website. http://crystalia.amusecraft.com/red/download.html#Trial Run it with LANG=ja_JP.UTF8 wine red_cherish_try.exe. Logo movie does not play after starting the game. You can only hear the sound with a white screen. Download save file from here https://drive.google.com/drive/folders/17dWKzRiuPasS34ea-vkjpQQFFlk6eIzy?us… to get quick access to opening movie. Place save folder in the game directory. After the 2,3 clicks, opening movie fails to play. -- 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.

Aug. 31, 2022

[Bug 50771] msys2 unlink() fails on read-only files [needs CreateFile(FILE_WRITE_ATTRIBUTES)]

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=50771 --- Comment #7 from Zeb Figura <z.figura12(a)gmail.com> --- The thing that seems questionable to me about the wine-staging patch is that it changes permissions. I'm not sure we want to do that, especially given the (theoretical) prospect that the user might not be able to do that anyway. (Is it possible to omit FILE_SHARE_* flags if you don't have the corresponding access flags? Do we need to respect that? Seems like a security hole on Windows if so...) (In reply to Joel Holdsworth from comment #5) > I might find time to attempt these changes, but what is the policy for > evolving other people's patches? Is there a label I can put on for dual > authorship? Would I make my changes as a seperate patch? Or just rewrite the > patch, and submit it as my own work? The general practice is to either submit the patch under the name of the original author, or write a new patch with something like "Based on a patch by X" in the subject. (In reply to Joel Holdsworth from comment #6) > This looks like good stuff. What is the process for submitting these? If I > want these to go upstream, should I submit a GitLab MR? Or ask the authors > or wine-staging maintainers to submit? Is the patch in staging because it > was once rejected? Is there any way to find out why it wasn't approved years > ago? The majority of patches in wine-staging were written by the original wine-staging maintainers, Michael Müller and Sebastian Lackner. While they did submit many patches upstream (successfully or unsuccessfully), they also wrote many patches which were never submitted upstream. They also largely disappeared several years ago, and attempts to contact them are rarely successful. This patch in particular does seem to have been sent upstream in April 2015, but judging from wine-patches and wine-devel archives it never received an on-list review. -- 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.

Aug. 30, 2022

[Bug 53032] winedevice.exe segfaults on exit when built with GCC

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53032 Béla Gyebrószki <gyebro69(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gyebro69(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.

Aug. 30, 2022

[Bug 53609] Segmentation fault when starting Dosbox.exe in virtual desktop mode

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53609 --- Comment #2 from Béla Gyebrószki <gyebro69(a)gmail.com> --- Created attachment 73009 --> https://bugs.winehq.org/attachment.cgi?id=73009 +win,+msg,+message,+seh,+hook,+pid debug log -- 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.

Aug. 30, 2022

[Bug 53612] Rise of Kingdoms Game crashes when I try launch browser for Game account login

by WineHQ Bugzilla

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

Aug. 30, 2022

[Bug 53612] Rise of Kingdoms Game crashes when I try launch browser for Game account login

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53612 --- Comment #4 from SJ <swrajjoshi(a)gmail.com> --- I'm new to crossover. Could you give me steps to run in terminal and capture trace? -- 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.

Aug. 30, 2022

[Bug 53609] Segmentation fault when starting Dosbox.exe in virtual desktop mode

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53609 --- Comment #1 from Jacek Caban <jacek(a)codeweavers.com> --- I can't reproduce the problem, please attach win,msg,message,seh,hook,pid debug channels output. -- 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.

Aug. 30, 2022

[Bug 50771] msys2 unlink() fails on read-only files [needs CreateFile(FILE_WRITE_ATTRIBUTES)]

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=50771 --- Comment #6 from Joel Holdsworth <joel(a)airwebreathe.org.uk> --- This patch is relevant also: https://github.com/wine-staging/wine-staging/blob/master/patches/server-Fil… Also there is at least one patch containing test cases: https://github.com/wine-staging/wine-staging/blob/master/patches/server-Fil… This looks like good stuff. What is the process for submitting these? If I want these to go upstream, should I submit a GitLab MR? Or ask the authors or wine-staging maintainers to submit? Is the patch in staging because it was once rejected? Is there any way to find out why it wasn't approved years ago? -- 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.

Aug. 30, 2022

[Bug 50771] msys2 unlink() fails on read-only files [needs CreateFile(FILE_WRITE_ATTRIBUTES)]

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=50771 --- Comment #5 from Joel Holdsworth <joel(a)airwebreathe.org.uk> --- https://github.com/wine-staging/wine-staging/blob/master/patches/server-Fil… That patch looks extremely promising. My only comment on it is that I don't think FILE_WRITE_ATTRIBUTES (and perhaps FILE_WRITE_EA?) should be in the FILE_UNIX_WRITE_ACCESS in any case. If the application requests to write a file's attributes, that is no reason to attempt to open the file data. This patch relies on open() failing but I wonder if FILE_WRITE_ATTRIBUTES should be handled differently in the first place. Something like: 1. open() the file if the application requested FILE_READ_DATA, FILE_WRITE_DATA or FILE_APPEND_DATA 2. If the application requested FILE_WRITE_ATTRIBUTES, FILE_UNIX_READ_ACCESS or DELETE, then stat() the file. Open it with whatever permissions are avaiable. 3. If the file is non-read and non-write, then temporarily chmod() and open(). On Linux, there would be a benefit to handling #2 and #3 through a seperate code path using O_PATH, because it would remove the vulnerability to TOCTOU (time-of-check to time-of-use) issues. I might find time to attempt these changes, but what is the policy for evolving other people's patches? Is there a label I can put on for dual authorship? Would I make my changes as a seperate patch? Or just rewrite the patch, and submit it as my own work? -- 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.

Aug. 30, 2022