I'm having a weird problem.

I downloaded a bios and put it on a freshly bought usb stick. I then entered bios and put it in the flashing mode. Before with spacefm I took the bios out of the folder and put it into the root of the usb stick. Then I deleted the folder.

Now in the bios flash mode i selected that bios in the root of the usb stick. Flash service then said: "This is not a correct bios!"
I was surprised, I was even more surprised to see the folder I deleted before with spacefm. I went into the folder and a bios was there. I tried that bios and it worked. That was actually really risky looking back lol

So I ignored that and days went by without anything happening.

Now I made a filter on filterblade.xyz. I downloaded the filter. I downloaded it twice after I made a little change. I went into the folder with spacefm to delete the old filter. Then I played the game with the new filter. After some time the game crashed. Then it crashed again. Then it was ok again.
I looked into the folder where the filter was before and IT IS GONE!

I'm panicking here right now...did I get some malware or something? This is not good :(
I just remember that a few years ago a friend of mine had similar problems when moving files from disk to disk or to a usb stick.

Dropping Spacefm.

Don't use it.
I don't think spacefm is to blame, after all all filemanagement guis use commands like cp, mv, rm, rmdir, mkdir, chown, chmod, and refresh ls with options. It is not like they have their own fs to work with.
What I think the problem is the doings of USB sticks. USB sticks and ssd-s are not magnetic or optical mediums, they rely on a chip and firmware to simulate writing and deleting. What appears on the file system (like ext4, dos, etc) as written and deleted in another fs like what is used by bios may be different. For example in dos when you deleted a file it only renamed the file by changing its first character with something that dos wouldn't show as a file. Only when space was running out would it write over this renamed file. There was a command called undelete which made all those renamed files reappear and you could just rename them changing the first character and you would get it back, except when something had been written over it again.
Not all USB sticks use the same firmware, it is not open and free to see, and each brand may use a different one. Mechanically a stick may be fine, but if somehow that firmware gets corrupt they are done, dead, not even the manufacturer may be able to bring it back. Same thing with some androids, the OS is imbeded in this chip, and if it gets bothered you get what they call a bricked device.

After all that said, I use pcmanfm, but when in doubt I use commands on the terminal. Depending on how essential it is to copy and move things.
oh yes spacefm is to blame. It failed on the usb stick, it failed on the other harddrive which is ext4 formated nvm. It failed twice and I consider it as shit software. It even crashed on a different task. People shouldn't be allowed to use it.

I use worker now, let's see if it is reliable.
interesting, ive always thought that spacefm was the better version of pcmanfm. i still use pcmanfm just because it looks nicer (and is not newer.) though i do think this warrants more investigation than just dismissal.
filemanagement guis use commands like cp, mv, rm, rmdir, mkdir, chown, chmod, and refresh ls with options.
no? i mean thats true of many guis that call complex command line software, but far less likely for a file manager. you wouldnt even want to do it that way, generally. if spacefm does that, then that might explain the problem nic is having. gui file managers generally call libraries or other apis, they dont call command line tools unless there are library interfaces (like curl has.)
Didn't see anything wrong after three years of use... but well, if it's not good for you, change it for sure
if spacefm does that, then that might explain the problem nic is having. gui file managers generally call libraries or other apis, they dont call command line tools unless there are library interfaces (like curl has.)
I don't know what spacefm is doing but it is even fishy when it comes to mount drives, which it claims to do automatically, without sudo. In worker it doesn't allow that, you have to sudo worker to mount drives. And so far it works beautifully, even has a image view or text view. I'm happy now :)
I think the automounting is handled by gvfs and udisks2 and whether this needs root rights or not can be handled by polkit and groups.
Not only I don't miss systemd's automounting I have learned to hate it, I like mounting and dismounting things on my own.
I am not trying to defend spacefm but it would be interesting to see what it does and how two different usb's would behave, or whether the same stick does the same with other -fm

Powered by Obarun