there have been like 10 github issues
If an issue were kept open, users could complain in one place, rather than keep opening new ones.
Git Clone URL: | https://aur.archlinux.org/vesktop.git (read-only, click to copy) |
---|---|
Package Base: | vesktop |
Description: | Vesktop gives you the performance of web Discord and the comfort of Discord Desktop |
Upstream URL: | https://github.com/Vencord/Vesktop |
Keywords: | discord vencord vesktop |
Licenses: | GPL3 |
Conflicts: | vesktop-bin |
Submitter: | picokan |
Maintainer: | Edu4rdSHL |
Last Packager: | Edu4rdSHL |
Votes: | 14 |
Popularity: | 8.01 |
First Submitted: | 2024-01-16 08:05 (UTC) |
Last Updated: | 2024-05-09 03:11 (UTC) |
there have been like 10 github issues
If an issue were kept open, users could complain in one place, rather than keep opening new ones.
hello, project maintainer here
seems that only a few users are having the issue
it probably seems that way because noone is complaining to you. most users instead report this upstream and add a lot of noise to our issue tracker and support channel. there have been like 10 github issues related to this issue already with multiple people replying on each, and even more people complaining in support. so no, this is not an issue only a few users have, this is a major problem that essentially makes this package broken
if you're gonna package the app, please stick to proper stable electron versions officially supported by us, especially considering you hold the very prominent "vesktop" name which makes it seem official. if you want to experiment with newer electron versions, it would be better to create a separate package akin to the discord_electron package
on a different note, why does this package provide "vencord"? this is vesktop, not vencord. vencord is a different project. it should provide "vesktop"
The /bin/sh
shebang in the shell script is incorrect; the double brackets ([[
and ]]
) are a bashism and ought to be converted to single brackets or explicitly requesting bash as the shell.
I'm using the package on Gnome Wayland, and I'm certainly not affected, so your claim is false. Plus, the upstream issue has very little interaction, so I doubt that's impacting "everyone".
In fact, only 3 persons have reported issues here on this package.
The issue is with electron, but it affects everyone using KDE Wayland (possible Gnome or Wayland in general?) EDIT: It affects everyone using Wayland, which is most people on Arch...
The package should be downgraded to electron29 until it's fixed upstream, this issue also affects alot of other electron packages such as VSCode/VSCodium which have also held back electron and added the platform hint flag.
This package works just fine, the issue is present on only a few setups and is a problem with electron, not the package itself.
This package is broken, segfaults. vesktop-bin seems to work fine.
The workaround isn't functional on my setup, even explicitly giving --ozone-platform-hint=x11
outright.
That said, I have instead:
1. Installed electron29
2. Put the following script early in my PATH
as vesktop
:
#!/bin/sh
exec electron29 /usr/lib/vesktop/app.asar
...and this works for me for now.
(...Copying the handling of vesktop-flags.conf
is left as an exercise to the reader :P)
I don't want to be that guy, but:
makepkg -s
, I don't care if your AUR helper doesn't work, it's a problem with your AUR helper and needs to be fixed there. Here's the build log for the latest version: https://gist.github.com/Edu4rdSHL/929a7eba81165da5166c4d0974d0e96fThe Wayland issue has been fixed from 1.5.1-2
onwards.
On Wayland a fix I found was by passing in --ozone-platform-hint=auto
from the command line or setting it in the electron config file.
See: https://wiki.archlinux.org/title/Wayland#Command_line_flags
Pinned Comments
Edu4rdSHL commented on 2024-04-19 19:11 (UTC) (edited on 2024-04-29 18:33 (UTC) by Edu4rdSHL)
I don't want to be that guy, but:
makepkg -s
, I don't care if your AUR helper doesn't work, it's a problem with your AUR helper and needs to be fixed there. Here's the build log for the latest version: https://gist.github.com/Edu4rdSHL/929a7eba81165da5166c4d0974d0e96fI can't reproduce the current electron issue with v30, and seems that only a few users are having the issue. So I don't see any reason to downgrade the electron version for everyone. Plus, Athonathonathon put a workaround for it, which seems to be related to the current Chrome breakage on Wayland setups.The Wayland issue has been fixed from
1.5.1-2
onwards.