From 4b5c6a174696d8a4b8a2e003ff5123e0d9959b43 Mon Sep 17 00:00:00 2001 From: xXJsonDeruloXx Date: Thu, 22 Oct 2026 07:42:54 -0400 Subject: [PATCH] docs: keep uninstall guidance outside desktop package build inputs --- docs/desktop-uninstall.md | 13 +++++++++++++ tools/desktop-kde/README.md | 3 --- 2 files changed, 13 insertions(+), 3 deletions(-) create mode 100644 docs/desktop-uninstall.md diff --git a/docs/desktop-uninstall.md b/docs/desktop-uninstall.md new file mode 100644 index 0000000000..dd9c5f6746 --- /dev/null +++ b/docs/desktop-uninstall.md @@ -0,0 +1,13 @@ +# Uninstall desktop mode + +Choose **Uninstall** beside **Open desktop**, then confirm. The same action is available under +**Desktop → Files**. Stop any running session and let other installs finish first. + +Removal keeps Steam, games, added apps, settings, modified files and shared dependencies. It uses +the pinned desktop file inventory and only removes matching files. Unknown desktop versions and +missing runtime package ownership cause removal to fail before deleting files. + +An interrupted desktop install also offers Uninstall. Successful removal clears that desktop +installation's recovery record and cached download so the next guest launch cannot reinstall it +through package recovery. If removal is interrupted, choose Uninstall again to retry. Open desktop +installs the desktop again when needed. diff --git a/tools/desktop-kde/README.md b/tools/desktop-kde/README.md index 549651101a..ced96147e1 100644 --- a/tools/desktop-kde/README.md +++ b/tools/desktop-kde/README.md @@ -49,9 +49,6 @@ pacman files and emulator bundle paths are protected even when they overlap an a It never follows parent symlinks or recursively deletes directories. Home, added apps, custom files and modified package files stay. A pending marker disables the installed state and allows retry after interruption. Installing the desktop again repairs its package files and clears it. -Uninstall is available beside Open desktop and under Desktop → Files, including for an -interrupted installation. Successful removal clears that desktop installation's recovery record -and cached download so the next guest launch cannot reinstall it through package recovery. The old LXQt applications are cleaned after KDE installation and before the next guest launch on an already-upgraded runtime, protecting both KDE inventories as well as the runtime and emulators. Only files owned by `lxqt-applications.txt`'s application packages are candidates; dependencies