Path: ...!weretis.net!feeder9.news.weretis.net!news.quux.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: The Natural Philosopher <tnp@invalid.invalid>
Newsgroups: comp.os.linux.misc
Subject: Re: Odd behaviour?
Date: Thu, 5 Dec 2024 18:02:26 +0000
Organization: A little, after lunch
Lines: 54
Message-ID: <vispri$1olu2$3@dont-email.me>
References: <vinptp$b4ht$1@dont-email.me> <bn942lxcti.ln2@Telcontar.valinor>
 <vinvtv$ci03$1@dont-email.me> <lr9ep2F6hc8U1@mid.individual.net>
 <viphkr$rnso$9@dont-email.me> <viq7p0$11lmp$1@dont-email.me>
 <virmhp$1fqan$5@dont-email.me> <v6c82lxib.ln2@Telcontar.valinor>
 <vis1f1$1iiku$2@dont-email.me> <vqe82lxjg7.ln2@Telcontar.valinor>
 <vis65i$1jn2s$1@dont-email.me> <pkj82lxaro.ln2@Telcontar.valinor>
 <wwvmshaxe33.fsf@LkoBDZeT.terraraq.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 05 Dec 2024 19:02:27 +0100 (CET)
Injection-Info: dont-email.me; posting-host="0b294da1aa85fdc66c387388c1472a0b";
	logging-data="1857474"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+MT5PxdZVWE3vkpPWCV20ZjJIJ8g9s8hg="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:rQbywI5y2V27+pDZ1gwkqkXeCH4=
In-Reply-To: <wwvmshaxe33.fsf@LkoBDZeT.terraraq.uk>
Content-Language: en-GB
Bytes: 3383

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