`Could no send: libsignal-service error: Protocol error: protobuf encoding was invalid`

[samuela]

Got this error trying to send a message. Nothing particularly out of ordinary leading up to the error AFAICT.

[mwillfox]

Experiencing the same issue, I cannot send messages. Gurk still receives the messages fine, though.

[gclarkjr5]

I received this issue after using whats available from nixpkgs which was not the latest release 0.8.0. I think maybe 0.6.4..? After upgrading to 0.8.0, this error was gone. Outgoing messages work just fine, but incoming messages do not work now. It seems to maybe be an encrypt/decrypt, or certs issue stemming from libsignal_service.

[mattkang]

@gclarkjr5 0.8.0 is on nixpkgs-unstable FYI

[samuela]

Using latest nixpkgs-unstable as of NixOS/nixpkgs@13868c0 gives me

Error: failed to load config

Caused by:
    TOML parse error at line 5, column 17
      |
    5 | notifications = true
      |                 ^^^^
    invalid type: boolean `true`, expected struct NotificationConfig

[mattkang]

Using latest nixpkgs-unstable as of NixOS/nixpkgs@13868c0 gives me

Error: failed to load config

Caused by:
    TOML parse error at line 5, column 17
      |
    5 | notifications = true
      |                 ^^^^
    invalid type: boolean `true`, expected struct NotificationConfig

@samuela just delete that line in the TOML

[boxdot]

Incoming messages should be fixed in 0.8.1 now.

[dimpase]

Using latest nixpkgs-unstable as of NixOS/nixpkgs@13868c0 gives me

Error: failed to load config

Caused by:
    TOML parse error at line 5, column 17
      |
    5 | notifications = true
      |                 ^^^^
    invalid type: boolean `true`, expected struct NotificationConfig

@samuela just delete that line in the TOML

sorry, what TOML do you mean? I see the same error in cabal-installed latest version, as well as in v0.8.1. But where does it come from?

[hexadecimalDinosaur]

the config file format completely changed between 0.6.4 and 0.8.0

[dimpase]

do you mean to say there is a stale config file somewhere which breaks the thing?

[hexadecimalDinosaur]

do you mean to say there is a stale config file somewhere which breaks the thing?

yes, the new version fails to parse the old config files

[dimpase]

Oh, oops, there is stuff in ~/.config/gurk/ --- I thought everything is in ~/.cargo/...

That's very unusual - at least for someone without working knowledge of Rust - to see obviously runtime configs breaking the building process. I'd have understood the issue if it happened at start up time, not during the build time.