Last 7 days

• Dec 10, 2009

  issue 77 (flyback does not run on Debian Lenny) reported by nomo17k   -   I installed flyback_0.6.1_r111-1_all.deb on Debian Lenny. Unfortunately I cannot get it to run at all. When running it with python flyback.py, I get the following error: (flyback.py:5646): libglade-WARNING **: unknown property `orientation' for class `GtkVBox' (flyback.py:5646): libglade-WARNING **: unknown property `orientation' for class `GtkVBox' Traceback (most recent call last): File "flyback.py", line 72, in <module> launch_select_backup_gui() File "flyback.py", line 43, in launch_select_backup_gui register_gui( select_backup_gui.GUI(register_gui, unregister_gui) ) File "/usr/local/src/flyback/flyback-read-only/src/select_backup_gui.py", line 138, in __init__ util.register_device_added_removed_callback(self.refresh_device_list) File "/usr/local/src/flyback/flyback-read-only/src/util.py", line 75, in register_device_added_removed_callback if not device_monitor_thread.is_alive(): AttributeError: 'DeviceMonitorThread' object has no attribute 'is_alive'

  I installed flyback_0.6.1_r111-1_all.deb on Debian Lenny. Unfortunately I cannot get it to run at all. When running it with python flyback.py, I get the following error: (flyback.py:5646): libglade-WARNING **: unknown property `orientation' for class `GtkVBox' (flyback.py:5646): libglade-WARNING **: unknown property `orientation' for class `GtkVBox' Traceback (most recent call last): File "flyback.py", line 72, in <module> launch_select_backup_gui() File "flyback.py", line 43, in launch_select_backup_gui register_gui( select_backup_gui.GUI(register_gui, unregister_gui) ) File "/usr/local/src/flyback/flyback-read-only/src/select_backup_gui.py", line 138, in __init__ util.register_device_added_removed_callback(self.refresh_device_list) File "/usr/local/src/flyback/flyback-read-only/src/util.py", line 75, in register_device_added_removed_callback if not device_monitor_thread.is_alive(): AttributeError: 'DeviceMonitorThread' object has no attribute 'is_alive'

Last 30 days

• Dec 04, 2009

  FAQ Wiki page commented on by radek.blecha   -   I run $ python flyback.py and got following: {{{ $ python flyback.py /usr/share/flyback (flyback.py:21959): libglade-WARNING **: unknown property `orientation' for class `GtkVBox' (flyback.py:21959): libglade-WARNING **: unknown property `orientation' for class `GtkVBox' Traceback (most recent call last): File "flyback.py", line 39, in <module> launch_select_backup_gui() File "flyback.py", line 23, in launch_select_backup_gui register_gui( select_backup_gui.GUI(register_gui, unregister_gui) ) File "/usr/share/flyback/select_backup_gui.py", line 138, in __init__ util.register_device_added_removed_callback(self.refresh_device_list) File "/usr/share/flyback/util.py", line 62, in register_device_added_removed_callback if not device_monitor_thread.is_alive(): AttributeError: 'DeviceMonitorThread' object has no attribute 'is_alive' }}}

  I run $ python flyback.py and got following: {{{ $ python flyback.py /usr/share/flyback (flyback.py:21959): libglade-WARNING **: unknown property `orientation' for class `GtkVBox' (flyback.py:21959): libglade-WARNING **: unknown property `orientation' for class `GtkVBox' Traceback (most recent call last): File "flyback.py", line 39, in <module> launch_select_backup_gui() File "flyback.py", line 23, in launch_select_backup_gui register_gui( select_backup_gui.GUI(register_gui, unregister_gui) ) File "/usr/share/flyback/select_backup_gui.py", line 138, in __init__ util.register_device_added_removed_callback(self.refresh_device_list) File "/usr/share/flyback/util.py", line 62, in register_device_added_removed_callback if not device_monitor_thread.is_alive(): AttributeError: 'DeviceMonitorThread' object has no attribute 'is_alive' }}}

Earlier this year

• Nov 13, 2009

  HowToUse (How to use FlyBack) Wiki page commented on by francis.fish   -   I've given up with this because it won't recognise an external HDD. I used to get round this by specifying a directory that would be mounted if the HDD was plugged in and some clever boot stuff in crontab that would mount if it was there, the new restricted interface doesn't allow this and doesn't see the external HDD. This also involved hacking the crontab command so that it wouldn't run flyback if the disk wasn't mounted, but it worked. I think I need to track down the old rsync command, which is sad, because the interface here is 10x better.

  I've given up with this because it won't recognise an external HDD. I used to get round this by specifying a directory that would be mounted if the HDD was plugged in and some clever boot stuff in crontab that would mount if it was there, the new restricted interface doesn't allow this and doesn't see the external HDD. This also involved hacking the crontab command so that it wouldn't run flyback if the disk wasn't mounted, but it worked. I think I need to track down the old rsync command, which is sad, because the interface here is 10x better.
• Nov 07, 2009

  issue 76 (Adding support for nfs mounts) reported by marinalink   -   What steps will reproduce the problem? 1. start "Flyback Backup Manager" from applications menu 2. follow instructions to create new backup 3. Mount point of NFS drive can not be selected in the list of "device you want to backup to". What is the expected output? What do you see instead? Expected is to see the NFS mount point in the list "device you want to backup to". There is not a way to select the NFS mount point as a target for the backup. What version of the product are you using? On what operating system? flyback_0.6.1_r111-1_all.deb, Ubuntu 9.04 Please provide any additional information below. My NFS mount (a NAS, DNS-323 from Dlink) is mapped in such a way: 192.168.3.101:/mnt/HD_a2/ on /media/nas_data type nfs (rw,addr=192.168.3.101) Previous version of fly-back (0.4.1) had no issues using this directory/mount point.

  What steps will reproduce the problem? 1. start "Flyback Backup Manager" from applications menu 2. follow instructions to create new backup 3. Mount point of NFS drive can not be selected in the list of "device you want to backup to". What is the expected output? What do you see instead? Expected is to see the NFS mount point in the list "device you want to backup to". There is not a way to select the NFS mount point as a target for the backup. What version of the product are you using? On what operating system? flyback_0.6.1_r111-1_all.deb, Ubuntu 9.04 Please provide any additional information below. My NFS mount (a NAS, DNS-323 from Dlink) is mapped in such a way: 192.168.3.101:/mnt/HD_a2/ on /media/nas_data type nfs (rw,addr=192.168.3.101) Previous version of fly-back (0.4.1) had no issues using this directory/mount point.
• Nov 05, 2009

  issue 75 (Name with space on partition (on external USB storage)) reported by lucmult   -   What steps will reproduce the problem? 1. On external storage, with a name with space, like "backup mac" 2. Start the flyback 3. What is the expected output? What do you see instead? I expact that it works, but it fails emiting a traceback. What version of the product are you using? On what operating system? I'm on Ubuntu 9.04 and flyback flyback_0.6.1_r111-1_all.deb. Please provide any additional information below. Now, you read the mount point with "mount" utility, I changed to use /etc/mtab. Se patch attached

  What steps will reproduce the problem? 1. On external storage, with a name with space, like "backup mac" 2. Start the flyback 3. What is the expected output? What do you see instead? I expact that it works, but it fails emiting a traceback. What version of the product are you using? On what operating system? I'm on Ubuntu 9.04 and flyback flyback_0.6.1_r111-1_all.deb. Please provide any additional information below. Now, you read the mount point with "mount" utility, I changed to use /etc/mtab. Se patch attached
• Oct 30, 2009

  issue 74 (add support for NAS-type storages) Status changed by pub...@kered.org   -   good to hear! is the performance ok?

  Status: Fixed

  good to hear! is the performance ok?

  Status: Fixed
• Oct 30, 2009

  issue 74 (add support for NAS-type storages) commented on by m...@oclab.net   -   It works with gvfs-mounted smb shares! Thanks for the fast support! :-)

  It works with gvfs-mounted smb shares! Thanks for the fast support! :-)
• Oct 29, 2009

  issue 74 (add support for NAS-type storages) commented on by pub...@kered.org   -   glad you like. :) can you attach the command-line output the program writes when you try to create a backup on the sftp share? 1) click applications -> accessories -> terminal 2) type "/usr/share/flyback/flyback.py" into the window and press return

  glad you like. :) can you attach the command-line output the program writes when you try to create a backup on the sftp share? 1) click applications -> accessories -> terminal 2) type "/usr/share/flyback/flyback.py" into the window and press return
• Oct 29, 2009

  r114 (added running time info to the running tasks list) committed by pub...@kered.org   -   added running time info to the running tasks list

  added running time info to the running tasks list
• Oct 29, 2009

  issue 74 (add support for NAS-type storages) commented on by m...@oclab.net   -   Wow, that was fast! :-) I just did a quick try via gvfs-mount of an sftp account, but that wasn't offered as a target. Currently I can't try smb, I'll do that later (tomorrow?) ... Btw. I now get a different (more informative) screen when trying to create a new backup (see screenshot). Nice improvement!

  Wow, that was fast! :-) I just did a quick try via gvfs-mount of an sftp account, but that wasn't offered as a target. Currently I can't try smb, I'll do that later (tomorrow?) ... Btw. I now get a different (more informative) screen when trying to create a new backup (see screenshot). Nice improvement!
• Oct 29, 2009

  r113 (added command line support) committed by pub...@kered.org   -   added command line support

  added command line support
• Oct 29, 2009

  r112 (humanized unknown free space reporting) committed by pub...@kered.org   -   humanized unknown free space reporting

  humanized unknown free space reporting
• Oct 29, 2009

  issue 74 (add support for NAS-type storages) changed by pub...@kered.org   -   note you have to mount your smb share via gnome before flyback will detect it.

  Summary: add support for NAS-type storages

  Labels: Type-Enhancement

  note you have to mount your smb share via gnome before flyback will detect it.

  Summary: add support for NAS-type storages

  Labels: Type-Enhancement
• Oct 29, 2009

  issue 74 (unable to create new backup with "Flyback Backup Manager") Status changed by pub...@kered.org   -   i added gvfs support, which supports smb. can't say it's well-tested tho. =P let me know how it works... http://flyback.googlecode.com/files/flyback_0.6.1_r111-1_all.deb

  Status: Accepted

  i added gvfs support, which supports smb. can't say it's well-tested tho. =P let me know how it works... http://flyback.googlecode.com/files/flyback_0.6.1_r111-1_all.deb

  Status: Accepted
• Oct 29, 2009

  flyback_0.6.1_r111-1_all.deb (Flyback v0.6.1) file uploaded by pub...@kered.org   -  

  Labels: Featured Type-Package OpSys-Linux

  Labels: Featured Type-Package OpSys-Linux
• Oct 29, 2009

  r111 (implemented gvfs support) committed by pub...@kered.org   -   implemented gvfs support

  implemented gvfs support
• Oct 29, 2009

  issue 74 (unable to create new backup with "Flyback Backup Manager") commented on by pub...@kered.org   -   well, i was using rsync over ssh. that could have been part of it. but there were other issues w/ rsync as well. i never could get it to reliably create the hard-links back to previous versions of the files.

  well, i was using rsync over ssh. that could have been part of it. but there were other issues w/ rsync as well. i never could get it to reliably create the hard-links back to previous versions of the files.
• Oct 29, 2009

  issue 74 (unable to create new backup with "Flyback Backup Manager") commented on by m...@oclab.net   -   I'm a bit surprised by that. I'm currently using rsync to sync my Data (~80GB) to the NAS. I found it being incredibly fast compared to all other solutions I tried before: Scanning for files that changed takes about some seconds. Since only few files change in daily use I put my priority on finding something with fast scanning and did not benchmark the transfer throughput (though rsync should (!) be pretty efficient with that). Did you think of the scanning or the transferring of files when addressing the slow performance?

  I'm a bit surprised by that. I'm currently using rsync to sync my Data (~80GB) to the NAS. I found it being incredibly fast compared to all other solutions I tried before: Scanning for files that changed takes about some seconds. Since only few files change in daily use I put my priority on finding something with fast scanning and did not benchmark the transfer throughput (though rsync should (!) be pretty efficient with that). Did you think of the scanning or the transferring of files when addressing the slow performance?
• Oct 28, 2009

  flyback_0.6.1_r110-1_all.deb (Flyback v0.6.1) file uploaded by pub...@kered.org   -  

  Labels: Featured Type-Package OpSys-Linux

  Labels: Featured Type-Package OpSys-Linux
• Oct 28, 2009

  r110 (dep error) committed by pub...@kered.org   -   dep error

  dep error
• Oct 28, 2009

  flyback_0.6.1_r109-1_all.deb (Flyback v0.6.1) file uploaded by pub...@kered.org   -  

  Labels: Featured Type-Package OpSys-Linux

  Labels: Featured Type-Package OpSys-Linux
• Oct 28, 2009

  r109 (updated revision ) committed by pub...@kered.org   -   updated revision

  updated revision
• Oct 28, 2009

  r108 (implemented the delete button) committed by pub...@kered.org   -   implemented the delete button

  implemented the delete button
• Oct 28, 2009

  flyback_0.6.0_r107-1_all.deb (Flyback v0.6.0) file uploaded by pub...@kered.org   -  

  Labels: Featured Type-Package OpSys-Linux

  Labels: Featured Type-Package OpSys-Linux
• Oct 28, 2009

  r107 (added "please add drive" message) committed by pub...@kered.org   -   added "please add drive" message

  added "please add drive" message
• Oct 28, 2009

  r106 (changed max pack size) committed by pub...@kered.org   -   changed max pack size

  changed max pack size
• Oct 28, 2009

  issue 74 (unable to create new backup with "Flyback Backup Manager") commented on by pub...@kered.org   -   there was rsync support originally, but it was so god-awful slow as to be almost unusable. i would consider adding smb tho. let me try to see if i can get repo auto-detecting working for it.

  there was rsync support originally, but it was so god-awful slow as to be almost unusable. i would consider adding smb tho. let me try to see if i can get repo auto-detecting working for it.
• Oct 28, 2009

  issue 74 (unable to create new backup with "Flyback Backup Manager") commented on by m...@oclab.net   -   No, no UUID. It's a netgear readynas duo offering smb, ftp, webdav and rsync. Seems I misunderstood the comment to issue #73 ... :-( After a long time of searching I thought flyback was the solution for my backup needs. Is there any chance that any of the above network protocols will be supported?

  No, no UUID. It's a netgear readynas duo offering smb, ftp, webdav and rsync. Seems I misunderstood the comment to issue #73 ... :-( After a long time of searching I thought flyback was the solution for my backup needs. Is there any chance that any of the above network protocols will be supported?
• Oct 28, 2009

  issue 74 (unable to create new backup with "Flyback Backup Manager") commented on by pub...@kered.org   -   issue #73 was related to the previous incarnation. there is no support yet for NAS. when you mount your NAS, does the OS give it a UUID?

  issue #73 was related to the previous incarnation. there is no support yet for NAS. when you mount your NAS, does the OS give it a UUID?
• Oct 28, 2009

  issue 74 (unable to create new backup with "Flyback Backup Manager") reported by m...@oclab.net   -   What steps will reproduce the problem? 1. start "Flyback Backup Manager" from applications menu 2. follow instructions to create new backup (see screenshots) 3. When pressing "new" an error ocurrs "No Drive Selected" "You must select a drive from the list...", but there is no list to select from. What is the expected output? What do you see instead? There is no way to select a target. What version of the product are you using? On what operating system? Using "flyback_0.6.0_r104-1_all.deb" on Ubuntu jaunty with german language settings. Please provide any additional information below. Since I assume this is a GUI-issue I'll attach some screenshots ... I have no external drive directly attached to the system, but would like to use rsync to my NAS box on the LAN, which should be possible as of the last comment on Issue 73 , right?

  What steps will reproduce the problem? 1. start "Flyback Backup Manager" from applications menu 2. follow instructions to create new backup (see screenshots) 3. When pressing "new" an error ocurrs "No Drive Selected" "You must select a drive from the list...", but there is no list to select from. What is the expected output? What do you see instead? There is no way to select a target. What version of the product are you using? On what operating system? Using "flyback_0.6.0_r104-1_all.deb" on Ubuntu jaunty with german language settings. Please provide any additional information below. Since I assume this is a GUI-issue I'll attach some screenshots ... I have no external drive directly attached to the system, but would like to use rsync to my NAS box on the LAN, which should be possible as of the last comment on Issue 73 , right?
• Oct 28, 2009

  r105 (changed screenshots ) committed by pub...@kered.org   -   changed screenshots

  changed screenshots
• Oct 28, 2009

  flyback_0.6.0_r104-1_all.deb (Flyback v0.6.0) file uploaded by pub...@kered.org   -  

  Labels: Featured Type-Package OpSys-Linux

  Labels: Featured Type-Package OpSys-Linux
• Oct 28, 2009

  r104 (made deb versioning automatically match python version ) committed by pub...@kered.org   -   made deb versioning automatically match python version

  made deb versioning automatically match python version
• Oct 28, 2009

  r103 (ui improvements updated version ) committed by pub...@kered.org   -   ui improvements updated version

  ui improvements updated version
• Oct 28, 2009

  r102 (appended "_flyback" to all tmp dirs created) committed by pub...@kered.org   -   appended "_flyback" to all tmp dirs created

  appended "_flyback" to all tmp dirs created
• Oct 28, 2009

  r101 (misc. minor improvements) committed by pub...@kered.org   -   misc. minor improvements

  misc. minor improvements
• Oct 28, 2009

  r100 (added repack after backup to speed up operations on really l...) committed by pub...@kered.org   -   added repack after backup to speed up operations on really large repos

  added repack after backup to speed up operations on really large repos
• Oct 28, 2009

  r99 (added dbus support to refresh drive lists when any are added...) committed by pub...@kered.org   -   added dbus support to refresh drive lists when any are added/removed

  added dbus support to refresh drive lists when any are added/removed
• Oct 27, 2009

  r98 (minor ui changes added "max file size" pref (non-functional ...) committed by pub...@kered.org   -   minor ui changes added "max file size" pref (non-functional as of yet)

  minor ui changes added "max file size" pref (non-functional as of yet)
• Oct 27, 2009

  r97 (added status view ) committed by pub...@kered.org   -   added status view

  added status view
• Oct 27, 2009

  r96 (some performance improvements for large repos ) committed by pub...@kered.org   -   some performance improvements for large repos

  some performance improvements for large repos
• Oct 27, 2009

  issue 35 (phyton.pl issued by crontab does not remove lockfile) Status changed by pub...@kered.org   -   resolved in v0.5

  Status: Fixed

  resolved in v0.5

  Status: Fixed
• Oct 27, 2009

  issue 36 (Lockfile.txt reappears) Status changed by pub...@kered.org   -   resolved in v0.5

  Status: Fixed

  resolved in v0.5

  Status: Fixed
• Oct 27, 2009

  issue 37 (Backup not linking to previous fiels) Status changed by pub...@kered.org   -   resolved in v0.5

  Status: Fixed

  resolved in v0.5

  Status: Fixed
• Oct 27, 2009

  issue 41 (Resolve filelock creation problem) Status changed by pub...@kered.org   -   resolved in v0.5

  Status: Fixed

  resolved in v0.5

  Status: Fixed
• Oct 27, 2009

  issue 43 (how to specify an existing config file) Status changed by pub...@kered.org   -   resolved in v0.5

  Status: Fixed

  resolved in v0.5

  Status: Fixed
• Oct 27, 2009

  issue 44 (Flyback does not archive visible directories) Status changed by pub...@kered.org   -   resolved in v0.5

  Status: Fixed

  resolved in v0.5

  Status: Fixed
• Oct 27, 2009

  issue 45 (Backup doesn't finish cleanly when copying files it has no p...) Status changed by pub...@kered.org   -   resolved in v0.5

  Status: Fixed

  resolved in v0.5

  Status: Fixed
• Oct 27, 2009

  issue 46 (Flyback will only run as root) Status changed by pub...@kered.org   -   resolved in v0.5

  Status: Fixed

  resolved in v0.5

  Status: Fixed
• Oct 27, 2009

  issue 48 (resulting Backup contains folders w/o filess) Status changed by pub...@kered.org   -   resolved in v0.5

  Status: Fixed

  resolved in v0.5

  Status: Fixed