Skip Navigation
120 comments
  • Just recently XDG Portals to get video sharing working. It just kept using the GTK fallbacks instead of KDE as I configured it, but it used the correct ones when starting from the terminal.

    Eventually I figured out I had set an env override for XDG_CURRENT_DESKTOP="sway" in my user systemd environment, because that's what I used previously.

  • I use sway, and for the life of me can not get steam link to display my games. I have tried so many things. If I use flatpak steam it works, but it breaks remote play together, which works fine not flatpak! I can get them both to work with KDE Wayland as well. It's frustrating but also not a huge deal.

  • I've been on arch for years, but have recently started pc gaming. Lutris has been surprisingly easy to get working. I have a nintendo switch already and decided I want to try to use the joycons for the computer, don't want to buy gamepads but it gives and alternative to keyboard and mouse. Getting them consistently recognized by bluetooth has been a massive pain, but after searching I've figured out a package that I can install that fixes the issues. In fact, I couldn't find anyone who found a solution to this issue without installing this specific package.

    That package is pulseaudio-bluetooth, even though the nintendo joycons do not have an audio jack or capability to receive audio. I've had my audio set up and configured with alsa, and alsa does everything (relating to audio) that I need it to, but pulseaudio-bluetooth requires me to install pulseaudio (duh) and will not work unless I enable the pulseaudio service, which fucks up my alsa config. I've spent a while dicking around trying to get pulseaudio to pretend it doesn't exist except for connecting joycons, but there's always some nuisance popping up. I also tried using a different usb bluetooth controller and plugging them into different usb ports. Given up for the moment and will probably just buy another gamepad and hope it works better without needing pulseaudio-bluetooth.

    In all honesty I still don't really know what the hell I'm doing on arch, I originally installed it to learn this stuff better but all I've really learned is how to read documentation well enough to get things working by trial-and-error. I've had a stable system for like ten years now though and I'm too comfortable with it to warrant switching to a friendlier distro, but this specific issue is a pain in the ass.

  • hostapd. I have no idea how you’re supposed to figure out the 50 or so options OpenWrt outputs for an AX card that I just ended up copying. And why doesn’t it detect those on its own?

    1. Setting up Nvidia runtime for rootless Docker containers in Linux.
    2. Resolving port :53 conflict between AdGuardHome (rootless) docker container and Systemd-Resolved.
  • Getting Keycloak and Headscale working together.

    But I did it after three weeks.

    I captured my efforts in a set of interdependent Ansible roles so I never have to do it again.

  • Rootless podman, PostgreSQL, redis, nextcloud, nginx, iptables in one....

  • I gave up trying to setup a Mastodon server in docker. Lemmy was pretty tricky at the time as the docs were wrong. My email server was a bit tricky, but I've not really done much to tinker with it in the proceeding 6 years, so was worth it.

120 comments