# Binary packaged Ocenaudio segfaults, need help
**URL:** https://discourse.nixos.org/t/binary-packaged-ocenaudio-segfaults-need-help/8697
**Category:** Development
**Created:** [August 22, 2020, 10:05am UTC](https://discourse.nixos.org/t/binary-packaged-ocenaudio-segfaults-need-help/8697 "2020-08-22T10:05:04Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@onny](https://discourse.nixos.org/u/onny)
#### Post date: [August 22, 2020, 10:05am UTC](https://discourse.nixos.org/t/binary-packaged-ocenaudio-segfaults-need-help/8697/1 "2020-08-22T10:05:04Z")
Hey,
I’m new to packaging on NixOS but I already managed to successfully package Ocenaudio audio editor on my NUR repository. Here is the build file [Files · master · onny / nur-packages · GitLab](https://git.project-insanity.org/onny/nur-packages/-/blob/master/pkgs/applications/audio/ocenaudio/default.nix)
Unfortunately it is unable to start and segfaults. I captured the Valgrind debug output here [ocenaudio segfault ($64) · Snippets · GitLab](https://git.project-insanity.org/snippets/64)
What is the best way to debug this issue?
Best regards
Jonas
---
### Author:  [@rph](https://discourse.nixos.org/u/rph)
#### Post date: [October 25, 2026, 5:41am UTC](https://discourse.nixos.org/t/binary-packaged-ocenaudio-segfaults-need-help/8697/2 "2026-10-25T05:41:21Z")
hey @onny sorry to resurrect a necrothread but i noticed that ocenaudio was segfaulting when i recently tried to use the nix package and you’re [listed as the maintainer](https://github.com/NixOS/nixpkgs/blob/922f5432d702aaf638433eb01864813578c2eef8/pkgs/by-name/oc/ocenaudio/package.nix#L69) so figured this might be a good place to break in.
looks like the config checked into nixpkgs is [using the debian ~~13~~ 12 binary release](https://github.com/NixOS/nixpkgs/blob/922f5432d702aaf638433eb01864813578c2eef8/pkgs/by-name/oc/ocenaudio/package.nix#L21) and when i `strace`d it found a pile of libraries missing.
i was able to (quickly) wrap the [current AppImage release](https://www.ocenaudio.com/fileinfo/ocenaudio_appimage.AppImage) and successfully run it locally, so guess I’m wondering if sourcing the `.deb` pkg is intentional and/or needed and if there’s anything I can do to help move a PR along, whether that’s opening one to adjust the existing derivation to depend on the AppImage release, try to inject the necessary deps, or something else?
appreciate the insight. thanks!