That reddit thread is horrible advice, it’s just mapping the LXC root user to the host root user, which is just a privileged LXC with extra steps (and maybe less secure).

The reason you’re probably having issues is that your root user in the LXC is mapped to the host user 100000 by default, and that user doesn’t have access to the share, but you can change that with mount options or creating a user with 100000:100000 and adding it to a group with access.

Gnome is very functional, it’s just meant to function one very specific way.

I use Tautulli, but I’m not sure if that is going to cover all the same use cases.

I haven’t gotten around to spinning it up yet, but I was just looking into this myself and was going to try out Pinchflat. If anyone has used it and has any feedback I’d love to hear it.

I was between it and Tube Archivist.

For anything. You can get a push notification for anything you can make run a script or send an http request.

Me too. I recently switched from an RTX 2080 to a 7900 XTX, which is way more powerful for games, but local LLM performance tanked without CUDA.

My distro hops have been more like distro evacuations.

Just run docker in an LXC. That’s what I do when I have to.

I’m not really worried about it. Each LXC runs as its own user on the host, and they only have access to what they need to run each service.

If there’s an exploit found that makes that setup inherently vulnerable then a lot of people would be way more screwed than I would.

I don’t have anything publically accesible on my network (other than wireguard), but if I did I’d just put whatever it was on its own VLAN, run a wireguard server on it, and use a VPS as a reverse proxy that connects to it.

I only use unprivileged LXCs and everything I host on my network runs in its own LXC, so I’m not really worried about someone getting access to the host from there.

I occasionally get this same thing, or it’ll render one frame of SDDM and then freeze on that frame, and I’ve also never been able to fix it. I’m on CachyOS with an RTX 2080.

I just bought a 7900 XTX that I’m waiting to be shipped, so I wonder if it’ll go away with an AMD GPU.

Truly one of the most embarassing things I have ever seen someone share publically.

Over polite comments responding to an opinion about a video game.

For me it has always just defaulted to the left-most monitor. I had a script that would disable that monitor with xrandr when sddm loaded and then re-enable it on logon, but I couldn’t get something similar working in Wayland.

What is sketchy about downloading a torrent that it could save you from? Wouldn’t it be executing whatever you downloaded on another machine that would be the risky part?

lol I would open every port on my router and route them all to wireguard before I would ever consider doing this

Plus in Linux you can actually fix this with a live USB, while on Windows you can run startup repair and hope for the best.

The power is out and my laptop has less than 10% battery left?

It’s pacman -Syu time.

I use notifications in Thunder and I’ve had no issues. I haven’t compared the difference or anything, but when I’ve happened to check battery usage it’s always been a reasonable amount for how much I’ve used it that day. It does generate a decent amount of network traffic since it’s regularly checking with you instance for it, and that traffic is generated for each account you have reaching out to each instance. That should be how any FOSS app works though, the alternative would be something like Sync where you pay to have actual pushes sent from their server.

I did this once to install a different distro on a free oracle VPS lol

My theory is that the RTSP port (554) is for streaming and that when I go to the local address (that is on 80), the site ITSELF initiates a connection to port 554 in the background. However, this apparently does not happen when I connect remotely.

I think you’re on the right track here. The DVR is probably telling your browser to connect to http://192.168.1.222:554 for the stream, which on LAN is fine because you have a route to 192.168.1.222, but when connecting externally you won’t be able to get to 192.168.1.222.

You can probably check the network connections in dev tools in the browser to confirm that.