jiebi/CodeConvo huggingface dataset:
Code change:
, protobuf, speechd, libXdamage, cups , ffmpeg, libxslt, libxml2, at-spi2-core , jre <ins> , pipewire_0_2 </ins> # optional dependencies , libgcrypt ? null # gnomeSupport || cupsSupport

Related discussion:
text: Project description This flag is available in most other major distros. It is necessary to enable screen sharing on wayland inside of chromium, combined with xlr-desktop-portal-wlr and pipewire. It requires the build flag and a dependency on libpipewire02. See as an example. Metadata homepage URL: source URL: license: mit, bsd, gpl2+ , ... platforms: unix, linux, darwin, ...
that would definitely be nice to have :) I actually also noticed this but unfortunately cannot test this easily as I'm not using screen sharing. If you could contribute a PR that would be awesome (but be aware that Chromium does unfortunately take quite some time to compile). Alternatively (but less preferably) we could make the required changes with the next update and test the core functionality (as always) and you could test screen sharing after the new version is available in the binary caches. Additionally we would need to package in Nixpkgs to make this work on wlroots based compositors. On Gnome/KDE this might work out-of-the-box, but I don't know what they currently implement/provide.
was just merged w/ . I'll try building chromium w/ the flag - as you say it takes a while, so I can leave it overnight and give it a shot.
how does the situation look like with ? Is the flag available there, as in, screensharing with wayland already works there?
yes, it's available in google-chrome. ! I'm still trying to get it to work with xlr-desktop-portal-wlr - I've done this in the past, but it's not working out of the box yet with
And just to make sure, you also did set as described there?
yes I did. I'm almost got it working I think. There are a few issues out of the box: -chrome is missing the pipewire 0.2 runtime dependency, so I it as (I'm on 20.03 so pkgs.pipewire is 0.2): .pipewire service doesn't work - it doesn't seem to be setting up the path correctly. I'm trying to fix this now: My current config on 20.03 looks like: Where is the same package that was recently merged.
Code change:
, protobuf, speechd, libXdamage, cups , ffmpeg, libxslt, libxml2, at-spi2-core , jre <ins> , pipewire_0_2 </ins> # optional dependencies , libgcrypt ? null # gnomeSupport || cupsSupport

Related discussion:
text: yeah, I'm currently already looking at it - pipewire wants to execute , but it's not in . We can patch to contain the absolute path. I'll check if it works and will get back to you.
Btw, we /really/ need a sway NixOS test, and better documentation on how to use sway. I was trying stuff until it worked, and does autologin me into a sway, but there might be a smarter way to do this, without also starting X.
The sway recommendation is to just run sway from the terminal after login - that's how I do it at least. I was able to workaround the environment issue by doing (but this is a kludge I think and shouldn't be necessary). But unfortunately it's now crashing and I'm not sure why:
Yeah, even my sddm config I also had to , otherwise pipewire complained about not being able to reach dbus: Afterwards, it segfaulted, as it wasn't able to find ; I patched to be able to find the path to , and that error message is gone. Now (apart from not being able to find bluez or rtkit) it /might/ only be some version incompatibilities, not sure: I'll see if I can get as far with your chromium PR, will merge that then, and also submit the pipewire patch.
Okay, with the pipewire patch and , It seems I'm able to share at least my own application window :tada:. I don't know yet why the alacritty window nearby isn't shown, and why "Entire Screen" is black, but that's probably due to me running sway inside X via ssdm.
pipewire PRs:
I don't think you're using pipewire in that case. xdg-desktop-portal-wlr only supports full screen sharing atm. If it is black that means it's not working. By the way I had to add pipewire02 to my system packages to prevent xdg-desktop-portal from crashing. But now there seems to be some incompatibility in the pipewire service logs when chrome tries to connect:
you should be able to cherry-pick the to not have to manually add this to $PATH.
Thanks! I'm suspecting google-chrome is compiled with a too old version of pipewire.
Code change:
, protobuf, speechd, libXdamage, cups , ffmpeg, libxslt, libxml2, at-spi2-core , jre <ins> , pipewire_0_2 </ins> # optional dependencies , libgcrypt ? null # gnomeSupport || cupsSupport

Related discussion:
text: Enabling pipewire debug logs, it seems to be sending an incompatible format to the pipewire server (similar to ). I have got this working with chromium compiled against pipewire 0.2.7 in the past, so I'm pretty sure it should work assuming the client library is recent enough. Once the chromium package has that flag enabled I'll try to retest.
I just confirmed my last comment by building chromium locally w/ rtcusepipewire=true. It works perfectly for fullscreen sharing.
Hmm take that back - it worked the first time but not anymore :/. Not sure what lib is missing where.
Seems like xdg-desktop-portal is crashing:
This might be yet another version incompatibility problem. I propose merging (as it's built with 0.2 everywhere else too), and then see if we can get it to work if the system pipewire also is 0.2. I asked upstream about these problems in - maybe 0.3 needs to support 0.2 clients for some time until we should switch.
Heads-up: the bad client situation should have been fixed with the latest pipewire release, PR at
Thanks for your help! I'm still getting the xdg-desktop-portal crash, however. I'm guessing there is something missing from my dbus environment - or perhaps it's trying to access a file/directory not available in nixos.
could you open a new issue with some more details, like logs etc.?
Okay, I made
Code change:
, makeWrapper , autoreconfHook , gtk-doc <ins> , graphviz </ins> }: let python = python2.withPackages (pp: [ pp.pygtk ]);

Related discussion:
text: Installing results in a broken application that exits on startup with the message "GEGL operation missing! Glimpse requires the GEGL operation "gegl:introspect". This operation cannot be found. Check your GEGL install and ensure it has been compiled with any dependencies required for Glimpse." Steps to reproduce the behavior: to Glimpse Glimpse should work! works fine for me. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Maintainer information:
Thanks for the report, Unfortunately I cannot reproduce your issue. Neither on as you reported nor on current . Could you elaborate on your setup a bit? Which window manager/desktop environment are you using? Is it possible that you modified glimpse in an overlay? I'm running Sway (Wayland) and deleted and before testing to make sure I didn't have any leftover state in my home directory.
I'm using i3wm (with no separate desktop manager); I installed Glimpse by adding it to environment.systemPackages in , I don't think there's any chance I did anything special with overlays there. I can't think of anything else I've done that might have affected this – I only installed NixOS a few days ago. I do have Home Manager installed, so I guess is it possible that something I've installed via that is causing a problem? (I don't have that much stuff installed, though, I don't think.) on my system is a tmpfs, so if something put a file outside of /nix or /home on install and is expecting it to still be there then it'll be unhappy, but I think I tried running Glimpse immediately after installing it with and it didn't work even then, so it shouldn't be anything related to that. Deleting changes the icon in the popup, which is weird, it looks like this if that directory isn't present at statup: ! and like this if I leave the directory there: ! but nothing else seems to change. (I noticed there's a directory in and , but removing it doesn't seem to do anything.)
aha, I found the problem: works just fine, and adding graphviz to environment.systemPackages fixes it permanently. see e.g.
Code change:
, makeWrapper , autoreconfHook , gtk-doc <ins> , graphviz </ins> }: let python = python2.withPackages (pp: [ pp.pygtk ]);

Related discussion:
text: Ooh nice, didn't think about using a pure nix-shell to circumvent already installed packages clouding the issue. Now I'm able to reproduce the issue. Will add graphviz as runtime dependency then.
Looks like Gimp is not affected, as they got it . Glimpse didn't receive that fix, and it won't in the foreseeable future as the project .
Code change:
doCheck = false; postPatch = '' <del> substituteInPlace CMakeLists.txt --replace $'{SoQt_INCLUDE_DIRS}'  </del> <ins> substituteInPlace distutils_cmake/CMakeLists.txt --replace $'{SoQt_INCLUDE_DIRS}'  </ins> $'{Coin_INCLUDE_DIR}';$'{SoQt_INCLUDE_DIRS}' '';

Related discussion:
text: pivy fails to build due to being unable to find some files Steps to reproduce the behavior: try to build pivy from nixpkgs HEAD
Code change:
"-DCMAKE_INSTALL_LIBDIR=lib" "-DBUILD_DOCS:BOOL=ON" (lib.optionalString usePython "-DUSE_PYTHON=true") <ins> ] ++ lib.optionals (usePython && stdenv.isDarwin) [ # Fix python lookup on Darwin. Not necessary after # https://github.com/NixOS/nixpkgs/pull/94090 lands in master "-DPython_ROOT_DIR=${python}" </ins> ]; # by default, it will query the python interpreter for it's sitepackages location

Related discussion:
text: Describe the bug Since the recent commit ( ledger fails to build on Darwin. To Reproduce or similar. Additional context Add any other context about the problem here. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(steve): channels(root): nixpkgs: Maintainer information:
if you don't need python. do you mind trying to build it with it off?
the error you're seeing is that a header from package isn't able to be found. I don't have a darwin machine to see why these two are different
Thanks. I don't need to work around it particularly, more interested in identifying a fix. I think the issue is that it's somehow picking up the system python: so probably some of the handling is broken, and indeed there are a few suspicious portions in the output I pasted, e.g. and subsequently:
I got the same cmake warnings, upstream needs to update some of their files. I'm not familiar enough with nix-darwin to have it NOT pull in system python
Code change:
# ToDo: a ligther version of libsoup to have FTP/HTTP support? ] ++ stdenv.lib.optionals gnomeSupport (with gnome; [ libsoup gcr <ins> glib-networking # TLS support </ins> gnome-online-accounts libsecret libgdata ]);

Related discussion:
text: Inkscape has support for openclipart but it doesn't work in the package provided by nixpkgs. inkscape to File -Import Clip Art... a search term and click the Search button. the in the GUI and in the terminal. NixOS 18.09 and nixpkgs master.
I researched a bit and thought adding glib-networking would fix it. I wrote the following patch, but it doesn't seem to have any effect:
I wonder whether it really is because TLS support is unavailable, or because uses an invalid security certificate?
Good point. Hm, that's weird. I followed that URL () a day or two ago (when I first noticed this) and was redirected to https:// without problems. But now I see the certificate warning in firefox.
I think it may be a packaging bug after all. Look at this grep: The message only appears in the glib tree, in the gdummytlsbackend.c file. No matches from glib-networking, which AFAIK, provides TLS support.
I tried the patch and am getting Probably because the site is down.
is not down for me.
Thank you!
Code change:
<del> { lib , stdenv , fetchFromGitHub , buildNpmPackage , nix-update-script , electron , writeShellScriptBin , makeWrapper , copyDesktopItems , giflib , makeDesktopItem , pkg-config , pixman , cairo , pango , npm-lockfile-fix , overrideSDK , darwin </del> <ins> { lib, stdenv, fetchFromGitHub, buildNpmPackage, nix-update-script, electron, writeShellScriptBin, makeWrapper, copyDesktopItems, makeDesktopItem, pkg-config, pixman, cairo, pango, npm-lockfile-fix, overrideSDK, darwin, </ins> }: let # fix for: https://github.com/NixOS/nixpkgs/issues/272156 <del> buildNpmPackage' = buildNpmPackage.override { stdenv = if stdenv.isDarwin then overrideSDK stdenv "11.0" else stdenv; }; </del> <ins> buildNpmPackage' = buildNpmPackage.override { stdenv = if stdenv.isDarwin then overrideSDK stdenv "11.0" else stdenv; }; </ins> in buildNpmPackage' rec { pname = "bruno";

Related discussion:
text: Attempt to build on Sample This is on an M2 chip, and it seems the issue is with node-canvas not being able to install due to missing giflib. Building with: Fixes this. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Code change:
buildNpmPackage rec { pname = "bitwarden-cli"; <del> version = "2023.10.0"; </del> <ins> version = "2023.12.0"; </ins> src = fetchFromGitHub { owner = "bitwarden"; repo = "clients"; rev = "cli-v${version}"; <del> hash = "sha256-egXToXWfb9XV7JuCRBYJO4p/e+WOwMncPKz0oBgeALQ="; </del> <ins> hash = "sha256-WYhLKV3j3Ktite5u1H4fSku38hCCrMzKoxtjq6aT9yo="; </ins> }; nodejs = nodejs_18; <del> npmDepsHash = "sha256-iO8ZozVl1vOOqowQARnRJWSFUFnau46+dKfcMSkyU3o="; </del> <ins> npmDepsHash = "sha256-bnYpvHO9Pnob+MbrSshv03mSwXCADH/2xw33nLVKMdg="; </ins> nativeBuildInputs = [ python3

Related discussion:
text: Steps to reproduce the behavior: bitwarden Please run and paste the result.
Will be fixed by
Code change:
<ins> #! @bash@/bin/bash set -eo pipefail PATH=@coreutils@/bin:$PATH export CLASSPATH=@CLASSPATH@ export FREENET_HOME="$HOME/.local/share/freenet" if [ -n "$XDG_DATA_HOME" ] ; then FREENET_HOME="$XDG_DATA_HOME/freenet" fi mkdir -p -- $FREENET_HOME cp -u -- @seednodes@/seednodes.fref $FREENET_HOME/seednodes.fref chmod u+rw -- $FREENET_HOME/seednodes.fref cd -- $FREENET_HOME exec @jre@/bin/java -Xmx1024M freenet.node.NodeStarter "$@" </ins>

Related discussion:
text: Freenet installs successfully but fails to run for both the service and the package with Steps to reproduce the behavior: Failure with Or alternatively with the service = true; to config For Freenet to start and be able to access setup wizard on 127.0.0.1:8888 Add any other context about the problem here. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Code change:
<!-- To avoid merge conflicts, consider adding your item at an arbitrary place in the list instead. --> <ins> - The `power.ups` module now generates `upsd.conf`, `upsd.users` and `upsmon.conf` automatically from a set of new configuration options. This breaks compatibility with existing `power.ups` setups where these files were created manually. Back up these files before upgrading NixOS. </ins> - `mkosi` was updated to v19. Parts of the user interface have changed. Consult the [release notes](https://github.com/systemd/mkosi/releases/tag/v19) for a list of changes.

Related discussion:
text: Describe the bug I'm trying to use NixOS in a UPS client (not server). When , the and services shouldn't be running. There is a note that says that is not used currently. To Reproduce Steps to reproduce the behavior: Error: and fail. Expected behavior only upsmon should be running Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Metadata Maintainer information: See also
Looks like there's a pretty simple workaround:
I marked this as stale due to inactivity. &rarr;
Code change:
<!-- To avoid merge conflicts, consider adding your item at an arbitrary place in the list instead. --> <ins> - The `power.ups` module now generates `upsd.conf`, `upsd.users` and `upsmon.conf` automatically from a set of new configuration options. This breaks compatibility with existing `power.ups` setups where these files were created manually. Back up these files before upgrading NixOS. </ins> - `mkosi` was updated to v19. Parts of the user interface have changed. Consult the [release notes](https://github.com/systemd/mkosi/releases/tag/v19) for a list of changes.

Related discussion:
text: Describe the bug The following snippet: results in services failing to start due to missing config files etc. : : ( fails too, but that could be down to the fact that I haven't plugged the UPS in yet -- but for the record, it complains ) Expected behavior I'd expect the services to start successfully (and probably complain about the missing actual UPS). Notify maintainers (The UPS module appears to have received only drive-by changes for the last several years, so no idea who to bug personally). Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
OK, should've read the whole module: I'm supposed to supply the missing /etc/nut files myself because it's unwise to keep them in the store (they could contain passwords and whatnot, I guess?). Declaring (in the service definitions) the state directory to be but creating for the purpose appears to be a real bug, though :)
Also (sorry for the semi-off-topic) what are best practices for referencing hand-written config files without their contents winding up in the store? Double-symlinking? If this is documented somewhere, then I haven't found where.
I was struggling with the same problem as until I noticed this bug report. After copying and editing , , and from to (and setting on all those files), I was able to get it to work. I think this should be more discoverable. If it's not appropriate to copy those sample files to on the users behalf, there should at least be detailed instructions on the option to explain what else needs to be done.
I marked this as stale due to inactivity. &rarr;
Agreed this should be more discoverable. Perhaps at least could be defaulted to empty and written, since I seem to be getting away without anything in there. In case it helps anyone, I got it working with something like this:
I was hit this bug today, too. Maybe we can fix it by using a startup unit that handles the secrets and setup the state directories like nextcloud or syncthing do
Been working on today and wanted to put some notes here. Using version 2.7.4. First, isn't used by for PIDs and it will try to write to .
Code change:
<!-- To avoid merge conflicts, consider adding your item at an arbitrary place in the list instead. --> <ins> - The `power.ups` module now generates `upsd.conf`, `upsd.users` and `upsmon.conf` automatically from a set of new configuration options. This breaks compatibility with existing `power.ups` setups where these files were created manually. Back up these files before upgrading NixOS. </ins> - `mkosi` was updated to v19. Parts of the user interface have changed. Consult the [release notes](https://github.com/systemd/mkosi/releases/tag/v19) for a list of changes.

Related discussion:
text: flags , , may be needed instead of environment variables until a 2.7.5 release. Ref: Using for debug makes it non-forking, requiring a change to the systemd unit . I was able to get to run as non-root: I'm still working on understanding how to manage state directories in NixOS but this was needed:
I set out to get my UPS (cyberpower CP1500 AVR UPS) working with NixOS today. This was the first issue I came across, I figured this was the best place to share my configuration. I probably made this more complex than it needed to be because I have no idea what I am doing, and it is definitely not secure; one problem at a time.
Not stale; still relevant
Thanks for providing your standalone config! I learned a ton tweaking it into a netserver config! The below config creates a working NUT netserver that other machines on your local network can be connected to. The only thing I have yet to figure out is a secure way to include passwords in .nix files that won't show up if I push my local copy to github. Any ideas? If you want to tweak when NUT shuts down your computers you can modify the values of " = <percentage" and " = <seconds" under "directives". SHUTDOWNCMD will be triggered when both conditions are met. The "ignorelb" directive is necessary to have NUT ignore the UPS's defaults. Anyone using this config may want to make sure SHUTDOWNCMD and NOTIFYCMD point to the correct binaries in their filesystem. One other thing of note is to check the value of the "schedulerRules" field under below. You must give it the path to your file. I just put a copy of it inside my /etc/nixos. Could probably add another variable to hold the path for convenience. `
For secrets in nix config, I think the current recommendation is to put it in a separate file and not include it in the repo. See also
I have been using sops-nix to commit encrypted passwords to my NixOS repo, but I have yet to put in the elbow grease to make this work with my upsmon password.
is my attempt at making generate the config files necessary for basic operation. If you are using , could you try out the changes and leave a review?
Code change:
with lib; let cfg = config.services.networkd-dispatcher; in { options = { services.networkd-dispatcher = {

Related discussion:
text: refuses to work since it requires the directories containing the scripts to have mode 755, but the nixos module creates them with mode 750. Steps to reproduce the behavior: (re)-configure an interface (for example by unplugging and replugging a network cable) something like in the journal and that does not exist, i.e. the hook was never run. networkd-dispatcher works. <!-- 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.
Thank you for the report! I'm thinking about adding a rules option to the networkd-dispatcher module so this might solve your issue
Code change:
nlohmann_json ]; <del> NIX_LDFLAGS = lib.optionals (!atLeast24) [ # https://github.com/NixOS/nix/commit/3e85c57a6cbf46d5f0fe8a89b368a43abd26daba (lib.optionalString enableStatic "-lssl -lbrotlicommon -lssh2 -lz -lnghttp2 -lcrypto") # https://github.com/NixOS/nix/commits/74b4737d8f0e1922ef5314a158271acf81cd79f8 (lib.optionalString (stdenv.hostPlatform.system == "armv5tel-linux" || stdenv.hostPlatform.system == "armv6l-linux") "-latomic") ]; </del> postPatch = '' patchShebangs --build tests '';

Related discussion:
text: Package name: nix23 Latest released version: 2.3.17 (see ) Current version on the unstable channel: 2.3.16 Current version on the stable/release channel: 2.3.16 Notify maintainers Note for maintainers: Please tag this issue in your PR. See for context. The release script apparently doesn't upload source tarballs anymore, so 2.3.17 sources look more like the other ones. There's a bunch of expressions in that might need to be revisited.
Code change:
doCheck = (!stdenv.isDarwin); <ins> # examples.complex.xss_scanner doesn't import correctly with pytest5 </ins> checkPhase = '' export HOME=$(mktemp -d) export LC_CTYPE=en_US.UTF-8 <del> pytest -k 'not test_find_unclaimed_URLs and not test_tcp' </del> <ins> pytest --ignore test/examples  -k 'not test_find_unclaimed_URLs and not test_tcp' </ins> ''; propagatedBuildInputs = [

Related discussion:
text: Describe the bug A clear and concise description of what the bug is. mitmproxy tests broken on unstable. To Reproduce Steps to reproduce the behavior: nix-env -iA nixos-unstable.mitmproxy Additional context Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
thank you for submitting this, ill get it fixed