Hi everyone!

A few days ago, I had a problem while trying to run KDE and Gnome as DE on Fedora 40. That problem was solved (see crosspost), but now, I can’t update Fedora anymore as it says “the transaction did not complete” and I can’t install or uninstall anything as it says I don’t have space on my disk (which is not true).

Does anyone have an idea what to do?

Edit: apparently dnf clean and dnf clean all solved the problem, so thank you everyone as I was kind of panicking when I thought about all the work involved into having my perfect install again.

publication croisée depuis : https://sh.itjust.works/post/20027102

Hi everyone!

Today I tried to install KDE alongside Gnome to give it a try on Fedora on something else than a virtual machine.

For a reason I can’t understand, the terminal couldn’t finish the installation of KDE as something failed. Despite all of this, all the KDE apps were installed and Plasma is appearing as an option on the login screen under Gnome and Gnome Classic. Still I couldn’t launch KDE plasma and nothing was happening after typing my login.

I took it as a sign that KDE isn’t for me, especially because I’m 99% happy with Gnome.

So I removed KDE via the terminal and the remaining apps via the software center. Sadly, there is one app called “Centre de bienvenue” or “Welcome center” from KDE that I can’t remove. Nothing is happening when I try removing it.

I tried removing it via the terminal, but when I type “dnf list installed” I can’t find it as there are too many packages. Could anyone help me?

I also tried « dnf list installed » with the words « welcome », « bienvenue », « kde » and « plasma ».

  • ffhein@lemmy.world
    11·
    6 months ago

    If you’re using btrfs then you might need to rebalance it. I had the same problem, i.e. “no free space” while tools like df reporting that there should be available disk space, and it confused the hell out of me until I found the solution.

    See manual: https://btrfs.readthedocs.io/en/latest/Balance.html

    This are the commands I run every now and then, especially if my drive has been close to full and I delete a bunch of files to make more space:

    sudo btrfs balance start -dusage=10 /
sudo btrfs balance start -dusage=20 /
sudo btrfs balance start -dusage=30 /

    The / at the end is the path, since it’s my root mount which uses btrfs. The example in the manual does 40 and 50 too, but higher numbers take longer time, even on an nvme ssd.

    • Dariusmiles2123OPEnglish
      2·
      6 months ago

      sudo btrfs balance start -dusage=30 /

      That’s what I’m getting when I’m trying to run the command

    • Lojcs@lemm.ee
      1·
      6 months ago

      What does balance do in that context? As I understand unless the volume spans multiple drives or the files were so numerous and small that metadata was a significant portion of their disk usage, rebalancing will only unallocate data chunks just for them to be allocated again when that space gets used.

      Unless the program you’re using is wrongly checking unallocated space instead of free space, it shouldn’t really affect disk usage

      Edit: It might help with trim and make the drive faster though. But you’re also putting a bunch of unnecessary wear on it so it might not be worth it

      • ffhein@lemmy.world
        1·
        6 months ago

        Don’t know that much about how btrfs works, just had a problem with the same symptoms as OP a while ago… Things started failing due to “no space left on device” despite df reporting several gigabytes available. Took a while to figure out what was going on but eventually found some stackoverflow/reddit post that told me to run the balance command and it worked. Just a single drive with btrfs, no raid.

    • Dariusmiles2123OP
      1·
      6 months ago

      sudo btrfs balance start -dusage=30 /

      That’s what I got in the end after I was able to use the command you gave me. I don’t know if it helped or not. I just hope the problem I had is gone for good.

      • ffhein@lemmy.world
        1·
        6 months ago

        That output means that it did something, but I suspect there’s a risk the same thing could happen in the future. I run this command every now and then in an attempt to avoid fragmentation, especially if the disk has been close to full, but I’m not entirely sure what’s causing it to happen in the first place.