SpaceCadet

Move your .weechat directory out of the way, to see if the problem is in your profile or with the weechat installation itself.

I don't think that's the case anymore.

I just checked, the time in the UEFI BIOS is in UTC, yet both Linux and Windows 10 display the local time correctly as an offset to UTC. I didn't have to do anything special for that.

Edit:

So I looked a bit deeper into it, and this is apparently controlled by a registry key called RealTimeIsUniversal in [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation]. You can paste the text below in a .reg file and then import it to set the parameter:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation]
"RealTimeIsUniversal"=dword:00000001

I confirmed that this setting exists on my system, but I have no memory of ever manually setting this parameter. It's documented in the Arch wiki though, so it's possible that I did set it and forgot about it.

In any case, if you do a fresh Windows install and your time differs between Linux and Windows , this is what you should check.

I'm blaming it for making it a pain in the ass to debug dependency problems and for having the confusing, non-intuitive, overly verbose and redundant syntax that probably caused the problem in the first place.

Like, who the hell can memorize all the subtle differences in behavior between After=, Requires=, Wants=, Requisite=, BindsTo=, PartOf=, UpHolds= and then all their "reverse" equivalents?

Everybody gangsta until A start job is running for ... (10s / 1min 30s)

Thanks for summarizing my feelings on systemd in a less inflammatory way than if I had written it myself.

I've found that most distributions have implemented it properly and for the most part it works quite well and stays out of my way, it's only when for some reason you have to dive into the minutiae of a unit file and getting into all the dependencies and stuff that it gets annoying quickly.