SSD’s dont work like old HD’s depending on the generation of tech it might be storing multiple values per cell which means when you “filled” the SSD you put a charge into every single storage cell on the drive.
Garbage collection and TRIM will slowly over time clear out all the cells flagged as deleted but if one bit is still valid in a cell that was holding 3-4 other bits it cant overwrite that, or relocate it.
That means that your files/videos and such stay fragmented and may never get put back together sequentially or in a way that the controller can optimize again for speed.
The only fix, may be running a factory wipe from the Drive MFG’s tool set, that should fully blank each cell and let you re-install and make it feel fresh again.
Be warned though, you have already done a full drive write once at least, this would be another. You can expect some dead cells and while there is over provisioning that should provide replacements you could see a loss in usable space sooner than later.
alright edit: I have a Flatpak issue, not an SSD issue. does anyone have any thoughts? this could be due to the new linux mint update. my pc is a samsung galaxy s2 (750XED P13CFG)
the linux mint discussion forum has a post about my model not being great but last update my system worked just fine. i actually think having a full ssd broke flatpak. otherwise ive hit a horrible regression issue github.com/orgs/linuxmint/discussions/277
I had this problem with flatpaks, I changed the dbus implementation to dbus-broker (in endeavouros) and it fixed the issue. It may be the same problem.
I installed dbus-broker and the package manager checked the dependencies and removed the unnecessary stuff. After that I applied the dbus-broker services:
Yes, I remember reading about a gtk thing that interacts with flatpak, they said it should not give this error in April, but it seems to still be happening, idk.
Edit: I just saw that you deleted the gtk portal and it worked! So no need to install another dbus daemon.
Not an answer to you actual question, but: I stopped using dead keys long ago because I found it irritating to have to hit space whenever I needed to break out. Instead I mapped my CapsLock to be a Compose-key which lets me make almost any symbol I ever need in a very intuitive wsy. It works everywhere (incl. Wayland).
usually when I have problems with YubiKey being detected it is because the pcscd service has not been started, or I forgot to enable it so it would start automatically on boot.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.