Closed stuartlangridge closed 9 months ago
Did someone just promote a really old version to stable?
latest/stable: 1.11.0 2023-11-23 (35) 137MB -
latest/candidate: 6.39.1 2023-11-23 (556) 181MB -
Did someone just promote a really old version to stable?
Well, I can certainly confirm that snap refresh --candidate signal-desktop
fixes it, so... it looks like that, maybe. I don't know whether this "1.11.0" version is very old (it doesn't look very old, UI-wise) or some other version or fork or something, but it doesn't work :)
Thanks for filing the issue. Sorry this happened. Not quite how this occurred. I have just (re)pushed revision 554 to stable which is the revision you would have previously been on. My current theory is something went awry with a github action. Will investigate.
I believe it's this: https://github.com/snapcrafters/signal-desktop/issues/201#issuecomment-1824076161 which triggered the problem.
Going to close this as the revision that was promoted has been replaced with the correct revision. Will open a separate issue for why the GH action erroneously suggested to promote an old issue.
What happened?
I closed down the previous version of Signal, which was happily connected to the servers (and was installed from the snap), and I refreshed Signal Desktop to the latest version from the snap, and this latest version does not connect. The UI says "Something went wrong! Failed to connect to server." In the terminal, output contains this repeatedly:
which seems relevant.
What should have happened?
the new 1.11.0 version should have worked, as the previous (up to date) version I was running did ten seconds previously!
Output of
snap info $snap_name
Output of
snap connections $snap_name
Output of
snap version
Relevant log output
No response
Teminal output of app