Bug 750470 - backup does not start
Summary: backup does not start
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: deja-dup
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rahul Sundaram
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-01 09:06 UTC by Matthias Runge
Modified: 2012-01-04 19:39 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-04 19:39:15 UTC
Type: ---


Attachments (Terms of Use)
screenshot (12.35 KB, image/png)
2011-11-01 09:06 UTC, Matthias Runge
no flags Details

Description Matthias Runge 2011-11-01 09:06:47 UTC
Created attachment 531085 [details]
screenshot

Description of problem:

deja-dup --backup

(deja-dup:5145): libnotify-WARNING **: Failed to connect to proxy

---------

deja-dup opens a window asking for a password to connect to the server
----------
(deja-dup:5145): Gtk-WARNING **: Attempting to add a widget with type GtkBox to a GtkEventBox, but as a GtkBin subclass a GtkEventBox can only contain one widget at a time; it already contains a widget of type GtkBox
----------

deja-dup shows an (nearly) empty window (appended as screenshot). Is this reason for the error or just a side-effect?

Version-Release number of selected component (if applicable):
deja-dup-20.1-1.fc16.x86_64
same with deja-dup-19.4-1.fc16.x86_64

How reproducible:
every time

Steps to Reproduce:
1. follow the steps above
2. 
3.
  
Actual results:
backup does not start


I'm doing a backup over the net on a samba file server. I'm pretty sure, this worked 10-14 days ago without any problem.

Comment 1 Rahul Sundaram 2011-11-13 20:05:19 UTC
Please attach output of

rpm -q deja-dup duplicity

gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings

DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-dup.log

Comment 2 Matthias Runge 2011-11-14 08:26:41 UTC
Ok, looks like this is a subsequent fault of not being able to write on storage.

Problem still exists, and the error message (shown in attachment https://bugzilla.redhat.com/attachment.cgi?id=531085 ) is not helpfull.

I was able to start a backup to another location. So, question is, how to enhance the error message.

Comment 3 Matthias Runge 2012-01-04 19:39:15 UTC
I'm closing this,  the issue disappeared. Thanks anyway!


Note You need to log in before you can comment on or make changes to this bug.