Christian Buhtz

When my refactoring work on the manage profiles dialog is finished I think about a release candidate and release 1.5.3. After this we can merge your PR, after intense testing...

FYI: I do plan a [1.5.3 release](https://github.com/bit-team/backintime/milestone/31) in the near future. After that release I would target your PR for a [1.6.0 release](https://github.com/bit-team/backintime/milestone/33).

> The remaining lint errors are because there is similarity between the encfs and gocryptfs modules... Perhaps this can be ignored? Usually I would say "no" and recommend to create...

Hello David, your PR is the next. I leave it up to you to update your branch to the latest dev version. Then I will do some manual testing in...

> why the new GoCryptFS profile creation screen is missing a few important fields compared to the old EncFS local screen. Otherwise, I'll see if I can figure it out....

Hello David, I will try this weekend to take a closer look to your PR. Don't worry if it isn't finished yet. But before please take care that the PR...

Mhm... I am not able to reproduce your dbus related error. But I do see something like this.  So I executed the gocryptfs command from the error message directly...

That is a trail. If you can identify a commit where it worked, we can do a diff.

I still get this askpass error I described. Can you reproduce it?

I do run this on a VM with Debian 12. This is the full debug output. ``` user@worf ~/backtinime_daviewales/qt (gocrypt-rebase)$ ./backintime-qt --debug DEBUG: [common/backintime.py:616 argParse] Argument(s) used: {'debug': True, 'quiet':...