On 05/08/2018 09:39 PM, The Wanderer wrote:
On 2018-05-08 at 13:48, Richard Owlett wrote:
[massive SNIP]
What method are you using to delete it?
Moving directory to trash and then emptying the trash with MATE's
graphical tools.
If you haven't already, I'd recommend trying 'rm -r', *very* carefully,
from a command prompt. (Unless you have an extremely unusual setup, that
should avoid any possibility of an intermediary "Trash" to need emptying.)
Do you have mlocate installed on your system? If so, the output of
locate 'grub2 problem-2018-02-13'
It starts off with:
/home/richard/.local/share/Trash/expunged/1449727740/grub2 problem-2018-02-13
/home/richard/.local/share/Trash/expunged/1449727740/grub2
problem-2018-02-13/grub2 problem-2018-02-13
/home/richard/.local/share/Trash/expunged/1449727740/grub2
problem-2018-02-13/grub2 problem-2018-02-13/grub2 problem-2018-02-13
/home/richard/.local/share/Trash/expunged/1449727740/grub2
problem-2018-02-13/grub2 problem-2018-02-13/grub2 problem-2018-02-13/grub2
problem-2018-02-13
and goes on for >100 kB.
Running
/home/richard# tree -adRA -L 8
/home/richard/.local/share/Trash/expunged/1449727740/
gives:>
/home/richard/.local/share/Trash/expunged/1449727740/
└── grub2 problem-2018-02-13
└── grub2 problem-2018-02-13
└── grub2 problem-2018-02-13
└── grub2 problem-2018-02-13
└── grub2 problem-2018-02-13
└── grub2 problem-2018-02-13
└── grub2 problem-2018-02-13
└── grub2 problem-2018-02-13
Goes on for 161 directories
might be informative; if it finds a copy of the directory somewhere
else, that might tell us where it's being restored from, if it is indeed
being restored.
I'll try this afternoon or tomorrow. I'll read documentation for "rm"
first and use it to purge what I know I'm not interested in. Then re-run
"locate". I'll wait until I know that I don't have to preserve the
machine' current state.
Thanks
