[PR #383] [MERGED] Handle the RemoteDesktop portal restore token correctly #396

New issue

Closed

opened 2026-05-05 22:18:13 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 22:18:13 -06:00

Owner

📋 Pull Request Information

Original PR: https://github.com/feschber/lan-mouse/pull/383
Author: @whot
Created: 2/10/2026
Status: ✅ Merged
Merged: 2/11/2026
Merged by: @feschber

Base: main ← Head: wip/remote-desktop-restore-token

📝 Commits (1)

c3616e1 Handle the RemoteDesktop portal restore token correctly

📊 Changes

1 file changed (+46 additions, -3 deletions)

View changed files

📝 input-emulation/src/libei.rs (+46 -3)

📄 Description

For a session to actually persist, we need to request a persistence mode which we already do. The portal then returns a restore-token (in the form of an uuid) to us as part of the response to Start.

This token must then be passed into the next session during SelectDevices to restore the previous session.

The token is officially a single-use token, so we need to overwrite it every time. In practise the current XDP implementation may re-use the token but we cannot rely on that.

Reading and writing the token is not async since we expect them to be uuid-length.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/feschber/lan-mouse/pull/383 **Author:** [@whot](https://github.com/whot) **Created:** 2/10/2026 **Status:** ✅ Merged **Merged:** 2/11/2026 **Merged by:** [@feschber](https://github.com/feschber) **Base:** `main` ← **Head:** `wip/remote-desktop-restore-token` --- ### 📝 Commits (1) - [`c3616e1`](https://github.com/feschber/lan-mouse/commit/c3616e1ec414848e7f951afdbd4666e34eeb34c3) Handle the RemoteDesktop portal restore token correctly ### 📊 Changes **1 file changed** (+46 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `input-emulation/src/libei.rs` (+46 -3) </details> ### 📄 Description For a session to actually persist, we need to request a persistence mode which we already do. The portal then returns a restore-token (in the form of an uuid) to us as part of the response to Start. This token must then be passed into the *next* session during SelectDevices to restore the previous session. The token is officially a single-use token, so we need to overwrite it every time. In practise the current XDP implementation may re-use the token but we cannot rely on that. Reading and writing the token is not async since we expect them to be uuid-length. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>