Mainly here to keep up with the news on Linux.

  • 1 Post
  • 25 Comments
Joined 1 year ago
cake
Cake day: July 15th, 2023

help-circle
rss


  • It mentions it fixed bluetooth issues with certain devices, I wonder if it’s related to what I’m experiencing on regular fedora KDE (and EndeavorOS too) with a kernel version 6.9.3, CachyOS kernel on fedora, Liqourix on EndeavorOS, where my game controller will not connect to Bluetooth unless I restart the bluetooth service or pair the controller again.

    With Fedora’s default kernel which is currently 6.8.11 I don’t have this issue. Honeslty I don’t know what’s up, and from a quick search I couldn’t find people with the same issue. I’ll search again later just in case


  • One pet peeve of mine is how in Windows 10 switching between virtual desktops was flawless, and somehow in Windows 11 they fucked it up. At first it had no animation when switching, the taskbar kind of glitches. Now it has an animation but it’s kind of delayed and the taskbar still kind of glitches, it seems to reload or something. Kinda crazy honestly




  • I can speak at least for rootless podman, I spent some hours on it and different ways I tried all ended in permission issues.

    I gave up on trying to do it properly and just set the permissions of the /dev/dri device to 666, so that my podman container can use the gpu for transcoding.

    Part of the issue with the container images that I tried is that they create a new user with whatever uid:gid I pass to the container, and so even if my nonroot user is part of the render group, the new user inside the container is not and so it can’t write to the /dev/dri/renderD128 (gpu), and so transcode wouldn’t work.

    That’s where I left the troubleshooting at cause it was being a headache



  • Yeah I’m fairly certain it’s a permission issue. Having the gpu with permissions 666 makes it work inside the containers.

    The thing is also that these container images (plex and jellyfin) create a separate user inside, instead of using the root user, and this new user (“abc” for lsio images) doesn’t get added to the same groups as the root user.

    Also the render group that gets passed to the container appears as “nogroup”, so I thought of adding user abc to “nogroup” but still didn’t seem to work.










  • Just between yesterday and today I was struggling with this, to get DoH or DoT working, but Network Manager would override /etc/resolv.conf. At least I figured out how to stop NM from modifying the DNS.

    I tried my putting my dns settings in /etc/systemd/resolv.conf, as suggested by Nextdns setup page, but that didn't seem to work, at least on Tumbleweed. On my Debian laptop running as a headless server, the /etc/systemd/resolv.conf does work.

    I'm currently with Stubby, and it's working at least, but I would've liked to figure out the systemd-resolved way on Tumbleweed.


  • I would say option 3.

    I can share my current setup in case you're interested.

    I recently moved back to Tumbleweed, and did the following:

    / -> 50GB, BTRFS, currently 13GB used I think

    /home -> 800something GB, BTRFS, same drive

    /boot/efi -> 512MB i think, same drive

    Then a separate drive mounted to a folder in my home directory, for games mostly.

    So far it eworks well, at least for me. BTRFS snapshots are working fine too. Flatpaks I have installed as user so they get installed in my home directory.