Vesktop failling to launch (again with new error)

So i previously had issues with vesktop that were mostly fixed by setting selinux to permissive now I am getting a new issue when trying to run vesktop
flatpak run --branch=stable --arch=x86_64 --command=startvesktop dev.vencord.Vesktop ─╯
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:0809/193413.266674: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
APPIMAGE env is not defined, current application is not an AppImage
checkForUpdatesAndNotify called, downloadPromise is null
[3:0809/193413.481161: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
[3:0809/193413.481201: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
(node:3) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, mkdir '/run/user/1000/doc/a306d307/dist'
at mkdirSync (node:fs:1372:26)
at j2 (VCDMain:13:813)
at async Ln (VCDMain:15:4727)
(Use `vesktop.bin --trace-warnings ...` to show where the warning was created)
(node:3) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 5)

flatpak run --branch=stable --arch=x86_64 --command=startvesktop dev.vencord.Vesktop ─╯
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:0809/193413.266674: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
APPIMAGE env is not defined, current application is not an AppImage
checkForUpdatesAndNotify called, downloadPromise is null
[3:0809/193413.481161: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
[3:0809/193413.481201: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
(node:3) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, mkdir '/run/user/1000/doc/a306d307/dist'
at mkdirSync (node:fs:1372:26)
at j2 (VCDMain:13:813)
at async Ln (VCDMain:15:4727)
(Use `vesktop.bin --trace-warnings ...` to show where the warning was created)
(node:3) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 5)

Solution:
figured it out https://github.com/Vencord/Vesktop/issues/809 for some reason the vesktop settings got messed up and it was pointing to a vencord install in /run/user/1000/doc/a306d307/dist but my login keeps getting reset now so im switching to the appimage...
GitHub
[Bug] flatpak not running on bazzite · Issue #809 · Vencord/Vesktop
Discord Account zany130 Operating System Bazzite Linux Only ~ Desktop Environment KDE wayland Package Type Flatpak What happens when the bug or crash occurs? vesktop does not fully launch (stuck on...
Jump to solution
4 Replies
Kyle Gospo
Kyle Gospo4mo ago
I can't recommend SE Linux permissive under any circumstance and I don't need it to run this software on my end This is also a flatpak so we have zero control over it I would open an issue with them
zany130
zany130OP4mo ago
i did they say they don't support selinux and to disable it ( i set it to permissive as I heard disabling is a really bad idea)
Kyle Gospo
Kyle Gospo4mo ago
It is
Solution
zany130
zany1304mo ago
figured it out https://github.com/Vencord/Vesktop/issues/809 for some reason the vesktop settings got messed up and it was pointing to a vencord install in /run/user/1000/doc/a306d307/dist but my login keeps getting reset now so im switching to the appimage
GitHub
[Bug] flatpak not running on bazzite · Issue #809 · Vencord/Vesktop
Discord Account zany130 Operating System Bazzite Linux Only ~ Desktop Environment KDE wayland Package Type Flatpak What happens when the bug or crash occurs? vesktop does not fully launch (stuck on...
Want results from more Discord servers?
Add your server