• 2 Posts
  • 34 Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle
  • Arch Linux. Everyone said it was hard to use, unstable, etc. but my experience with it has been the exact opposite.

    Yes, the install process is needlessly complicated (although it got a lot simpler now that we have archinstall), but the OS itself is rock solid and rarely has any issues that require more than a reboot or a package reinstall to solve. The AUR is a godsend too if you don’t want or don’t know how to compile stuff from source.






  • I think this one beats them all.

    My home server keeps a few services up, including an instance of Jitsi Meet. The server runs nixos and the nixos package for jitsi is incomplete to say the least and doesn’t even support authentication, so I use the docker-compose version and I have a script that runs periodically to keep it updated. So far so good, right? Well, no.

    Because the server is at home, I have a dynamic external IP address, so I have to use a DDNS provider, but jitsi doesn’t expect this and uses a stun server at startup to determine the public IP of the server once, so if my connection goes down or is restarted and the IP changes, jitsi needs to be restarted or it won’t work anymore.

    The solution?

    • My router runs OpenWrt, so I am able to run a script that checks for external IP changes. When a change is detected, it uses SSH to connect to my server to restart jitsi
    • Because I don’t want the router to just be able to run any command, I created a jitsi-restart user that has no shell
    • When the router tries to log in with its pubkey, sshd creates a file called restartasap in the jitsi folder and closes the connection
    • On the server, there’s a systemd unit running a script as the jitsi user that periodically checks for that file, and if it exists it deletes it and restarts jitsi

    I’ve been running this setup since mid 2020 and I expect this to continue until IPv6 becomes the norm.












  • I’ve been using it since Plasma 6 came out so about 3-4 weeks.

    Overall, it’s been a very negative experience for me. The main problems have been:

    • Random scaling issues in apps: some apps show a slightly smaller cursor, other show a poorly upscaled one, others have random rendering issues like lines remaining on the screen after an option is no longer highlighted (gimp, libreoffice, many others), some apps have random flickering of parts of the UI, some apps no longer scale at all or are scaled twice. Plasmashell itself has blurry icons on the desktop but all other KDE apps don’t. I know fractional scaling has always been problematic, but it has gotten worse to the point of being almost unusable
    • Random crashes of GTK apps when using the wayland backend. Some GTK apps don’t even start and segfault immediately with a wayland error in the terminal
    • Some apps like okular and libreoffice lag like crazy or outright freeze when scrolling
    • Some games not capturing the cursor properly (Proton)
    • Inconsistent font rendering, some fonts look fine in some apps and atrocious in others
    • Issues when resizing or moving windows, some times they “jerk” off the screen or resize to a very tiny window and I’m forced to use key combinations to resize them again
    • Random issues with window decoration not appearing in some apps but randomy appearing for things like context menus

    This is on a full AMD system with Arch Linux, the latest kernel and mesa-git. I hope for KDE’s sake that there’s something broken in my installation because I can’t believe the KDE team released Plasma 6 in this sorry state.