backintime-gnome crashes after initial setup

Bug #451754 reported by Peter Surňák
This bug report is a duplicate of:  Bug #409130: launching backintime fails to start. Edit Remove
8
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Back In Time
New
Undecided
Unassigned

Bug Description

Backintime version: 0.9.26
Gnome version:
Ubuntu 9.10 Karmic (beta)

How to reproduce:
1. Start backintime-gnome for the first time (or remove config).
2. System presents you with settings dialog (for backup). Keep default setting, change folder so it lets you save it. I also disabled original cron option.
Click OK.
3. The app crashes with this in console:

$ backintime-gnome
Back In Time
Version: 0.9.26

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime-gnome --license' for details.

Path: /home/petko/Plocha
SnapshotsPath2: /home/petko/
Snapshots path: /home/petko/Download
Automatic backup: Disabled
Traceback (most recent call last):
  File "/usr/share/backintime/gnome/app.py", line 1056, in <module>
    main_window = MainWindow( cfg, app_instance )
  File "/usr/share/backintime/gnome/app.py", line 281, in __init__
    self.update_all( True )
  File "/usr/share/backintime/gnome/app.py", line 388, in update_all
    self.update_folder_view( 1, selected_file, show_snapshots )
  File "/usr/share/backintime/gnome/app.py", line 1000, in update_folder_view
    new_iter = self.store_folder_view.append( [ item[0], rel_path, item[3], item[5], item[1], item[2], item[4] ] )
TypeError: value is of wrong type for this column

Notes:
I tried seveal combination of setting, always the same result.
If I try to run the app again (with config file in place), it will crash without even showing settings dialog. App window just flashes in and crashes immediately.

This is what I found in ".config/backintime/config":
config.version=2
snapshots.automatic_backup_mode=0
snapshots.cron.nice=false
snapshots.dont_remove_named_snapshots=true
snapshots.exclude_patterns=.*:*.backup*:*~
snapshots.expert.per_directory_schedule=false
snapshots.include_folders=/home/petko/Plocha|0
snapshots.min_free_space.enabled=true
snapshots.min_free_space.unit=20
snapshots.min_free_space.value=1
snapshots.notify.enabled=false
snapshots.path=/home/petko/Download
snapshots.remove_old_snapshots.enabled=true
snapshots.remove_old_snapshots.unit=80
snapshots.remove_old_snapshots.value=10
snapshots.smart_remove=false

Revision history for this message
Richard Bailey (rmjb) wrote :

Unfortunately this is a known bug in 0.9.26, the main bug has a fix that you can implement manually.

Revision history for this message
Peter Surňák (okolnost) wrote :

ok, thanks, that fix from the other bug does work for me fine

i would just suggest renaming that bug so it does not stand "as root" because that does not matter and in my case it was the reason i did not read that bug report before posting this one

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.