[Bug] Screenshare broken on Vesktop flatpak.

[Monttukani]

Discord Account

monttukani

Operating System

Fedora 40

Linux Only ~ Desktop Environment

KDE on Wayland

What happens when the bug or crash occurs?

Screenshare doesn't share the screen. After clicking on Go live, the sharing dialog closes and nothing happens. I think that some OS package update has broken the feature as it did work fine until last week. As Fedora updates packages daily and I don't stream nearly as often, I sadly can't tell witch update it was.

However I found out that when installing Vesktop from RPM or AppImage, it works correctly.

What is the expected behaviour?

Start the screenshare stream.

How do you recreate this bug or crash?

-Join a channel or start a private call.
-Start screenshare. (The first error message gets logged when you click on the screenshare button.)
-Doesn't matter what you put in the sharing settings.
-Go live and observe as absolutely nothing happens in the UI. (The rest of the error logs appear.)

Debug Logs

20.6.2024 15.39	flatpak	[3:0620/153904.388447:ERROR:shared_x_display.cc(39)] Unable to open display
20.6.2024 15.39	flatpak	'loop->recurse > 0' failed at ../src/pipewire/thread-loop.c:426 pw_thread_loop_wait()
20.6.2024 15.39	flatpak	(node:3) UnhandledPromiseRejectionWarning: TypeError: Video was requested, but no video stream was provided
20.6.2024 15.39	flatpak	    at AsyncFunction.<anonymous> (VCDMain:24:2411)
20.6.2024 15.39	flatpak	(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)

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)

[shawn-peery]

Hello guys!

I am also having this issue on Arch Linux.

I have installed the package through flatpak as well and it has the most recent version when I list my flatpak packages of 1.5.2

One thing I don't know how to check if the version of vencord I'm using unless it's automatically updated by Vesktop itself.

If not could someone let me know how to see the version of vencord installed and how to update it?

Discord Account

cloakingpotion3818

Operating System

Arch Linux

Linux Only ~ Desktop Environment

Gnome with X Org.

What happens when the bug or crash occurs?

I'll put my own description of the but but it's very similar to the original posters. I click "Share your Screen", select the screen I want to share, choose the audio source and click on prefer smoothness, and then hit "Go Live". After I hit "Go Live" the dialog box closes and nothing happens. I haven't tried installing Vesktop from somewhere else but I figured I'd mention I have the same issue as the above person.

What is the expected behavior?
Start the screenshare stream.

How do you recreate this bug or crash?

-Join a channel or start a private call.
-Start screenshare.
-Doesn't matter what you put in the sharing settings.
-Go live and observe as absolutely nothing happens in the UI.
Debug Logs
[shawn@shawn-desktop ~]$ flatpak run dev.vencord.Vesktop
Passing the following arguments to Electron: --ozone-platform-hint=auto
[3:0621/101349.244737: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
Gtk-Message: 10:13:49.421: Failed to load module "canberra-gtk-module"
Gtk-Message: 10:13:49.422: Failed to load module "canberra-gtk-module"
[3:0621/101349.435413: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:0621/101349.435456: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
[arRPC > ipc] listening at /run/user/1000/discord-ipc-0
[arRPC > websocket] listening on 6463
[arRPC > process] started
[2024-06-21 10:14:02.448] [venmic] [info] [patchbay] (get) running venmic 3.4.2
[2024-06-21 10:14:02.456] [venmic] [info] [patchbay] (handle) found default metadata: 38
[2024-06-21 10:14:02.456] [venmic] [info] [patchbay] (meta_update) speaker name: "alsa_output.usb-Logitech_PRO_X_Wireless_Gaming_Headset-00.analog-stereo"
Error during screenshare picker Aborted
(node:3) UnhandledPromiseRejectionWarning: TypeError: Video was requested, but no video stream was provided
at AsyncFunction. (VCDMain:24:2653)
(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: 4)
i^C
[shawn@shawn-desktop ~]$ [3 preload-host-spawn-strategy] Dropping 0x81800241140 (3) because of connection closed
[3:0621/101416.992630:FATAL:bus.cc(1246)] D-Bus connection was disconnected. Aborting.
/app/bin/startvesktop: line 14: 3 Trace/breakpoint trap (core dumped) zypak-wrapper /app/bin/vesktop/vesktop.bin "${FLAGS[@]}" "$@"

Request Agreement

X I have searched the existing issues and found no similar issue
X I am using the latest Vesktop and Vencord versions (I believe so but am not sure.)
X This issue occurs on an official release (not just the AUR or Nix packages) Yes this happens on flatpac

I see that the system issue label on the original post has the text if you hover your mouse over it:

Issued caused by incapatibilities with user's system e.g. nvidia + wayland combo.

I just want to say I have the same issue on Arch Linux using Gnome and X Org instead of Wayland. I will post my Wayland logs below. Hopefully my additional information will get this issue reopened potentially. Unless people from Vesktop already know that this is something that can't be resolve due to a system issue.

Anyways, thanks for reading.

Wayland Logs:
[shawn@shawn-desktop ~]$ flatpak run dev.vencord.Vesktop
Passing the following arguments to Electron: --ozone-platform-hint=auto
[3:0621/102351.035083: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:0621/102351.279245: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:0621/102351.279288: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
[arRPC > ipc] listening at /run/user/1000/discord-ipc-0
[arRPC > websocket] listening on 6463
[arRPC > process] started
[3:0621/102351.525026:ERROR:browser_main_loop.cc(278)] Gtk: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
[3:0621/102359.206614:ERROR:shared_x_display.cc(39)] Unable to open display
[2024-06-21 10:24:02.361] [venmic] [info] [patchbay] (get) running venmic 3.4.2
[2024-06-21 10:24:02.372] [venmic] [info] [patchbay] (handle) found default metadata: 39
[2024-06-21 10:24:02.372] [venmic] [info] [patchbay] (meta_update) speaker name: "alsa_output.usb-Logitech_PRO_X_Wireless_Gaming_Headset-00.analog-stereo"
(node:3) UnhandledPromiseRejectionWarning: TypeError: Video was requested, but no video stream was provided
at AsyncFunction. (VCDMain:24:2411)
(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: 4)
i^C
[shawn@shawn-desktop ~]$ [3 preload-host-spawn-strategy] Dropping 0x122000241140 (3) because of connection closed
[3:0621/102415.225465:FATAL:bus.cc(1246)] D-Bus connection was disconnected. Aborting.
/app/bin/startvesktop: line 14: 3 Trace/breakpoint trap (core dumped) zypak-wrapper /app/bin/vesktop/vesktop.bin "${FLAGS[@]}" "$@"

[johnwongapi]

Hello, i also faced the same issue since this week.
It is resolved after running the command in #669

[shawn-peery]

Ah okay I apologize, Thank you! I don't quite know where to run the command but I've moved to the AUR on Arch Linux which is working fine.

Thanks for letting me know though!