Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 42 |
Nodes: | 6 (0 / 6) |
Uptime: | 02:00:25 |
Calls: | 220 |
Calls today: | 1 |
Files: | 824 |
Messages: | 121,544 |
Posted today: | 6 |
Linux Mint MATE here.
On my desktop is a file named TMPEEB.tmp
It shows up in the file browser as well
It doesn't show up in the console using ls.
If I try and delete it it says it doesn't exist.
Before I reboot the desktop does any one know whats going on?
On 2024-12-03 21:32, The Natural Philosopher wrote:
Linux Mint MATE here.
On my desktop is a file named TMPEEB.tmp
It shows up in the file browser as well
https://vms.drweb.com/virus/?i=24143207
But it attacks Windows, not Linux.
It doesn't show up in the console using ls.
If I try and delete it it says it doesn't exist.
Before I reboot the desktop does any one know whats going on?
What I find puzzling is how it appears in the GUI but isn't on the
actual machine file system
The Natural Philosopher wrote:
What I find puzzling is how it appears in the GUI but isn't on the
actual machine file system
funky characters in filename?
ls -la | cat -v
On 2024-12-03 21:32, The Natural Philosopher wrote:
Linux Mint MATE here.
On my desktop is a file named TMPEEB.tmp
It shows up in the file browser as well
https://vms.drweb.com/virus/?i=24143207
But it attacks Windows, not Linux.
It doesn't show up in the console using ls.
If I try and delete it it says it doesn't exist.
Before I reboot the desktop does any one know whats going on?
On Tue, 3 Dec 2024, Carlos E.R. wrote:
On 2024-12-03 21:32, The Natural Philosopher wrote:
Linux Mint MATE here.
On my desktop is a file named TMPEEB.tmp
It shows up in the file browser as well
https://vms.drweb.com/virus/?i=24143207
But it attacks Windows, not Linux.
So it exploits chrome?
The Natural Philosopher wrote:
What I find puzzling is how it appears in the GUI but isn't on the
actual machine file system
funky characters in filename?
ls -la | cat -v
ls --color=no
On 2024-12-04 10:29, D wrote:
On Tue, 3 Dec 2024, Carlos E.R. wrote:
On 2024-12-03 21:32, The Natural Philosopher wrote:
Linux Mint MATE here.
On my desktop is a file named TMPEEB.tmp
It shows up in the file browser as well
https://vms.drweb.com/virus/?i=24143207
But it attacks Windows, not Linux.
So it exploits chrome?
Chrome is not windows.
On 03/12/2024 22:24, Andy Burns wrote:
The Natural Philosopher wrote:
What I find puzzling is how it appears in the GUI but isn't on the
actual machine file system
funky characters in filename?
ls -la | cat -v
Nope. Still no sign
I think some part of the GUI environment builds a cache, and its in
that, but not in the real world so to speak
On 03/12/2024 22:24, Andy Burns wrote:
The Natural Philosopher wrote:
What I find puzzling is how it appears in the GUI but isn't on the
actual machine file system
funky characters in filename?
ls -la | cat -v
Nope. Still no sign
I think some part of the GUI environment builds a cache, and its in
that, but not in the real world so to speak
The Natural Philosopher <tnp@invalid.invalid> wrote:
On 03/12/2024 22:24, Andy Burns wrote:
The Natural Philosopher wrote:
What I find puzzling is how it appears in the GUI but isn't on the
actual machine file system
funky characters in filename?
ls -la | cat -v
Nope. Still no sign
I think some part of the GUI environment builds a cache, and its in
that, but not in the real world so to speak
What is the GUI file browser program you use under Mate?
Many "GUI file browsers" have a tendancy to "combine" plural actual
disk paths into the 'appearance' of a singular view (and "Desktop" is
one of those 'views' that GUI dev's think need this miss-feature).
So it is possible the file it is located somewhere other than
~/Desktop/ and the GUI is merging together that other location with the contents of the actual ~/Desktop/, and presenting the combination to
you as "Desktop".
Which would explain why it does not appear when you actually view
~/Desktop/ with ls from a terminal.
On 12/4/24 12:23, The Natural Philosopher wrote:
On 03/12/2024 22:24, Andy Burns wrote:
The Natural Philosopher wrote:
What I find puzzling is how it appears in the GUI but isn't on the
actual machine file system
funky characters in filename?
ls -la | cat -v
Nope. Still no sign
I think some part of the GUI environment builds a cache, and its in
that, but not in the real world so to speak
Yes, that it what I think I have seen in Gnome Desktop and the Gnome
Files App (file explorer) vs bash ls. I think I have seen behaviour that could only be explained by caching. I tested yesterday, but some kind of observer type behaviour was keeping everything perfectly and promptly
synced.
On 04/12/2024 18:41, Rich wrote:
The Natural Philosopher <tnp@invalid.invalid> wrote:Caja
On 03/12/2024 22:24, Andy Burns wrote:
The Natural Philosopher wrote:
What I find puzzling is how it appears in the GUI but isn't on the
actual machine file system
funky characters in filename?
ls -la | cat -v
Nope. Still no sign
I think some part of the GUI environment builds a cache, and its in
that, but not in the real world so to speak
What is the GUI file browser program you use under Mate?
Many "GUI file browsers" have a tendancy to "combine" plural actualHmm. Still doesn't say why it cant be deleted/found Even from the GUI
disk paths into the 'appearance' of a singular view (and "Desktop" is
one of those 'views' that GUI dev's think need this miss-feature).
So it is possible the file it is located somewhere other than
~/Desktop/ and the GUI is merging together that other location with the
contents of the actual ~/Desktop/, and presenting the combination to
you as "Desktop".
file manager
Which would explain why it does not appear when you actually view
~/Desktop/ with ls from a terminal.
On 2024-12-05 08:59, The Natural Philosopher wrote:
On 04/12/2024 18:41, Rich wrote:
The Natural Philosopher <tnp@invalid.invalid> wrote:Caja
On 03/12/2024 22:24, Andy Burns wrote:
The Natural Philosopher wrote:
What I find puzzling is how it appears in the GUI but isn't on the >>>>>> actual machine file system
funky characters in filename?
ls -la | cat -v
Nope. Still no sign
I think some part of the GUI environment builds a cache, and its in
that, but not in the real world so to speak
What is the GUI file browser program you use under Mate?
Many "GUI file browsers" have a tendancy to "combine" plural actualHmm. Still doesn't say why it cant be deleted/found Even from the GUI
disk paths into the 'appearance' of a singular view (and "Desktop" is
one of those 'views' that GUI dev's think need this miss-feature).
So it is possible the file it is located somewhere other than
~/Desktop/ and the GUI is merging together that other location with the
contents of the actual ~/Desktop/, and presenting the combination to
you as "Desktop".
file manager
Because it would be on another directory.
Which would explain why it does not appear when you actually view
~/Desktop/ with ls from a terminal.
On 05/12/2024 10:34, Carlos E.R. wrote:
On 2024-12-05 08:59, The Natural Philosopher wrote:But if the GUI knows where it is the GUI should be able to delete it.
On 04/12/2024 18:41, Rich wrote:
The Natural Philosopher <tnp@invalid.invalid> wrote:Caja
On 03/12/2024 22:24, Andy Burns wrote:
The Natural Philosopher wrote:
What I find puzzling is how it appears in the GUI but isn't on the >>>>>>> actual machine file system
funky characters in filename?
ls -la | cat -v
Nope. Still no sign
I think some part of the GUI environment builds a cache, and its in
that, but not in the real world so to speak
What is the GUI file browser program you use under Mate?
Many "GUI file browsers" have a tendancy to "combine" plural actualHmm. Still doesn't say why it cant be deleted/found Even from the GUI
disk paths into the 'appearance' of a singular view (and "Desktop" is
one of those 'views' that GUI dev's think need this miss-feature).
So it is possible the file it is located somewhere other than
~/Desktop/ and the GUI is merging together that other location with the >>>> contents of the actual ~/Desktop/, and presenting the combination to
you as "Desktop".
file manager
Because it would be on another directory.
Rebooting X windows disappeared it, anyway
Which would explain why it does not appear when you actually view
~/Desktop/ with ls from a terminal.
On 2024-12-05 12:06, The Natural Philosopher wrote:
On 05/12/2024 10:34, Carlos E.R. wrote:
On 2024-12-05 08:59, The Natural Philosopher wrote:But if the GUI knows where it is the GUI should be able to delete it.
On 04/12/2024 18:41, Rich wrote:
The Natural Philosopher <tnp@invalid.invalid> wrote:Caja
On 03/12/2024 22:24, Andy Burns wrote:
The Natural Philosopher wrote:
What I find puzzling is how it appears in the GUI but isn't on the >>>>>>>> actual machine file system
funky characters in filename?
ls -la | cat -v
Nope. Still no sign
I think some part of the GUI environment builds a cache, and its in >>>>>> that, but not in the real world so to speak
What is the GUI file browser program you use under Mate?
Many "GUI file browsers" have a tendancy to "combine" plural actualHmm. Still doesn't say why it cant be deleted/found Even from the
disk paths into the 'appearance' of a singular view (and "Desktop" is >>>>> one of those 'views' that GUI dev's think need this miss-feature).
So it is possible the file it is located somewhere other than
~/Desktop/ and the GUI is merging together that other location with
the
contents of the actual ~/Desktop/, and presenting the combination to >>>>> you as "Desktop".
GUI file manager
Because it would be on another directory.
The GUI is not a magician.
On 05/12/2024 11:19, Carlos E.R. wrote:
On 2024-12-05 12:06, The Natural Philosopher wrote:
On 05/12/2024 10:34, Carlos E.R. wrote:
On 2024-12-05 08:59, The Natural Philosopher wrote:But if the GUI knows where it is the GUI should be able to delete it.
On 04/12/2024 18:41, Rich wrote:
The Natural Philosopher <tnp@invalid.invalid> wrote:Caja
On 03/12/2024 22:24, Andy Burns wrote:
The Natural Philosopher wrote:
What I find puzzling is how it appears in the GUI but isn't on the >>>>>>>>> actual machine file system
funky characters in filename?
ls -la | cat -v
Nope. Still no sign
I think some part of the GUI environment builds a cache, and its in >>>>>>> that, but not in the real world so to speak
What is the GUI file browser program you use under Mate?
Many "GUI file browsers" have a tendancy to "combine" plural actual >>>>>> disk paths into the 'appearance' of a singular view (and "Desktop" is >>>>>> one of those 'views' that GUI dev's think need this miss-feature). >>>>>>Hmm. Still doesn't say why it cant be deleted/found Even from the
So it is possible the file it is located somewhere other than
~/Desktop/ and the GUI is merging together that other location
with the
contents of the actual ~/Desktop/, and presenting the combination to >>>>>> you as "Desktop".
GUI file manager
Because it would be on another directory.
The GUI is not a magician.
No, but it must have consistent rules. If Caja displays it Caja can
delete it and the same for the desktop manager as well
The fact is it is - or was - a ghost. It only existed as far as I can
tell in the GUI cache...
On 2024-12-05 13:26, The Natural Philosopher wrote:
On 05/12/2024 11:19, Carlos E.R. wrote:
On 2024-12-05 12:06, The Natural Philosopher wrote:
On 05/12/2024 10:34, Carlos E.R. wrote:
On 2024-12-05 08:59, The Natural Philosopher wrote:But if the GUI knows where it is the GUI should be able to delete it.
On 04/12/2024 18:41, Rich wrote:
The Natural Philosopher <tnp@invalid.invalid> wrote:Caja
On 03/12/2024 22:24, Andy Burns wrote:
The Natural Philosopher wrote:
What I find puzzling is how it appears in the GUI but isn't on >>>>>>>>>> the
actual machine file system
funky characters in filename?
ls -la | cat -v
Nope. Still no sign
I think some part of the GUI environment builds a cache, and its in >>>>>>>> that, but not in the real world so to speak
What is the GUI file browser program you use under Mate?
Many "GUI file browsers" have a tendancy to "combine" plural actual >>>>>>> disk paths into the 'appearance' of a singular view (andHmm. Still doesn't say why it cant be deleted/found Even from the
"Desktop" is
one of those 'views' that GUI dev's think need this miss-feature). >>>>>>>
So it is possible the file it is located somewhere other than
~/Desktop/ and the GUI is merging together that other location
with the
contents of the actual ~/Desktop/, and presenting the combination to >>>>>>> you as "Desktop".
GUI file manager
Because it would be on another directory.
The GUI is not a magician.
No, but it must have consistent rules. If Caja displays it Caja can
delete it and the same for the desktop manager as well
The fact is it is - or was - a ghost. It only existed as far as I can
tell in the GUI cache...
Sigh...
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.
Both the desktop AND the file manager displayed it and both said they
could not access or delete it.
The Natural Philosopher wrote:
Both the desktop AND the file manager displayed it and both said they
could not access or delete it.
If it happens again, can you view properties of a file, to see where it really is?
The Natural Philosopher wrote:
Both the desktop AND the file manager displayed it and both said they could >> not access or delete it.
If it happens again, can you view properties of a file, to see where it really is?
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.
"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.
* 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.
* 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.
* 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).