Can you clarify, in which file would this go? Also, given that now, June '23, there seems to be a dropbox package, is this still the way you’d do it?
Thanks
That earlier example would go into configuration.nix - please note that I no longer use dropbox (replaced it with maestral which is open source and doesn’t count against the 3 device maximum imposed by dropbox), so I don’t know if it still works.
On a hunch I switched from niri to kde plasma, and **the dropbox command started working**.
Previously, the dropbox client would start, tray icon show up, and dropbox would auth with the browser. Then after 10s it would auth again. And again, in a loop.
I guessed that perhaps the session wasn’t being saved properly in the keyring, and instead of deugging THAT I switched my entire DE to a known good state: plasma.enable = true; !
I don’t know if this helps anyone, but I will continue to post here as I figure out what the underlying problem is - I don’t want to be on plasma forever!
If anyone knows about how dropbox stores its session or how to debug keyring issues, please reply!
I sat down at my laptop this morning, assuming I would need to follow the above dance of installing plasma to get dropbox working but… no.
Maestral was still working, no key errors, and when I replaced it with the dropbox package, it authed once and worked fine. (I replaced it because maestral is now abandoned)
I don’t really understand what could be the difference…
Personally, I currently use Dropbox via home-manager. Home-manager has a built-in module but it doesn’t quite work. So I use the fix from the Pull Request, except locally. I have this ./dropbox.nix file, definining a fixed-dropbox module and I can then import it and enable it with services.fixed-dropbox.enable = true;.