Sure, I could suspect it…but how can I try to troubleshoot it? Is there a way to see what blocks the desktop from locking the screen?

Thanks! This is what I’m getting here. If I understand this correctly, this is a list of POSSIBLE inhibitors…not which one was triggered last time blocking the actual suspension right?

WHO            UID  USER    PID   COMM            WHAT                                                                       WHY                                                       >
Libvirt        0    root    77709 libvirtd        shutdown                                                                   Virtual machines need to be saved                         >
ModemManager   0    root    1183  ModemManager    sleep                                                                      ModemManager needs to reset devices                       >
NetworkManager 0    root    1087  NetworkManager  sleep                                                                      NetworkManager needs to turn off networks                 >
UPower         0    root    1896  upowerd         sleep                                                                      Pause device polling                                      >
PowerDevil     1000 timonoj 2165  org_kde_powerde handle-power-key:handle-suspend-key:handle-hibernate-key:handle-lid-switch KDE handles power events                                  >
Screen Locker  1000 timonoj 1878  kwin_wayland    sleep                                                                      Ensuring that the screen gets locked before going to sleep>

6 inhibitors listed.
lines 1-9/9 (END)

Having a second thought about this, it looks like Screen Locker might be the culprit. But I’m not completely sure. I really could see the desktop wasn’t even locked after a whole night. So maybe it failed to trigger? How can I look at…what’s inhibiting the screen from locking, now? Just like suspension, it works when manually triggered with Meta key + L.

Is it called ONN in the UK too? Thanks!

Thanks…yeah that’s the one. I’m not sure where to source it from, either in Europe or in Asia.

Is it possible to make it to only activate when plugged in?

I have a dedicated LXC container called docker where I install all my docker images.

Thanks. I think I might rebuild the pihole-unbound server and try again with this setting.

They also don’t allow country/located results but then in English. Hell, English is one of the legally accepted languages of this country :(

I’m sure familiar with CLI, no worries. I just don’t think a full remote desktop tool which has hundreds of switches/options and needs to go through SSO custom addresses and 2-factor is at its best on CLI mode.

freerdp

So…freerdp does NOT include a GUI…right? Just trying to figure it out. Thanks!

RISCV

Yeah i have the one with the doc feeder. One thing they don’t tell you is that while yeah, you can print double sided no problem, the doc feeder is single-sided no matter what.

Thanks…tvdb extension is indeed installed. Seems the issue derived from the .nfo files having still old crap from S01. That, and the episodes had S02 naming on it, even being the “first” season of Bly Manor. So that messed with Jellyfin…I think it got it correctly identified now, using different folders for each show. But now Sonarr can’t find it, as it wants a single show and folder for both of these :(

I’m also using a brother with ink tanks. So far, very happy. I noticed it auto cleans the heads every other day around noon or so, without asking. So far really happy with its performance, although the Linux implementation for the scanner leaves to be desired, and the windows version is also hit or miss.

Wow…I’ve been reading a bit about the drama involving this guy. It really seems to show that’s the attitude that got him kicked out of TB in the first place. Yeah, I’m gonna steer clear of the “better” bird.

Sorry…what do you mean changing the resolv to the up of the pihole? I’m a bit lost here 😅

Rate limited…by whom? I’m using unbound, so I’m not forwarding my DNS requests to my ISP.

Welp…Not sure what was wrong, but seems to now be resolving again. I…restored a few previous backups to no avail, rebooted to no avail…and after just giving up and upgrading, and rebooting…now it seems to work again. And I still have no idea how to troubleshoot this if it ever happens again :(

I have purposely disabled IPv6 everywhere. Router, Pihole etc. What do you mean which DNS am I using? The computer failing to resolve, or the Pihole that successfully resolves with dig, but somehow fails to actually resolve it to the pihole request/requesting computer?

I use linux, yeah. nameserver is 127.0.0.53 (?). search is pointing to the pihole server.