[Bug 56340] New: Update to 9.0.0-1.3 wine-mono from 8.1.0-1.2 wipes out Quicken 2011 (which needs .net) in Tumbleweed
https://bugs.winehq.org/show_bug.cgi?id=56340 Bug ID: 56340 Summary: Update to 9.0.0-1.3 wine-mono from 8.1.0-1.2 wipes out Quicken 2011 (which needs .net) in Tumbleweed Product: Wine Version: 9.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: timothyadams(a)ymail.com Distribution: --- A recent openSUSE Tumbleweed (rolling distro) snapshot pulled in a new version of wine-mono: 9.0.0-1.3, replacing 8.1.0-1.2. After I updated my system to this snapshot via "zypper dup," I discovered that I could no longer load Quicken 2011 in wine. The program would start to load, then crash. I have locked wine-mono and restored to an earlier snapshot with wine-mono 8.1.0-1.2. Quicken now loads properly again, with no other packages locked. Still, I thought I should file a bug to let you know. I have installed wine 9.1-1.1, wine-32bit 9.1-1.1, wine-gecko 2.47.4-1.2, and winetricks 20240105-1.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.
https://bugs.winehq.org/show_bug.cgi?id=56340 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression Component|-unknown |mscoree -- 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=56340 Esme Povirk <madewokherd(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |madewokherd(a)gmail.com --- Comment #1 from Esme Povirk <madewokherd(a)gmail.com> --- Can you provide the output of "wine uninstaller --list" from your prefix? -- 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=56340 --- Comment #2 from timothyadams(a)ymail.com --- (In reply to Esme Povirk from comment #1)
Can you provide the output of "wine uninstaller --list" from your prefix?
Sure! wine uninstaller --list {18A8E78B-9EF2-496E-B310-BCD8E4C1DAB3}|||iSEEK AnswerWorks English Runtime MoffFreeCalc_is1|||Moffsoft FreeCalc {5FE545A1-D215-4216-9189-E7B39C9D1CC1}|||Quicken 2011 {B1266608-93DD-5FEE-AA21-C7D707CADCC1}|||Wine Mono Runtime {17063F55-8827-53EA-96B4-EFD23A602ABF}|||Wine Mono Windows Support -- 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=56340 --- Comment #3 from Esme Povirk <madewokherd(a)gmail.com> --- OK, I somehow got confused and thought .NET Framework was involved, but I see that's not the case (and now that I'm rereading, I'm not sure where I even got that idea). I didn't know this had worked, so that's cool to find out. If you run "wine uninstaller", you can see what version of Wine Mono is actually installed in your Wine prefix. You can also uninstall it there and install whatever version you want via MSI (see https://dl.winehq.org/wine/wine-mono/ for the msi downloads). Assuming this is a Wine Mono regression, you should be able to work around it while upgrading your system by keeping 8.1.0 in your Wine prefix (though you may need to redo this step as Wine will update it when it updates your prefix). If it works, that also confirms that it was the Wine Mono upgrade that broke this. Unfortunately, I wasn't able to reproduce the bug here. Can you get console output from the crash with WINE_MONO_TRACE=x set? -- 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=56340 timothyadams(a)ymail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from timothyadams(a)ymail.com --- Before anything else, Esme, thank you for the prompt response and the efforts to help. openSUSE maintainer Marcus Meissner explained what turned out to be the root of the problem in: https://bugzilla.opensuse.org/show_bug.cgi?id=1220067 "one thing is that i might have been to quick to pusxh newer wine mono as wine 9.2 is not yet available. "I will fixup and get wine 9.2 released, after that it might work again also with new wine mono." I brought in wine 9.2 via zypper dup, removed the lock, upgraded wine-mono ... and all is working well again. Problem fixed! -- 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=56340 Esme Povirk <madewokherd(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |NOTOURBUG -- 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=56340 Esme Povirk <madewokherd(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #5 from Esme Povirk <madewokherd(a)gmail.com> --- Closing. -- 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)
-
WineHQ Bugzilla