today the update of deja-dup came in (35.6-0ubuntu1 -> 36.0-0ubuntu1) There is no directory /var/cache/samba which the application searches for.
creating it, does not help -> Backup failed Operation not supported by backend $ deja-dup (org.gnome.DejaDup:5945): Gtk-WARNING **: Allocating size to AssistantBackup 0x55b7940d0d70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? ** (org.gnome.DejaDup:5945): WARNING **: BackendRemote.vala:83: Could not find enclosing mount ** (org.gnome.DejaDup:5945): WARNING **: BackendRemote.vala:83: Could not find enclosing mount starting deja-dup with sudo rights -> Backup failed volume doesn’t implement mount on the console deja-dup complains that it cannot find /var/cache/smb: $ sudo deja-dup ** (org.gnome.DejaDup:5846): CRITICAL **: string_contains: assertion 'self != NULL' failed (org.gnome.DejaDup:5846): Gtk-WARNING **: Allocating size to AssistantBackup 0x5609b7db2070 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? gpg: WARNING: unsafe ownership on homedir '/home/wolf/.gnupg' ** (org.gnome.DejaDup:5846): WARNING **: BackendRemote.vala:83: Containing mount for file /var/cache/smb:/s4 not found mounting the backup volume -> Backup failed volume doesn’t implement mount $ sudo deja-dup ** (org.gnome.DejaDup:5987): CRITICAL **: string_contains: assertion 'self != NULL' failed (org.gnome.DejaDup:5987): Gtk-WARNING **: Allocating size to AssistantBackup 0x55f188b7f450 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? gpg: WARNING: unsafe ownership on homedir '/home/wolf/.gnupg' ** (org.gnome.DejaDup:5987): WARNING **: BackendRemote.vala:83: Containing mount for file /var/cache/smb:/s4 not found creating /var/cache/smb -> Backup failed volume doesn’t implement mount $ sudo mkdir smb wolf@mbpr13b:/var/cache$ sudo deja-dup ** (org.gnome.DejaDup:6045): CRITICAL **: string_contains: assertion 'self != NULL' failed (org.gnome.DejaDup:6045): Gtk-WARNING **: Allocating size to AssistantBackup 0x558b0333f3a0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? gpg: WARNING: unsafe ownership on homedir '/home/wolf/.gnupg' ** (org.gnome.DejaDup:6045): WARNING **: BackendRemote.vala:83: Containing mount for file /var/cache/smb:/s4 not found Even giving o+w does not help This can be tested on a plain 17.10 installation -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1715582 Title: deja-dup fails to backup Status in deja-dup package in Ubuntu: Fix Committed Bug description: OS: Ubuntu 17.10 beta setting up deja-dup to backup to smb/ssh server fails With ssh: Permission denied syslog: Sep 7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from uid 1000 finished with success after 414ms with smb: Backup failed InvalidBackendURL: missing // - relative paths not supported for scheme gio+invalid: gio+invalid:// syslog: Sep 7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from uid 1000 finished with success after 402ms ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: deja-dup 35.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 10:30:37 2017 InstallationDate: Installed on 2017-09-05 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1715582/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
