[Bug 1093611] Re: After the last update, the scheduling of déjà-dup is not working anymore

2017-10-10 Thread Vej
Closing as none of the mentioned releases is currently supported. Please open a new bug if you see this using a more recent version of Ubuntu. Thanks! ** Changed in: deja-dup (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu

[Bug 1093611] Re: After the last update, the scheduling of déjà-dup is not working anymore

2013-04-26 Thread Christopher Barrington-Leigh
Still, in the released 13.04, automatic/scheduled backup is not working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093611 Title: After the last update, the scheduling of déjà-dup is not

[Bug 1093611] Re: After the last update, the scheduling of déjà-dup is not working anymore

2013-04-09 Thread Christopher Barrington-Leigh
I have the same problem in the latest 13.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093611 Title: After the last update, the scheduling of déjà-dup is not working anymore To manage

[Bug 1093611] Re: After the last update, the scheduling of déjà-dup is not working anymore

2013-04-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: deja-dup (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093611 Title:

[Bug 1093611] Re: After the last update, the scheduling of déjà-dup is not working anymore

2012-12-30 Thread Nicola Jelmorini
Well, this morning I have made a reboot of my PC, and the backup was started automatically again as usual :-) Better so, but really I don't know if this has to do with other recent updates, or if this was only a temporary problem on my system. For me now this bug can be closed, unless other