[Linux] Newly updated 6.46.0 (latest) still ask for update

[wargreen]

Using a supported version?

• [X] I have searched searched open and closed issues for duplicates.
• [X] I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.

Overall summary

After upgrade to 6.46.0 from official repo, signal still ask for upgrade.

Steps to reproduce

Upgrade from 6.39.0 to 6.46.0 via apt.

Expected result

Able to talk with latest version.

Actual result

Can't talk, ask for upgrade with latest version...

Screenshots

Signal version

6.46.0

Operating system

Debian SID

Version of Signal on your phone

6.41.3

Link to debug log

https://debuglogs.org/desktop/6.46.0/2b21eafa19b511ae6eb8e8d5fc20dba5ac3065b517bc5a6bc8a48b718c27d4db.gz

[scottnonnenberg-signal]

I'm sorry this is happening to you. Please provide a debug log, so we can see what's going on.

[wargreen]

Original post updated. I've think that debug log is only generated when a crash happen. Thank's !

[scottnonnenberg-signal]

Your log shows that you did get a 499 from the server, telling you that your Desktop was too old. What we don't see in the log is Desktop starting up and detecting that its version changed, so that server expiration was not reset:

ERROR 2024-02-05T17:31:59.008Z Got 499 from Signal Server. Build is expired.
// No mention of 'new version detected'
INFO  2024-02-05T19:15:02.914Z starting version 6.46.0
INFO  2024-02-05T19:22:43.781Z starting version 6.46.0
INFO  2024-02-05T19:26:26.919Z starting version 6.46.0
INFO  2024-02-05T20:17:26.121Z starting version 6.46.0
INFO  2024-02-05T20:54:08.417Z starting version 6.46.0

Can you talk about what exactly happened with this Desktop instance? It seems like maybe something crashed, and we don't have logs for it? I do see this in the log:

WARN  2024-02-05T19:15:02.917Z MainSQL: Database log code=283: recovered 88 frames from WAL file [REDACTED]/sql/db.sqlite-wal

[teizz]

I can confirm I have the same issue on MacOS Intel build:

~> grep -E 'version|expire' ~/Library/Application\ Support/Signal/logs/{main.log,app.log}
main.log:{"level":30,"time":"2024-02-05T23:41:15.796Z","msg":"starting version 6.46.0"}
main.log:{"level":30,"time":"2024-02-05T23:41:15.865Z","msg":"MainSQL: updateSchema:\n  Current user_version: 980;\n  Most recent db schema: 980;\n  SQLite version: 3.42.0;\n  SQLCipher version: 4.5.5 community;\n  (deprecated) schema_version: 439;\n"}
app.log:{"level":30,"time":"2024-02-05T23:41:17.099Z","msg":"@signalapp/libsignal-client Initializing libsignal version:0.39.1 signal_node::logging rust/bridge/node/src/logging.rs:133"}
app.log:{"level":30,"time":"2024-02-05T23:41:17.302Z","msg":"Starting background data migration. Target version: 11"}
app.log:{"level":30,"time":"2024-02-05T23:41:18.564Z","msg":"Build expires (remote): 2024-02-05T22:32:34.691Z"}
app.log:{"level":30,"time":"2024-02-05T23:41:19.597Z","msg":"checkExpiringMessages: found no messages to expire"}
app.log:{"level":30,"time":"2024-02-05T23:41:24.426Z","msg":"checkExpiringMessages: found no messages to expire"}

main.log says I'm on the latest version, app.log says the build expired right before I started it. All I did was update to the latest version when it asked me to. No crashes.

[scottnonnenberg-signal]

@teizz A full log would better help us understand what's going on. Thanks!

[jivandabeast]

Can confirm i have the same issue! Not sure where to get logs though

[dpflug]

Can confirm i have the same issue! Not sure where to get logs though

If you launch the program, you'll find the option in the View menu.

I'm also affected by this. Here's my debug log: debuglog.txt

[scottnonnenberg-signal]

To get debug logs: open the View menu, then select the Debug Logs option. Copy and paste the resultant URL here. Thanks!

[teizz]

👍 https://debuglogs.org/desktop/6.46.0/51a979c93de4f96d384514a04b84cf100134502c5f4a9ac48fb91ea7f29c2aa3.gz

I may or may not have deleted my logs from prior (I did) 😳.

These lines are amusing though:

INFO  2024-02-06T18:27:06.319Z Build expires (remote): 2024-02-05T22:32:34.691Z
INFO  2024-02-06T18:27:06.349Z createHTTPSAgent.createConnection(updates2.signal.org): connected to IPv4 addr after 39ms (attempts v4=1 v6=0)
INFO  2024-02-06T18:27:06.375Z checkForUpdates: 6.46.0 is not newer than 6.46.0; no new update available

I did turn off IPv6 since it was using that before... Just in case it routes to a different server that's feeling under the weather... no joy.

[scottnonnenberg-signal]

@teizz Yep, unfortunately your log doesn't have the history we're looking for. There was no capture of the initial discovery that it was expired fom the server, just this:

INFO  2024-02-06T18:27:04.181Z starting version 6.46.0
INFO  2024-02-06T18:27:06.319Z Build expires (remote): 2024-02-05T22:32:34.691Z
INFO  2024-02-06T18:33:13.917Z starting version 6.46.0
INFO  2024-02-06T18:33:16.222Z Build expires (remote): 2024-02-05T22:32:34.691Z

[scottnonnenberg-signal]

All, we do have a workaround for you - if you install 6.45.0 and start up, it should fix things. And if that doesn't fix things, when that auto-updates to 6.46.0 again, it will have another opportunity to fix things.

You can install 6.45.0 from apt on linux, or by using these links on the other platforms:

macOS: https://updates.signal.org/desktop/signal-desktop-mac-universal-6.45.0.dmg Windows: https://updates.signal.org/desktop/signal-desktop-win-6.45.0.exe

[wargreen]

I can confirm that downgrade to 6.45.0, start signal then re-upgrade to 4.46.0 fix the issue.

Thank you !

[teizz]

@scottnonnenberg-signal I was afraid that might be the case. Down + Upgrade worked though... Here's the debug log for that if that's any help: https://debuglogs.org/desktop/6.46.0/8fce68aa64c2b5179eba3474cd17fae2a2572fcde2c1a2a9d1ad76bd6abf4158.gz

I guess wiping everything in "Application Support" on MacOS or Linux equivalent folder would have solved the issue too while getting rid of any hisotry too... the workaround is appreciated.

[jivandabeast]

The downgrade & re-upgrade worked perfectly, thanks!

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been closed due to inactivity.