Deja Dup needs to wait for any network-up on login

Bug #397720 reported by Jeff
This bug report is a duplicate of:  Bug #306978: Don't network-backup if no network. Edit Remove
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Déjà Dup
Triaged
Medium
Unassigned

Bug Description

Ubuntu Jaunty 9.04, Gnome, Notebook, wifi - when logging in, Dup launches immediately before wifi can restore default connection (or any connection). Throws error about "smb:xxx not available". Should 1) check for any network up first, 2) wait 60+ sec before attempting to initialize backup.

/tmp/deja-dup.gconf...

<gconfentryfile>
  <entrylist base="/apps/deja-dup">
    <entry>
      <key>backend</key>
      <schema_key>/schemas/apps/deja-dup/backend</schema_key>
      <value>
        <string>file</string>
      </value>
    </entry>
    <entry>
      <key>encrypt</key>
      <schema_key>/schemas/apps/deja-dup/encrypt</schema_key>
      <value>
        <bool>true</bool>
      </value>
    </entry>
    <entry>
      <key>exclude-list</key>
      <schema_key>/schemas/apps/deja-dup/exclude-list</schema_key>
      <value>
        <list type="string">
            <value>
              <string>$TRASH</string>
            </value>
        </list>
      </value>
    </entry>
    <entry>
      <key>include-list</key>
      <schema_key>/schemas/apps/deja-dup/include-list</schema_key>
      <value>
        <list type="string">
            <value>
              <string>$HOME</string>
            </value>
        </list>
      </value>
    </entry>
    <entry>
      <key>last-run</key>
      <schema_key>/schemas/apps/deja-dup/last-run</schema_key>
    </entry>
    <entry>
      <key>periodic</key>
      <schema_key>/schemas/apps/deja-dup/periodic</schema_key>
      <value>
        <bool>true</bool>
      </value>
    </entry>
    <entry>
      <key>periodic-period</key>
      <schema_key>/schemas/apps/deja-dup/periodic-period</schema_key>
      <value>
        <int>7</int>
      </value>
    </entry>
    <entry>
      <key>file/path</key>
      <schema_key>/schemas/apps/deja-dup/file/path</schema_key>
      <value>
        <string>smb://iostorage-001/backup/</string>
      </value>
    </entry>
    <entry>
      <key>s3/bucket</key>
      <schema_key>/schemas/apps/deja-dup/s3/bucket</schema_key>
    </entry>
    <entry>
      <key>s3/folder</key>
      <schema_key>/schemas/apps/deja-dup/s3/folder</schema_key>
      <value>
        <string>/</string>
      </value>
    </entry>
    <entry>
      <key>s3/id</key>
      <schema_key>/schemas/apps/deja-dup/s3/id</schema_key>
    </entry>
    <entry>
      <key>ssh/directory</key>
      <value>
        <string>/Backup/conveyor/</string>
      </value>
    </entry>
    <entry>
      <key>ssh/server</key>
      <value>
        <string>192.168.1.7</string>
      </value>
    </entry>
    <entry>
      <key>ssh/username</key>
      <value>
        <string>sopolev</string>
      </value>
    </entry>
  </entrylist>
</gconfentryfile>

dpkg-query -W deja-dup duplicity...
deja-dup 10.1-0jaunty1
duplicity 0.6.00-0jaunty2

Related branches

Revision history for this message
Michael Terry (mterry) wrote :

Agreed. It should talk to NetworkManager and know not to do anything without a network connection (if the backup location is remote). Then it should wait until one is available.

Changed in deja-dup:
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Jeff (sopolev) wrote :

Thanks - appreciate the great work.

Revision history for this message
emilio (emiliomaggio) wrote :

Probably the easiest solution is to catch this error and simply retry in 10 minutes.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.