I agree.
she/they
I agree.
If your build fails because you can’t track down the literal ≠
in the code I would recommend just looking at the compiler error. I understand the concerns about ==
vs =
more but the vast majority of LSPs (and some compilers) will catch that too.
I have also yet to see any IDE enable ligatures by default, at least VS Code and the JetBrains suite both require opting into them even though their default fonts support them.
The GDPR conversation is hilarious. Sure they’re a US based company, but after 5 years of operation I would’ve expected them to have consulted a lawyer about this at some point. Forgetting (assuming it’s not “forgetting”) about the required documentation is not the worst thing in the world morally but it doesn’t exactly make them look competent either.
Indeed, that all looks fairly innocuous. Just in case, you are sure that you didn’t just accidentially kill
or killall
rclone or bash?
Perhaps wrapping the script in strace
might help debug where the offending signal is coming from.
TimeoutStopSec
applies to the ExecStop
command, TimeoutStartSec
would be the culprit here. I’m not sure why there would be a default timeout of specifically 1:39 minutes though.
Does your script fork at some point (and might exit before the rsync job is completed)? Because then you need to use Type=forking
instead of simple
or oneshot
, otherwise systemd will start trying to clean up child processes when the script exits.
Edit: Actually considering the time span involved Type=forking
will not solve your issue because it will timeout, if this is the problem you need to change your script to not do that.
While unfortunate, not shipping these standard Google apps is not really an option for any Android manufacturer due to Google requirements. Including them is required if you want to use anything from the GSM, which includes things like the Play Store and everything it touches. You can technically ship a different Android distribution like Lineage or /e/, but that’s not really what most people will be expecting of an “Android” phone and will narrow the viable target demographic even more than the value proposition already does.
I’m running KDE Plasma with the revived Krohnkite for auto tiling. Plasma 6.2 seems to have fixed most of the bugs from 6.0 and 6.1, at least the ones I’ve noticed.
I was using Sway/SwayFX for a few months but was missing some KDE Gear apps like Dolphin and Okular which I couldn’t get to display correctly. KDE is afaik the only desktop with a working Qt theming engine right now, so I can’t really see myself switching (unless maybe if they break Krohnkite again).