=> Re: "Shutdown at new ID choice ?" | In: s/Lagrange-Issues
But nothing happens. Neither a printed message nor a file gets generated.
This is because the app has been built as a GUI application and it thus does not by default have access to the console stdout/stderr where it was started. Unfortunately, this means on Windows you don't get console output unless you build the app yourself in MSYS2.
To fix this issue, I would have to add some new Windows-specific log output code.
2024-01-18 · 1 year ago
=> 🦥 aRubes [OP] · 2024-01-22 at 00:55:
Yes, basically.
Description I've got a weird problem. I just tried to connect to [gemini link] root Station page after a long absence. I get error 62 Invalid Certificate. When I choose the newer one Lagrange unexpectedly shuts down. Assumptions I assume that I forgot to switch Station to my newer client certificate. The older one expired on December 31st. However, it is possible that I did not forget ! Expected Behaviour Succesfull choice of the ID for the entire domain without a shutdown, whether it was...
=> 💬 aRubes · 4 comments · 2024-01-17 · 1 year ago · #bug #Station #Windows10 This content has been proxied by September (3851b).Proxy Information
text/gemini; charset=utf-8