[BUG] Clicking on desktop notification crashes the app
See original GitHub issueAknowledgements
-
I have checked that there’s no other issue describing the same or similar problem that I currently have, regardless if it has been closed or open.
-
I can confirm that this is not an issue with the Discord website, but it is a problem specific to the WebCord itself.
-
I have tried running the build from the
master
branch and it does not have any fixes implemented according to my issue. -
My issue describes one of the unstable and/or not fully implemented features.
-
I have found a workaround to mitigate or temporarily fix this issue (please write it in Additional context section).
Operating System / Platform
🐧️ Linux
Operating system architecture
x64 (64-bit Intel/AMD)
Electron version
18.2.4
Application version
v3.1.4
Bug description
Clicking on the desktop notification about a mention crashes the app.
- turn on “Enable Desktop Notifications” in discord settings
- get a mention
- click on the notification.
- the app dies.
log:
ega@dart ~/Downloads [1]> webcord
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[1077788:0530/114333.330003:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
[WebSocket] Listening at port 6463.
[UPDATE] New application version is available! (v3.1.4 → v3.2.0)
[1077788:0530/114410.606077:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
fish: Job 1, 'webcord' terminated by signal SIGTRAP (Trace or breakpoint trap)
Additional context
Disabling notifications stops it from crashing, but then there are obviously no notifications…
Issue Analytics
- State:
- Created a year ago
- Comments:9 (5 by maintainers)
Top GitHub Comments
Unrelated with issue #134, maybe start a discussion or new issue? I want to keep threads clean, which means comments should be related to the current topic, in this example – notifications crash.
I believe this issue is stale, as a lot has changed in terms of the Electron. I will close it but if you have any thoughts or want to confirm it still occurs on WebCord 3.7.0+, you can reply to me there and I will re-open this issue.