[Bug 39099] New: Wine's msiexec crashes when invoking Nvidia Physx maintenance tool via 'wine uninstaller -> Modify...'
https://bugs.winehq.org/show_bug.cgi?id=39099 Bug ID: 39099 Summary: Wine's msiexec crashes when invoking Nvidia Physx maintenance tool via 'wine uninstaller -> Modify...' Product: Wine Version: 1.7.48 Hardware: x86 OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: dmitry(a)baikal.ru Regression SHA1: 268cdbbfb627dd64e527bb8603d9f8d8d788f0ae Distribution: Fedora Created attachment 52093 --> https://bugs.winehq.org/attachment.cgi?id=52093 terminal output Steps to reproduce the problem: 1. create a new prefix, install Nvidia Physx: 'winetricks physx' 2. start 'wine uninstaller', select Nvidia Physx entry and click on the <Modify...> button below --> msiexec crashes Expected result: the Nvidia maintenance tool should appear, offering to repair(reinstall) or remove Physx. The crash was introduced by commit 268cdbbfb627dd64e527bb8603d9f8d8d788f0ae Author: Dmitry Timoshkov <dmitry(a)baikal.ru> Date: Fri Jul 17 17:23:24 2015 +0800 user32: SystemParametersInfo(SPI_GETNONCLIENTMETRICS) should return real font names. Reverting the commit on current git or installing Tahoma fonts via winetricks makes the crash go away for me. wine-1.7.49-41-g36a39ce Fedora 22 32-bit -- 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=39099 super_man(a)post.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man(a)post.com --- Comment #1 from super_man(a)post.com --- I cant reproduce the crash gcc (Ubuntu 4.8.4-2ubuntu1~14.04) 4.8.4 wine-1.7.49-41-g36a39ce -- 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=39099 Béla Gyebrószki <gyebro69(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #2 from Béla Gyebrószki <gyebro69(a)gmail.com> --- (In reply to super_man from comment #1)
I cant reproduce the crash
Nor do I, after rebooting..marking invalid. -- 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=39099 --- Comment #3 from Béla Gyebrószki <gyebro69(a)gmail.com> --- Created attachment 52097 --> https://bugs.winehq.org/attachment.cgi?id=52097 +relay,+seh,+tid,+msi log (uncompressed 12 MB) This morning, after a fresh boot and in a newly created prefix this bug struck me again. I logged out and in several times, but the crash remained. Now it's reproducible after a complete system reboot. Dmitry asked me to create a +relay,+seh,+tid,+msi log if the crash pops up again. When the crash is reproducible, I confirmed that either reverting that commit or installing tahoma.ttf/tahomabd.ttf makes the crash go away. I don't want to waste your time dealing with such a heisenbug hence I'm not reopening. Yet it annoys me that I'm the only one having this problem. Fedora 22 32-bit wine-1.7.49-104-gbd7f43d -- 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=39099 --- Comment #4 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- Created attachment 52104 --> https://bugs.winehq.org/attachment.cgi?id=52104 patch Does the attached patch help? -- 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=39099 --- Comment #5 from Béla Gyebrószki <gyebro69(a)gmail.com> --- (In reply to Dmitry Timoshkov from comment #4)
Created attachment 52104 [details] patch
Does the attached patch help?
Yes, it does. -- 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=39099 Dmitry Timoshkov <dmitry(a)baikal.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Component|user32 |msi Resolution|INVALID |--- --- Comment #6 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- (In reply to Béla Gyebrószki from comment #5)
Yes, it does.
https://www.winehq.org/pipermail/wine-patches/2015-August/141653.html -- 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=39099 Dmitry Timoshkov <dmitry(a)baikal.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |2ad9312f02b86591073532737f8 | |afac20aed8a9b Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- The patch was committed. -- 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=39099 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #8 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 1.7.50. -- 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.
participants (1)
-
wine-bugs＠winehq.org