Yeah, although Cockpit is a web UI thing, while systemd pilot looks like a proper GTK app.

If you absolutely have to scan a face, apparently this works: nofacescan.app

So it seems I was wrong about Cloudflare having seperate prefixes for WAF and workers. And these are all WAF/workers IPs (but not warp). My guess is that someone’s made themselves a http proxy worker, and are using that to proxy their bot’s requests.

What’s the IPv4? I believe Cloudflare has different prefixes for WAF, warp, and workers.

2a06:98c0:3600::103 is definitely a Cloudflare WAF IP, so my guess is someone using either warp or workers is sending requests and added that IP to X-Forwarded-For as a red herring.

Switching ttys wouldn’t have done anything. The kernel logs are usually saved to efi_pstore (or sometimes erst) by default though.

Edit: you can also set drm.panic_screen=kmsg as a kernel parameter to print the logs instead of the QR.

Nah, when a kernel panic hits then everything’s screwed.

Pressing ESC does work for systemd-bsod (which is different) and as you mentioned Plymouth; but not drm_panic.

Edit: yes, it was Systemd who implemented it.

Nah, systemd-bsod is different and designed to show info about boot failures:

It’s rather quite useless.

drm_panic on the other hand has nothing to do with systemd, and is what’s shown in OPs post. The link can be quite useful for users to post their issues on bug reports or whatever. But if you know what you’re doing, then it’s pretty easy to configure it to print text instead.

Also remember, the reason drm_panic exists is because graphical outputs would otherwise freeze during a kernel panic, and not show anything useful.

This probably isn’t too useful for you as they only have 24v and 54v models, but Ubiquiti used to make EdgePower UPSes. They have a http management interface that lets you monitor the power usage or power cycle the router if a ping stops responding, and etc. I installed one recently for a POE switch of mine.

Regarding Google Coral, from the docs: https://docs.frigate.video/frigate/hardware

The Coral is no longer recommended for new Frigate installations, except in deployments with particularly low power requirements or hardware incapable of utilizing alternative AI accelerators for object detection. Instead, we suggest using one of the numerous other supported object detectors. Frigate will continue to provide support for the Coral TPU for as long as practicably possible given its still one of the most power-efficient devices for executing object detection models.

Personally, I’d recommend OpenVINO. It works on iGPUs, and if that’s not possible it’s quite performant on CPUs. I currently run a Google Coral and the Linux driver is no longer officially maintained meaning it breaks every now and then after a kernel update, next time it breaks I’m going with OpenVINO.

Also, I’d install Docker in an LXC for Frigate, it makes passing the iGPU through to it a lot easier.

Can confirm it does:

OrgAbuseHandle: ABUSE9107-ARIN
OrgAbuseName:   ABUSE
OrgAbusePhone:  +1-313-516-8908
OrgAbuseEmail:  abuse@hostodo.com
OrgAbuseRef:    https://rdap.arin.net/registry/entity/ABUSE9107-ARIN

I believe OP would require an authoritative DNS server, which AFAIK Quad9 is not. desec.io would be my recommendation though.

The data included a transcript of all messenger messages.

Not to defend Facebook, but it would be weird if they didn’t, since you can use messenger on any device, and it’s obviously saved on their servers. A transcript of WhatsApp messages would’ve been different though, as they say they can’t read them.

No doubt it’s worse now.

Yeah definitely, and they’re probably hiding some the data too.

Systemd can also create a temporary user, with DynamicUser. But I so very rarely see that being used.

the service would start as root to do privileged operations like opening specific ports

You can also add the CAP_NET_BIND_SERVICE capability to do this without root.

IMO, there’s usually no reason to use root in a systemd service, it’s just ignorant developers.

I haven’t properly used Windows in a long time, but I have a feeling the disk checking might be caused by fast startup. Basically Windows hibernates instead of fully shutting down, and the disk should never be touched while hibernated. But if you have the NTFS partition mounted in Linux, then it touches the disk anyway.

Is fast startup enabled in Windows? If so, try disabling it. It also isn’t needed on SSDs and does more harm than good.

I can dig it…but surely the simple option is to have the PC wake up on power restoration, right?

After the PC shuts down, the UPS runtime will increase by a lot. So the power might come back before the UPS turns off, so as far as the PC can see, the power was never lost.

Edit: Also I assumed you meant restore on after AC loss, and not the last state.

What type of SSD? NVMe usually has a special instruction which will reset each whole NAND chip, and usually takes a few seconds. I think SATA does as well, but it’s not commonly supported.

Also kernel 6.12 has support until 2035, so it’s not like anyone running these CPUs would be missing out on security updates for a while.

Personally, when I get a new SSD I:

• Format as 4Kn (for ‘Better’ or ‘Best’ performance)
• Reinstall my preferred distro with a seperate home subvolume/partition (and tmp, var, etc. often with nodev,nosuid,noexec set)
• Copy my /home across, and parts of /etc.

The <noscript> messages seem to work for me with uBO.

I’ve got a Framework 13 7840U and I’ve never had issues with S0ix sleep. Very early on, apparently the keyboard would spuriously wake the laptop, but that’s been fixed for years now, and I’ve never noticed it.

On some other (non-Framework) laptops you can enable S3 using Smokeless_UMAF, but it just results in a black screen on resume for mine.