Hello folks. I use many distro from Debian to Fedora to OpenSuse and Arch. I also use many window managers like i3, dwm and qtile. On desktop environment, I use XFCE the most. Currently, I am looking to try something new, hence KDE.

I am looking for something with a beautiful UI and works out of the box. So, something on the same spectrum as XFCE but more pretty.

I tried out the distros with preinstalled KDE: Fedora KDE, Manjaro KDE, Kubuntu.

The good: KDE is beautiful and very easy to use. I actually enjoy using my computer more.

The bad: it crashes… a lot even when I turn off all the animations. My system is not that slow: AMD 7 Pro with 64 GB of RAM. Some examples:

  • Logging in, KDE hangs for 30 seconds. Even when I finally see the desktop, I would need to wait a further 10 seconds to finally able to interact, i.e. click and open stuff.

  • After resume suspend, system would hang and there is nothing I can do except for a forced reboot.

  • Browsing the web with only 3 tabs opened, KDE also hang.

As much as I hate GNOME, everything just works. I installed the GNOME flavors of above distros and never experience any hiccups.

If KDE works for you, do you use a preinstalled distro and which one? How about if you install KDE from scratch, like Arch?

  • N0x0n@lemmy.ml
    3·
    1 day ago
    1. Copy 1Gb movie to flash drive, says it’s done in 10 seconds. Try to remove the flash drive, still in use. Turns out it’s actually still copying.

    This is not distro related but GNU/Linux and a known “issue” for over decades ! Everything gets into you ram memory and gets dumped from there into your USB storage device.

    watch grep -e Dirty: -e Writeback: /proc/meminfo

    A long term solution would like to write a udev rule something like here:

    https://unix.stackexchange.com/questions/771398/solving-the-usb-drive-mass-storage-stall-issue

    • lemmeBe@sh.itjust.works
      21·
      1 day ago

      Thanks! I’ll try that out today!

      Why quotation marks? Issue is an issue, decades or days old. 😄

      Copying mechanism itself isn’t an issue here; false reporting that something is done when it’s not is.

      • N0x0n@lemmy.ml
        2·
        1 day ago

        The question marks are because I read somethere that Linus himself doesn’t see it like an issue by itself but more like a feature? And that’s why it hasn’t been resolved for soo long ! I can’t exactly remember what he said but that’s the gist !

        But I do agree, I also see it as an issue :/ and most people who aren’t aware probably fucked up some USB sticks that way…

      • Jerkface (any/all)@lemmy.caEnglish
        11·
        24 hours ago

        Because it’s not an issue. This is the system functioning as intended. Changing this behaviour would cause dramatic performance degradation for the 99.999% of the time when the device you are writing to isn’t removable media that you want to eject right away.

        • lemmeBe@sh.itjust.works
          2·
          4 hours ago

          It’s an issue according to any UX pattern. If something says that it’s done when it’s not, it’s misrepresenting the state of the action.

          Hard to believe that modifying the counter to include the necessary time for actual writing to the flash drive would break everything. Target flash drives only etc.

          System functioning as intended doesn’t mean that it’s a good UX.