mirror of https://github.com/rustdesk/rustdesk.git synced 2026-09-05 15:41:23 +03:00

Files

xPrimeTime 4389687d9d fix(wayland): subscribe to portal Response before making the request (#15726 )

`request_remote_desktop` and its response handlers call the portal method
first and only then subscribe to the resulting Request's `Response` signal,
using the object path returned by the call. The comment above
`create_session` already describes why that is wrong:

> To avoid a race condition between the caller subscribing to the signal
> after receiving the reply for the method call and the signal getting
> emitted, a convention for Request object paths has been established that
> allows the caller to subscribe to the signal before making the method
> call.

The code then does the opposite of what the comment says. When the portal
emits `Response` before our match rule is installed, the signal is dropped
and the flow stalls: `request_remote_desktop` spins its 3-minute wait loop
and gives up, so the user sees the screen picker again (or a failure) even
when a valid restore token would have restored the session silently.

Build the request path from our unique bus name plus the `handle_token` we
pass in the call arguments, per the Request documentation, and subscribe
before calling. Applied to all five portal calls: CreateSession,
SelectSources (both the ScreenCast and post-SelectDevices paths),
SelectDevices, and Start. The `handle_token` values are unchanged; they are
now named locals so the path and the argument cannot drift apart.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

2026-08-04 12:46:09 +08:00

examples

opt qos (#10459 )

2025-01-20 17:59:36 +08:00

src

fix(wayland): subscribe to portal Response before making the request (#15726 )

2026-08-04 12:46:09 +08:00

.gitignore

source code

2021-03-29 15:59:14 +08:00

build.rs

Add Windows arm64 support (#15139 )

2026-06-18 22:37:15 +08:00

Cargo.toml

fix linux llvm22 build (#15565 )

2026-07-15 13:27:15 +08:00

README.md

scrap readme

2021-07-29 13:33:26 +08:00

README.md

Derived from https://github.com/quadrupleslap/scrap

scrap

Scrap records your screen! At least it does if you're on Windows, macOS, or Linux.

Usage

[dependencies]
scrap = "0.5"

Its API is as simple as it gets!

struct Display; /// A screen.
struct Frame; /// An array of the pixels that were on-screen.
struct Capturer; /// A recording instance.

impl Capturer {
    /// Begin recording.
    pub fn new(display: Display) -> io::Result<Capturer>;

    /// Try to get a frame.
    /// Returns WouldBlock if it's not ready yet.
    pub fn frame<'a>(&'a mut self) -> io::Result<Frame<'a>>;

    pub fn width(&self) -> usize;
    pub fn height(&self) -> usize;
}

impl Display {
    /// The primary screen.
    pub fn primary() -> io::Result<Display>;

    /// All the screens.
    pub fn all() -> io::Result<Vec<Display>>;

    pub fn width(&self) -> usize;
    pub fn height(&self) -> usize;
}

impl<'a> ops::Deref for Frame<'a> {
    /// A frame is just an array of bytes.
    type Target = [u8];
}

The Frame Format

The frame format is guaranteed to be packed BGRA.
The width and height are guaranteed to remain constant.
The stride might be greater than the width, and it may also vary between frames.

System Requirements

OS	Minimum Requirements
macOS	macOS 10.8
Linux	XCB + SHM + RandR
Windows	DirectX 11.1