Skip to content

[Bug] Vesktop screenshare does not allow to share Pipewire sources (neither applications nor virtual devices) #24

Description

@mora-unie-youer

Discord Account

mora_unie_youer

Operating System

NixOS 24.11.20240531.57610d2 (Vicuña)

Linux Only ~ Desktop Environment

Niri (Wayland)

What happens when the bug or crash occurs?

Audio Sources in Screenshare window do not show anything but Pulseaudio sources.

image

As an example I can provide MPV, but for example osu!lazer and something else is not being shown too.

(MPV is launched using Pipewire Audio Output)
image

And if I run MPV in Pulseaudio mode, Vesktop shows more audio sources:
image

(MPV is launched using Pulseaudio Audio Output)
image

What is the expected behaviour?

Pipewire audio sources must be listed.

How do you recreate this bug or crash?

  1. Start Pipewire application/source/virtual device
  2. Try to start screenshare
  3. No Pipewire audio source is being shown in menu

Debug Logs

MESA-INTEL: warning: cannot initialize blitter engine
[arRPC > ipc] listening at /run/user/1000/discord-ipc-0
[arRPC > websocket] listening on 6463
[arRPC > process] started
[66179:0623/181146.986992:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
[66179:0623/181154.997377:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[66179:0623/181155.001400:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
'loop->recurse > 0' failed at ../src/pipewire/thread-loop.c:426 pw_thread_loop_wait()
[2024-06-23 18:11:56.077] [venmic] [info] [patchbay] (handle) found default metadata: 42
[2024-06-23 18:11:56.077] [venmic] [info] [patchbay] (meta_update) speaker name: "alsa_output.pci-0000_30_00.6.analog-stereo"
[2024-06-23 18:11:56.077] [venmic] [info] [patchbay] (get) running venmic 6.1.0
(node:66144) UnhandledPromiseRejectionWarning: TypeError: Video was requested, but no video stream was provided
    at AsyncFunction.<anonymous> (VCDMain:24:2433)
(Use `electron --trace-warnings ...` to show where the warning was created)
(node:66144) 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: 1)
[66144:0623/181214.226898:ERROR:screencast_portal.cc(367)] Failed to start the screen cast session.
[66144:0623/181214.226926:ERROR:base_capturer_pipewire.cc(81)] ScreenCastPortal failed: 2
Error during screenshare picker Failed to get sources.
(node:66144) UnhandledPromiseRejectionWarning: TypeError: Video was requested, but no video stream was provided
    at AsyncFunction.<anonymous> (VCDMain:24:2180)
(node:66144) 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: 2)
'loop->recurse > 0' failed at ../src/pipewire/thread-loop.c:426 pw_thread_loop_wait()
(node:66144) UnhandledPromiseRejectionWarning: TypeError: Video was requested, but no video stream was provided
    at AsyncFunction.<anonymous> (VCDMain:24:2433)
(node:66144) 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: 3)

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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions