Change:
sha256 = "0zp2iydd46analda9cfnbmzdkjphz5m7dynrdj5qdnmq6j3px9fw"; name = "audacity_xdg_paths.patch"; }) <ins> # This is required to make audacity work with nixpkgs’ sqlite # https://github.com/audacity/audacity/pull/1802 rebased onto 3.0.2 ./0001-Use-a-different-approach-to-estimate-the-disk-space-.patch </ins> ]; postPatch = ''

Discussion:
Describe the bug Since the last NixOS upgrade, from 20.09 to 21.05 version, I have this problem with audacity, the same as specified in this forum : “Internal Error at ” It occures after saving a project and quitting the audacity application. and they say the solution migth be : “SQLite must be compiled with SQLITEENABLEDBPAGEVTAB” To Reproduce Steps to reproduce the behavior: ... ... ... Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata Please run and paste the result. these paths will be fetched (0.05 MiB download, 0.28 MiB unpacked): /nix/store/wzach25vwapl3sa6f7gylqank3jhhsin-bash-interactive-4.4-p23-dev copying path '/nix/store/wzach25vwapl3sa6f7gylqank3jhhsin-bash-interactive-4.4-p23-dev' from ''... system: host os: multi-user?: sandbox: version: channels(root): channels(jc): nixpkgs: Maintainer information:
Hello, My problem have been resolved by msackman on Discourse, there : I finally /adapted his solution in my : and it works. I hope it will help thanks
This still is a problem, overriding sqlite should not be necessary. I don’t know if adding the build flag to sqlite globally is a reasonable fix.
OK, thank you for answering. Do you mean it could cause a security issue ? That would be a shame, because it works for me like that. I'm not at home to try anything else on my computer, and anyway not very skillful.
No, I meant that I don’t know if always building sqlite with the required option is acceptable, since it increases the closure size and could theoretically cause breakage in unrelated packages. Adding the build flag to sqlite isn’t very complicated, I’ve already patched it locally in my nixpkgs clone.

I’m just not sure if that is the preferred way of fixing this problem.
I don't think it's a security issue. Based on a cursory reading of however, I do think we shouldn't enable it globally. I dug in a bit, and it seems that it's only used for some optional functionality (or at least optional enough that . Which also leads me to the conclusion that this wouldn't happen with tenacity. Would using tenacity instead of audacity be a workable solution for you?
The requirement has also been removed by Audacity (), which now uses a different method to estimate disk usage. Applying that patch could be an option, I’ll look into that later. I tried tenacity, which fixed the problem, but it didn’t work as reliably as Audacity, so I personally will continue to use the overriden Audacity for now. The reason why I reopened this issue is because I wanted to avoid frustration with people trying to run the audacity package and experiencing this problem. I think the package should be either functional out of the box without requiring to manually override sqlite or be marked as broken.
Just a probably stupid question, but I wonder why not packaging the last audacity version ?
Versions after 3.0.2 implemented telemetry, which many people dislike for privacy reasons. They don’t include telemetry anymore, but that still prompted some users to fork Audacity to tenacity. The decision to not update it until a solution is found was merged here: Some more discussion about it can be found in the NixOS discourse:
OK thank you !