# Telegram fails to run: SIGSEGV (Address boundary error)

**URL:** https://discourse.nixos.org/t/telegram-fails-to-run-sigsegv-address-boundary-error/27667
**Category:** Help
**Created:** [April 27, 2023, 6:32pm UTC](https://discourse.nixos.org/t/telegram-fails-to-run-sigsegv-address-boundary-error/27667 "2023-04-27T18:32:50Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![nairou](https://discourse.nixos.org/user_avatar/discourse.nixos.org/nairou/32/9192_2.png) [@nairou](https://discourse.nixos.org/u/nairou)
#### Post date: [April 27, 2023, 6:32pm UTC](https://discourse.nixos.org/t/telegram-fails-to-run-sigsegv-address-boundary-error/27667/1 "2023-04-27T18:32:50Z")

</div>

New NixOS install, using sway (wayland). I have `telegram-desktop` installed via Home Manager.

Attempting to launch telegram gives an immediate crash.

```auto
❯ telegram-desktop
fish: Job 1, 'telegram-desktop' terminated by signal SIGSEGV (Address boundary error)

```

I haven’t been able to find anyone else experiencing this issue, so maybe it’s something I’m missing in my nix configs? Does Telegram require configuration to work under NixOS?

---

<div class="post-metadata">

### Author: ![matklad](https://discourse.nixos.org/user_avatar/discourse.nixos.org/matklad/32/26467_2.png) [@matklad](https://discourse.nixos.org/u/matklad)
#### Post date: [April 27, 2023, 6:48pm UTC](https://discourse.nixos.org/t/telegram-fails-to-run-sigsegv-address-boundary-error/27667/2 "2023-04-27T18:48:56Z")

</div>

Broken by me in [write-qt-apps-hook.sh: use make-binary-wrapper for significant speedups by matklad · Pull Request #225881 · NixOS/nixpkgs · GitHub](https://github.com/NixOS/nixpkgs/pull/225881) and fixed on master by [telegram-desktop: remove crimes by K900 · Pull Request #228410 · NixOS/nixpkgs · GitHub](https://github.com/NixOS/nixpkgs/pull/228410)

---

<div class="post-metadata">

### Author: ![K900](https://discourse.nixos.org/user_avatar/discourse.nixos.org/k900/32/8762_2.png) [@K900](https://discourse.nixos.org/u/K900)
#### Post date: [April 27, 2023, 6:50pm UTC](https://discourse.nixos.org/t/telegram-fails-to-run-sigsegv-address-boundary-error/27667/3 "2023-04-27T18:50:36Z")

</div>

Broken years ago by trying to do crimes to the wrapper, more like, and only exposed just now.

---

<div class="post-metadata">

### Author: ![nairou](https://discourse.nixos.org/user_avatar/discourse.nixos.org/nairou/32/9192_2.png) [@nairou](https://discourse.nixos.org/u/nairou)
#### Post date: [April 27, 2023, 6:58pm UTC](https://discourse.nixos.org/t/telegram-fails-to-run-sigsegv-address-boundary-error/27667/4 "2023-04-27T18:58:33Z")

</div>

Awesome! I’ll wait for that update to trickle down then. Thanks for the quick responses!

---

<div class="post-metadata">

### Author: ![matklad](https://discourse.nixos.org/user_avatar/discourse.nixos.org/matklad/32/26467_2.png) [@matklad](https://discourse.nixos.org/u/matklad)
#### Post date: [April 27, 2023, 7:17pm UTC](https://discourse.nixos.org/t/telegram-fails-to-run-sigsegv-address-boundary-error/27667/5 "2023-04-27T19:17:26Z")

</div>

You can also revert to a slightly older version of nixpkgs for now, it might take a couple of days to get the update in. Eg, if you are using flakes, the following hash should work:

> <https://github.com/matklad/config/blob/d3e812903dd4aece97d3bfba29f74f8f9ef0db67/flake.lock#L9>

---

<div class="post-metadata">

### Author: ![aJWXSLWNVHRrz](https://discourse.nixos.org/letter_avatar_proxy/v4/letter/a/ea5d25/32.png) [@aJWXSLWNVHRrz](https://discourse.nixos.org/u/aJWXSLWNVHRrz)
#### Post date: [April 28, 2023, 1:55am UTC](https://discourse.nixos.org/t/telegram-fails-to-run-sigsegv-address-boundary-error/27667/6 "2023-04-28T01:55:23Z")

</div>

re-reading the whole conversation, like mentioned above, the fix is comming 🙂

already in nixos-unstable-small 🙂

( sorry, i posted a previous comment before the edit without reading everything… goes to teach against quick posting 😛 )