Package Details: vesktop-git 1.5.1.r4.gdf05d12-1

Git Clone URL: https://aur.archlinux.org/vesktop-git.git (read-only, click to copy)
Package Base: vesktop-git
Description: Custom Discord desktop app with Vencord preinstalled
Upstream URL: https://github.com/Vencord/Vesktop
Licenses: GPL-3.0-only
Conflicts: vencord, vesktop
Provides: vesktop
Submitter: xiota
Maintainer: xiota (zt64)
Last Packager: xiota
Votes: 1
Popularity: 0.90
First Submitted: 2024-01-23 02:15 (UTC)
Last Updated: 2024-04-17 12:49 (UTC)

Pinned Comments

xiota commented on 2024-04-18 22:11 (UTC) (edited on 2024-04-18 22:16 (UTC) by xiota)

@everyone To build with different electron version: _electron_version=29 makepkg

If you had segfaults, edit your previous comments to add info about your system, like processor, gpu, x11/wayland, desktop environment, distro, etc.

@ReStranger Edit your comment to remove everything after the first three lines of the error message. In the future, use a pastebin if you think necessary to include long blocks of text.

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

xiota commented on 2024-04-17 15:41 (UTC)

@Kagukara Does electron30 crash if you run it by itself: electron30 https://some.website

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

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

xiota commented on 2024-04-17 15:37 (UTC)

@Kagukara If clearing cache doesn't help, you can use electron 29 by building with:

_electron_version=29 paru -Sa --rebuild vesktop-git

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."

xiota commented on 2024-04-17 15:30 (UTC)

@Kagukara Nevermind the options. I don't think it will make any difference because the real binary is from extra/electron.

Try running paru -Scd to clear the cache. Then rebuild to see if there's any improvement.

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.

xiota commented on 2024-04-17 15:18 (UTC) (edited on 2024-04-17 15:23 (UTC) by xiota)

@Kagukara Did you clear the cache and any extra folders created during build?

gdb wouldn't be very helpful. /usr/bin/vesktop is a shell script. The real binary is from extra/electron. Also, the options I mentioned in the first draft most likely wouldn't help.

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.

xiota commented on 2024-04-17 12:49 (UTC) (edited on 2024-04-17 12:58 (UTC) by xiota)

@Kagukara @D3SOX Specifically what issues are occurring, and how to reproduce them? Could it be only a rebuild was needed?

I tried rebuilding this and saw no errors during build. Running the resulting package also works as expected.

I'm updating the package to make it easier for users to change electron version by setting a variable: _electron_version=29 makepkg

The problem with using upstream specified electron versions is many projects "require" electron versions outside the range of what's available in Arch repos (can be too old or too new). I'll think about reading the requested version from package.json and using pacman to check if it's available.

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?