[Bug 42845] New: Hearthstone crashes at loading screen
https://bugs.winehq.org/show_bug.cgi?id=42845 Bug ID: 42845 Summary: Hearthstone crashes at loading screen Product: Wine Version: 2.6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ttmigueltt(a)gmail.com Distribution: --- Created attachment 57938 --> https://bugs.winehq.org/attachment.cgi?id=57938 The wine stdout/stderr log from running Hearthstone Since today, Hearthstone has crashed on both my Ubuntu machines, running 16.04 and 17.04, with multiple Wine versions (1.7, 2.5, and 2.6) It crashes as the game is loading, while the blue rune is glowing at the top, and after the friend list button appears on the bottom left, but before any other things have loaded. However, I have not changed my wine settings recently, so it must be related to the game or to my account. The fact that the crash seems related to a "LocationAPI", make me wonder if a new patch has introduced a feature that my Wine installation doesn't have. Or perhaps I accidentally enabled such a feature by either adding more friends or by clicking the "Fireside Gatherings" button on my friends list. Either way, my guess is the crash is related to the friends list, because Hearthstone only crashes when I log onto my normal region (US), where I have added friends. It does *not* crash when I log on to another region, such as Europe, where I have no friends. -- 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=42845 ttmigueltt(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Ubuntu -- 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=42845 --- Comment #1 from ttmigueltt(a)gmail.com --- Created attachment 57939 --> https://bugs.winehq.org/attachment.cgi?id=57939 A screenshot from the point during loading that the game crashes -- 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=42845 shevvek.twitch(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |shevvek.twitch(a)gmail.com --- Comment #2 from shevvek.twitch(a)gmail.com --- I've been experiencing the exact same symptoms, starting at exactly the same time. -- 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=42845 --- Comment #3 from shevvek.twitch(a)gmail.com --- System.BadImageFormatException apparently has to do with mono: https://forum.unity3d.com/threads/mysterious-crash-for-no-reason-can-anyone-.... -- 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=42845 --- Comment #4 from ttmigueltt(a)gmail.com --- I don't doubt it's related to Mono, but the "System.BadImageFormatException: Could not resolve field token" error seems like a generic error message for a missing class, which in this case is probably LocationAPI, the real culprit. -- 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=42845 --- Comment #5 from shevvek.twitch(a)gmail.com --- My thought was, since in that link it looks like sometimes that error shows up with mono but not with .Net, maybe it would go away with dotnet in winetricks. Every time I try to install any dotnet more recent than 3.0, though, wine appears to crash, so I haven't been able to test it. -- 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=42845 mancubus220(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mancubus220(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.
https://bugs.winehq.org/show_bug.cgi?id=42845 ttmigueltt(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ttmigueltt(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.
https://bugs.winehq.org/show_bug.cgi?id=42845 winetest(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest(a)luukku.com --- Comment #6 from winetest(a)luukku.com --- (In reply to shevvek.twitch from comment #5)
My thought was, since in that link it looks like sometimes that error shows up with mono but not with .Net, maybe it would go away with dotnet in winetricks. Every time I try to install any dotnet more recent than 3.0, though, wine appears to crash, so I haven't been able to test it.
You need to use winetricks to install dotnet or it wont install correctly. -- 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=42845 --- Comment #7 from ttmigueltt(a)gmail.com --- Oddly, I have the same issue - dotnet versions up to 3.0 work fine, but all later versions just hang forever. When I try to install dotnet40 with winetricks, it gets up to Executing winetricks_early_wine regedit C:\windows\Temp\_winxp\set-winver.reg and then it just never completes. I wonder if this is related. -- 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=42845 Gijs Vermeulen <acescopezz(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |acescopezz(a)gmail.com --- Comment #8 from Gijs Vermeulen <acescopezz(a)gmail.com> --- (In reply to ttmigueltt from comment #7)
Oddly, I have the same issue - dotnet versions up to 3.0 work fine, but all later versions just hang forever.
When I try to install dotnet40 with winetricks, it gets up to Executing winetricks_early_wine regedit C:\windows\Temp\_winxp\set-winver.reg and then it just never completes.
I wonder if this is related.
What is your winetricks version? -- 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=42845 --- Comment #9 from shevvek.twitch(a)gmail.com --- (In reply to Gijs Vermeulen from comment #8)
(In reply to ttmigueltt from comment #7)
Oddly, I have the same issue - dotnet versions up to 3.0 work fine, but all later versions just hang forever.
When I try to install dotnet40 with winetricks, it gets up to Executing winetricks_early_wine regedit C:\windows\Temp\_winxp\set-winver.reg and then it just never completes.
I wonder if this is related.
What is your winetricks version?
I'm using whatever version of winetricks is part of PlayOnLinux on Ubuntu 16.04. -- 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=42845 Diara <elmo.mantynen(a)iki.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |elmo.mantynen(a)iki.fi --- Comment #10 from Diara <elmo.mantynen(a)iki.fi> --- I clicked something in the new "Fireside Gatherings" UI. Pretty sure that triggered something persistent that crashes the client upon loading. -- 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=42845 --- Comment #11 from Diara <elmo.mantynen(a)iki.fi> --- Installing dotnet40 from within PlayOnLinux fixes it (Ubuntu 16.10). -- 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=42845 --- Comment #12 from Gijs Vermeulen <acescopezz(a)gmail.com> --- (In reply to shevvek.twitch from comment #9)
(In reply to Gijs Vermeulen from comment #8)
(In reply to ttmigueltt from comment #7)
Oddly, I have the same issue - dotnet versions up to 3.0 work fine, but all later versions just hang forever.
When I try to install dotnet40 with winetricks, it gets up to Executing winetricks_early_wine regedit C:\windows\Temp\_winxp\set-winver.reg and then it just never completes.
I wonder if this is related.
What is your winetricks version?
I'm using whatever version of winetricks is part of PlayOnLinux on Ubuntu 16.04.
AFAIK PlayOnLinux doesn't use winetricks, they have their own system to install things like dotnet. The comment above said that it worked for him through POL when installing dotnet40. -- 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=42845 --- Comment #13 from mancubus220(a)gmail.com --- Installing dotnet40 using winetricks worked for me (Fedora 25, upstream winetricks). Winetricks URLs for dotnet were not working for me earlier and when I tried manually installing the dotnet exe with the wine command it did not work (they didn't set the correct library overrides?). -- 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=42845 --- Comment #14 from ttmigueltt(a)gmail.com --- Created attachment 57948 --> https://bugs.winehq.org/attachment.cgi?id=57948 The PlayOnLinux log for a working environment for running Hearthstone I created a new PlayOnLinux (POL) environment today on Ubuntu 17.04, and installing and playing Hearthstone worked fine. I think this could be done with regular Wine, I just used POL to make it easier for me. The key things I did here were: * I used a 32-bit wine prefix. Installing dotnet and Hearthstone had issues with 64 bit * I used Wine 1.9, although I believe versions 2.XX should work fine, since they did before * I installed the following POL components (I believe all of these can also be installed using `winetricks install <component name>`: - corefonts - dotnet40 - vcrun2013 I believe that the main difference between this environment and the ones that weren't working is that this was 32-bit, and had dotnet40 installed. I have attached my exact playonlinux log, which should tell you the exact details of my working environment. I hope this helps you resolve this problem. -- 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=42845 --- Comment #15 from ttmigueltt(a)gmail.com --- And to summarise, the key issue seems to be this LocationAPI, which is only required by Hearthstone after clicking the Fireside Gatherings button (which makes sense, since it seems to be a feature for finding nearby players? I'm not certain, I've never used it). However once it's turned on, it's impossible to turn off, and will crash for that user whenever they log in to the same zone. This LocationAPI must be a dotnet component that comes with dotnet 4.0, which only seems to install correctly in a 32-bit wine prefix, and thus installing it seems to resolve the issue. -- 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=42845 --- Comment #16 from shevvek.twitch(a)gmail.com --- I can confirm that the problem started after I clicked the Fireside Gathering button. I was able to solve the problem by installing dotnet45 in my existing 32-bit wine 2.6 wineprefix in PlayOnLinux. I noticed that the dotnet installation appeared to hang at two specific points: msxml3 and during the patches to dotnet3. I installed msxml3 by itself using PlayOnLinux, which seemed to work. I surmise that the problem with the PoL dotnet3+ installation script is caused by the script incorrectly waiting for human input. Here's the log message from the point where it hangs: Running wine-2.6 reg delete HKLM\Software\Microsoft\NET Framework Setup\NDP\v3.5 (Working directory : ~/.PlayOnLinux/ressources/dotnet35) Are you sure you want to delete the registry key 'HKEY_LOCAL_MACHINE\Software\Microsoft\NET Framework Setup\NDP\v3.5'? (Yes|No) I also observed that during the freeze there was a process called "reg" hogging CPU, which I presume is wine regedit. I was able to get past this by waiting until the PlayOnLinux GUI froze at this point in the dotnet install script. Then I ran "killall wineserver," and PlayOnLinux resumed the install script successfully. Hearthstone now works. -- 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=42845 Frédéric Delanoy <frederic.delanoy(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |frederic.delanoy(a)gmail.com Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #17 from Frédéric Delanoy <frederic.delanoy(a)gmail.com> --- Confirmed with wine-2.6-154-gcced5dfbde -- 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=42845 howkj1(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |howkj1(a)gmail.com --- Comment #18 from howkj1(a)gmail.com --- Confirmed: April 25, 2017 System: Ubuntu 16.04.2 LTS Codeweavers Crossover Linux 16.2.0 [wine 2.x] Installation: Used default Battle.net bottle installer provided by Crossover Linux. (which may also install Visual Studio core runtime?) Launched Battle.net Desktop App and used it to install Hearthstone. Issue: After enabling Fireside Gatherings Beta button in Hearthstone Chat and exiting the app during week of April 25, 2017, Hearthstone would no longer load beyond the blue loading swirl with settings button at the bottom. The app would immediately crash/close and dump back to the Battle.net Desktop App Launcher. Fix: [wine] Install .Net Framework 4.x in your app bottle / environment. [For Crossover Users] Use Crossover menu to select Battle.net bottle and "Install Windows Software..." to install Microsoft .Net Framework 4.6, which downloads and installs 2.0 and 4.0 and attempts to install 4.6.1 but fails with a "Blocking Issues: The .NET Framework 4.6.1 is not supported on this operating system." but is an irrelevant issue since 4.x installed just fine. It seems that .Net 4.x (or 4.0 minimum) is the requirement for the new Fireside Gathering feature to not crash on initial start of Hearthstone. Thanks: To all the Bug 42845 commenters and the O.P. in helping this to be a quick fix and being visible in the search engines. -- 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=42845 Yehia Hafez <yehia.wael(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yehia.wael(a)gmail.com --- Comment #19 from Yehia Hafez <yehia.wael(a)gmail.com> --- Disabling dbghelp seemed to have fixed the same problem for me. -- 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=42845 adrussel(a)hotmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adrussel(a)hotmail.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.
https://bugs.winehq.org/show_bug.cgi?id=42845 evilny0 <evilny0(a)moomoocamp.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |evilny0(a)moomoocamp.net --- Comment #20 from evilny0 <evilny0(a)moomoocamp.net> --- (In reply to Yehia Hafez from comment #19)
Disabling dbghelp seemed to have fixed the same problem for me.
This was enough to fix the problem for me as well with wine staging 2.7. -- 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=42845 volerig(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |volerig(a)gmail.com --- Comment #21 from volerig(a)gmail.com --- (In reply to evilny0 from comment #20)
(In reply to Yehia Hafez from comment #19)
Disabling dbghelp seemed to have fixed the same problem for me.
This was enough to fix the problem for me as well with wine staging 2.7.
Same here, all the other workarounds did not work for me. But one have to know that disabling dbghelp will prevent the Blizzard app from displaying the "login" button on the login window. -- 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=42845 --- Comment #22 from winetest(a)luukku.com --- Those of you who are able to play this game, could you comment on bug 37111? More activity on bugs means that we can solve them faster. -- 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=42845 --- Comment #23 from Yehia Hafez <yehia.wael(a)gmail.com> --- (In reply to volerig from comment #21)
(In reply to evilny0 from comment #20)
(In reply to Yehia Hafez from comment #19)
Disabling dbghelp seemed to have fixed the same problem for me.
This was enough to fix the problem for me as well with wine staging 2.7.
Same here, all the other workarounds did not work for me. But one have to know that disabling dbghelp will prevent the Blizzard app from displaying the "login" button on the login window.
You can make an application override for hearthstone only, which would allow you to use the login button in the Blizzard app. If this bug is widespread, we should probably change the game's rating to gold. -- 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=42845 --- Comment #24 from volerig(a)gmail.com --- (In reply to Yehia Hafez from comment #23)
(In reply to volerig from comment #21)
(In reply to evilny0 from comment #20)
(In reply to Yehia Hafez from comment #19)
Disabling dbghelp seemed to have fixed the same problem for me.
This was enough to fix the problem for me as well with wine staging 2.7.
Same here, all the other workarounds did not work for me. But one have to know that disabling dbghelp will prevent the Blizzard app from displaying the "login" button on the login window.
You can make an application override for hearthstone only, which would allow you to use the login button in the Blizzard app. If this bug is widespread, we should probably change the game's rating to gold.
Didn't thought of that. Thanks. -- 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=42845 Maik Wagner <maiktapwagner(a)aol.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maiktapwagner(a)aol.com --- Comment #25 from Maik Wagner <maiktapwagner(a)aol.com> --- It is the first time that I am playing this game and I am using wine 2.12 staging which just works fine to get the game to run. The intro screen shows up for quite a while but eventually I am able to get into the game and 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.
https://bugs.winehq.org/show_bug.cgi?id=42845 Amosar <maxi.cass11(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maxi.cass11(a)gmail.com --- Comment #26 from Amosar <maxi.cass11(a)gmail.com> --- The bug is already present in 2.16-staging The temporary fix is disable locationapi on winecfg but the Fireside Gatherings feature seems not work after that. -- 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=42845 David M <davs.ms(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |davs.ms(a)gmail.com --- Comment #27 from David M <davs.ms(a)gmail.com> --- Doing winetricks dotnet40 fixed the problem for me, currently playing on Tumbleweed (Linux 4.14.2-1-default) -- 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=42845 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #28 from joaopa <jeremielapuree(a)yahoo.fr> --- Does the bug still occur with wine-5.11? -- 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=42845 minion <minion.procyk(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |minion.procyk(a)gmail.com --- Comment #29 from minion <minion.procyk(a)gmail.com> --- i verified using wine-5.11 that the game loads/plays without any major issues without using any winetricks -- 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=42845 --- Comment #30 from joaopa <jeremielapuree(a)yahoo.fr> --- Reported fixed. Can an administrator close this bug as 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=42845 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #31 from Austin English <austinenglish(a)gmail.com> --- (In reply to minion from comment #29)
i verified using wine-5.11 that the game loads/plays without any major issues without using any winetricks
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=42845 Maciej Stanczew <maciej.stanczew+b(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maciej.stanczew+b(a)gmail.com --- Comment #32 from Maciej Stanczew <maciej.stanczew+b(a)gmail.com> --- This is *NOT* fixed. Running the game without 'locationapi' workaround results in a crash and the following log: Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'System.Device, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. File name: 'System.Device, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' at (wrapper native-to-managed) <Module>.GetReady() After adding 'locationapi' as 'disabled' for Hearthstone.exe, the game launches successfully. Please note that this bug only impacts people who have enabled Fireside Gatherings in the game. Only people who have not enabled this feature can launch the game without workarounds. Unfortunately once you enable Fireside Gatherings in the game, there is no way to go back and disable it. -- 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=42845 --- Comment #33 from Maciej Stanczew <maciej.stanczew+b(a)gmail.com> --- Can someone please reopen this bug before it gets incorrectly reported as fixed in release notes for 5.12? Thanks. -- 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=42845 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #34 from Zebediah Figura <z.figura12(a)gmail.com> --- Reopening... -- 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=42845 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Hearthstone crashes at |Hearthstone crashes at |loading screen |loading screen with | |wine-mono 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=42845 Neko-san <nekoNexus(a)protonmail.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nekoNexus(a)protonmail.ch -- 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=42845 Esme Povirk <madewokherd(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |madewokherd(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.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla