Package Details: vesktop-git 1.5.5.r17.g391ad94-1

Git Clone URL: https://aur.archlinux.org/vesktop-git.git (read-only, click to copy)
Package Base: vesktop-git
Description: A standalone Electron-based Discord app with Vencord & improved Linux support
Upstream URL: https://github.com/Vencord/Vesktop
Licenses: GPL-3.0-only
Conflicts: vesktop
Provides: vesktop
Submitter: xiota
Maintainer: xiota (zt64, Covkie)
Last Packager: Covkie
Votes: 8
Popularity: 0.36
First Submitted: 2024-01-23 02:15 (UTC)
Last Updated: 2025-04-01 22:22 (UTC)

Dependencies (8)

Required by (3)

Sources (4)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

Kagukara commented on 2024-04-17 15:38 (UTC)

@xiota I know, doesn't help with finding out why electron30 doesn't work though.

Kagukara commented on 2024-04-17 15:31 (UTC) (edited on 2024-04-17 15:32 (UTC) by Kagukara)

@xiota I literally just said I did that.

"Clearing the cache with paru -Scd then paru --rebuild -S vesktop-git still results in the segfault."

Kagukara commented on 2024-04-17 15:22 (UTC) (edited on 2024-04-17 15:23 (UTC) by Kagukara)

@xiota I use paru for my aur helper, how would I go about "building after adding options=(!lto)" and where do I add "options=(!lto)"? I've never had to do this before, usually I just do paru --rebuild -S <package_name> if I need to rebuild a package.

Clearing the cache with paru -Scd then paru --rebuild -S vesktop-git still results in the segfault.

Kagukara commented on 2024-04-17 14:26 (UTC) (edited on 2024-04-17 14:28 (UTC) by Kagukara)

@xiota when running vesktop after rebuilding I get (not using electron29):

[53237:0100/000000.234846:ERROR:broker_posix.cc(41)] Recvmsg error: Connection reset by peer (104)
Segmentation fault (core dumped)

I've tried to run gdb vesktop but it outputs "/usr/bin/vesktop": not in executable format: file format not recognized. Not sure how else to get the segfault information you'd need to help.

Kagukara commented on 2024-04-17 11:40 (UTC) (edited on 2024-04-17 11:40 (UTC) by Kagukara)

Editing the PKGBUILD to what D3SOX has provided has fixed the segfault that would happen.

@xiota would you be able to edit the PKGBUILD to add these changes?