[Bug 58889] New: Blish.HUD.1.2.0 : crashes at lauch
http://bugs.winehq.org/show_bug.cgi?id=58889 Bug ID: 58889 Summary: Blish.HUD.1.2.0 : crashes at lauch Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dreamworks1691(a)gmail.com Distribution: --- Created attachment 79559 --> http://bugs.winehq.org/attachment.cgi?id=79559 error details file from wine directly When launched using wine, Blish crashes and wine says it crashed. That's 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.
http://bugs.winehq.org/show_bug.cgi?id=58889 LingM <lingm+winebz(a)posteo.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lingm+winebz(a)posteo.org --- Comment #1 from LingM <lingm+winebz(a)posteo.org> --- What are the exact reproduction steps? Running a plain 'wine "Blish HUD.exe"' with wine 10.18 gives a working tray icon. No Guild Wars 2 installed in the prefix though and there are some suspicious mono assert failures.
/builds/mono/wine-mono/wine-mono-10.3.0/mono/mono/eglib/gpath.c:115: assertion 'filename != NULL' failed
For anybody not aware, Blish HUD is a community addon for the game Guild Wars 2. It's open source and available here: https://github.com/blish-hud/Blish-HUD/releases/download/v1.2.0/Blish.HUD.1.... The game itself is free to play in the base version, which should be enough for any testing needed here.
$ sha1sum Blish.HUD.1.2.0.zip 815d8d654d68b37ec296a5bdedf61a83e5f54bc3 Blish.HUD.1.2.0.zip $ du -h Blish.HUD.1.2.0.zip 16M Blish.HUD.1.2.0.zip
-- 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.
http://bugs.winehq.org/show_bug.cgi?id=58889 --- Comment #2 from LingM <lingm+winebz(a)posteo.org> --- Created attachment 79588 --> http://bugs.winehq.org/attachment.cgi?id=79588 blishhud fatal exception Can reproduce a crash when starting Guild Wars. 1. Download Blish HUD 1.2.0 from https://github.com/blish-hud/Blish-HUD/releases/download/v1.2.0/Blish.HUD.1.... (also on the Wayback Machine should this link die) and extract it. 2. Start Blish HUD with 'wine "Blish HUD.exe"'. 3. Download the game installer from https://www.guildwars2.com/en/ 4. Install the game with `wine Gw2Setup-64.exe` into the same prefix you're running Blish HUD in. The installer downloads everything. ~83 GiB in total as of this writing. 5. Start the game. Register an account if you haven't. As mentioned above it's free for the base game. You might need to create a character, not sure. My game launches into the character select screen. No need to load into the world. 6. Blish HUD crashes as soon as the game reaches the character select screen with "[ERROR] FATAL UNHANDLED EXCEPTION: System.NotImplementedException: The method or operation is not implemented." It doesn't really matter if you start the HUD or the game first. As soon as the game finished starting the HUD crashes. Full wine output for the blish process attached. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=58889 --- Comment #3 from dreamworks1691(a)gmail.com --- (In reply to LingM from comment #1)
What are the exact reproduction steps? Running a plain 'wine "Blish HUD.exe"' with wine 10.18 gives a working tray icon. No Guild Wars 2 installed in the prefix though and there are some suspicious mono assert failures.
/builds/mono/wine-mono/wine-mono-10.3.0/mono/mono/eglib/gpath.c:115: assertion 'filename != NULL' failed
For anybody not aware, Blish HUD is a community addon for the game Guild Wars 2. It's open source and available here: https://github.com/blish-hud/Blish-HUD/releases/download/v1.2.0/Blish.HUD.1. 2.0.zip
The game itself is free to play in the base version, which should be enough for any testing needed here.
$ sha1sum Blish.HUD.1.2.0.zip 815d8d654d68b37ec296a5bdedf61a83e5f54bc3 Blish.HUD.1.2.0.zip $ du -h Blish.HUD.1.2.0.zip 16M Blish.HUD.1.2.0.zip
Oh waw, sorry, it's my first time reporting a bug for Wine or otherwise, I had no idea of the amount of details that could be usefull, thought the details given by Wine when crashing were enough. So, Blish does not only crashes when Guild Wars 2 is launched, I can't even start it by itself, with Guild Wars 2 not running. My OS is Garuda Linux, my desktop environment is Cinnamon. I launch Blish using Wine (not using terminal, I double click the .exe or right-click > launch with wine) and then Wine load, then tells me there is an error and crashes. While writing this comment I thought about trying using higher system permission. So I opened the blish directory by right-clicking it and selecting "open as Root" and then I launched Blish. It worked, the program launches. I then launched GW2, no crash from Blish, but the overlay does not appears in the game. I then stopped Blish, with GW2 still running, and started it again. Still no crash, but still no overlay. I closed everything and tryed to launch Blish alone again, with no elevated privilege : crash again. So, using Root privilege seems to allow Blish to run ? And I guess the problem that makes it not appear in game may comes from somewhere else ? I hope this helps, thank you for your time already ! -- 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.
http://bugs.winehq.org/show_bug.cgi?id=58889 --- Comment #4 from LingM <lingm+winebz(a)posteo.org> --- If at all possible, a dev will want to reproduce on their own machine. It may be someone who doesn't know what the software is even supposed to do. It may take a few years at which point it's unclear if the bug was accidentally fixed in the mean time. That's why exact reproduction steps and links to the specific software version are important. My testing was done on EndeavourOS (Arch-based, just like Garuda) with KDE Plasma x11.
And I guess the problem that makes it not appear in game may comes from somewhere else ? How do you start Guild Wars? If you have it in Steam and just press the play button there, the game and blish will launch in different wine prefixes and not even see each other.
-- 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.
http://bugs.winehq.org/show_bug.cgi?id=58889 --- Comment #5 from dreamworks1691(a)gmail.com ---
If at all possible, a dev will want to reproduce on their own machine. It may be someone who doesn't know what the software is even supposed to do. It may take a few years at which point it's unclear if the bug was accidentally fixed in the mean time. That's why exact reproduction steps and links to the specific software version are important.
I understand, it makes sense and I will remember that (or try to at least) for the future.
And I guess the problem that makes it not appear in game may comes from somewhere else ? How do you start Guild Wars? If you have it in Steam and just press the play button there, the game and blish will launch in different wine prefixes and not even see each other.
I don't use Steam for GW2, I have the game installed (using Wine iirc) on its own. Now I'm only starting to get the concept of prefixes, so I guess the problem could come from there. I should probably check where in Wine is installed Guild Wars and start Blish from the same place ? Prefixes are like... directories of sorts ? I'm not sure to understand it 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.
http://bugs.winehq.org/show_bug.cgi?id=58889 --- Comment #6 from LingM <lingm+winebz(a)posteo.org> --- You can think of prefixes as separate Windows installations. That includes files on disk, which is why they are kind of a directory, but I think they are also separate in which other processes are visible at runtime. Usually that's irrelevant from a user's perspective, but here Blish and Guild Wars need to interact. On the command line you can specify which prefix to use by setting the environment variable "WINEPREFIX=/path/to/your/prefix". Although if you're not using any helpers like Lutris or Steam, and don't specify which prefix to use, I'd expect all programs to already share the default prefix. That should be at ~/.wine -- 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