Open pbabinca opened 2 years ago
Hello! I'm sorry that Deja Dup is giving you a hassle.
That's an odd error - we do have --filesystem=xdg-run/gvfsd
permissions set on the flatpak already. And you even manually gave yourself the permission.
I've not heard similar reports yet of this and can't reproduce myself. So at least this doesn't sound like a widespread problem.
I'm not sure what to try next to debug this. Have you used bustle
before? It might shed some light on dbus traffic that could be relevant (some gvfs communications happen on dbus).
I also note that your user id is 18031
, which feels unusual. Is your user/desktop setup particularly interesting in a way that might be a clue?
Hi all. I'm getting this error too. My last (daily) backup that ran successfully is reported as being 2 days ago.
This is what I've started getting:
flatpak run org.gnome.DejaDup
I'm then asked to Grant Access to my Onedrive backup location. This outputs the error message below, opens my web browser at the appropriate OneDrive page "Are you trying to sign in to DejDup backups?". Clicking "Continue" on the page produces no result.
The expected result would be for backup to proceed.
(org.gnome.DejaDup:2): GVFS-WARNING **: 15:31:50.774: The peer-to-peer connection failed: Error when getting information for file “/run/user/1000/gvfsd”: No such file or directory. Falling back to the session bus. Your application is probably missing --filesystem=xdg-run/gvfsd privileges.
This error message is new to me, though Deja has been running in the background on this machine for some time.
Happy to provide more information to help
`flatpak info org.gnome.DejaDup
Déjà Dup Backups - Protect yourself from data loss
ID: org.gnome.DejaDup
Ref: app/org.gnome.DejaDup/x86_64/stable
Arch: x86_64
Branch: stable
Version: 44.0
License: GPL-3.0-or-later
Origin: flathub
Collection: org.flathub.Stable Installation: system Installed: 166.2 MB Runtime: org.gnome.Platform/x86_64/43 Sdk: org.gnome.Sdk/x86_64/43
Commit: b0c8464da96102fed09c62c9a2f14b0d85f7de329dce3599fb61e00d81c50eaf
Parent: 05ec1a904e821787b27795e9459b7d118ca6d53a2e0a7e378c38333395229cdd
Subject: Update to 44.0 (9f5f4664)
Date: 2022-11-26 01:41:39 +0000
`
Hmm, there was a new release not long ago (44.0, which you have). It didn't change anything that is likely to affect this.
But... I'm wondering if just the process of updating the flatpak is screwing us up. If you reboot / relogin to a fresh session, do things improve?
Hi,
Thanks for taking the time to reply.
A reboot and relogin produces the same result.
Here is what changed on my system 3/4 days ago through normal updates.
Start-Date: 2023-01-29 08:58:27 Commandline: packagekit role='update-packages' Requested-By: rick (1000) Upgrade: openjdk-11-jre:amd64 (11.0.16+8-1~deb11u1, 11.0.18+10-1~deb11u1), libcurl4:amd64 (7.74.0-1.3+deb11u3, 7.74.0-1.3+deb11u5), libcurl4:i386 (7.74.0-1.3+deb11u3, 7.74.0-1.3+deb11u5), openjdk-11-jre-headless:amd64 (11.0.16+8-1~deb11u1, 11.0.18+10-1~deb11u1), libcurl3-gnutls:amd64 (7.74.0-1.3+deb11u3, 7.74.0-1.3+deb11u5), libcurl3-gnutls:i386 (7.74.0-1.3+deb11u3, 7.74.0-1.3+deb11u5), curl:amd64 (7.74.0-1.3+deb11u3, 7.74.0-1.3+deb11u5) End-Date: 2023-01-29 08:58:38
Start-Date: 2023-01-30 07:53:15 Commandline: packagekit role='update-packages' Requested-By: work (1001) Upgrade: git:amd64 (1:2.30.2-1, 1:2.30.2-1+deb11u1), libtiff5:amd64 (4.2.0-1+deb11u1, 4.2.0-1+deb11u3), libtiff5:i386 (4.2.0-1+deb11u1, 4.2.0-1+deb11u3), libtiff-tools:amd64 (4.2.0-1+deb11u1, 4.2.0-1+deb11u3), git-man:amd64 (1:2.30.2-1, 1:2.30.2-1+deb11u1) End-Date: 2023-01-30 07:53:25
System = Debian 11.
I'm unable to select folders to include or exclude through file-picker:
+
either under "Folders to Back Up" or "Folders to Ignore" (behavior is the same)The issue is that the "Add" button is grey - disabled.
There is nothing related to this in default logs. When I start the app with more verbosity:
and then follow same steps as above, after 4th step I get bunch of warnings:
18031
is my UID.I have tried to override privileges:
then kill all running instances to make sure those permissions are applied and ran the app with verbose log. There was no change in behavior, issue persists.
As a side note, I'm able to remove entries from folders by clicking on
-
(minus) sign.I'm using Déjà Dup Backups in version 43.1: