Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2025 Poal.co

1.0K

For anyone who is using the Mailspring-Libre package (especially on Arch or Arch based distributions) and found your client no longer launches and spews out this kind of error in the terminal:

{"error":null} Error Downloading Update: Unexpected token < in JSON at position 0 Failed to get crash dump id. Report Id: Failed to get crash dump id. Report Id:

The problem appears to be with a recent update to the gtk3 package and downgrading to the last known working version (1:3.24.26) gets Mailspring working again.

For anyone who is using the Mailspring-Libre package (especially on Arch or Arch based distributions) and found your client no longer launches and spews out this kind of error in the terminal: >{"error":null} Error Downloading Update: Unexpected token < in JSON at position 0 Failed to get crash dump id. Report Id: Failed to get crash dump id. Report Id: The problem appears to be with a recent update to the gtk3 package and downgrading to the last known working version (1:3.24.26) gets Mailspring working again.

(post is archived)

[–] • 1 pt

Shit like that is what stops me from using rolling releases

[–] • 0 pt

Well, they've released a new version of gtk3 that fixes that issue. Just the price of being on the bleeding edge, I guess. Or in my case, on the testing branch.