lyse
lyse.isobeef.org
No description provided.
No description provided.
org.kde.pim.webengineviewer: WebEngine render process crashed
being printed to stdout.
Looking at the Qt WebEngine docs on debugging helped: QTWEBENGINE_CHROMIUM_FLAGS="--single-process" kmail
surpringly works… O_o WTF. This goes in the /usr/local/bin/kmail wrapper script then.
Bloody hell, my system update affected the libc, libc6, locales and golang-1.19 packages and after a reboot KMail is fucked. Uses 100% CPU and doesn’t show any mail texts anymore. Starting it in a terminal then shows heaps of org.kde.pim.webengineviewer: WebEngine render process crashed
being printed to stdout.
https://bugreports.qt.io/browse/QTBUG-73293 Closed as invalid.
https://bugs.archlinux.org/task/61534 suggests to QTWEBENGINE_CHROMIUM_FLAGS="--enable-logging --v=3" kmail
, unfortunately, nothing useful shows up:
[32957:1:0813/153712.828577:VERBOSE1:sandbox_linux.cc(69)] Activated seccomp-bpf sandbox for process type: renderer.
[32491:32555:0813/153712.854714:VERBOSE1:gles2_cmd_decoder.cc(3850)] GL_EXT_packed_depth_stencil supported.
org.kde.pim.webengineviewer: WebEngine render process crashed
Why is there not a single decent e-mail program out there? Anybody using only mutt?
@prologic@twtxt.net I reckon pretty much the same like you did. I haven’t looked at this OpenAI API, in case it is simple enough, I would probably not have used their client library, though. Again, no idea if that would be feasible. I like WTFPL and even got a proper answer when trying to ask about it on your demo. ;-)
@prologic@twtxt.net No doubt about that. Typing them up took me pretty much exactly an hour each. ;-) Thanks, bookmarked!
@movq@www.uninformativ.de Absolutely. It’s more blurry than you probably hoped for, though.
@movq@www.uninformativ.de Mate, this looks fantastic! :-D
seq
despite not being part of POSIX
* Spam prevention on Yarn pods
* Subreply, another alternative microblogging service
@mckinley@twtxt.net Cool. Do you plan on writing an article on your time shell script? I was quite happy to see basically simple (in practice could be more complicated) things like this cobbled together in a short time. The script itself would also suffice, but maythere there is more to tell. :-)
@xuu@txt.sour.is Yup, metrics are a different story. Need to take a deeper look at them some day. With logs I meant analyzing why requests could not be processed. It’s not necessarily the actual service that has a problem.
@off_grid_living@twtxt.net Wow, that’s a lot! On the other hand, your garden is also large. Overall progress is looking great. Soon, your only worry is rodents.
@prologic@twtxt.net Exactly, errors are part of the interfaces. The only problem is that I cannot formally express it in detail so that the Go compiler would give me any hints or step on my foot. Java’s checked exceptions are a mess, too. So, no idea how to solve that in an ideal world.