desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #129471
[Bug 1261435] Re: deja-dup-monitor fails backup to smb, while deja-dup itself succeeds (error resolving server name)
This version has expired
** Changed in: deja-dup (Ubuntu)
Status: New => Invalid
--
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/1261435
Title:
deja-dup-monitor fails backup to smb, while deja-dup itself succeeds
(error resolving server name)
Status in deja-dup package in Ubuntu:
Invalid
Bug description:
I have a backup location on a Samba share, which is reachable under an URL of the form
smb://MyGroup;myname@myservername/myname/deja-dup
Backing from the main Gui (using "Backup now") or using "deja-dup
--backup" from the commandline works without problems. However
automatic backups do not work. If I start deja-dup-monitor by hand, I
get the following error whenever it tries to perform a backup:
** (deja-dup-monitor:22068): WARNING **: Network.vala:48: Error
resolving 'myservername': Name or service not known
This seems to happen in the function can_reach, which itself seems to
call the GTK network library. I already checked whether the function
is called with the correct url by inserting a bit of debug code into
the can_reach function, and it does indeed use the correct url. So the
error IMHO seems to be on the network library side.
Ubuntu Release:
Ubuntu 13.10
Deja-dup Package:
27.3.1-0ubuntu1 0
Additional Information:
I use the KDE Desktop environment (4.11.2) and the passwords are to my knowledge all saved in the KDE Keyring (KDE Wallet Manager).
What I expect to happen:
I expect the automatic backup to an smb share to work
What happened instead:
Automatic Backups are not performed and I always have to initiate the backup by hand.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1261435/+subscriptions