

printing to a console could enforce a flush, sync thread or other shenanigans.
usually setting a breakpoint would have the same effect and gives me the suggestion of a threading issue.


printing to a console could enforce a flush, sync thread or other shenanigans.
usually setting a breakpoint would have the same effect and gives me the suggestion of a threading issue.
with a car the other person has a licence for it, which comes with the assumption of at least some basic skills operating the device.
Users with computers? Some people really shouldn’t even approach one.
wiggle it until it’s the size of a monitor, and if you’re brave, it’ll take over EVERYTHING.
I love it that KDE didn’t limit the growing of it :)
the last part is one of my biggest annoyances. People just clicking away the dialogs that almost exactly tell what is wrong and at most just say: “yeah of gave me an error but I just clicked it away and it still didn’t work”.
As a software developer, pretty much every error you see I made there for you to either read or screenshot and send to IT, because I had to pretty much implement each one of them. (usually with a standard library, but it’s still a deliberate choice to show it to the user)
Real unexpected errors are hopefully written to logfiles, but that’s not always possible (try logging an error when your system disk is no longer available).
addendum: please also include the gibberish at the end of the error, because its likely there for IT or me to find more details of this specific error in the thousands to millions of things that are logged for the software or website.
on my normal desktop I use the flavor of the day DE, gnome is only used on my 40 inch touchscreen, because its the only one I could imagine being good on a touchscreen
lemmy loop you in: https://infosec.exchange/@ifin/116735279416101129
TL;DR; lots of aur packages got hijacked and install a infostealer, if you updated today/yday, there is a reasonable chance you got hit by it :(
also: the info stealer is installed by aur via npm