[Bug] Latest update doesn't launch on Ubuntu 24

[koyuawsmbrtn]

Discord Account

No response

Operating System

Xubuntu 24.04

Linux Only ~ Desktop Environment

XFCE

Package Type

DEB

What happens when the bug or crash occurs?

When starting Vesktop I get this printed in the command line and it won't start up. Only after setting the correct permissions everything works fine then.

What is the expected behaviour?

Vesktop should start without problems

How do you recreate this bug or crash?

1. Have 1.5.3 installed
2. Update to 1.5.4 by restarting Vesktop
3. Crash

Debug Logs

[10207:1206/034953.916379:FATAL:setuid_sandbox_host.cc(163)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /opt/Vesktop/chrome-sandbox is owned by root and has mode 4755.
Segmentation fault (core dumped)

Request Agreement

• I have searched the existing issues and found no similar issue
• I am using the latest Vesktop and Vencord versions
• This issue occurs on an official release (not just the AUR or Nix packages)

[NerjalNosk]

Same issue occurs on Ubuntu 24.04
Also seems to be a full release issue rather than only an update one. Removing the package and installing it again, or directly running a package reinstall (overwrite of existing install) gives the same result.

[hugoarnal]

I personally uninstalled and reinstalled via Flatpak, which has the previous 1.5.3 version available.

[junpeikyu]

Same here on Ubuntu 24.04 - started it this morning just to see it crashing. Previous version works.
Edit: running vesktop --no-sandbox works, I just tried it. But it is only a workaround.
Edit 2: I changed the permissions as stated in the terminal by using the following commands:
sudo chown root:root /opt/Vesktop/chrome-sandbox
and
sudo chmod 4755 /opt/Vesktop/chrome-sandbox
now running it with the Vesktop command it starts normally

[Covkie]

electron-userland/electron-builder#8635

Bumping to electron builder 26 alpha 6 will fix this but not for appimage.

[DustyJinx]

I'm on Kubuntu 24.10, Update to 1.5.4 broke vencord for me aswell due to the appimage (I guess).
Vesktop reported "an update is available and will install on exit" and ran this command when exiting:

/bin/bash -c dpkg -i /home/[USERNAME]/.cache/vesktop-updater/pending/vesktop_1.5.4_amd64.deb || apt-get install -f -y

took a while and after around 5-6 minutes or so vesktop finally closed after hanging and not responding.

Opening it isn't possible anymore, journal gives this error message:

Dez 06 23:54:54 my-hostname kernel: audit: type=1400 audit(1733525694.804:390): apparmor="AUDIT" operation="userns_create" class="namespace" info="Userns create - transitioning profile" profile="unconfined" pid=39481 comm="vesktop" requested="userns_create" target="unprivileged_userns"
Dez 06 23:54:54 my-hostname kernel: audit: type=1400 audit(1733525694.805:391): apparmor="DENIED" operation="capable" class="cap" profile="unprivileged_userns" pid=39491 comm="vesktop" capability=21  capname="sys_admin"

Dez 06 23:54:54 my-hostname vesktop[39481]: [39481:1206/235454.808273:FATAL:setuid_sandbox_host.cc(163)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /opt/Vesktop/chrome-sandbox is owned by root and has mode 4>

Dez 06 23:54:54 my-hostname kernel: traps: vesktop[39481] trap int3 ip:5bc86317910e sp:7ffc487a3e50 error:0 in vesktop[606510e,5bc85f1ca000+8998000]
Dez 06 23:54:54 my-hostname systemd[1]: Started whoopsie.service - crash report submission.
Dez 06 23:54:54 my-hostname whoopsie[39509]: [23:54:54] Using lock path: /var/lock/whoopsie/lock
Dez 06 23:54:54 my-hostname systemd[1]: whoopsie.service: Deactivated successfully.
Dez 06 23:54:55 my-hostname systemd[1]: Started whoopsie.service - crash report submission.
Dez 06 23:54:55 my-hostname systemd[1922]: [email protected]: Main process exited, code=dumped, status=5/TRAP
Dez 06 23:54:55 my-hostname systemd[1922]: [email protected]: Failed with result 'core-dump'.

[slxdy]

I'm also on Kubuntu. Same behavior

[slxdy]

For some reason, the deb package from the README links to v1.5.3. BUT, downgrading to it temporarily solved it. Ig just don't update until it's fixed?

[slxdy]

And for anyone wondering, I also tried the v1.5.4 deb package from the releases page, but it still doesn't launch.

[slxdy]

Additional info: my friend has Debian with Gnome and it works just fine for him.

[Vendicated]

This is an issue with Ubuntu 24

You can work around it by running

sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0

Or try some of the other solutions in this thread

There is nothing to do from our side except wait til electron-builder releases a fix and make a new release

Blame ubuntu (see how many different apps mention the below electron issue lol)

See also electron/electron#41066

[NerjalNosk]

Better yet, rather than fully disabling this safety feature, it can be toggled only for Vesktop.

In order to do that, one only needs to create a opt.Vektop.vesktop file under /etc/apparmor.d/, include the following:

abi <abi/4.0>,

include <tunables/global>

/opt/Vesktop/vesktop flags=(default_allow) {
  userns,

  include if exists <local/opt.Vesktop.vesktop>
}

A reboot should apply the changes, but also running apparmor_parser -r /etc/apparmor.d/opt.Vesktop.vesktop as root would do it immediately, without any need for reboot.

(based on the Ubuntu blog post about Apparmor restriction on unpriviledged user namespaces)

Side note, the aforementioned solution only works for the default deb build installation, but will not help in any way for AppImage release