Comment 13 for bug 569261

It's been quite a while and I'm not sure if this bug is still being looked into? My previous comment still holds true, which doesn't look good for an LTS release like Isadora. Using a friendly GUI tool should never require any user to drop into the command-line to delete the resulting folder with sudo if they wish to move/delete what they just created.

I understand that the Backup Tool must be run with root permissions in order to lock the apt database, but can't this be done alternatively? An example is with Network Manager. You run it as a normal user, but if you wish to modify a global setting (or require root) it will prompt for the password.

Basically, using the Mint Backup Tool should look something like this:

1) User launches the Backup Tool
2) User makes a backup of their files/folders
3) On a later date, User launches Backup Tool
4) User restores from earlier backup
5) Done

Or

1) User launches the Backup Tool
2) User makes a backup of their software list
3) On a later date, User launches Backup Tool
4) User restores installed software
5) Done

That's the idea, right? How to smoothly handle root privileges without interfering with the workflow (e.g, requiring sudo to delete a folder) is up to the developer(s), not the *end-users*. I'm not trying to come off as condescending or rude. This is simply how it is. I can only tell you how I believe the Backup Tool should behave. The coding is up to the Mint *developers*.

The above 5 steps are simple and practical, as the Backup Tool was designed for. That is the goal trying to be achieved. The problem arises when the user has to drop into the terminal (or use an outside method) to work around a bug in the Backup Tool.

Can this bug be looked into? Version 2.0.6 on Isadora (LTS) still contains this bug. Thank you, Mint devs!