Former title: SSD having issues after I filled up its storage

I wrote this poorly last time so here’s a more clear description: Hey all, so I filled my SSD up on Linux Mint and it’s running sluggishly. I deleted more than half of my storage but there’s still issues. It can read / write fast according to my inexperienced testing and I have trimmed it (to my knowledge) but there’s still issues. Loading up programs now takes 30 seconds (even something like VLC which typically took like 0.5 seconds). Loading new audio files into VLC can take 10 seconds. I have checked my system monitor and nothing seems out of place. Also, when the program starts running, it runs perfectly. The computer itself is fast but loading anything new takes ages. Does anyone have any ideas? It’s a new laptop, not even two months old.

Edit: This is somehow, and strangely, a Flatpak issue apparently? It was triggered either by a full SSD or the new Linux Mint 21.3 Cinnamon update.

Edit 2: Interesting experiment result

‘it took 30 seconds but this got outputted and then the file ran: dave@dog: ~$ flatpak run org.x.Warpinator Gtx-Message: 14:29:03.389: Failed to load module “xapp-gtk3-module” Using landlock for incoming file isolation’

It appears there’s either a xdg-desktop-portal-gtk and/or xdg-desktop-portal-gnome error and I’m not alone, Mint and Arch users are both reporting it as of recent strangely???

This was a real sneaky fu(ker as it dodged all logical system testing. The only reason I caught it was cause it was suspicious how fast system programs booted and how flatpaks booted like sh(t. Not sure if I’m even right about the module, but I’m highly suspicious

Some comment mentioned this and it explained it well: Random shot, because it’s probably not an issue on Mint like it was on Arch a few months ago, but xdg-desktop-portal problems can cause apps to take forever to load, but run fine once loaded.

edit: Try removing xdg-desktop-portal-gtk and/or xdg-desktop-portal-gnome

  • jackpot@lemmy.mlOP
    link
    fedilink
    arrow-up
    0
    ·
    10 months ago

    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)

  • infinitevalence@discuss.online
    link
    fedilink
    English
    arrow-up
    0
    ·
    10 months ago

    How long ago did you delete everything?

    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.

    • jackpot@lemmy.mlOP
      link
      fedilink
      arrow-up
      0
      ·
      10 months ago

      i deleted everything ywsterday, and i trimmed today. i was unaware of the dead cell issue. is there a way to disk defragment an ssd?

      • infinitevalence@discuss.online
        link
        fedilink
        English
        arrow-up
        0
        ·
        10 months ago

        in theory time, it should slowly rewrite everything to consolidate it. If you dont have time, then factory format and reinstall.

  • Limcon@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    10 months ago

    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.

      • Limcon@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        10 months ago

        I installed dbus-broker and the package manager checked the dependencies and removed the unnecessary stuff. After that I applied the dbus-broker services:

        systemctl enable dbus-broker.service

        sudo systemctl --global enable dbus-broker.service

        And then restarted.

        Idk if it might break things in mint, so I would be cautious.