Closed 00-kat closed 6 months ago
the aur packages are not ofdicial and thus not supported. Try official builds like the flatpak or AppImage
But which issue is this a duplicate of?
Edit: also, is the .deb
file from releases an official build? Because if it is, the AUR package vesktop-bin
is almost official (since it just downloads the deb archive, unpacks it and installs it). Not saying that it should make this a valid issue, just saying that it's what it does.
Describe the bug
I launch Vesktop. The loading screen thing opens. It disappears. According to my terminal it was terminated by a 'trace or breakpoint trap' (SIGTRAP).
To Reproduce
vesktop-bin
from the AUR (notvesktop
which apparently has segfaults). This will pull in electron 29 (not 30).Expected behavior
Vesktop doesn't crash.
Screenshots
I open it. I see this: It disappears. SIGTRAP.
Desktop (please complete the following information):
vesktop-bin
version 1.5.1-3,electron29
version 29.3.1-1It could possibly be because I'm using the hardened kernel, but I doubt it.
Command line output
Ran it with
ELECTRON_ENABLE_LOGGING=1
, yw.Looks perfectly fine until it just decides to die. Can't find any reason why, because those logs look like normal-ish runtime logs.
Also noticed that there are some warm, fresh coredumps (/s). Here's
coredumpctl info
:I am hesitant to upload the coredump as that probably has my Discord token in it.
Additional context
This did not happen 18 hours ago when I was using Vesktop. It happened 6 hours ago though. I checked
pacman.log
and there doesn't seem to have been any Vesktop or Electron update? I think? I definitely know I updated yesterday and I did not close Vesktop until I went to sleep, so maybe it got updated ¯_(ツ)_/¯.I don't feel like compiling Chromium from source today, and I hear from many other issues that
vesktop
from the AUR is broken with recommendations to usevesktop-bin
instead, so I won't be trying either of those.