[#69] Shutdown at new ID choice ?

Description

I've got a weird problem. I just tried to connect to

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 previously registered or no.

So far, I tried [UPDATE in 1st comment !]:

• Stopping the "use on this page" (for both certificates)
• Updating Lagrange to v1.17.6from v1.17.5
• Restarting following the above

Debug Info

System

Windows 10 Pro Version 22H2

Lagrange Version

- Version 1.17.5

- Version 1.17.6

station.martinrue.com

Idx |   Cache |   Memory | SP% | URL
----+---------+----------+-----+-----
  2 |      -- |       -- |   0 | gemini://station.martinrue.com/arubes/notifications
  1 |      -- |       -- |   0 | gemini://station.martinrue.com/arubes/
  0 |      -- |       -- |   0 | gemini://station.martinrue.com/

Total cached data: 0.000 MB

Total memory usage: 0.000 MB

Navigation position: 0

On Windows (as an admin), I try the following using CMD, PS and ConEmu:

 lagrange gemini:\\station.martinrue.com\ --dump

But nothing happens. Neither a printed message nor a file gets generated.

The same for

lagrange -V
lagrange --help

#bug ✔︎ #Station #Windows10

2024-01-17 · 2 years ago

5 Comments ↓

[Update & Clarification]

It just occured to me to check this behaviour on other sites, It's probably a Lagrange thing becuase this happens on Astrobotany, too, only this time, in reverse !

To be clear: my newer ID is the default one connected, choosing to Not use it also kills the process !

It seems that this happens regardless of choosing whether to Use or to Not Use.

I think I was not clear on the original post. The older ID doesn't seem to be the source of the problem.

So you're saying that whenever you activate or deactivate an identity, the app crashes?

Are all of your identities created in Lagrange or did you import the client certificates from elsewhere?

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.

Yes, basically.

Closing as obsolete. At least this doesn't seem like a widespread issue.