The derivation of creates a different .desktop file from the "official" one that has a different name. This is probably done in order to differentiate the two versions of in case someone installs both of them, but the problem is that while it creates a new one, it doesn't delete the "official" one. Also, the new .desktop file should also set , otherwise games don't launch in Wayland. (Though maybe it should be a wrapper instead) (And, unrelated, but why and not ?) The same also applies to PATH: there are both and (which is a link made by the derivation to in the folder). For consistency, there should be made a , otherwise if both dolphins are installed, one overwrites the other in PATH. Steps to reproduce the behavior: dolphinEmuMaster; an app launcher; are both the original "Dolphin Emulator" and the new "Dolphin Emulator (master)" that open the same app (the master one doesn't set `QTQPAPLATFORM=xcb). PATH there are both and (which is a link). There should only be the "Dolphin Emulator (master)" desktop file, and in PATH there should be only (and instead of ). <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --


After enable HBase module , and rebuild. The service unit cannot start, it says JVM option not exists. Steps to reproduce the behavior: HBase by adding config . , it should be failed. shows VM option is Unrecognized. I found the same issues on the StackOverFlow, it seems jre 15 dropped the option: I fixes this by adding this line, but it should be fixed in module. I can do the fixes PR if you want. Maintainer information:
go for it. I'm also not maintaining this anymore, so may be best to also remove from .


Found in It does build on and . Refs ZHF <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result. Maintainer information:
Is there a general fix for the error? I'm seeing this with (this issue was the only one in nixpkgs that matched that string, sorry if I'm completely off base, I just have no idea where to go on this)


Broken package: 'groove' Install package. Run 'groove-simulator'. File -New Grammar... Try to save, get an exception. system: host os: multi-user?: sandbox: version: channels(maestro): channels(root): nixpkgs: Permalink to broken package: It seems that the broken Nix package depends on OpenJDK17. Found that running their latest version (5.8.1) from SourceForge with the much older OpenJDK8 works just fine. Did not test with OpenJDK11. Probably just have to depend on an older Java version. Package version can also be bumped to 5.8.1. Don't have sufficient knowledge of Nix to fix this myself. Thanks
Probably should be assigned to
I think I've fixed it. I'll submit a PR soon. Also, I tested OpenJDK11 and it crashed there as well.


Project description Pipeable Ruby - forget about grep / sed / awk / wc ... use pure, readable Ruby Metadata homepage URL: source URL: license: mit platforms: ruby
Looks like you got this in


Project description Teapot is an interesting project that implements a compact spreadsheet in roughly 140k, with the following features: UI: Ncurses terminal UI, FLTK windowed GUI, and a batch processing mode all available. Cell Syntax: Cell locations represented as lists of coordinates. Eg, instead of "B1" or "R1C2", cells are referenced as " Three Dimensions: This 3-coordinate style adds a third dimension to the spreadsheet, reducing the need for hiding columns or rows of intermediate results as is sometimes the case in traditional spreadsheets, among other things. Relative References: This also enables both relative cell and relative formula references that make refactoring the spreadsheet easier. Type-Safety: All values have a type, and all operations and formulas check types. No more adding a float to a string and getting a (probably undesirable) result. Iterative Expressions: Modeled on clocked expressions, these solve problems with circular dependencies in traditional spreadsheets and effectively make teapot Turing-complete. Platform-Independent File format: Defined by XDR and portable across machines, especially floating point representation that may differ across platforms Legacy File format support: Portable ASCII file format, standard CSV, SpreadsheetCalculator SC and Lotus 1-2-3 WK1 format. Extensibility: Easily extended by new functions in C. Internationalization: Can be internationalized and comes with English, Dutch, German and Polish message catalogs. Interoperability: Interfaces to troff/tbl, LATEX, HTML and CSV which are well-suited for further processing, be it graphing, typesetting, accounting or anything else. Metadata homepage URL: source URL: (bottom of page) license: GPL3 platforms: unix, linux, darwin
I tried to build this from source, but I'm getting an issue with it. Here is what I did so far, in case someone wants to try it: I am going to try with the deb and see if it works.
I got the deb working successfully (even created a desktop entry for the GUI client, although no icon). I'm going to keep trying with the source today (it is an issue regarding mbslen not being recognized), but if I can't get that, then I will post the working one.
is just a warning, it can be fixed with a simple patch. The more serious problems are compiling with FLTK support and build the docs. Maybe more patches are needed. (On the other hand, it can be useful to package the already-given binary targz.)


The service seems to be executed before the module is loaded, causing automatic modeswitching not to be enabled. The following is seen in the : Restarting after login resolves the problem, as does adding the following to the guest's configuration: Steps to reproduce the behavior: a nix guest with X11 enabled in vmware fusion windowed mode, resize window by dragging appears stretched/blurry or centered in window (dependent on host configuration). Display resolution is automatically switched to match dimensions of window. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Maintainer information:
Hey, I'm no longer using VMware with NixOS, so would be great to find new maintainers for the vmware-guest and open-vm-tools. you've worked on vmware support recently. Would any of you be able and interested in taking over?


shairport-sync module creates the user without a default group, running into enabling causes the following error:


<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on github to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: dstp <!-- The current version can be found easily with the same process than above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 0.3.0 desired version: 0.4.0 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: I'd love to update the package myself without annoying you :) If there is a documentation about how to upgrade packages, i'd love to learn it and try my best next time, thanks in advance!
For simple version updates, I update the version number and to get the new hash I run (in the nixpkgs top directory): For go packages, we also have to update the hash, that one is tricky, and what I do is to try to build the package. That will fail, but it gives us the new hash, I don't know a better way. There is also a bot () creating PR for those simple version updates. It uses repology to find the latest version:
Awesome, thanks!


Project description Tile World 2 Metadata homepage URL: source URL: license: gpl2+ platforms: linux


Project description Graphical application for generating different color variations of a Materia and Oomox themes (GTK2, GTK3 and others), Archdroid, Gnome-Colors, Numix, Papirus, Suru++ icons, and terminal palette. Metadata homepage URL: source URL: license: gpl3 platforms: linux


Project description Cubiomes Viewer provides a graphical interface for the efficient and flexible seed-finding utilities provided by cubiomes and a map viewer for the Minecraft biomes and structure generation. The tool is designed for high performance and supports Minecraft Java Edition main releases 1.0 - 1.18. Metadata what does this mean? homepage URL: source URL: license: GPL-3.0 platforms: Linux


Since won't build () From the above logs: Steps to reproduce the behavior: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Can reproduce on my ZFS system, not on my ext4 system though.
I can't reproduce by running on any system.
I was able to build from that commit nix store is zfs backed
It's more relevant whether is.
The renameat2 syscall used isn't (fully?) supported by ZFS: I'm not sure how that relates to this issue only occurring with , I guess it's related to the sandbox.
/tmp is tmpfs for me
Thanks for filing the upstream issue!


Project description Junction lets you choose the application to open files and links. Junction will pop up automatically when you open a link in a desktop application. Use the mouse or keyboard navigation to choose the application to open the link or file with. Metadata homepage URL: source URL: license: gpl3 platforms: linux


Recently variety stops working on NixOS. Pictures are downloaded well but the wallpaper can't be changed and can only be set in system setting. That's because of the hardcoded shebang which is taken from on the first installation. So when the bash is updated the script can't find it. It should be set as something like . Not sure if this is a nixos bug. Steps to reproduce the behavior: variety bash It works after the bash update. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
IIRC now we use . I am patching it now.


No GNOME Shell Extension can enable desktop icons. . to enable desktop icons. Should be able to enable desktop icons in GNOME Shell, one way or another. About the time of NixOS 20.03, i was still able to have desktop icons using some old version of extension. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
I can confirm this. The systemd journal shows (once every second):
This probably requires patching all paths referencing other libraries or binaries. Which of those extensions shall I have a look at first?
, maybe the one that is easier to fix? I did not have an opportunity to test , so i cannot decide between the two. Thanks!
Haven't had the opportunity to check out any of them so I also cannot decide. Any one of them would be fine for me, so I guess start with the one that is easier to fix (if there is a difference). If I can be of any help let me know.
WIP: I have the following override and the following patch: But I somehow can't get it to find nautilus. It will always end with a null exception while trying to access nautilus stuff (can't copy the stack trace out of the testing VM, sorry).
still not solved :
Made a PR for , a similar technique can be used on the other desktop icon extensions. Would like if someone could test that everything's working. Note the schema path bit, that was causing . For any path you cannot directly list with you most likely need to do the thing (or otherwise find a way to make it find the schema source).


If I only do: then I get virtualbox + nvidia: If I enable virtualbox guest additions: then I get only virtualbox!!! and nvidia does not work anymore on my machine: this is because virtualbox guest additions is overriding services.xserver.videoDrivers: this is not necessary since by default the lists are merged workaround: then I get virtualbox + guest additions + nvidia: Ideally this should work out-of-the box, debugging this kind of behavior is very obscure, and also different configuration options should cohexist


vulkan-tools fails with an assertion error from vulkan-headers Steps to reproduce the behavior: the nixos-unstable-small channel vulkan-tools being installed # nix-shell -p vulkan-tools --show-trace error: assertion '(version == (vulkan-headers).version)' failed at /nix/store/cqbcz8k1wq604f8b8nc8khamyh2cl6dl-nixos-22.05pre348006./nixos/pkgs/tools/graphics/vulkan- 10| # the rest of nixpkgs. 11| src = (assert version == vulkan-headers.version; | ^ 12| fetchFromGitHub { … while evaluating the attribute 'src' of the derivation 'vulkan-tools-1.2.189.1' at /nix/store/cqbcz8k1wq604f8b8nc8khamyh2cl6dl-nixos-22.05pre348006./nixos/pkgs/stdenv/generic/make- 204 (attrs ? pname && attrs ? version)) { 205| name = | ^ 206| let … while evaluating the attribute 'buildInputs' of the derivation 'shell' at /nix/store/cqbcz8k1wq604f8b8nc8khamyh2cl6dl-nixos-22.05pre348006./nixos/pkgs/stdenv/generic/make- 204 (attrs ? pname && attrs ? version)) { 205| name = | ^ 206| let
Fix at , thanks for the report. I thought we had tests for this stuff...
fixed it for me. Thanks!


Trying to install tetrio fails (see screenshots) Steps to reproduce the behavior: tetrio-desktop from nixpkgs-unstable (I did it using a flake) The package should install with no errors. ! <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result.
Oops, it looks like I accidentally used a non-direct download link for the source. It also looks like audio is broken, so I'll start a PR soon.


As of , the build of is broken. This is currently breaking the build of other packages including and certainly many others... ~I suspect this was triggered by , , or one of the redis upgrades.~ I believe this was triggered by . Steps to reproduce the behavior: nixpkgs at failure The build to succeed. n/a n/a <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result.
I tried patching around the issue with but that gives me a test failure:
should fix that. Also please use postPatch.


Project description Fprintd replacement which allows you to have your own backend as a standalone service. Metadata homepage URL: source URL: license: GPL2 platforms: linux


nix-shell -p supercollider [anders $ nixos-version (Flounder) [anders $ nix-env --version nix-env (Nix) 1.11.2 [anders $ nix-instantiate --eval '<nixpkgs' -A lib.nixpkgsVersion ""
you use supercollider ?
no, sorry.
Same here:


When using with the I get the following error. ! I'm assuming this is caused by the following code. Since it doesn't include the module. Steps to reproduce the behavior: the to open Libreoffice Writer The Languagetool plugin doesn't cause a runtime error. Please run and paste the result.
Hm, jre_minimal tests seem to confirm it; does adding "java.logging" there help?
Happy to take a look by the end of the week :)
That'd be great if you could do that. I tried building it on my laptop. But it was still building after ~3 hours. :)


, CVSSv3=5.5 (nixos-21.11, nixos-unstable) CVSSv3=4.9 (nixos-21.11, nixos-unstable) CVSSv3=4.9 (nixos-21.11, nixos-unstable) CVSSv3=4.9 (nixos-21.11, nixos-unstable) CVSSv3=4.9 (nixos-21.11, nixos-unstable) CVSSv3=4.3 (nixos-21.11, nixos-unstable) Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Compiling). Supported versions that are affected are 5.7.36 and prior and 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server as well as unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.1 Base Score 5.5 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H). Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Federated). Supported versions that are affected are 5.7.36 and prior and 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Stored Procedure). Supported versions that are affected are 5.7.36 and prior and 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Parser). Supported versions that are affected are 5.7.36 and prior and 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Replication). Supported versions that are affected are 5.7.36 and prior and 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Security: Privileges). Supported versions that are affected are 5.7.36 and prior and 8.0.27 and prior. Easily exploitable vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.1 Base Score 4.3 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N). Scanned versions: nixos-21.11: ; nixos-unstable: .
See also: , , , , , ,
Fixed: nixos-21.11: mysql-5.7.37, mysql-8.0.28 nixos-unstable: mysql-5.7.39, mysql-8.0.30


<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 4.1.6 desired version: 4.1.7 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.


After Wireplumber was enabled by default in , audio and video playback completely broke on my machine (NixOS-unstable, GNOME on X11, x86_64-linux). Preview thumbnails of videos did show, but clicking "play" on audio/video tracks does nothing. I've observed this directly in Firefox, Element Desktop, Freetube, Rhythmbox and Signal. Reverting by putting into my config resolves the issue. Steps to reproduce the behavior: Firefox to play a video since you authored the PR Please run and paste the result.
I've also verified that this isn't resolved by .
I am also experiencing issues with video playback, I am glad i found this issue. seems to have fixed it
Known regression with pipewire 0.3.48 and wireplumber 0.4.8. Should be fixed by .
I've tried to apply the fix from with: but it didn't resolve the issue for me.
That is strange. What's the store hash of your wireplumber build after this?
With the nixpkgs revision , I get: I haven't applied any overlays that influence wireplumber. (Checked by directly building wireplumber from your Nixpkgs PR branch)
That hash does seem to match. I wonder if it's a different issue then... Can you also run ?
By the way, if you want to, we can continue this on Matrix (I'm there).
Honestly at this point I'd probably just report a bug upstream, or ask around in
Okay, thanks, I'll try that. Do you happen to know whether wireplumber has some sort of "verbose/debug log" build option which might make it easier to find the bug?
Try WIREPLUMBER_DEBUG=10
You should try zapping all config and cache. Especially if you use bluetooth (in which case the bluez cache).
I've been having this issue, too, on unstable. What I've noticed is that, on reboot or logout/login, playing a video works just fine the first time. But on the second and subsequent times, video won't play. A stil image from the video is displayed, but the video doesn't play at all. Here's what I see with : For me, running fixes this problem immediately. That is, videos suddenly start playing.
Is this with the patch or without?
I also wanted to note that I've reported the issue upstream now (), maybe a few more log dumps from other people with this issue will help the developers over there
there might be relevant details here
How are you enabling Pipewire? Something like the snippet below?
That's an interesting question. I didn't explicitly enable Pipewire anythere, my sound config is just: Basically, I have no idea of audio systems on Linux and I just assumed that it was some sort of backend for PulseAudio. On my system however, the Pipewire and Wireplumber services are there. Maybe that's some sort of bug in the NixOS audio submodules?
With , I've confirmed that something in my config indeed causes to be set to true, but are all false.
I've backtraced this and is set by , which is in turn enabled by default on Gnome (nixos/modules/services/x11/desktop-). It might be worth to open an issue for that.
This is really useful debugging information! Take my next paragraph with a grain of salt, since I am not a PipeWire expert. Some parts of PipeWire relate to screensharing (which is probably why enables it) and supposedly should work even without the ALSA/PulseAudio/Jack emulation, but sometimes there are bugs in the session managers; for example, was a bug in the old session manager with a similar outcome. I think that screensharing use cases are meant to work even for PulseAudio users (that is, without enabling PipeWire's PulseAudio "emulation" layer).
It seems that part of the problem is that had those extra knobs for turning various emulation layers on and off (such as and ), but those are no longer respected when using WirePlumber. This might lead to some weird conflicts for PulseAudio users (for example, if WirePlumber decides to start pipewire-pulse).
But does this mean that the WirePlumber switch broke audio for every GNOME user that does not use PipeWire? This seems like the default config!
Those knobs are for Pipewire itself, not pipewire-media-session. Wireplumber should still be functional in a mixed PW/Pulse setup, so it's probably worth reopening the upstream issue.
I'd ask someone else to open that issue though because my knowledge on this topic is close to zero, and I'll probably not be able to accurately describe the technical details here. I've also tested this on my laptop, and it has the same issue, so that actually seems like a realistic possibility. I'm not really sure when it comes to user statistics, but from what I've seen, GNOME tends to be mostly used by less experienced users, while KDE and WMs like i3 are a lot more popular among advanced users, and the unstable repositories of an operating system are generally almost exclusively used by advanced users. So after considering the small user base of NixOS, it's really possible that there are just not that many GNOME/nixos-unstable users who are likely to encounter that bug.
Ideally yes, but there are two places in the NixOS module that look at : uses it to decide if the systemd service should be installed, and looks at it to create the file. Therefore, is given a hint that pipewire-pulse shouldn't be started, while upstream WirePlumber does not seem to have such an option. If I had to bet, I'd say WirePlumber does not currently support this use case.
pipewire-media-session doesn't start pipewire-pulse, systemd does. Wireplumber should detect the right setup automatically.
Yeah the file dates back to before the systemd service for pipewire-pulse existed. It is probably redundant nowadays.
I agree with what you two are saying, but I think I didn't express myself clearly, so I will try again; apologies if this is annoying. My point is that we have no indication that WirePlumber is designed to support mixed setups. The release notes for WirePlumber 0.4.0 say "It is a fundamental goal of this series to maintain compatibility with pipewire-media-session, making WirePlumber suitable for a desktop PulseAudio & JACK replacement setup, while supporting other setups as well (ex. automotive) by making use of its brand new Lua scripting engine, which allows making customizations easily." and it's unclear if they care about our use case (IMO it would be perfectly reasonable to not support PulseAudio). I'll ask upstream.
Pipewire and Pulseaudio are (should be) mutually exclusive. They both try to multiplex the underlying hardware, so if you're running both of them, that may or may not work depending on whether the physical sound hardware is capable of handling multiple streams. Some is, some isn't. It's not as common to have that functionality as it used to be, since modern CPUs are more than capable of handling it in software. How it should work is that: If is set, that brings up the default audio manager. Whatever that is. Pipewire would be a good choice. If is also set, that enables pulseaudio and disables pipewire. If both pulseaudio and pipewire are explicitly enabled, that should hit an assert. There are very few cases in which enabling both makes any sense. Pipewire has a pulseaudio compat layer; this is not the same thing as running pulseaudio itself. But I haven't checked the actual behaviour of nixos, so I have no idea what's happening. Try ; this should tell us what is running on your system.
That is not true. Pipewire can be used for video and audio, and running Pulse for audio and Pipewire for video is a supported configuration.
Is that in fact how we're using it? Or is it opening the sound devices regardless? ...I should just check. Will report back later.
With Pulseaudio enabled (by ), Pipewire started when I opened a video on youtube, and no sooner — there was, however, no sound. Chrome connected to pulseaudio regardless. Pavucontrol reported no sound output devices available; only sound input was possible. A bit of searching in /proc indicated that pipewire was holding the audio devices open, and my sound card indeed only supports one stream at a time... but I'm unable to confirm that this is the issue. Regardless, I was only able to make sound work by either completely disabling pipewire, or completely disabling pulseaudio. I concur the Pipewire should be usable without making it grab the sound devices. However, how does one tell it to avoid that?
Hmm without looking deeply into it, I'm guessing the problem is that wireplumber and we don't have any way of configuring that via nix yet. Can you try if it works with pipewire-media-session if you disable all the audio stuff? This should cause alsa-monitor to never get loaded in pipewire:
That works flawlessly, as mentioned in my initial message in this thread.
Right, so this is the point where we have to make wireplumber configurable via nix. There has been towards that but the lua system maps rather badly to nix so nothing in nixpkgs yet. As an interim solution I think we should add an assert that tells people to manually switch back to media-session if they have both wireplumber and pulseaudio enabled?
Fixed problem for me
I must say that this problem has been driving me crazy and you guys just prevented hours of debugging. I will try your fix and report any problems.
OK, I think we need to add an assertion here. I'll do it tomorrow unless someone snipes me.
So, while switching to Pipewire is nice, I really don't think that justifies breaking people's mixed PW/Pulse setups. Please test the fix in if you're affected (and make sure you disable Pipewire beforehand).
where do you put this?
Please don't bump one-year-old threads. File a new issue.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:


I don't use at all, but I'm getting this error when I'm trying to rebuild my flakes (same happens when I run ) and also I don't really use it or install it Steps to reproduce the behavior: or Expect or to work fine I ran before running <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result.
By grepping through nixpkgs, depends on by default. (see ). However, abook is only lists linux as supported (Im not sure if this this is just nixpkgs or abook in general) Up until , lbdb has not depended on abook by default. Perhaps a mistake was made while refactoring. In the meantime, you can just override the package.


are you on top of this?
Thanks for the heads up, yeah, just waited for the GitHub releases to appear. I’ll create a PR soon.


<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: lapce <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 0.0.10 desired version: 0.0.12 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Maybe it will fix the crash:
can you create a pull request?
I am using changes in local build. it is working fine


After the update, with an seemingly related build error on . This blocks the channel at the moment. Possibly related: . <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --cc
Note: this affects both unstable and 21.11.
Is there any plan to make a different branch? unstable has been blocked for every platform for half a month because of darwin issues (after just a few days of being working after another blockage of more than a week also because of darwin).
From the perspective of a dual darwin/linux user, the issue seems to be that insufficiently tested PRs keep getting merged to master, which repeatedly regress behavior on darwin and break unstable. I'm not sure how downgrading darwin to not even deserve a place on unstable will do anything to alleviate the deeper issue that the PRs aren't being tested enough in the first place.
If you use a Linux, why don't you use NixOS channels instead? Even if you don't use a NixOS, the packages get extra testing through the NixOS tests.
From the perspective of a person without any Apple devices, testing darwin stuff is quite hard, even though builds work nowadays, at least for small rebuilds. Some people get even annoyed by having to deal with darwin-specific issues, and I have sympathy for that. The zlib update in particular fixes quite a severe security problem. I certainly would not want to delay that on Linux (or even on Darwins) because of this qtbase regression.
That’s fair of course - the status quo has lots of underlying factors! I know it’s outside the scope of this issue, but should we all think about how to use some of the recently Mac build machines to, say, be able to trigger something like a more full nixpkgs-review on packages that could cascade a bunch of failures like this? Barring that, I know that the Darwin maintainers group has grown a lot. If we could find a way to get looped in on some of these changes before merge, that might help avoid the breakage churn. There’s gotta be a way to help Linux-only maintainers and committers prevent regressions more proactively, rather than frantically fixing things after the fact. Sorry I don’t have an obvious solution!
Well, it depends. This regression in particular was known and reported (to a thread with quite many participants) before merging to master.
Is it possible to use nixos-unstable with home-manager in a non nixOS distro? If it is, I had no idea.
I don't think there can be anything preventing it. Though I don't really know home-manager in particular.
I use (along with ) on macOS, so presumably yes. The branch isn’t NixOS-specific. It’s just what criteria are used to advance the branch (so sometimes things are broken on Darwin IME).
Non-NixOS Linuxes use the same binaries as NixOS (contrary to darwin). And you always have the whole binary cache available, not just what's associated with the particular channel.
Thanks a lot, I'm changing to that branch right now, you made my day.
Fwiw, for Darwin in particular, nixpkgs-unstable does run some tests that nixos-unstable doesn't.
Yes, NixOS channels have no dependency on darwin at all.
I did the change and it's working nice, but some packages are not getting downloaded from the cache (till now zathura and llpp) and painfully they also fail while compiling locally no idea why, any pointer to what can I check??. I know this is not the place to ask this kind of questions but I don't know which is the correct one either.
There's no guarantee that everything in nixpkgs is working all the time, for zathura see .


Steps to reproduce the behavior: Please run and paste the result.
Thank you for reporting this issue; I can reproduce it. The problem is not in the warning displayed in the last 10 log lines, but in an earlier error: Unfortunately I don't think that I will be able to contribute further to this issue.
I'm aware of this failure, but fixing it will require a bit of patching. Upstream didn't update the package to ghc 9 yet. Right now I don't have much time to do that, so in the meantime you could install it from stable, where it does build. Please change the title to something like "jl: build failure due to ghc 9"
This has been correctly marked broken in . See also where there was a small amount of discussion about marking this broken.
I've created an upstream .
The PR is now merged, and the package is now on Hackage for the first time. However, since it's not been to Stackage Nightly yet, it won't make its way into for quite some time. I'll update the derivation to use the new version directly from Hackage.


While checking why we have two subversion releases I noticed that both releases are LTS versions. They receive 4 years of support and 1.10 was first released on 2018-04-13, so it's probably wise to remove it before the 22.05 release. Originally posted by in
I don't see anything that depends on in nixpkgs (anymore), so IMO we can just remove it now, instead of waiting for some kind of EOL announcement.


Try to build for . Note, I'm trying staging because is necessary. fails: staging is at :
This was caused by setuptools 60, which now uses bundled distutils. All Python packages with extension modules fail to cross-compile currently, but this will be fixed by . I also noticed that the libbtrfsutil Python bindings are never actually installed, so I also created .


For example: fails similarly. The line that causes the failure according to my testing is: A list of some packages that didn't break: Could be this is an upstream issue.
So digging into it, this is an issue raised by Octave's package management system itself. Namely, this -statement from Line 80 in that file is the statement. It expects to remove a file, which is not existing. The reason the other packages did not break was because they either do not have a directory () or they actually do have a generated file (netcdf & control). You can technically solve this by adding an empty script to the directory. I manually did this, and the package built correctly again. As for why this change happened, I cannot tell. The particular statement shown did not change between 6.4.0 and 7.1.0 in the file.
Looks like
That's the exact issue. Seems like we will need to wait for upstream to fix it. How does this usually get handled
Seems like we should apply to the patch:
There are still 5 packages failing to build, but that is a lot fewer than before.


Traceback (most recent call last): File "/nix/store/z4sd700l05shq1z72g21w0fav2xs955d-pipenv-2022.1.8/lib/python3.9/site-", line 83, in androidfolder from jnius import autoclass # noqa: SC200 ModuleNotFoundError: No module named 'jnius' The error is belong in pipenv using jnius on Android. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --- system: host os: multi-user?: sandbox: version: channels(nix-on-droid): nixpkgs:


Build of failed on x86_64-linux as of . This is currently breaking python3Packages.tensorflow-bin. python3Packages.tensorflow-bin maintainers cc: python39Packages.tensorflow maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tag:
I'm not quite sure why this doesn't have the same internal tag as they seem to be the same AFAICT.
oh I see... the hashes in /nix/store/[hash]-pname-version for each of the dependencies changed. hmmmm


Build of failed on x86_64-linux as of . This is currently breaking maintainers cc: google-cloud-cpp maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tag:
This has also broken tensorflow-datasets.
Fixed in


I am new to nixos... When I try to use printScr Key on keyboard. it not responding. non of the printScreen optins working.. Steps to reproduce the behavior: ... press Key PrintScr ... ... Should take a screen shot ask for location to save to. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result.
I am not too sure but according to the , cinnamon does not have a "native" screenshot tool but gnome-screenshot could be used. I am not too sure if enabling cinnamon auto includes gnome-screenshot. If it doesn't you can just add it and see if it solves your problem.


Build of failed on x86_64-linux as of . This is currently breaking . python3Packages.pytorchWithCuda maintainers cc: magma maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tag:
This looks like another gcc11 failure. could you take a look?
Sure thing
Going to attempt to bump from 2.5.4 (2020) to 2.6.2 (2022)


Somewhere between and there is a commit that changes the default fonts on NixOS. Most text is just different (I'd say, a bit less readable). But some text in the terminal (gnome-terminal) is completely borked (in regards to positioning): ! Look at how the 's' is drawn on top of the 'M'. And generally the positioning of glyphs is... not right! Compare how fonts look in a few apps on nixpkgs vs . System: x8664-linux NixOS at master branch (). No fonts.* settings in my file (never had that). GNOME3 desktop and gnome-terminal.
My guess is . cc I'll try to switch to master and debug what happens.
Wild guess, is there a and a folder? Could you post the result of ?
Hm, I upgraded another machine to the same commit. Fonts look generally a bit different than they used to (for instance, in chromium + gmail). (I think the glyphs are just thinner and there is a lot of "air" around each letter.) But the horribly broken stuff in gnome-terminal doesn't happen on this machine. What's going on?
Can you try to remove and and do a to see if that improve the situation?
Yes it does! Now all text look like it used to. Thanks! After this, is no more, only /etc/fonts:
Is this something we can fix in the NixOS module that sets up /etc/fonts, so that users upgrading from 16.03 to 16.09 won't hit this?
A heuristic idea for this -- a function : if path is a file, return True iff it's a symlink to . if path is a directory, return True iff for all items in it is True. On any conflicts, if old path is static, it's safe to replace and/or delete stale. Otherwise make a backup and notify the user via a journal entry and console output. What are the possible caveats? This would certainly be nice to implement. I can look into this if it seems a good idea, but I suspect corresponding code is in Perl, which I'm illiterate with. On July 15, 2016 1:25:53 PM GMT+03:00, "Bjørn Forsman" wrote:
Yes, the cause seems to be in the function of .
Truth be told, I like better an idea of making fully static, with several files (like when ) explicitly set as symlinks to somewhere (?). This simplifies the whole bookkeeping a lot, but however is a radical move. I'm eager to try implementing this but we need to survey possible cases when people manually change something in . Maybe I'll get a chance asking in the ML...
in principle I'd like that, but in practice FHS is pretty unclear about whether /etc is supposed to be mutable. Would definitely be interested in what you came up with though. Personally, I'd rather fix more programs to not use /etc and rather to link directly to configuration in the store that they need (since we get more granularity there and know exactly what needs to be mutable), but that's probably a lot of work in some cases.
For input method packages, I used dedicated packages for the and the folders under via . Could a similar approach for be a way to solve this problem? (edit: and accessorily a way to too?)
why would we care what FHS says? :-D
I get this line when switching (and then fonts look ugly): Where 81 line is Next fixes the fonts:
Opened a PR with a fix:
see for read-only /etc
Nice find! I haven't yet done any research, so this thread will come handy.


<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: haruna <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 0.7.3 desired version: 0.8.0 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: I tried to update it myself, but when trying to open the result I get either: or: Some dependencies could be moved to , since they are build time only. The project supports other than . Since uses the former, maybe switching could be considered. The homepage is outdated. It's now "". Please tag this issue in your PR.
Can you (re)produce after this update?
This is an issue requesting an update, not a pull request (edited the title to be more clear). Still, with the update I tried to do by myself I couldn't open Haruna in the first place.


Enabling services.hardware. (as a systemd service) breaks. Steps to reproduce the behavior: error about and several other errors like "has not been declared", "does not name a type", etc. To rebuild xow and everything else without any issues. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
The git not found problem is not fatal and the derivation overrides the version info anyway. Looks like another victim of our stdenv compiler upgrade. Looks like upstream master has a fix for that. Upstream is also orphaned so upgrading the derivation to an unstable revision is going to be needed in the short term and in the long term a replacement should probably be found. I don't have a working controller to test xow with any more so if someone wants to adopt the package, feel free to.


<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: rtl-sdr <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 0.6.0 desired version: 0.8.0 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: This package is currenty using but it should probably switch to Please tag this issue in your PR.


For example This test has always been failing: From the logs: /cc
Whoopsie! Maybe instead of keeping hard-coded URL to x86-64's Alpine we could build something dynamically? (this way the test would automatically work on all architectures) I'll try to take a look over the weekend, but feel free to take a shot at it, if you want
Hmm that is a cool idea. Though OTOH it is currently nice that when this test fails it is clear it is a problem with running the image, and not with creating it. Did you get that from somewhere or did you create it? Is it the 'mini root fs' from ?
Yeah, that's the one;


fails to build. Looking at hydra when it started to fail () it could be due to GCC 11 update. Just adding to the only leads to the next error. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --


On nixos-unstable it appears that was renamed to . However the config line for applying the option still references the obsolete option name: This means that enabling produces a warning like Relatedly, using this without defining also throws an error ' is used but not defined.confignullOr submodule` with no default value). Steps to reproduce the behavior: should not produce any warnings or errors. Uncommenting the line removes the error but leaves the warning. (though the flake output in question is for )
You used the wrong GitHub handles for some of the maintainers. cc
Oops. I copied the names out of the file as there's no GitHub team for it, but I forgot to indirect through . Is there any simple way to look up the github handles for a given module? I'm not even sure how to get at the module programmatically.
It works, but it isn't pretty.


See Hydra failure: I could not find anything directly keepassxc-related in the changes on hydra from last successful to first failing build. CC Also relevant: Version bump to 2.7: A fix for this issue might give a merge conflict there in the worst case, or alleviate the build problems there in the best case.
Does keepassxc depend on Qt? We're stuck on an older Qt because of the SDK version for x86_64-darwin. I think keepassxc may require a newer SDK.
mentions QT = 5.9.5.
Current version builds just fine. There's one test failure instead: I'll see if that's fixable...
Another issue though is that somehow became wrapped so can't be loaded anymore. Which may be related to the test failure... Either way, after trying to run the app, the gui just spins with 100% CPU. The cli part works just fine though.
I came across this issue because I was investigating something else, this is because of the wrap qt apps hook which wraps all the executable files, even if it's a dynamic library. This can be fixed by removing the executable flag from the library. You might be able to resolve it with something like: In the derivation. This should be fixed in the fixup script however


nixpkgs-review stopped working on recent branches, I didn't update nixpkgs-review before it break so I assume something internal in nixpkgs has been broken. Steps to reproduce the behavior: or there is a build failure related to hydra <details<summaryLong output of the failure</summary</detailsit shouldn't fail
This is certainly related to , ping :)
Sorry about that, it's a bit annoying that aliases are allowed locally and not in nixpkgs-review :/.


, CVSSv3=9.8 (nixos-unstable) CVSSv3=9.8 (nixos-unstable) Vyper is a pythonic Smart Contract Language for the ethereum virtual machine. Versions of vyper prior to 0.3.2 suffer from a potential buffer overrun. Importing a function from a JSON interface which returns generates bytecode which does not clamp bytes length, potentially resulting in a buffer overrun. Users are advised to upgrade. There are no known workarounds for this issue. Vyper is a pythonic Smart Contract Language for the ethereum virtual machine. In affected versions, the return of is not validated to fall within the bounds of . This issue can result in a misinterpretation of the integer value and lead to incorrect behavior. As of v0.3.0, is validated in simple expressions, but not complex expressions. Users are advised to upgrade. There is no known workaround for this issue. Scanned versions: nixos-unstable: . Cc
See also:


, CVSSv3=7.5 (nixos-unstable) CVSSv3=7.5 (nixos-unstable) A lack of password length restriction in Zammad v5.1.0 allows for the creation of extremely long passwords which can cause a Denial of Service (DoS) during password verification. A lack of rate limiting in the 'forgot password' feature of Zammad v5.1.0 allows attackers to send an excessive amount of reset requests for a legitimate user, leading to a possible Denial of Service (DoS) via a large amount of generated e-mail messages. Scanned versions: nixos-unstable: . Cc Cc Cc


Project description KDiskMark is an HDD and SSD benchmark tool with a very friendly graphical user interface. KDiskMark with its presets and powerful GUI calls and handles the output to provide an easy to view and interpret comprehensive benchmark result. The application is written in C++ with Qt and doesn't have any KDE dependencies. Metadata homepage URL: source URL: license: GPL 3.0 platforms: Linux
I am currently trying to work on this. It builds and runs, sometimes I run into a Kauth error
see , please review


Since May 10, .NET 5.0 is EOL (End Of Life), and should not be used. Should it be marked as EOF similar to dotnet 2.2 and 3.0? See All packages using dotnet 5.0 should be updated to use a newer, supported version. These packages still need updating: [x] - [x] - [x] - [x] pkgs/development/tools/build- - [x] -
There is at least one package, which currently uses dotnet 5 sdk - . So we will need to update it beforehand. Btw, I'm not sure if we have any policy regarding packages removal, for nixpkgs in general or specifically for it's dotnet part. , what do you think?
The package is also using .NET 5: . But this is because I made the PR upstream updating it from .NET 4 to 5. I suspect that the transition to 6 will be similarly easy.
I think we should just mark it as depricated, as many projects do still use it upstream. Dotnet version 3 is also still commonly used, so I dont expect it would be realistic to remove version 5 any time soon. also uses dotnet 5 by default, I'll go ahead and switch that over now. See . That doesnt mark dotnet 5 as deprecated or change anything from a SDK perspective, just some preperation work.
See as well, it adds a warning whenever dotnet version 5 is used. Not using a throw for now since a few packages depend on it and I dont have the time to clean that all up at the moment.
Can you provide a list of packages that need updating?
Based on a quick grep: pkgs/development/tools/build-
I believe that after all the above PRs are merged, we should be able to safely remove .NET 5 from nixpkgs :)


Shotwell can't build thumbnails for video files. package has an additional executable , which is broken. When run manually, it fails with this message:


Project description  Selectdefaultapplication is a very simple GUI application that lets you define default applications on Linux in a sane way. Basically it just loads all installed applications by reading their .desktop files, reads the MimeType fields to see what it supports, and updates with what the user wants. Not all desktop environments provide such a tool, prompting for an agnostic tool. Metadata homepage URL: source URL: license: gpl2 platforms: linux Additional info: AUR package:
You can try using this in an overlay, use .
Seems to work!


I'm bringing up new RPis and their clocks are often wrong. Even though upstream systemd has given exceptions to be able to skip dnssec check for ntp sync, it doesn't... appear to be working. If I set the date manually, often by time I check timesyncd will have already taken care of kicking in and it reports that it's synced. Steps to reproduce the behavior: the clock badly. . and see if your DNS works
If I read it right, only works for systemd-resolved. One general workaround is to use hard-coded IP addresses for NTP (our routers actually do that IIRC).
That commit seems to indicate that it should bypass DNSSEC for timesyncd. This would get my clock back in sync, thus resolving DNSSEC errors for the rest of the system. But timesyncd isn't doing its job. I assume that's because: date wrong -dnssec failure. But maybe also fails if the clock is just too askew? I'll try to look more later, maybe I have to opt-in large corrections? Seems a bit weird to me. Or do we maybe use timesyncd in a non-standard way?
I ran into this on a Raspberry Pi 3B. I'm using systemd-networkd including systemd-resolved. At some point DNS started failing, and I noticed the system clock was out of sync by about 4 hours and not synchronizing anymore. The log of systemd-resolved was full of DNSSEC s: I'm not sure what changed, because I was able to install NixOS just fine. It also was offline before for some time without this problem happening (as far as I noticed at least), and it started happening after it was online for some time without break. Also, the systemd-native workaround should be working on NixOS as well, I can't find anything that indicates a non-standard setup that might overwrite tha workaround. Checking is the standard original systemd unit file that includes the relevant line and as far as I can see it isn't overridden. I also checked and it includes . For now, I worked around the issue by specifying my NTP servers by IP (I used the ones by the ).
Closing as this should be fixed by Please reopen if this is still an issue.


<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: syncthingtray <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 1.1.3 desired version: 1.1.20 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.
There's a new dependency now needed for syncthingtray - but there's a problem in the logic upstream here: Here's my packaging attempt:


The file generated for nixos is not compatible with the R programming language's interpreter (). On startup, the R interpreter prints the following warning (though it does continue as normal after printing the warning): This could be resolved by adding a trailing newline to . Steps to reproduce the behavior: the R interpreter by running , or if you don't have R installed. No error message should be printed. I'm not entirely sure whether this should be resolved adding the trailing newline to , or whether R should be modified so it doesn't assume a trailing newline. The man page for describes the format of the file as "a newline-separated list of environment-like shell-compatible variable assignments". The existing format (no trailing newline) is indeed newline-separated and shell-compatible (bash and zsh both have no problems with it), so maybe I should bring this up with the R folks instead? On the other hand, all the other distros I've checked (ubuntu, archlinux, and alpine) include a trailing newline, so maybe we should just stick to what they're doing? The fix is trivial: Let me know what you think, and I'd be happy to open a PR wherever we decide the fix should be made. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
This! It shouldn’t be needed and yet here we are. No harm in doing so that though, so I’m all for this. Sounds great!


The Zen kernel is failing to build for me since the update to 5.18, and so I thought I'd open an issue since I can't seem to find any existing info about it. Bisected to system: host os: multi-user?: sandbox: version: channels(root): channels(alex): nixpkgs:
Looks like it didn't build even in the CI of : But, we already have a new version: Cc (since you're always the one to bump it)
Unfortunately 5.18.1 doesn't seem to build either for me. :( Given that the file in question hasn't been touched in months, I'm wondering if this has something to do with the move to C11 for the 5.18 kernel. But that's just a guess. I can think of two possible quick solutions: Include a patch that adds a comment Ignore that warning everywhere in the kernel
Staging recently got change to avoid Werror-style failures.
Given that that change will take a bit to get to master, do you think it would make sense to set for just the zen kernel in the meantime? Or even just revert and move it to staging so that it gets merged when the change does? I'm asking because—while it's not too much trouble to add patches to my personal NixOS configuration—right now the zen kernel is broken for everyone, and so it might be a good idea to get it back to a working state in the meantime. I'm not sure how many people use the zen kernel though, it seems to be not very many, and so if it's better to just leave it as-is for a bit that's fine too; I don't really know how such things are usually handled in nixpkgs and am trying to learn. :)
I'd say setting for zen kernel is perfectly fine. Should be a matter of adding it to Do you want to give it a try and propose a PR? AFAIU you already run that kernel version and have a chance to validate it if still boots. You could also add a TODO to remove it once staging is merged.
should've gone to master and/or be merged with the next kernel bump or something if the rebuilds were that critical which I don't think they are. We could cherry-pick it if we need it now.
I made , but it's late here so I don't have time to test it properly and am waiting to open a PR until I can do so. It at least builds though. I figured while I was at it I should also bump the version to 5.18.1-zen1, but in hindsight maybe I should wait until the mainline kernel is updated to 5.18.1 in nixpkgs? Anyway, I'll test it when I have time tomorrow evening, make any necessary changes, and open a PR, unless we decide to cherry-pick ? That seems like a nicer solution to me personally, but I don't really have a strong preference.
I finally got around to testing this and opened a PR: :). I'm personally in favor of cherry-picking , though.


I setup the server quite a while ago. I recognized that the service is not running. As I normally do auto update I saw that the process failed as the configuration changed. After rebuild + switch the service fails to start: Steps to reproduce the behavior: Service be able to start. I tried to 1) chmod +w -still fails and permissions are somehow adjusted 2) delete -file is created, startup still fails
Digged a little bit deeper: The error is thrown by the pre-start script. It seems that my installation is missing the which causes some gitea command to generate it and write it into . Which fails as the file is set to non writable by the pre-start script.


I've been using PipeWire+JACK with until now. I'd like to switch to , but the service crashes at startup. The key error in the logs seems to be: . The result is that : (1) I have no sound, (2) I see no volume control knob in GNOME, (3) I see no devices appear in or any other JACK patchbay tools. Here's (hopefully) all relevant build configuration: Here are some logs: It seems others haven't run into this. What could I be doing wrong? Steps to reproduce the behavior: the above build configuration in the computer the above-written commands to view relevant logs I expect to the service to start, and to have sound.
Do you need a systemwide setup? That seems to be the issue here.
My use case is: I use virtual machines that run as another user (for security), but I want them to have sound. Using allows this, and it's the only (secure) solution I'm aware of.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Thanks for this patch. I was finally able to test it. Unfortunately, I still have the issue. Your patch removed the "" error, but the wireplumber service still fails to start. Here's some evidence that your patch is applied: Here's the failure output/logs: According to the "" shouldn't be a problem because wireplumber shouldn't require X11. Looking more broadly at logs, there's this:
There have been some dbus related fixes in Wireplumber master, can you try that?
: I don't know how to cherry-pick from wireplumber; I only recently learned to cherry pick your pull request. I suppose I can wait until the next release. Maybe I should open this as an issue against wireplumber? Also, this crash only occurs with . Can you offer insight into what this means, so I can best phrase my question? I think the pipewire socket moves to a different what else? Does pipewire and/or wireplumber run as a different user? Anything else?
should get this fixed for good.
Also, if you don't know what does, you should probably disable it, as it's not a well supported configuration.


Fonts are missing, square characters are displayed ! Steps to reproduce the behavior: vmware-workstation vmware workstation or player I started a discussion on <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --/cc
I can reproduce this, probably related to some missing font in freshly installed systems
I launched vmware with FC_DEBUG=8, but I'm not able to interpret these errors messages, hope this can help
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
I found reason for missing fonts, it just loads from instead of system path and vmware's config points to wrong FHS paths, removing file fixes it, i will make a PR with fix, thanks.
I confirm that deleting fixes the issue. Thanks a lot !


Building fails when rebuilding system configuration. System configuration should build successfully with on kernel 5.18 There are no current maintainers. This appears to be a repetition of
Arch Linux appears to have a new patch here: Attempting to apply it has failed for me. I tried this block: Maybe someone who helped solve this the last time can comment?
Already have a PR up .
Looks like an issue with the patch for 5.17. Try replacing it with this one:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:


Steps to reproduce the behavior:
Can you check if has an effect?
I've got this error:
Please check the full log of that build and look for ( catching the actual error) and any preceding lines with (actual error from the compiler). What you posted are just harmless warnings and (an error has occurred somewhere else so needs to quit).
Upstream issue:


nicely describes the issue and the fix Steps to reproduce the behavior: salt on to run it errors salt working and may be of interest to ;) <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result.


tig crash on macOS (m1) Steps to reproduce the behavior: -shell -p tig ANYGITREPO type "/" to enter search mode Don't crash ! Exception Type: EXCBADACCESS (SIGSEGV) Exception Codes: KERNINVALIDADDRESS at 0x082a0d5c00ab0a2b -0x00000d5c00ab0a2b (possible pointer authentication failure) Exception Codes: 0x0000000000000001, 0x082a0d5c00ab0a2b Exception Note: EXCCORPSENOTIFY Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [] VM Region Info: 0xd5c00ab0a2b is not in any region. Bytes after previous region: Bytes before following region: REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL commpage (reserved) - [384.0G] ---/--- SM=NUL ...(unallocated) ---GAP OF 0x5f9000000000 BYTES MALLOCNANO - [128.0M] rw-/rwx SM=PRV Thread 0 Crashed:: Dispatch queue: 0 ??? 0x100b84c6c rlinitterminalio + 272 1 ??? 0x100b84c60 rlinitterminalio + 260 2 ??? 0x100b6fc2c readlineinitializeeverything + 164 3 ??? 0x100b6edd0 rlinitialize + 44 4 ??? 0x100b6ed48 readline + 36 5 ??? 0x100981ce4 readprompt + 80 6 ??? 0x10098aaa0 searchview + 56 7 ??? 0x100971680 main + 2608 8 dyld 0x100d61088 start + 516 <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result.


Noticed while debugging hash errors for . Since got merged via (bisect log further down), doesn't produce fully deterministic results anymore. Sometimes I get an identical hash, several times in a row even? But often it's different. It is worth noting that the fetcher output has changed after that commit. Using as an example, the final line has been replaced by for the main repository + every fetched submodule. Steps to reproduce the behavior: (current master at the time of writing) repl: multiple times and you should get a different hash eventually. "Best" combo I got so far is 3 identical hashes before a different one. Hashes shouldn't randomly be different. It would be understandable if the not-yet-deterministic was used, but this happens even with . Changing hashes: ! ! Changed output: (last identical lines are highlighted) ! Bisect log: Bisection done with . uses with , which uses under the hood, but the hash change should be observable by directly using as well. CC (commit author) CC (PR merger) Please run and paste the result.
I did a quick investigation. First of all: I was able to produce the same results as the OP on my machine. My initial investigation led me to believe that this behavior is caused by 2 bugs. One introduced by commit and the other one being unrelated to this commit. The bug introduced by the commit in question is that seems to use in situations where it shouldn't. The second bug is that specifying produces non deterministic results. Evidence for this is provided by the following experiment: I checked out a revision of that was before No I ran the same experiment as the OP suggested but instead of using I used . As you can see I got two different results for the same call. I suggest that should be reverted to mitigate the damage by the bug it introduced. I don't know well enough to do anything about "the other bug".
This is a .
Pinning this until the fix has made its way into and staging.
Thanks a lot to everyone involved in investigating and fixing this! Also, I'm sorry for breaking this in the first place!
Don't take all the credit for yourself. We broke this together ^^
I'm seeing behavior that I think may be related to this issue. Please consider the derivation contained within the following flake: Changing the dummy value of results in different suggested replacement values. It seems to me that any value except for the corrected one should result in the same suggestion. Furthermore, all suggestions do build successfully (so the allowed values of are not unique) but the only one that actually respects is the empty string case. This may indicate a separate problem with .


The reason why I didn't open a PR, is described in . I'm aware of four platforms for Qt's themes right now: Using GTK themes through + ; Using GNOME themes through + ; Using Qt themes, with the non-KDE solution , which uses ; Using Plasma-targeted Qt themes, with as , as done natively in a plasma session, using the theme's colorscheme. Steps to reproduce the behavior:  and it does not provide ; equivalent to  providing ; , then add some Pasma-target themes like , then adjust envvars , set the theme in or with , you'll get the right theme with the proper color scheme. should provide (or ) as an option, it should add only the required packages to the system, and set the proper envvars. (or maybe rename it, since qt6 also uses the same variables and envvars) qbittorrent + breeze + + dark: ! qbittorrent + breeze + + dark: ! qbittorrent + (ignored my theme): ! qbittorrent + (also ignored my theme): ! I tried to discover what package that is being when evaluating provides this platform-theme, but I failed miserably. stated as maintainers of plasma-integration: stated as maintainer of qt5ct: qt5 module contributors: cc Please run and paste the result.
Not exactly your bug, but we should remove and integrate it with configs instead.
is another QT platform theme that can be integrated into config.


Latest version uses Electron 18 instead of 16, which fixes issues with Wayland + Nvidia graphics. <!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: mullvad-vpn <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 2022.1 desired version: 2022.2 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.


Steps to reproduce the behavior:
I don't have an M1 to test
Oh, it suffices to use . I'll open a pull request.


<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: winePackages.{unstable,staging} <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 7.10 desired version: 7.12 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.
cc
PR at , needs to be tested still. My last attempts at updating have been held back by the fact that there are so many variants that building everything is prohibitively time consuming on my machine, and PRs that were ready have been lingering so long that I've had to update them with one or two even newer wine versions before they were merged, so I was not particularly motivated.


The onlykey package crashes when a file dialog should open ("Save as" / "Choose file") Steps to reproduce the behavior: onlykey to the Firmware / Backup Tab "Choose file" or "Save as" A select file window should open, not crash. ! ! I have nautilus and LF installed, which is successfully used by other programs (firefox etc). Already tried installing gsettings-desktop-schemas and setting XDGDATADIRS as described . I use dwm and no Gnome and no Gnome Packages except nautilus. I would guess it needs to use wrapGAppsHook as nativeBuildInputs but I have no idea how/where to add that. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- [username nix-shell -p nix-info --run "nix-info -m" system: host os: multi-user?: sandbox: version: channels(root): channels(username): nixpkgs:
Have you cloned nixpkgs? Did you find the nix file where the package recipe is defined?
Yes, the uses node2nix which I do not really understand. It doesn't look like other .nix files. According to this , wrapGAppsHook can be like in . But I can't find , the hook or even just the part where it is supposed to be .
the important parts of are and runCommand so you could replace the call with the usual


Project description music streaming server / subsonic server API implementation Metadata homepage URL: source URL: license: gpl3 platforms: linux package: The package is already there, maintained by It'd be nice to have a module too!
I can submit a module PR once is merged, as it adds some new options (filesystem watcher).


Dive now fails to build on darwin. This was working up until maybe a week ago. I poked at the vendor code that is failing. Looks like there some failed symbol references that look like: I saw some ramblings about libSystem updates, iirc. Is this related? Please run and paste the result.
Looks like dive doesn't build with go 1.18 yet. You can fix it with:
dive needs to update its vendoring, not reverting back to golang 1.17. Please don't pin programs needlessly to go 1.17 just because of this.
That is only true for aarch64-darwin, not any other platform.


Steps to reproduce the behavior: build /nix/store/1ikzh2ax90ji2156hh921gp4iambgwsm-kubectx- Add any other context about the problem here. Please run and paste the result.
sry I dont use darwin, my reflex would be to mark darwin as not supported except if someone can step up
it looks like this may be solved by upgrading x/sys but does anyone here know how to do that in nixpkgs? I have no idea about the go ecosystem here.
Please test from master.
I was able to get this to build with the following: rev: sha256: vendorSha256:
I can confirm it's working for me, thanks very much!
The approach to pin go 1.17 here is wrong. The package just requires a bump of


Steps to reproduce the behavior: The regression is directly caused by , and the root cause is the library is not properly linked, upstream issue: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result.


Project description Hatch is a modern, extensible Python project manager. Metadata homepage URL: source URL: license: MIT platforms: unix, linux, darwin
Isn't this already packaged as ? The projects look similar
According to


When u type grapejuice app or grapejuice player you get the following error: Steps to reproduce the behavior: Grapejuice opens as normal
gtk3 has to be to buildInputs
Adding gtk3 to buildInputs results in the app opening but results in the following error
check if that Wine home path exists and it contains a bin directory (very weird if it doesn't as I have the same path) for me after adding gtk3 to buildInputs the program starts successfully
ater doing: fixes te issue with the wine path, gonna send the pull request for the gtk3


Project description Chromium fork with performance & privacy benefits. Metadata homepage URL: source URL: license: GPL-3.0 platforms: Linux, Darwin
I wanted to try Thorium out of curiosity and built this: <details</summary</detailsBut I decided I wasn't going to use it, so I'll leave this here in case it's helpful to anyone. It seems to work just fine, but I haven't tested it very much.
What is with this?
that is not it, we need thorium in nixos, i suppose this is browser of choice for many users specially, it is not filled with unnecessary bullshitery like brave and has chome store support and widevine cdm (unlike ungoogled chromium)
Would definitely also like to give the thorium browser a whirl, as there is currently no easy way to use Google Chrome Sync for ARM based Linux.
PR
any update on this PR? popular browser. seems to have stalled
I have been using definition for a few months without any issue but since he has archived it and the version is out of date here is the same but
Thorium was removed again due to the mentioned comment. Unless things change upstream, we won't consider packaging Thorium in nixpkgs.


There are a few more flags we should enable on : - (I had to add these flags for the sake of something that depends on secp256k1 - I don't remember for sure, but I think it's bitcoinj.)
The schnorr flag appears to be gone in the latest version.


Project description vt-cli is the official command-line tool for interacting with VirusTotal. It is written in Go. Metadata homepage URL: source URL: license: asl2 platforms: unix


Steps to reproduce the behavior: purple-signal this as plugin for pidgin. Pidgin will not find it, as the output of the derivation are not as expected. First hydra build: Last hydra build: The generated output is within the wrong folder. It is expected to have folders and , but actually everything is within a subfolder . The expected structure can be compared with Got via: Please run and paste the result.


Project description Natural Language Search Engine for your Org-Mode and Markdown notes, Beancount transactions and Photos Metadata homepage URL: source URL: license: gpl3 , ...


Project description A program that allows you to set the terminal theme from the command line and scripts. ! Metadata homepage URL: source URL: license: MIT platforms: linux, macos


There are in-the-wild tarballs, especially in NPM registry, whose directory entries has permissions instead of . GNU Tar is unable to unpack them, while some other unpackers (WinZip, 7-Zip, ...) are We may need to patch or have a fall back unpacker to handle gnutar failures. Error about sha256, but it fails earlier on unpack phase.
The error caused by , , , .. directories are created with permissions which prevents creating files inside. That is clearly a bug - it should set relaxed permission for unpacking time. But taking into account the age of that software it is unlikely to be fixed upstream, so a modern replacement or fallback would be desired.
Perhaps bsdtar is an option. It also supports additional archive formats.
replicated. this should be fixable by passing to ensure all files are marked as writable.
was merged, tracks when it hits channels. This issue can be closed.


It's all about client libs (mis)trusting the server, so no security problem for most setups, but still – we should fix them. I propose to wait for actual releases (assumed within days).
Staged.


Project description Whisper is a general-purpose speech recognition model. It is trained on a large dataset of diverse audio and is also a multi-task model that can perform multilingual speech recognition as well as speech translation and language identification. Metadata homepage URL: source URL: license: mit platforms: all
PTAL.


After installing thunderbird via , no entries are to Gnome Default Applications for Mail and Calendar. Steps to reproduce the behavior: thunderbird Gnome Settings to Default Applications that Thunderbird is not in Mail or Calendar lists A clear and concise description of what you expected to happen. Thunderbird should be in Mail and Calendar in Gnome Default Applications. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
More specifically, the issue is that the desktop file lacks and in the key.
Uh, we generate the ourselves, by the same code as for Firefox, so it's a launcher for a browser
My proposal desktop entry: We cannot use since is hardcoded to in . References: Desktop Entry Specification: Desktop Menu Specification: Current wrong desktop entry: Template used for Gentoo: Debian:
I made PR .


<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: Jetbrains versions <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 2022.2.1 desired version: 2022.2.3 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.
I am not a JetBrains maintainer. Also, its probably easier to run and open a PR tagging me (would gladly review the MR)
Got it. Sorry I think I just saw your username and some previous PRs and you based on that. I created a PR from the update script. No idea how to test the updates.


User creation is broken: Invidious creates misnamed material views in the database leading to a crash. More precisely, creating a first user works, but a crash happens when creating a second user: Steps to reproduce the behavior: in your configuration your invidious instance in your browser a first account , and create a second account --It crashes with the following error message No crash happen Two material views have been properly created, named and instead of a single one named . ! I opened an issue upstream: The maintainer suggested to try with a newer version of invidious.
It seems that this can be fixed by passing the to . Source:


Same on nixpkgs-unstable:
see
also see
I tried cherry-picking both PR's but still unable to build on . I'm on 5.19.16 kernel.
FYI, your kernel doesn't matter. The headers used here are a separate thing.


The symlinking between the multiple outputs of seems to prevent it from installing. I was looking to install it to have the dig command available. - System: 17.03pre94050. (Gorilla) Nix version: nix-env (Nix) 1.11.4 Nixpkgs version: "17.03pre94050."
11.4 still doesn't contain :-( How could we have that as default in 16.09? I consider it quite an important feature for + multiple outputs. would you be against porting that PR to 1.11.5 and making that default in 16.09 and master?
+1 for a 1.11.5 Nix release in general :)
Since this seems to be an issue for multiple packages, I am raising the severity on here.
Looks like the same kind of issue as So +1 for Nix 1.11.5 on NixOS 16.09, if that's what it takes to fix this.
ping again about nix-1.11.5 (my comment above).


Steps to reproduce the behavior: streamdeck-ui I'm unsure why this happens and how to fix it so I would need help on this Please run and paste the result. (unstable - )
Looks like broke with That PR is full of mines that make it challenging to bisect fully.


The xen-bridge.service serves an invalid netmask over DHCP to VMs. Start with a NixOS host with Xen dom0 enabled using the following option in . By default, the VMs’ network controllers will be connected to a bridge set up by the xen-bridge.service. The network on is set to , but the VMs set up their networks as . The VMs get their networks configured using DHCP, through dnsmasq running on dom0. Looking at the DHCP exchange using reveals that the netmask sent to the clients (VMs) is instead of , as DHCP option 1 (shown below). The DHCP client on the VM side is likely ignoring the invalid netmask, and guessing a netmask instead. The problem can be fixed by removing the wrong netmask from the dnsmasq configuration file. Then, dnsmasq will infer the correct netmask by looking at how xenbr0 is configured. Will submit a PR. System: Nix version: Nixpkgs version:
The issue no longer appears
Dont know if related to this (not sure if it is a bug really) but if you set the mask for the aforementioned bridge, it set it incorrectly. I tried to set it as 24, get 255.0.0.0 as a result... Both 16.04 and this new 17.03 have this behaviour. I understand that this is not the best place to ask, but if what i am doing is producing the expected behaviour, I will apreciate any guidance on using it correctly.
Could you explain your issue in more detail, for example how to reproduce it? I am not sure how you are setting the net mask.
Hi, i am just using the configurations on section of configuration options. so: Setting to some valid ip adress works but Setting to anything other than the default gives a 8 bit mask. I must say that i used xen on Ubuntu, but I am very new to nixos, so can't say for sure that i'm not doing something else wrong.
Can't see what could be wrong. Anyway, this looks like a separate issue that should be reported. There might be something wrong with the scripts under in .
Opened at .


<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- : yes, <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 2.7.2 desired version: (cf. PyPI) <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.


When multiple ZFS filesystems are present and configured to import, each individual attempts to load the keys for ALL pools/datasets, instead of just its own. A clear and concise description of what the bug is. Steps to reproduce the behavior: encrypted zfs filesystems in your NixOS configuration. & Reboot All targets complete successfully The below snippet from the services's script. It's 'ing, and just looping over all pools/datasets. Instead, it should just specify the name directly in the command. (Generated in ) Please run and paste the result. system: host os: multi-user?: sandbox: version: nixpkgs:
Can you post the relevant Nix config you used? Do you have set to anything?
Yep, here's my zfs config. uses (unlocked at boot) is unencrypted and have on-disk
Ok, I think this is fundamentally the same issue as . Basically, when there are multiple pools and is a list, we accidentally run with no dataset argument in the import service for pools that have no datasets in the list. So those services end up iterating over all datasets on all pools instead of none.


twmnd does not launch because qt5 library path is missing. Install the twmn package and run twmnd. twmnd works when I manually set the LDLIBRARYPATH to <qtbase/lib. System: NixOS 16.09.931. Nix version: 1.11.4 Nixpkgs version:16.09.931.
I noticed the same or similar thing when trying to run twmnd as a systemd user service. It just SIGABRTs: I could reproduce with Although works fine... So clearly there is some impurity in my local environment which is making twmnd work "by accident?" Possibly related?:


BlueZ is currently setup to read auxiliary config files (i.e. , ) from its package directory, which makes it hard to write to them properly on a NixOS system. These configuration files are the only way to configure certain behaviours of , such as in , which is an important setting for device power saving. It's not possible to specify these options in . And it's not possible to specify the path of at runtime. Steps to reproduce the behavior: a file, either manually or from a nix configuration. with . hasn't loaded any settings from . (It's easy to test if you fill with trash since it should log: ). It should be possible to configure all aspects of in the same way. BlueZ loads from a hardcoded path: The same is try for : The define is set to the package directory by default. For a symlink is setup, however no such link is setup for or : I wonder if a fix for this might be adding to the of BlueZ? There's no maintainer listed in , so I'm pinging the people who last touched it :) , Please run and paste the result.
I feel like this could be easily fixed rather in the by adding 2 more options for and under (?) Let me see if I can carve out some time later this week..
Fixed in


Build PHP on non-NixOS. Both PHP 5.6 and PHP 7 fail to build for the same reason. System: Debian Nixpkgs version: 16.09
Apparently, LDAP_xxx variables are ignored: This is output by Near
Damn, this is because I have LDAP on the host system.
Ok? This also helps PHP forget host and probably other stuff.
Are you building with sandboxing disabled? If so, I think this kind of stuff is to be expected.
I know this is kind of old, but it looks like the Travis build for failed due to this issue. Any reason that patch hasn't been applied? https://travis-


I would like to use the dolibarr module without nginx. I plan to use caddy instead. In my NixOS configuration, I have . All the nginx-related settings in the dolibarr module are ignored if which is good. However, this line is not: I get the following output: This happens with simply adding to my config.
Opened for the fix, as I do not use any other web server beyond NGINX, I have no plan to maintain advanced integrations of other web servers, if you are interested into this, I will need another co-maintainer :).


Upstream issue: Since the issue seems to be specific to NixOS, let's track it here. The two commands above should only print "True". If applicable, add screenshots to help explain your problem. Tested on xonsh 0.13.3 and 0.13.4 system: host os: multi-user?: sandbox: version: nixpkgs:
Upstream fix:


The build fails in the test phase when CUDA is enabled with errors like this: Note that the did not have this problem. Steps to reproduce the behavior:
I've played around a little bit and couldn't get it working. The problems is that the CUDA drivers are available at runtime in but not in the cudatoolkit. I've symlinked and then the library is found but CUDA is not running properly in the sandbox (). I've looked around somewhat and neither Torch, nor Tensorflow, nor Numba, ... have CUDA tests running in their respective expressions. I would assume for exactly this reasons. I suggest to just disable the CUDA tests and have them running for CPU only.
That sounds reasonable.


Configuring airscan by writing to via silently does nothing, i. e. the file still has the default content. Steps to reproduce the behavior: airscan to sane backends: airscan, e. g. specific devices: After (or & reboot, etc) should contain This stopped working when upgrading from 22.05 to 22.11. I suspect the change to the module in is the root cause. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --I didn't find a entry in the sane module, so excuse me pinging the last few people who touched the module / were involved in the discussion of : Please run and paste the result.
Oh, sorry about that! I guess we can either point to somewhere else but , or figure out how to override using instead of ? As to why your config is ignored, does perhaps get ignored when is set? If so, that should probably be fixed.
Since this worked before, doesn't that mean airscan isn't using , and instead hardcodes ?
Using both and results in an error/warning at build time, but it doesn't prevent successful activation: Btw, you wrote (wrong order) in the first post :-)
You can use this workaround for now:
According to it's using the enviroment variable first, then falling back to . I guess that means in nixos 22.05 it was reading both the found in $SANECONFIGDIR (/nix/store/...) and then also I guess we can bring back the old behaviour by just pointing to or something instead of . Thoughts?
I made
Oops, I should start to copy paste this option, I always mess up the order That is a lot cleaner than what I came up with. Thanks. Wow, that was fast. Again, many thanks to you :)


Building this package twice does not produce the bit-by-bit identical result each time, making it harder to detect CI breaches. You can read more about this at https://reproducible- . Fixing bit-by-bit reproducibility also has additional advantages, such as avoiding hard-to-reproduce bugs, making content-addressed storage more effective and reducing rebuilds in such systems. You can use to analyze the differences in the output of the two builds. To view the build log of the build that produced the artifact in the binary cache: Looks like symbol ordering differences:


Since which updated from 1.9.2 to 1.10.2, the scheduler service can't be started, the error reported in the logs is: Steps to reproduce the behavior: or to see error as above in the logs The service starts succesfully <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Module maintainers: Package maintainers: Please run and paste the result.
Probably fixed by


A clear and concise description of what the bug is. Prism Launcher doesn't allow enabling Feral GameMode or MangoHud under the "Performance" tab because it can't find it. Steps to reproduce the behavior: GameMode ( ) MangoHud ( ) Prism Launcher ( ) new instance in Prism Launcher instance and go to "Performance" tab A clear and concise description of what you expected to happen. GameMode and MangoHud should be able to be enabled when installed. If applicable, add screenshots to help explain your problem. ! ! Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result.
Addressed here -


does not running when you edit . Steps to reproduce the behavior: JSON value of Running service with my setting. ! Left is generated by nixos, Right is generated by supergfxd and edit me. ! I can run without and can edit conf generated by . However, I cannot run with same setting. (edit ) I use zephyrus G14. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Please test
Complete ! Thank you !


$ nixops --version Traceback (most recent call last): File "/nix/store/ni55r1wq3wp907bii23wzxnji0myd296-nixops-", line 5, in <modulefrom nixops import deployment File "/nix/store/ni55r1wq3wp907bii23wzxnji0myd296-nixops-1.4/lib/python2.7/site-", line 15, in <moduleimport nixops.statefile File "/nix/store/ni55r1wq3wp907bii23wzxnji0myd296-nixops-1.4/lib/python2.7/site-", line 6, in <moduleimport sqlite3 File "/nix/store/rawxj3af8l2sbxv6kpclwx5f1gdxi631-python-", line 24, in <modulefrom dbapi2 import File "/nix/store/rawxj3af8l2sbxv6kpclwx5f1gdxi631-python-", line 28, in <modulefrom sqlite3 import ImportError: No module named sqlite3 System: (NixOS: 16.09.1149. (Flounder)) Nix version: (1.11.4) Nixpkgs version: (16.09.1149.)
copy
Looks like it cannot find python C extensions for sqlite3. Looking at the nix expression for the package it should actually use pysqlite instead of sqlite from python stdlib.
It seems pysqlite is broken: But pythonPackage.sqlite3 is ok. If you replace the pysqlite dep by sqlite3 in nixops expression, nixops works again. Sorry, I don't really know why pysqlite is borken...
Fixed
Thanks!