Hey hey people. Relatively new Arch user here, but not new to Linux in general. I’ve been using Arch with KDE Plasma on this HP laptop from 2013, and I’ve been enjoying it a lot after spending a long time on Mint/Cinnamon.

But, I’ve noted that KDE is a bit slow on this machine, and is probably a bit too much. Earlier today, I decided to try out something lighter, and installed LXQt on it as a second DE. The experience was okay, with much improved responsiveness, a nice customizable retro look, and overall simpleness that still did the job mostly. But I also ran into a few issues that probably had to do with having two different DEs on the same machine and user. One thing in particular ended up annoying me so much I went back to KDE: The Discover app would just refuse to play nice with setting a dark theme on the rest of the environment, even when I tried setting it up with qt6ct.

So now I’m considering going to XFCE instead, as I probably should have done from the beginning. I just wish it had Wayland support already (I know it’s being worked on). Do you have any suggestions or tips for me in regards to this? I’m sure a lot of people will recommend their favorite tiling WM which I’m not sure I want to get into.

Also, other than that, upon returning to KDE, I found that my Discover would crash when trying to update Flatpaks (the only thing I install through it) and started thinking this experiment somehow broke it… but it’s Flatpak itself that seems to have an issue today. Might have to do with the latest curl update? Dunno if I should make a separate thread for that. https://discuss.kde.org/t/kde-discover-broken-with-latest-curl-update/21475

  • demesisx@infosec.pubEnglish
    141·
    2 months ago

    Try Xmonad! I run a community for it at https://infosec.pub/c/xmonad

    It’s super lightweight and is the only formally verified window manager. There’s a new version being created for Wayland called Waymonad.

      • demesisx@infosec.pubEnglish
        121·
        2 months ago

        I’m glad you asked!

        Formal verification is an automatic checking methodology that catches many common design errors and can uncover ambiguities in the design. It is an exhaustive methodology that covers all input scenarios and also detects corner case bugs.

        One of the most futuristic companies I know of is Runtime Verification that uses formal Methods in industry. They have a list of accomplishments that seem like vaporware including a semantic babel fish called the K framework that can translate between languages based on formal, semantic definitions of each.

        • superkretEnglish
          2·
          2 months ago

          I think a friend of mine has a job where he writes formally verified code. For sensors in a nuclear power plant. I’m curious why it would be important for a WM?

          • demesisx@infosec.pubEnglish
            121·
            2 months ago

            It’s not important unless Xmonad was being used for some kind of task where human lives are at risk if a mistake was made. In my case here (and indeed much of the Haskell world) it’s just fun to surround myself with software of that kind of code quality/reliability.