-
Notifications
You must be signed in to change notification settings - Fork 41
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
Discord 0.0.8 crashes on launch #53
Comments
I have the same issue. Also if I run Discord from console I get the following output: [aeder@ryzen-pc ~]$ flatpak run com.discordapp.Discord |
Also the workaround described in this comment makes it work for me: #48 (comment) So it might be this is just a duplicate of that issue. |
Hi all,
I stopped using the flatpak. Copy in AUR works perfectly so I use that now.
This is an issue specifically with the flatpak.
…On Thu, 14 Feb 2019, 10:46 aeder, ***@***.***> wrote:
Also the workaround described in this comment makes it work for me: #48
(comment)
<#48 (comment)>
So it might be this is just a duplicate of that issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#53 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Arbrzmb5IoGqsUxFCG1hTXvjHLmtRZdYks5vNM3ugaJpZM4aUhaK>
.
|
Same issue here. Fedora 30 Adding TZ environment variable to run command helped me.
|
This workaround works for me too. |
I am also having issues but running |
there's anyone maintaining the discord flatpak? |
Flatpak Discord still crashing |
Hi (im going to repost this in all the duplicated issues). After digging a while seems caused by this bug in chromium. Maybe updating the electron version will fix it? |
I think this issue has been fixed, I can no longer reproduce it. |
Hi,
Crashes upon launch and goes into a reload loop.
Error in console is..
TypeError: Cannot read property 'format' of undefined
at t.renderHeader (7380edb1e656997102a0.js:1)
at t.render (7380edb1e656997102a0.js:1)
at Qo (824772519e8b9ac65e01.js:117)
at Xo (824772519e8b9ac65e01.js:117)
at ti (824772519e8b9ac65e01.js:117)
at Li (824772519e8b9ac65e01.js:117)
at Mi (824772519e8b9ac65e01.js:117)
at fa (824772519e8b9ac65e01.js:117)
at ca (824772519e8b9ac65e01.js:117)
at _a (824772519e8b9ac65e01.js:117)
at Immediate._onImmediate (824772519e8b9ac65e01.js:45)
at runCallback (timers.js:694)
at tryOnImmediate (timers.js:665)
at processImmediate (timers.js:647)
The text was updated successfully, but these errors were encountered: