This bug was fixed in the package deja-dup - 35.3-0ubuntu1
---
deja-dup (35.3-0ubuntu1) artful; urgency=medium
* New upstream release
- Fixes handling of some unicode filenames
- Fixes accuracy of checking whether some servers are reachable
(LP: #982316)
- Fix
** Changed in: deja-dup
Status: Fix Committed => Fix Released
--
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/982316
Title:
Deja Dup is unable to detect network connection
** Branch linked: lp:~ubuntu-desktop/deja-dup/ubuntu
--
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/982316
Title:
Deja Dup is unable to detect network connection
Status in Déjà
Should be fixed in master now. Thanks for the investigation and example
ssh config files!
https://git.launchpad.net/deja-
dup/commit/?id=76ea4c79e6e017a553b562d2258502e4fd34a452
** Changed in: deja-dup
Status: Confirmed => Fix Committed
--
You received this bug notification because you
** Changed in: deja-dup
Importance: Undecided => High
--
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/982316
Title:
Deja Dup is unable to detect network connection
Status in Déjà
** Changed in: deja-dup (Ubuntu)
Importance: Undecided => High
--
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/982316
Title:
Deja Dup is unable to detect network connection
** Tags added: xenial
** Tags added: trusty
--
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/982316
Title:
Deja Dup is unable to detect network connection
Status in Déjà Dup:
Noticed "/etc/NetworkManager/NetworkManager.conf" being set to
[ifupdown]
managed=false
Setting to "true" did not change anything. Network connections
independently show up as expected in Network manager.
--
You received this bug notification because you are a member of Desktop
Packages,
I'm on 16.04.1 LTS and had the following error after configuring the
settings in the System Settings Backup:
"Backup location not available
Waiting for a network connection..."
For me, the issue was with NetworkManager. After getting the above
error, I went to look at the Connection
I can confirm the Bug. I try to backup using SSHFS to a remote location.
SSH works fine, scp works fine, duplicity from command line works fine.
Deja-dup is not able to find the backup location:
"Backup location not available
Waiting for a network connection..."
This affects both the scheduled
I got this after upgrading to "mint 18 sarah" (ubuntu 16.04). Adding
Nas' IP and Hostname to "hosts" file did resolve for me.
May be this relates to events logged on windows members of the same
local network:
NetBT 4321: "The name "%2" could not be registered on the interface with
IP address %3.
Same problem. Ubuntu 14.04.2 LTS.
Backup on Netgear ReadyNAS Duo as Windows Share.
Manual backup worked OK but scheduled backup delayed
Adding line to /etc/hosts fixed it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in
Same problem here. Ubuntu 14.10. Backup on Samba share. Just added
samba host to /etc/hosts, we'll see what gives next week :)
$ uname -a
Linux DLAL0412-032 3.16.0-29-generic #39-Ubuntu SMP Mon Dec 15 22:27:29 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification
Same problem here. Ubuntu 14.10. Backup on samba share. Manual backup
works ok. Adding samba host to /etc/hosts fixed it for me.
--
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/982316
Same problem here. Ubuntu 14.04.1. DejaDup never starts automaticly. The backup
folder is on a harddisc at the router and perfektly reachable over smb://
Starting the DejaDup backup manualy works perfekt.
--
You received this bug notification because you are a member of Desktop
Packages, which
I have same problem, Ubuntu 14.04, NAS over SMB. Works fine if started
manually.
--
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/982316
Title:
Deja Dup is unable to detect network
I have the same problem on ubuntu 13.10
I currently change the ip of my nas server inside the .ssh/config file
on a regular basis (similar to the ProxyCommand) - I've found a
workaround based on the comments here, basically add the Host alias from
.ssh/config to /etc/hosts (even just pointing to
Same here (Ubuntu 12.04.2, all updates applied). Backup will begin when
a network connection becomes available. Manual backup works after
entering password for both SMB share and backup.
Here is my %gconf.xml:
?xml version=1.0?
gconf
entry name=path mtime=1371905937 type=string
Perhaps the scheduled backup failures have something to do with the
encryption? Just a thought as nobody mentioned it before.
I'm also affected by this bug. I use samba share with the backup
encryption enabled. Both samba and backup credentials are saved in the
Seahorse password storage so I
Had the same problem on 12.10. I back up to a Windows Share on the local
network. I tried opening the share via Nautilus, but it made no
difference, I still got the network connection error message. I tried
schaze 's workaround and that worked for me.
In /etc/hosts I added the destination
One possible half-solution is to first try to mount the location. If we
can do so without needing to prompt the user, we're good. Else fallback
to the current code. This will catch tricky cases of SSH redirection,
as long as the user has saved their SSH password.
If they haven't... I don't
The /etc/hosts or ~/.ssh/config workaround didn't work from me (I
primarily used mDNS/Bonjour name resolution). However, I found this
error report in ~/.xsession-errors:
** (deja-dup-monitor:2413): WARNING **: Network.vala:50: Error resolving
'': No address associated with hostname
I'm using
This is the culprit code from http://bazaar.launchpad.net/~deja-dup-
hackers/deja-dup/22/view/head:/common/Network.vala:
public async bool can_reach(string url)
{
var mon = NetworkMonitor.get_default();
try {
var socket = NetworkAddress.parse_uri(url, 0);
return yield
Have had this issue for a while and believe it started for me when updating to
12.10.
Have been mucking around a lot this morning and when making coffee it just
started to work again.
Not sure what is the root cause is yet but have done the following.
I started with the theory that the fact I
I have this error too.
I'm using Ubuntu One to save the files.
Is there a workaround for this case?
--
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/982316
Title:
Deja Dup is unable
I guess the easiest way to fix this would be to special-case SSH URIs and
just use the
ssh command to try to make a connection, and use that for the can_reach
method - this
will also take care of ProxyCommand and friends, and should be more to the
point.
Since there are also errors being
I'm experiencing the same problem, as storage I'm using a SSH server,
and my configuration is set up in ~/.ssh/config, so I've only set the
Server and Folder fields in the Backup app.
Tracing this back to the code (looking at the deja-dup_22.0-0ubuntu2
source) gives me common/BackendFile.vala:
Same thing for me, the workaround is working for me too !
That should give a clue to Michael ! ;-)
--
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/982316
Title:
Deja Dup is unable to
Hello,
I have the same probleme with a Samba server. Manual backups are working
fine, but not the automatic backup (same error message as in bug
description). I'm on Ubuntu 12.04 LTS.
$ deja-dup --version
deja-dup 22.0
Please find dejadup.gesettings attached.
** Attachment added:
Hi,
the workaround of schaze was the solution for me.
I added in my case 192.168.10.1 nas in /etc/hosts. Now my Deja Dup
works autmaticallly in Ubuntu 12.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
Hi,
I was having the same problem and I found a workaround.
I am doing backups via ssh to a server running in my network. As I am using a
special user on the server I added a host config in my .ssh/config file
specifying the username IdentityFile and more to ease up access to the backuped
sorry for delay but yes, I can access my nas through nautilus whereas
Deja dup is unable to access it.
--
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/982316
Title:
Deja Dup is
if I stop scheduled backup and then strt it I always get the same
message : Backup will begin when a network connection becomes
available.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
So I agree that this is a problem and that multiple people are affected.
But I don't know how to reproduce. :( Until I can, it's difficult for
me to make any progress on this.
** Changed in: deja-dup
Status: Incomplete = Confirmed
--
You received this bug notification because you are a
When you experience this, can you browse to the windows share in your
File Browser?
--
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/982316
Title:
Deja Dup is unable to detect network
yes I still have the problem. Note that I 've upgraded from 11.10. I
have no clue about what is giong on.
--
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/982316
Title:
Deja Dup is
I am having the exact same problem only I have not upgraded. Started
with 12.04 alpha 2. I did do a restore from an 11.10 backup.
--
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/982316
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: deja-dup (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
Her is the file :
thanks
** Attachment added: deja-dup.gsettings
https://bugs.launchpad.net/deja-dup/+bug/982316/+attachment/3083116/+files/deja-dup.gsettings
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
Hmm, I thought at first that this might be some goofiness with SMB, but
I just tested with an SMB server, and it seems like it works.
This is still a problem?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
40 matches
Mail list logo
