Re: Odd behaviour?

On 05/12/2024 16:57, Richard Kettlewell wrote:

"Carlos E.R." <robin_listas@es.invalid> writes:

The GUI filemanager is just a filemanager, and follows filemanager
rules. It displays only ONE directory, not some desktop concoction
made of several structures and directories.

 Union filesystems are a thing, thought I don’t know of any reason to
think one is involved here, and I’d (possibly naively) expected unlink
calls to propagate through them to the appropriate underlying
filesystem.
 I don’t have a definitive explanation for the behavior seen. Some
guesswork:
 * If a file is sometimes visible and sometimes not that may reflect it
   being repeatedly deleted and re-created.
 

No. It was solid at all times and absent at all times from the respective voews

* If a file is visible in one view and not another than may reflect the
   views actually being different. e.g. user error about what directory
   they are looking at.
 

I hardly think ~/Desktop is confusing
All the other files on the desktop were in there

* Filesystem corruption of some kind might explain any kind of weird
   behavior, though (at least when running ls) you might expect some kind
   of error message. The kernel log would be likely to contain
   diagnostics in this case.
 

I might have a look

* A file that’s something to do with an attack may be deliberately
   hidden by the attack software, but perhaps in an inconsistent way
   (attackers screw up too).
 

According to a brief Google that is a Windows temporary file.  It may be something to do with the windows VM deleting it but the desktop retaining memory of it. Bit if it is, it's in a weird place.
--
Socialism is the philosophy of failure, the creed of ignorance and the gospel of envy.
Its inherent virtue is the equal sharing of misery.
Winston Churchill