Proton Drive CLI

Help
1

Would anyone have any insight on installing the Proton Drive CLI? I’m running NixOS 26.05 with Gnome 50.

In a Debian 13 virtual machine with Gnome 48, I can download the latest linux/x64 binary, and it works fine within that virtual machine.

When I download and try to use the same binary within NixOS, however, I get this error

12 |         let raw;
13 |         try {
14 |             raw = await Bun.secrets.get({ service: CREDENTIALS_SERVICE, name: CREDENTIALS_NAME });
15 |         } catch (error: unknown) {
16 |             const message = error instanceof Error ? error.message : String(error);
17 |             throw new ValidationError(
                       ^
ValidationError: Failed to load session from secrets (ensure you have secrets available, read the README for more information): libsecret not available
    code: undefined,
 details: {
  cause: error: libsecret not available
 code: "ERR_SECRETS_PLATFORM_ERROR"

,
},

      at load (src/credentials/secretCredentialsStore.ts:17:19)
      at async load (src/credentials/credentials.ts:62:38)
      at async loadSession (../incubating/account/js/src/auth.ts:31:32)
      at async SY (../incubating/account/js/src/index.ts:46:16)
      at async IY (src/api/index.ts:37:15)
      at async TP (src/init.ts:34:67)
      at async oSe (src/cli/repl.ts:10:27)
      at async aSe (src/cli/index.ts:27:15)

Under NixOS, gnome-keyring shows as installed at /run/current-system/sw/bin/gnome-keyring.

Thanks so much for your help!

P.S.: I’ve also made a start at a declarative installation for the Proton Drive CLI. I’m including it below for completeness. But when I do protondrive, I get output like I did bun --help with protondrive’s included bun dependency. So, I figure it’s better to sort out the binary download error first and then see if that resolves the declarative build issue.

  latestProtonDriveCLI = pkgs.stdenv.mkDerivation rec { # Issues possibly related to https://github.com/github/copilot-cli/issues/3081?
    pname = "protondrive";
    version = "0.9.0";

    src = pkgs.fetchurl {
      sha512 = "sha512:3533025ba69ae112b64e3e01fbcc1ad0688136a4043f6cf6a72886967d85fdcd9ec235479c2e113171614be5225bfba93427509a05ca5aa6071d924fa7e91ca8";
      url = "https://proton.me/download/drive/cli/${version}/linux-x64/proton-drive";
    };

    dontBuild = true;
    dontUnpack = true;

    installPhase = ''
      mkdir -p $out/bin
      cp ${src} $out/bin/protondrive
      chmod +x $out/bin/protondrive
    '';

    meta = with pkgs.lib; {
      description = "CLI for Proton Drive";
      homepage = "https://github.com/ProtonDriveApps/sdk/tree/main/cli";
      license = licenses.mit;
      mainProgram = "protondrive";
      platforms = [ "x86_64-linux" ];
    };
  };
2

Hi @jdavidstark. I’m fairly new to NixOS so please take my advice with several grains of salt, yet my first inclination would be to ensure that libsecret, libnotify or any other external link library dependencies that enable optional features you would like to use have been added to the buildInputs = [...] attribute of your derivation, so that the Proton Drive executable might find them at runtime within the same closure searched via the dynamic linker.

3

Thanks, I’m fairly new too. gnome-keyring and seahorse are installed, which should mean that libsecret is also (e.g., seahorse). But even the straight binary download from a browser fails with an error like the one above or `Failed to load session from secrets (ensure you have secrets available, read the README for more information): libsecret not available`.

I’ve tried several ways to incorporate libsecret in the build process but am so far still getting essentially the same kinds of errors. So, I’m clearly continuing to miss something.

4

You may be interested in this PR:

Generally, if something isn’t packaged in nixpkgs yet, it’s a good idea to search for any PRs by someone who has already done some of the packaging work.
Anyhow, that PR does this:

  postFixup = lib.optionalString stdenvNoCC.hostPlatform.isLinux ''
    wrapProgram $out/bin/proton-drive \
      --prefix LD_LIBRARY_PATH : ${
        lib.makeLibraryPath [
          libsecret
          glib
        ]
      }
  '';

AFAICT it needs to do this (rather than patchelf or similar) because of the way the library is loaded from Bun.secrets.

6

Indeed. Thanks for the suggestion. Thought I had done that, but will definitely do so more carefully next time around and will watch that PR for developments. In the meantime, this works perfectly (as referenced in the PR you mentioned), including for the current version (0.9.0). Thanks so much!

7

FYI, that’s a different packaging mentioned in another PR that linked to the nixpkgs one in its description.