Deja Dup (restic) gets stuck when trying to mount a backup

Hi

I’ve just started using the new Deja Dup, which now uses Restic under the hood.

I made a few backups on Google Drive, and now I am trying to mount them.

However, nothing happens: it keeps on “thinking” but after several minutes, nothing still happens.

I tried running with debug info

DEJA_DUP_DEBUG=1 deja-dup

When it comes to the real mounting I see

Running the following tool (7459) command: restic '--json' '--cleanup-cache' '--cache-dir=/home/bettini/.cache/deja-dup/restic' '--option=rclone.program=rclone' '--repo=rclone::drive:<my path>' 'mount' '--path-template=ids/%I' '/run/user/1000/deja-dup/restic/<an id>'

I’m on Arch, maybe I miss some dependencies?

2 Likes

You did nothing wrong - this is my bad. There’s an upstream ticket about this issue, which prevents that restore flow from working outside of flatpaks. Ahem. I’m going to cut a new release today with a fix.

1 Like

Thanks for the feedback and for the upcoming fix :slight_smile:

1 Like

I’m afraid the patched version still has a few problems.

While fusermount and fusermount3 are available on my system, I get this error:

The script looks like the fixed one:

# If not in a flatpak, just call onward.
if [ ! -f /.flatpak-info ]; then
  if [ -n "" ]; then
    exec echo ""
  elif command -pv fusermount3 > /dev/null; then
    exec command -pv fusermount3
  elif command -pv fusermount > /dev/null; then
    exec command -pv fusermount
  else
    exit 10  # fusermount not found
  fi
fi

In /usr/lib/deja-dup/deja-dup-find-fusermount

OK that issue is fixed by fusermount: avoid 'exec' calls (1f1d3749) · Commits · World / Déjà Dup Backups · GitLab which avoids “exec” calls because on Arch (and maybe other places? still working through the impact) it doesn’t like exec command

1 Like

Everything works like a charm now!

Thanks! :slight_smile:

2 Likes

This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.