Change:
buildInputs = [ libjpeg openssl libopus ffmpeg alsa-lib libpulseaudio protobuf <del> xorg.libX11 libXtst libXcomposite libXdamage libXext libXrender libXrandr </del> <ins> openh264 usrsctp libevent libvpx libX11 libXtst libXcomposite libXdamage libXext libXrender libXrandr libXi </ins> glib abseil-cpp pcre util-linuxMinimal libselinux libsepol pipewire <del> libXi </del> ]; cmakeFlags = [ <del> # Building as a shared library isn't officially supported and currently broken: </del> <ins> # Building as a shared library isn't officially supported and may break at any time. </ins> "-DBUILD_SHARED_LIBS=OFF" ]; <del> meta.license = lib.licenses.bsd3; </del> <ins> propagatedBuildInputs = [ # Required for linking downstream binaries. abseil-cpp openh264 usrsctp libevent libvpx ]; meta = with lib; { license = licenses.bsd3; maintainers = with maintainers; [ oxalica ]; }; </ins> }

Discussion:
Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: telegram desktop yourself from another account or make a call call crashes Expected behavior Calling works Screenshots Logs Additional context Error in webrtc library Notify maintainers Metadata Please run and paste the result. Maintainer information:
I debuged the issue and found that disabling RTCDCHECKIS_ON fixes the issue (also building in release but it's autoconf so I'm not touching it) Another idea which I'm currently working on is libtgvoip upgrade, as it seems that it wasn't updated since forever (1 year) and the new version has CMake, which automatically gets built as arelease build tdesktop doesn't like the new version
I completely forgot about that package (but I'm not maintaining it so that makes sense :D), sounds like it's time to add an update script for Telegram-Desktop to keep the dependencies in sync. Looking at Telegram-Desktop 2.7.5 currently depends on so maybe that version will work?
CMake seems to be introduced with the very latest commit, so this version doesn't have it yet. Another solution prob is to build libtgvoip in release mode (whatever that is in autotools)
Exactly the same issue as well.
I've just updated Telegram-Desktop to version 2.8.0 including it's dependencies. I wouldn't be surprised if it's still broken though. This issue might also be related to (packaging WebRTC in Nixpkgs is unfortunately extremely difficult, see ).
I have the same issue btw, in group calls.
Same issue with Telegram 2.8.1... <details</details
Hey, I am a bit of a NixOS noob, so excuse my dumb question. How could I apply this patch locally without recompiling the whole repo? I use telegram voice calls to talk with friends and I really need this to work. Thank you very much for your understanding.
should help with that. Personally I'd recommend git-clone + nix-shell/"nix run" but there are different approaches (so choose whatever fits your setup/workflow the best).
I tried the patch from on master (, tdesktop 2.8.1).

The original error message is gone, but it still crashed with different error messages when joining a chat room or starting a personal phone call. Note that I didn't have a microphone on my PC, but I'm able to listen-only before. Tested with pulseaudio-only and pipewire-only but with no luck. Start a personal phone call: Entering a group chat:
I encounter the same issue when joining a chat, after applying the patch. I built from (but replaced the telegram and with version 2.8.1), because did not want to compile for me.
is interesting. That should normally only happen if your CPU doesn't support some instruction set extension that (?) requires by default. Could you also paste the output of ? If this instruction comes from (a stack trace might be helpful to track down the source) then we could patch the source to avoid the extension set (a quick grep though the source-code reveals a lot of such conditionals). Edit: Forgot to mention: The instruction could obviously also come from libtgviop or Telegram-Desktop (bundles a lot of 3rd party libraries). A stack trace might be required to track it down (vs. looking though all sources).
Last time we had such crashes with calls it was because webRTC was missing. Instead of packaging vanilla the telegram webRTC fork was packaged. Is that still the case? Also are we building everything as a release and not debug build? The google groups post I linked in the first comment is mentioning that building in release should also fix that issue. Might it be that? Esp with libtgvoip I'm not sure if that flag is enabled
Hi! Sorry for not responding, I was away for a moment. This is the backtrace from gdb. FYI: If you really need voice calls to work you can use the flatpack version on Telegram, there it works no problem.
A funny backtrace. Firstly it calls webrtc functions from tgowt, at the medium of the backtrace it starts to use libtgvoip's webrtcdsp and then it uses destructors from tgowt, again. I don't think two copies of the same library of different versions could really co-exist in one address namespace. Maintainer should allow tdesktop to use bundled libtgvoip that links to tgowt.

could you elaborate what you mean by this? Does that mean we in Nixpkgs should use the bundled from Telegram-Desktop instead of the packaged in Nixpkgs (which is based on the same commit/version)?
Yeah, the difference is that bundled one links to tg_owt while nixpkgs one has its own copy of webrtc
Currently and are both packaged in nixpkgs. But do they really need to be separated packaged? They are only used by .
I guess packaging was required at some point but since says so we can certainly drop it. A PR would be welcome. AFAIK isn't bundled by Telegram-Desktop so that package is likely still required.
libtgvoip was never required, I packaged it for kotatogram at the time when there were no tg_owt and there were no problems with packaged libtgvoip. However, the only working way is using bundled libtgvoip now (or to patch libtgvoip's build scripts). Packaged libtgvoip could still be used for e.g. packaging (if they still using it) with calls support. But the package is here for quite long time and no of other packages started to use it, so maybe it's a good idea to drop it...
Thank you very much for your fix! Telegram desktop now works flawlessly (from the master branch)!
Would be nice to have in !