Universal Blue•5mo ago

Vesktop stoped working after reboot

I been using the vesktop flatpak instead of the normal discord and it stoped working after a reboot. this is what I get in a terminal

flatpak run --branch=stable --arch=x86_64 --command=startvesktop dev.vencord.Vesktop --enable-blink-features=MiddleClickAutoscroll
Wayland socket is available, running natively on Wayland.
To disable, remove the --socket=wayland permission.
Passing the following arguments to Electron: --enable-speech-dispatcher --ozone-platform-hint=auto
[3:0719/111019.722360:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory


#
# Fatal process out of memory: Failed to reserve virtual memory for CodeRange
#
----- Native stack trace -----

/app/bin/startvesktop: line 26:     3 Trace/breakpoint trap   (core dumped) zypak-wrapper /app/bin/vesktop/vesktop.bin "${FLAGS[@]}" "$@"

flatpak run --branch=stable --arch=x86_64 --command=startvesktop dev.vencord.Vesktop --enable-blink-features=MiddleClickAutoscroll
Wayland socket is available, running natively on Wayland.
To disable, remove the --socket=wayland permission.
Passing the following arguments to Electron: --enable-speech-dispatcher --ozone-platform-hint=auto
[3:0719/111019.722360:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory


#
# Fatal process out of memory: Failed to reserve virtual memory for CodeRange
#
----- Native stack trace -----

/app/bin/startvesktop: line 26:     3 Trace/breakpoint trap   (core dumped) zypak-wrapper /app/bin/vesktop/vesktop.bin "${FLAGS[@]}" "$@"

Solution:

yup setting SELINUX= to permissive in etc/selinux/config fixes the issue completly apperently for some reason changeing the arguments sometimes allows vesktop to not be blocked...

Jump to solution

2 Replies

zany130OP•5mo ago

apperently its a se linux issue according to the dev

Solution

zany130•5mo ago

yup setting SELINUX= to permissive in etc/selinux/config fixes the issue completly apperently for some reason changeing the arguments sometimes allows vesktop to not be blocked

Gaming

Programming

Vesktop stoped working after reboot