ZorinOS: Failed to start recording: Selected display is not available for browser capture on this system.

[Litemint09]

Hi webadderall! Thank you for creating this awesome app; below is my report I experience about the bug.

Describe the bug
When ever I press the Red Record Button, the error pops up. Im using the 118 version of Recordly.

Expected behavior
I would expect that the app would start the recording.

Desktop (please complete the following information):

• Device: Thinkpad T480, Intel® Core™ i5-8250U, 16GB ram
• OS: Zorin OS 18 Core
• Kernel version: Linux 6.17.0-19-generic
• Browser: Chrome
• Version 146.0.7680.164 (Official Build) (64-bit)

Additional context
I tried switching to different Display server Protocol: Wayland and X11, but the error still persist.

Thank you so much and more power!

[rinaldicdoe]

Same

[kenluzuriaga0]

same

[webadderall]

willing to accept prs, hard to test fixes as i'm on mac

[fulgidus]

willing to accept prs, hard to test fixes as i'm on mac

I'll try to patch it asap (first i want to see if I can get it to work...)

Apparently it's because of how desktopCapturer.getSources() on Wayland returns mismatched display_ids, causing fallback IDs which are blocked by the renderer's validation check, but I'll let you know here if I manage to propose a serious PR.

Cheers, Alessio

[webadderall]

It would be so great if you manage to get this working!

[fulgidus]

I'm fighting Wayland tooth and nail... apparently it's really protective about stuff like mouse events, context, screens, etc... If I manage to make it work I'll record a video of the new behavior for approval, because I'm basically forced to not use the built-in screen picker from Recordly...

I'll keep you posted, even if I drop it because i can't hack it.

Cheers

Getting this on X11 with bspwm but only when attempting to use the full screen (selecting a window works just fine).
After clicking ok on the message the following log is printed:
[98092:0410/155825.013049:ERROR:content/browser/browser_main_loop.cc:288] GLib-GObject: ../glib/gobject/gsignal.c:2723: instance '0xccc014fe100' has no handler with id '1406'

I have installed recordly from the AUR using the recordly-bin package.

[meiiie]

Update: two commits that landed on main after this thread look directly relevant to the display-ID mismatch @fulgidus traced:

• fa97c94 ("fix(linux): allow full-screen capture by matching display sources by position if IDs do not match") — directly handles the mismatched-display_id path that was blocking the renderer's validation check.
• 571bbb9 ("fix(linux/wayland): collapse 3-step capture flow into a single portal dialog") — removes the duplicate getSources() calls that returned stale IDs to Chromium on Wayland.

For anyone still hitting this on Zorin, X11 / bspwm, or the AUR build, a retest on current main or the next build would help confirm whether the "Selected display is not available for browser capture" error is resolved, or whether there is a remaining per-window or WM-specific variant.

[SahilPanhotra]

i did the testing and found out that on wayland the recording starts and native select screen dialog opens

but it should actually start countdown and recording after selecting the screen to record

on x11 the native screen select dialog doesn't open and leads to the error as shown above

ps: if you are a user and you are using x11 you can use my release build temporarily until a clear solution is found

i am not making a PR coz i don't believe my code quality is good as its vibe coded