mautrix-signal: 0.7.3 -> 0.7.4

[Ma27]

cc @niklaskorz

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[niklaskorz]

Getting:

Dec 22 21:42:53 korz-tech mautrix-signal[440803]: runtime/cgo: pthread_create failed: Permission denied
Dec 22 21:42:53 korz-tech mautrix-signal[440803]: SIGABRT: abort

I think the mautrix-signal module's systemd settings need adjustments.

Another note: libsignal-ffi should probably move to useFetchCargoVendor instead of updating the Cargo.lock. But to not cause conflicts with the backport for 24.05 it might be best to just wait until the next update for that change (useFetchCargoVendor has been backported to 24.11 but not 24.05 I think?).

[Ma27]

I think the mautrix-signal module's systemd settings need adjustments.

Right, I use my own module, hence I didn't encounter that (sent messages successfully with that update already).
Sometimes systemd writes into the journal (and dmesg) what triggered this, so you may wantt o check.

[niklaskorz]

I forgot the module change in #358785 and was running on the unchanged 24.11 module. Added backport labels to #358785 so the update does not break 24.05 and 24.11 modules.

[nix-backports]

Backport failed for release-24.05, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release-24.05
git worktree add -d .worktree/backport-367446-to-release-24.05 origin/release-24.05
cd .worktree/backport-367446-to-release-24.05
git switch --create backport-367446-to-release-24.05
git cherry-pick -x ad10a09e5a782212423e929986d533d7a0a5c707 70952477bf555847126f3e0bfe7027eaaf19f813

[nix-backports]

Successfully created backport PR for release-24.11:

• [Backport release-24.11] mautrix-signal: 0.7.3 -> 0.7.4 #369165