[Bug 52416] New: Metatogger 7.2: Wine crashes upon launching the software
https://bugs.winehq.org/show_bug.cgi?id=52416 Bug ID: 52416 Summary: Metatogger 7.2: Wine crashes upon launching the software Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: p10qjuhh(a)duck.com Distribution: --- Created attachment 71672 --> https://bugs.winehq.org/attachment.cgi?id=71672 The backtrace generated by Wine Launching Metatogger at all causes a crash. Download: https://www.luminescence-software.org/download/metatogger/Metatogger-Install... Name: Metatogger-Installer.exe MD5: 4fc5a6f1c39a95bb754c25207fe2bb9a (This installer is updated semi-regularly by the software maintainer, so determining the version is on you) At the time of writing, 7.2 is the latest release, but this problem is likely to still exist in later versions. -- 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=52416 p10qjuhh(a)duck.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from p10qjuhh(a)duck.com --- duplicate *** This bug has been marked as a duplicate of bug 52417 *** -- 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=52416 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download Ever confirmed|0 |1 Status|RESOLVED |REOPENED Severity|critical |normal URL| |https://www.luminescence-so | |ftware.org/download/metatog | |ger/Metatogger-Installer.ex | |e Resolution|DUPLICATE |--- --- Comment #2 from Austin English <austinenglish(a)gmail.com> --- Not critical. -- 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=52416 --- Comment #3 from Austin English <austinenglish(a)gmail.com> --- *** Bug 52417 has been marked as a duplicate of this bug. *** -- 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=52416 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEW CC| |xerox.xerox2000x(a)gmail.com --- Comment #4 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Confirming. As a guess I`d say it`s related to https://bugs.winehq.org/show_bug.cgi?id=52396 and https://bugs.winehq.org/show_bug.cgi?id=52407 (it apparently seems dotnetcore 6 application (64-bit)) before crash dialog comes up: 0104:fixme:nls:get_dummy_preferred_ui_language (0x8 0000000000197AE0 0000000000000000 0000000000197AD8) returning a dummy value (current locale) 0104:fixme:nls:get_dummy_preferred_ui_language (0x8 0000000000197AE0 0000000000197A30 0000000000197AD8) returning a dummy value (current locale) 0104:fixme:nls:CompareStringEx semi-stub behavior for flag(s) 0x8000000 0104:fixme:nls:ResolveLocaleName stub: L"eo", 000000000019D7F0, 85 Unhandled exception. System.TypeInitializationException: The type initializer for 'Metatogger.App' threw an exception. ---> System.Globalization.CultureNotFoundException: Culture is not supported. (Parameter 'name') eo is an invalid culture identifier. After applying patch from https://bugs.winehq.org/show_bug.cgi?id=52407 there`s no crash but it chokes with an endless: 00d4:trace:seh:handle_syscall_fault Couldn`t get any further -- 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=52416 --- Comment #5 from p10qjuhh(a)duck.com --- Should I make a new bug report with that patch and the new error? -- 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=52416 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #6 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- This is really a duplicate of https://bugs.winehq.org/show_bug.cgi?id=52396 and https://bugs.winehq.org/show_bug.cgi?id=52407 Resolving as such. @Reporter of bug: The application starts here after applying patches from aforementioned bugreports. (Unfortunately I don`t expect bug 52407 to be solved soon :() *** This bug has been marked as a duplicate of bug 52867 *** -- 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=52416 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #7 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- Closing duplicate. -- 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