Yes you are right. The problem is dcron. This cron daemon doesn't behave like the old normal crond. What is really annoying. :-/ I created a bug report for dcron and attached a patch for his miss behaviour.
By the way dcron is the reason why back in time switched from @hourly to 0 * * * *. The later version kills the anacron like features of some cron daemons for example dcron 4.4. -- UnboundLocalError: local variable 'first_error' referenced before assignment https://bugs.launchpad.net/bugs/520956 You received this bug notification because you are a member of Back In Time Team, which is subscribed to Back In Time. Status in Back In Time: Fix Committed Bug description: My cronjob throws this exception: Traceback (most recent call last): File "/usr/share/backintime/kde4/kde4systrayicon.py", line 126, in update_info if first_error: UnboundLocalError: local variable 'first_error' referenced before assignment The kde4 tray Icon give me this message: Can't find snapshots folder. If it is on a removable drive please plug it. Waiting 30 seconds. If updated from 0.9.26 because of some kde4 related problems to bzr 668 but still no luck with backups started by cron. Manual backups just working. _______________________________________________ Mailing list: https://launchpad.net/~bit-team Post to : bit-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~bit-team More help : https://help.launchpad.net/ListHelp
