u/PingMyHeart

I genuinely do not understand why Proxmox still feels like a second class citizen when it comes to Frigate.

I love Frigate. I love Proxmox. But trying to run the two together always turns into a headache, even though a massive amount of homelab users run Proxmox.

I have tried:

• VM deployments
• Unprivileged LXC
• Privileged LXC

The only setup that works somewhat consistently is privileged LXC, and even then, updates eventually break something. CPU spikes, hardware acceleration issues, random instability, etc. Everything works great until suddenly it does not.

And before people say "just run bare metal Debian," that completely misses the point. Many of us use Proxmox because it is the foundation of our homelab infrastructure. We are not going to dedicate an entire machine to Frigate when virtualization exists specifically to avoid that.

So why is Proxmox still not officially supported in a meaningful way?

Is it a technical limitation?
A maintenance burden?
Lack of developer interest?

Because at this point, Proxmox is not some obscure niche platform anymore. It is one of the most popular homelab hypervisors out there.

Can we please get proper official support, recommended configurations, or at least a supported deployment path that does not feel fragile after every update?

I love GNOME, I really do, but my gosh does it suck on bleeding edge distros compared to something like Debian.

First, the obvious issue: extensions breaking constantly whenever a new GNOME version drops. Sometimes they stay broken for weeks, sometimes months. For people like me who genuinely enjoy using extensions, it becomes exhausting.

Second, bugs with no real fix in sight. I used GNOME on Fedora Silverblue and Debian without major problems, but the moment I switched to Arch, everything went sideways.

Every time my screen locks, waking it back up hangs the display and I never get the screen back. I found an extension called “Unblank Lock Screen” but it feels like a band aid fix and barely works consistently.

My current “solution” is using GSConnect from my phone every single time I come back to my desktop so I can run systemctl reboot remotely.

Yes, seriously. I have to reboot my desktop from my phone just to use my computer again after it locks.

I still think GNOME is superior to KDE for my workflow and overall design philosophy, but dealing with this kind of stuff in 2026 is ridiculous. There has to be a better way than this.

Back to Debian I go. I’m done with bleeding edge distros.

Hi,

I switched back to Arch about a month ago and I'm running into a frustrating issue with GNOME 50. Every time I lock the screen and walk away for 15-20 minutes or so, the screen stays completely black when I come back and move the mouse. Nothing wakes it up no matter what I do.

I luckily have GS Connect set up (basically KDE Connect for GNOME) so I can send a systemctl reboot command from my phone to get back in, but I'm having to reboot every single time I want to use the computer after it's been locked.

This never happened on the same hardware with Fedora Silverblue or NixOS. The last time I used Arch I was on KDE and didn't have any issues there either.

Any thoughts?

Since upgrading to GNOME 50, I don't see a logout button anymore. What happened to it?

https://preview.redd.it/jxktd53mw70h1.png?width=1152&format=png&auto=webp&s=2214e62cdc5f2c8d7d822da77adac0084592842b

Hi,

Does anyone else launch their browser every now and then and think, "Oh, would you look at that, I’m signed out of my ProtonPass extension," only to sign back in and realize, "Oh wow, my settings got reset too"?

What the heck is going on? Why does this keep happening? It’s not the end of the world, but it’s really annoying when this is the only extension that seems to do it out of all the extensions I use.

I came across this Random Wallpaper extension recently and I gotta say, it's easily one of the actual best extensions available. If you hadn't heard of it, don't feel bad because I didn't either until very recently. If you like random wallpapers, this is for you.

https://extensions.gnome.org/extension/1040/random-wallpaper/

https://github.com/ifl0w/RandomWallpaperGnome3

Hear me out. I had to go to China for over a month, and although I really enjoyed my time there as a tourist eating really good food and getting to enjoy the big cities, I have to say I was underwhelmed by their big tech apps. WeChat, Alipay, and DiDi, which is like their Uber, all look terrible in my opinion. I thought maybe it had something to do with there being no real competition there, but if that were the case, then they would put more effort into the AliExpress app for Western users. Instead, it has a pretty bad design, and even right now on Android 16 it keeps crashing non stop.

So there is my rant for the day. China, if you are reading and listening, please do better with your app user interfaces because they are really ugly and an eye-sore.

AliExpress app is terrible

Not only is the design just awful, but it's constantly crashing on me. I can't even check out without this damn app constantly crashing.

Every other app on my phone works just fine. It's only this one that crashes.

Come on, Ali. You guys can do better than this.

Hi,

I've been getting screen flickering on both of my monitors after upgrading to GNOME 50 on Arch. It's happening on both displays even after lowering the refresh rate.

I was previously using a KVM switch that made it worse, so I removed it completely. I'm now running direct Ugreen VESA certified DP cables straight from my Intel NUC system to the monitors. I've reseated the cables and ruled out loose connections.

The flickering persists on both monitors, so it doesn't seem like a cable or monitor specific issue. Has anyone else on GNOME 50 with Intel graphics seen this? Any ideas what could be causing it?

Hi,

Lately I'm running into permissions nightmares with Syncthing since I have a bit of a complex setup. I can pinpoint what the issue is with Syncthing and frankly I'm a bit over it at this point.

I'm just wondering if there is a better option that doesnt give so much grief with permissions?

The way I am using syncthing is I like to sync my 'Downloads,Documents,Pictures,Music,Video' home folders across all my Linux devices with my NAS being the master sync location.

There's got to be a better way?

Hi,

For decades I used a single monitor setup but recently upgraded to a dual 4K monitor setup around the same time GNOME 48 was current, and honestly, up until now, I am not impressed.

Both monitors are the exact same Samsung model, both use DisplayPort, and both are 4K 144Hz. The physical monitor settings are identical, and the display settings in GNOME are also the same. Yet, for some reason, my primary monitor always looks correct while the secondary monitor’s brightness and colors look noticeably off. Right now it looks like someone cranked up the gamma on the secondary monitor. This might be related to HDR being enabled, but I have no choice but to use HDR because without it the screen is extremely dark.

Is this a known issue in GNOME? If so, what’s causing it? Could it be related to Wayland?

If this is a GNOME problem, I really hope it gets fully addressed in GNOME 51. I was hoping for a fix in GNOME 50 during GNOME 49, and so far, despite other improvements, this remains a major pain point.

Honestly, this issue ruins the daily user experience.

Does anyone have insights or solutions?

Thanks for reading.

Just wondering if anyone else using Signal Messenger from the official repo keeps seeing the loading spinner when trying to select or search for a GIF? Or is it just me?

Hey everyone,

I’m trying to understand what's going on with Proxmox and how it’s managing my LXCs, particularly with services like Tailscale. Let me explain the setup:

I have an unprivileged LXC running Docker for Jellyfin, and Tailscale is also installed on this LXC host. I use Tailscale ACLs to share the node with some friends. While everything usually works fine, I occasionally get messages from my friends saying they can’t connect, even though I haven’t changed anything other than auto updates running from time to time.

Here’s the odd part: when I test my own connection via Tailscale to my Jellyfin server during those times, it works fine for me, but my friends still can’t connect. The pattern I’ve noticed is that things tend to start working again once I reboot either the entire LXC or the Proxmox host itself.

Now, you might be wondering why I’m thinking this is a Proxmox issue. Well, before I migrated from TrueNAS to Proxmox, I never had this problem, and I’ve been experiencing it frequently since the switch. I’m starting to question my setup and wondering if there’s something I’m missing.

My suspicion is that something in the updates might be interfering, whether it’s auto-updates for Docker in the LXC for Jellyfin, automatic Debian LXC updates (which might affect Tailscale), or updates on the Proxmox host itself. Each time the issue happens, restarting seems to fix it temporarily.

So, is there something in how Proxmox works with LXCs that could be causing this issue? Has anyone else had a similar experience?

Any insights would be much appreciated! Thanks!

Hi,

I went to the Chrome Web Store to apply the Nord theme and quickly noticed what appears to be a bug to me, or maybe not.

For example in the image I provided, the tab in focus is Kagi but how the highlighting around the tabs looks, I would expect Kagi to be highlighted and the other 3 tabs to not be highlighted.

Is this a bug?

https://preview.redd.it/k09kxqzu7lyg1.png?width=250&format=png&auto=webp&s=fc5436a8f352c60e31bdfea9f6bc4b91056bb561

Hi,

I just want to pick some brains here about pass keys and password managers.

So, I keep reading that a lot of people like to separate their TOTP codes from their password managers (I don't do this), and I'm just wondering, is the same recommended for pass keys or no?

I'm also curious when enabling a pass key for a specific website, is it best practice to disable the TOTP code for that login, or is it best to keep both?

My aim here is to disable weak points if there are any.

Hi all,

I recently switched from Fedora Silverblue to Arch. On Silverblue I got very used to using Flatpaks, and for anything not available there I would rely on Distrobox.

Now on Arch I am being pretty cautious about how I install things. So far I have stuck to the official repos whenever possible, and used the AUR for anything else. That said, when I got to more sensitive applications like ProtonMail and ProtonPass, I hesitated to install them from the AUR even though packages exist there.

My thinking is that for apps handling very sensitive data, it might be safer to avoid AUR packages unless I am fully confident in auditing them. I have been considering using Distrobox instead and installing official Debian or RPM packages provided by the vendors.

Am I overthinking this, or is this actually a reasonable approach for high trust applications like password managers? Do you treat these differently from other software on Arch, or is careful AUR usage generally considered sufficient?

I would appreciate hearing how others approach this and what best practices you follow.

Hi,

Every now and then I run into a weird issue with a Linux ISO not working, probably something related to my BIOS requiring GPT partitioning and not playing nicely with MBR. Whenever I ask for help, the response is almost always “just use dd.”

I will be honest. I have been using Linux for years and have never once used dd to write a USB OS image. That is why I find this advice confusing. I usually make it clear that I used a tool like Fedora Media Writer.

Does a tool like Fedora Media Writer essentially use dd under the hood anyway? I do not really understand what is so special about dd that makes it the go to solution. Why is it treated as somehow more reliable than GUI image writers like those from Fedora, Pop!_OS, or others?

Hi,

I downloaded the official ISO and wrote it to a USB stick using the Fedora ISO writer. and to my surprise, my BIOS doesn't seem to recognize the USB.

I checked again with a fedora ISO and it detects just fine but for some reason the Debian one isn't working and this brings me back to a problem I had similar to this with a different distro. I think it was EndeavourOS a few years back and the problem was my Intel NUC 12 enthusiast device requires GPT partitioning and doesn't seem to read MBR.

Debian 12 didn't have this problem but for some reason Debian 13 is not being detected so I just thought I would come here and ask if anybody knows if something has changed and if so what can I do to make it work? The only way I made this work with the other distro a few years back was using Ventoy because Ventoy allows you to choose forcefully, GPT or MBR partitioning, but I really don't want to have to use Ventoy.

Any help is appreciated.

Hi,

I have a question about the USB-C display feature that’s expected to release hopefully sometime this year. Does this feature mean I'll have support for dual monitors, or is it limited to just a single monitor?

I currently use a dual monitor setup and so naturally I'm curious. Does anyone have more information on this? Thanks in advance!