- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: latest version of Discord Canary crashes after opening the app #196
Comments
Observing a similar issue here. Inspecting the startup logs I see the
I'm not sure where to go from here; spdlog is a logging library for C++, |
workaround: run the app from a terminal with the edit: this seems to work because it lets the app write to the log file, so the param might not actually be the fix - running Discord in a directory with write access might be the real reason why this works |
[IGNORE AS ISSUE IS FIXED. NEEDED TO ALLOW DISCORD TO RUN ITS INITIAL UPDATES BEFORE REAPPLYING OPENASAR. Sorry :) ] Same issue for me after latest discord update. Application crashes at startup. Ran discord in the terminal and same result. --disable-logging did not work for me. I reinstalled discord and no luck. I uninstalled openasar and reinstalled discord and everything works again: |
even if i let canary do its initial updates before installing openasar i still crash |
Yep, crashing on PTB now too, even after allowing Discord to update.
|
Writing to say here that I am also experiencing this issue on the stable build of discord (0.0.70) on arch linux. I also am experiencing nearly identical logs that l-zeuch provided but also with this coredump:
And my version of the other logs:
|
happing on stable as well macos
macOS Crash Log
|
Happens to me on stable, ptb and canary on macOS today. |
This is also happening on stable, on Linux. |
this is also happening on steam deck |
Another "happens to me too" comment to add to the pool: Using the AUR package |
Hello, The issue is caused only when i start discord from This is my
|
Can recreate it even in a terminal launch. My discord executable is in /usr/bin, if I cd there and run it, it'll crash. Agree with @Rexogamer :
See terminal output below;
|
strace confirms it, it's trying to write to /usr/bin/discord_utils.log Here is the offending strace line when I run discord from /usr/bin:
And here it is when run from anywhere else;
I symlinked /usr/bin/discord_utils.log to ~/.config/discord/.../discord_utils.log, and then had to do the same for "discord_krisp.log". After that it works :) Here's the needed files / symlinks, at least for me:
|
just wanted to note that Canary w/OpenAsar has been working fine for me for a few days without any workarounds or further tweaking. I didn't need to use the symlinks provided above - hopefully whatever fixed this rolls out to all channels soon :3 |
This seems to be resolved with Discord 0.0.71 stable (on Linux) |
nope still broken on stable, now its stuck on the forever starting loading screen
and all it does is spin spin spin & never starts if I start it from the terminal by invoking the binary directly it starts with a shit tone of errors: but I can't run discord within the shell for everyday use it needs to start via the .app executable on its own on macOS and the fix wont work for me since I'm on macOS the log directory is different + the error it self is a little different
|
closing this issue - there haven't been any issues on my end since my last comment, and the lack of any comments (from Linux users) since @edwloef's suggest that this hasn't reappeared elsewhere. @XxUnkn0wnxX, your issue appears to be unrelated - if you're still encountering this, please open a new issue. |
nm I figured it out, my desktop client adguard was killing it for some reason.. |
using the latest version of Discord Canary (0.0.492) and the latest version of OpenAsar, upon opening the app the main window appears for a few seconds before the whole app crashes and closes.
switching back to the default .asar file, the app works as normal.
I'm using Ubuntu 24.04.
(note that this isn't the same as #183 - this only started happening either today or yesterday, and the app doesn't open at all despite repeated attempts.)
Screencast.from.2024-09-21.21-27-23.webm
The text was updated successfully, but these errors were encountered: