Files
proton-drive-linux/docs
nvrl 38bd282d3a fix(core): reconnect to the Secret Service after it restarts
The keyring store keeps one D-Bus connection and one Secret Service
session for the whole process, and was installed once. The session lives
only in the provider's memory, so after the provider restarts every read
and write on it fails with NoSession until the process restarts. oo7,
the provider on Fedora 45, restarts on failure and can be replaced. A
daemon that met this kept every later token refresh only in memory and
the kernel keyring, and the next cold boot found the spent refresh token
(issue #78, B285).

Every keyring call now goes through with_keyring_entry. A platform
failure drops the store, unless another thread already replaced it, and
the call is made once more on a new connection. A locked keyring, a
dismissed prompt and a missing entry come back unchanged.

Reproduced against gnome-keyring 51.1 and oo7 0.7.1 restarted with
--replace in a throwaway session bus; the ignored test
real_secret_service_survives_a_provider_restart passes against both.

Refs #78
2026-11-14 19:17:11 +01:00
..
2026-11-12 10:22:04 +01:00
2026-11-05 19:12:21 +01:00

Proton Drive for Linux documentation

Proton Drive for Linux is an unofficial Proton Drive client for the Linux desktop. Your Drive appears as a folder that downloads files when you open them, local folders are backed up and kept in sync, and a GTK app with a tray icon and a search launcher covers Photos, sharing and more. A command-line client does all of it from a terminal.

These pages are also published as the wiki, generated from the docs/ folder of the repository.

Where to start

  • New here? Getting started takes you from installing to your first synced folder.
  • Installing or updating? Installation covers Fedora (COPR), Arch (AUR), Debian and Ubuntu, NixOS, and building from source.
  • Something not working? Troubleshooting starts with pdfs diagnose and goes through common problems.
  • New computer, or the old one is gone? Recovering on a new computer gets your synced folders back.
  • Quick question? Try the FAQ.

Using it

Page What it covers
User guide How the pieces fit together, the words the app uses, preferences
Files and offline access The ~/ProtonDrive folder, keeping files available offline, the Trash, earlier versions
Synced folders Backing up local folders, excluding files, changes waiting to upload, conflicts, pausing
Photos Timeline, albums, places, duplicates, importing from Google Photos
Sharing Invitations, public links, items shared with you
Computers Other computers in your account, syncing several computers
Search launcher and tray Finding files from a keyboard shortcut, the tray icon

Reference

Page What it covers
Command-line reference Every pdfs command, grouped by task, and scripting with --json
Configuration config.json, environment variables, file locations, the systemd service
Security model What protects your files, what is kept on this computer, what the client connects to
Changelog What changed in each release

Contributing

Page What it covers
Development guide Building, running and debugging from source; common changes; releasing
Architecture Crates, the local tree, read and write paths, the queue, the sync engine, the control protocol, threads, threat model
Testing Unit tests, simulation runs and the FUSE acceptance suite
Translating Adding and updating translations
Roadmap Planned work and verification still owed
Bug ledger Every tracked defect with its analysis and status

Also see CONTRIBUTING.md, and SECURITY.md to report a vulnerability privately.