LM 20.2 filezilla not downloading to /tmp directory

[flyingrhino]

I've got something weird on my LM 20.2 XFCE :
When downloading files over sftp to /tmp/ on my local box using filezilla - the transfers show they're succeeding but then there are no files to be found in /tmp/ .

If I do the same thing using scp from the command line - it works.

Has anyone experienced the same?

Thanks.

[Reddog1]

My wild guess is that filezilla is downloading your files to somewhere other than /tmp. Do a catfish search and see if so and where to would be the first step.

[flyingrhino]

Did that already and it's not downloading them anywhere.

The files do take time to download (at wifi speed) but then show up nowhere.

[Larry78723]

/tmp is part of the root file system and filezilla is running as a user app so doesn't have permission to write to it. Create a /home/username/tmp folder and download to it.

[flyingrhino]

/tmp/ is root:root with permissions of 777t which allows each user to write their own files.

This looks like a bug somewhere - possibly in filezilla.

[ajgringo619]

Did you happen to install Filezilla via flatpak? If so, /tmp has a whole new meaning.

What does flatpak list show?

[flyingrhino]

Did you happen to install Filezilla via flatpak? If so, /tmp has a whole new meaning.

Yes i used the flatpak version because it was newer than the one in the repos.
I've used flatpak for several other software installs too.

What's the story with flatpak?

Thanks.

[ajgringo619]

Depending on how the file access permissions are setup, what Filezilla is using for /tmp might be completely different from what normal apps use. You should search the entire disk for any downloads.

[mikeflan]

What's the story with flatpak?

Flatpaks take a lot of disk space and generally work very well. They also update automatically. I would encourage you to use them, especially on the larger, more complex programs that you use quite often.

[flyingrhino]

Depending on how the file access permissions are setup, what Filezilla is using for /tmp might be completely different from what normal apps use. You should search the entire disk for any downloads.

I checked and the download is nowhere to be found.
Using catfish it just says "Searching..." forever and finds nothing.
As root doing: find / -name "myfile*" -print yeilds no results.

But here's the weird bit - if I don't exit filezilla - I can upload this newly downloaded file to somewhere else and the file exists at the target.
But if I exit filezilla and start a new filezilla - the file no longer exists.

And it gets stranger - when I download the file and keep filezilla open - it's there in the /tmp/ . And if I open a second filezilla when the first one is still open - it's not there in the second filezilla, but it's there in the first filezilla - until I close the first one.

[Larry78723]

It sounds like you might have enabled TMPFS per https://easylinuxtipsproject.blogspot.c ... t.html#ID9, in which case temporary files will not be placed on the hard disk anymore, but on a virtual RAM disk instead.

[flyingrhino]

It sounds like you might have enabled TMPFS per https://easylinuxtipsproject.blogspot.c ... t.html#ID9, in which case temporary files will not be placed on the hard disk anymore, but on a virtual RAM disk instead.

Nope. Standard /tmp/ dir mounted on / .

When I do :
cd /tmp
df -h .

I get the same size as / .

Really strange.

[mikeflan]

When I do :
cd /tmp
df -h .

I get the same size as / .

Really strange.

Not so strange if you read man df
Perhaps you are thinking of du -sh

[flyingrhino]

Not so strange if you read man df
Perhaps you are thinking of du -sh

I meant to say that the space in /tmp/ is the same as in / (because they are mounted on the same point).
If //tmp/ was mounted on some ramdisk (suggested by Larry78723 as a possible cause) then I'd get something like 4Gb free in the 'df' rather than something like 80Gb.
This proves that /tmp/ is a real place (not some ramdisk) and filezilla is indeed behaving strangely.

[MAlfare]

[quote
But here's the weird bit - if I don't exit filezilla - I can upload this newly downloaded file to somewhere else and the file exists at the target.
But if I exit filezilla and start a new filezilla - the file no longer exists.

So your flatpak filezilla deletes the files it put in /tmp when it terminates.
Not very mysterious.