Bug 6095

Summary:	Discord won't open after upgrading to Fedora 35.
Product:	Fedora	Reporter:	pizzalovingnerd
Component:	discord	Assignee:	Sean Callaway <seancallaway>
Status:	RESOLVED CANTFIX
Severity:	normal	CC:	connor, henrik, leigh123linux, nixuser
Priority:	P1
Version:	f35
Hardware:	x86_64
OS:	GNU/Linux
namespace:

Description pizzalovingnerd 2021-09-26 06:17:29 CEST

Discord broken after upgrading to Fedora 35.

Hello, I am on Fedora 35's beta and it has seem to have broken Discord's RPM package. Whenever I launch Discord. I get this error:

```
Discord 0.0.15
(node:16007) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
Starting app.
Starting updater.
[Modules] Modules initializing
[Modules] Distribution: remote
[Modules] Host updates: enabled
[Modules] Module updates: enabled
[Modules] Module install path: /home/cameron/.config/discord/0.0.15/modules
[Modules] Module installed file path: /home/cameron/.config/discord/0.0.15/modules/installed.json
[Modules] Module download path: /home/cameron/.config/discord/0.0.15/modules/pending
[Modules] No updates to install
[Modules] Checking for host updates.
[Updates] You are out of date!
[Modules] Host update is available. Manual update required!
[16007:0925/212019.096963:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.

Unexpected crash report id length
Failed to get crash dump id.
Report Id: 

Unexpected crash report id length
Failed to get crash dump id.
Report Id: 
Illegal instruction (core dumped)
```

I am now using the Discord flatpak, but I prefer rpm packages, so a fix would be nice.

Comment 1 pizzalovingnerd 2021-09-26 06:18:32 CEST

Something I should have added, I am using a Nvidia 970 with RPMFusion Nvidia drivers.

Comment 2 Sean Callaway 2021-09-26 06:48:53 CEST

You're still running 0.0.15. 0.0.16 is required. Please see https://bugzilla.rpmfusion.org/show_bug.cgi?id=5953

*** This bug has been marked as a duplicate of bug 5953 ***

Comment 3 pizzalovingnerd 2021-09-26 08:28:41 CEST

Still not working after upgrading

Discord 0.0.16
Starting app.
Starting updater.
[Modules] Modules initializing
[Modules] Distribution: remote
[Modules] Host updates: enabled
[Modules] Module updates: enabled
[Modules] Module install path: /home/cameron/.config/discord/0.0.16/modules
[Modules] Module installed file path: /home/cameron/.config/discord/0.0.16/modules/installed.json
[Modules] Module download path: /home/cameron/.config/discord/0.0.16/modules/pending
[39934:0925/234008.519141:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.

Failed to get crash dump id.
Report Id: d56321a2-277c-4b

Failed to get crash dump id.
Report Id: fb332030-8cae-43
Illegal instruction (core dumped)

Comment 4 Sean Callaway 2021-09-26 18:27:12 CEST

Seems like it might be an Electron problem (https://github.com/electron/electron/pull/31091). Others have noted this problem as well (https://twitter.com/LordDudePlays/status/1440839362929778688).

Comment 5 Sean Callaway 2021-09-26 18:29:06 CEST

Please do note that our packaging agreement with Discord doesn't allow us to make changes to their software (aside from placing things in the proper locations on Fedora and ensuring that all requirements are also installed), so there's likely little we can do here. However, I'll continue to look into it.

Comment 6 leigh scott 2021-09-27 10:59:36 CEST

(In reply to Sean Callaway from comment #4)
> Seems like it might be an Electron problem
> (https://github.com/electron/electron/pull/31091). Others have noted this
> problem as well
> (https://twitter.com/LordDudePlays/status/1440839362929778688).

Discord really needs to update it's ancient bundled chrome-sandbox version, chrome fixed this in 93.0.4577.63.
The discord chrome-sandbox version probably has at least 20-30 CVE issues.

Comment 7 pizzalovingnerd 2021-09-28 03:40:05 CEST

(In reply to Sean Callaway from comment #5)
> Please do note that our packaging agreement with Discord doesn't allow us to
> make changes to their software (aside from placing things in the proper
> locations on Fedora and ensuring that all requirements are also installed),
> so there's likely little we can do here. However, I'll continue to look into
> it.

My bad, I wasn't having this issue on Flathub and Ubuntu so I thought it was an rpmfusion issue. You can close this if you want.

Comment 8 pizzalovingnerd 2021-10-05 06:14:17 CEST

Update, I am having this issue on ALL electron apps. this is not a discord specific issue. The only workaround is Flatpaks.

Comment 9 leigh scott 2021-10-20 06:58:21 CEST

*** Bug 6114 has been marked as a duplicate of this bug. ***

Comment 10 Ian Laurie 2021-10-21 02:13:57 CEST

Editing the launcher and changing the Exec line from:

Exec=/usr/bin/Discord

To:

Exec=/usr/bin/Discord --no-sandbox

works around the problem for now.  Not sure what the real world security implications of doing that are though.

Comment 11 Connor 2021-11-30 09:38:48 CET

While the --no-sandbox workaround does work, I would be interested to know when exactly the Discord devs would be looking to fix this (It seems the Linux client is over looked and rarely updated by them)

Comment 12 Sean Callaway 2021-12-01 16:34:45 CET

(In reply to Connor from comment #11)
> While the --no-sandbox workaround does work, I would be interested to know
> when exactly the Discord devs would be looking to fix this (It seems the
> Linux client is over looked and rarely updated by them)

You'd have to ask them on their forums. Our agreement with Discord (made via a dev who is no longer with Discord) was that we could package the executable they provided, but doesn't give us the right nor ability to modify what they provide.

Comment 13 Henrik Nordström 2022-02-18 19:06:56 CET

The 0.0.17 update fixes this.