jiebi/CodeConvo huggingface dataset:
Code change:
H.264 videos and specifically those (WebM and Theora are fine) don't play, which means that videos on Facebook and Twitter (at least) report an error. There are instructions for getting a patched version of the ffmpeg lib installed into your home folder which works, but ideally wouldn't be needed: to that the H.264 video don't work but the others do. System: (NixOS: , Ubuntu/Fedora: , ...) Nix version: (run ) Nixpkgs version: (run ) Sandboxing enabled: (run )
What browser are you using? Works on Chromium, Firefox and qutebrowser (qtwebkit) on master for me.
Vivaldi, hence the title of the issue...
Oh, sorry, didn't know there's a browser called vivaldi.

Related discussion:
text: atk alsaLib dbus_libs cups gtk3 gdk_pixbuf libexif ffmpeg systemd freetype fontconfig libXrender libuuid expat glib nss nspr gstreamer libxml2 gst-plugins-base pango cairo gnome3.gconf <del> ]; </del> <ins> ] ++ stdenv.lib.optional proprietaryCodecs vivaldi-ffmpeg-codecs; </ins> libPath = stdenv.lib.makeLibraryPath buildInputs + stdenv.lib.optionalString (stdenv.is64bit)
Code change:
H.264 videos and specifically those (WebM and Theora are fine) don't play, which means that videos on Facebook and Twitter (at least) report an error. There are instructions for getting a patched version of the ffmpeg lib installed into your home folder which works, but ideally wouldn't be needed: to that the H.264 video don't work but the others do. System: (NixOS: , Ubuntu/Fedora: , ...) Nix version: (run ) Nixpkgs version: (run ) Sandboxing enabled: (run )
What browser are you using? Works on Chromium, Firefox and qutebrowser (qtwebkit) on master for me.
Vivaldi, hence the title of the issue...
Oh, sorry, didn't know there's a browser called vivaldi.

Related discussion:
text: --set-interpreter "$(cat $NIX_CC/nix-support/dynamic-linker)"  --set-rpath "${libPath}"  opt/vivaldi/vivaldi-bin <ins> '' + stdenv.lib.optionalString proprietaryCodecs '' sed -i '/^VIVALDI_FFMPEG_FOUND/ a  checkffmpeg "${vivaldi-ffmpeg-codecs}/lib/libffmpeg.so"' opt/vivaldi/vivaldi '' + '' </ins> echo "Finished patching Vivaldi binaries" '';
Code change:
H.264 videos and specifically those (WebM and Theora are fine) don't play, which means that videos on Facebook and Twitter (at least) report an error. There are instructions for getting a patched version of the ffmpeg lib installed into your home folder which works, but ideally wouldn't be needed: to that the H.264 video don't work but the others do. System: (NixOS: , Ubuntu/Fedora: , ...) Nix version: (run ) Nixpkgs version: (run ) Sandboxing enabled: (run )
What browser are you using? Works on Chromium, Firefox and qutebrowser (qtwebkit) on master for me.
Vivaldi, hence the title of the issue...
Oh, sorry, didn't know there's a browser called vivaldi.

Related discussion:
text: "$out"/opt/vivaldi/product_logo_''${d}.png  "$out"/share/icons/hicolor/''${d}x''${d}/apps/vivaldi.png done <ins> wrapProgram "$out/bin/vivaldi"  --suffix XDG_DATA_DIRS : ${gtk3}/share/gsettings-schemas/${gtk3.name}/ </ins> ''; meta = with stdenv.lib; {
Code change:
H.264 videos and specifically those (WebM and Theora are fine) don't play, which means that videos on Facebook and Twitter (at least) report an error. There are instructions for getting a patched version of the ffmpeg lib installed into your home folder which works, but ideally wouldn't be needed: to that the H.264 video don't work but the others do. System: (NixOS: , Ubuntu/Fedora: , ...) Nix version: (run ) Nixpkgs version: (run ) Sandboxing enabled: (run )
What browser are you using? Works on Chromium, Firefox and qutebrowser (qtwebkit) on master for me.
Vivaldi, hence the title of the issue...
Oh, sorry, didn't know there's a browser called vivaldi.

Related discussion:
text: <ins> { stdenv, fetchurl, fetchpatch , dbus_glib, gtk2, gtk3, libexif, libpulseaudio, libXScrnSaver, ninja, nss , pciutils, pkgconfig, python2, xdg_utils }: stdenv.mkDerivation rec { name = "${product}-${version}"; product = "vivaldi-ffmpeg-codecs"; version = "59.0.3071.104"; src = fetchurl { url = "https://commondatastorage.googleapis.com/chromium-browser-official/chromium-${version}.tar.xz"; sha512 = "419cf5bafa80f190cd301c2933502351929c1ef1d5cfedc720ce6762674a0e6af3b4246a8f92e0c29743420338b056061d4e7f9f4a4066a5bdd4d2ee8db3ddbf"; }; buildInputs = [ ]; nativeBuildInputs = [ dbus_glib gtk2 gtk3 libexif libpulseaudio libXScrnSaver ninja nss pciutils pkgconfig python2 xdg_utils ]; configurePhase = '' runHook preConfigure local args="ffmpeg_branding="ChromeOS" proprietary_codecs=true enable_hevc_demuxing=true use_gconf=false use_gio=false use_gnome_keyring=false use_kerberos=false use_cups=false use_sysroot=false use_gold=false linux_use_bundled_binutils=false fatal_linker_warnings=false treat_warnings_as_errors=false is_clang=false is_component_build=true is_debug=false symbol_level=0" python tools/gn/bootstrap/bootstrap.py -v -s --no-clean --gn-gen-args "$args" out/Release/gn gen out/Release -v --args="$args" runHook postConfigure ''; buildPhase = '' ninja -C out/Release -v libffmpeg.so ''; dontStrip = true; installPhase = '' mkdir -p "$out/lib" cp out/Release/libffmpeg.so "$out/lib/libffmpeg.so" ''; meta = with stdenv.lib; { description = "Additional support for proprietary codecs for Vivaldi"; homepage    = "https://ffmpeg.org/"; license     = licenses.lgpl21; maintainers = with maintainers; [ lluchs ]; platforms   = [ "x86_64-linux" ]; }; } </ins>
Code change:
H.264 videos and specifically those (WebM and Theora are fine) don't play, which means that videos on Facebook and Twitter (at least) report an error. There are instructions for getting a patched version of the ffmpeg lib installed into your home folder which works, but ideally wouldn't be needed: to that the H.264 video don't work but the others do. System: (NixOS: , Ubuntu/Fedora: , ...) Nix version: (run ) Nixpkgs version: (run ) Sandboxing enabled: (run )
What browser are you using? Works on Chromium, Firefox and qutebrowser (qtwebkit) on master for me.
Vivaldi, hence the title of the issue...
Oh, sorry, didn't know there's a browser called vivaldi.

Related discussion:
text: <ins> #!/usr/bin/env nix-shell #!nix-shell -i bash -p libarchive curl common-updater-scripts set -eu -o pipefail cd "$(dirname "${BASH_SOURCE[0]}")" root=../../../../.. export NIXPKGS_ALLOW_UNFREE=1 version() { (cd "$root" && nix-instantiate --eval --strict -A "$1.version" | tr -d '"') } vivaldi_version_old=$(version vivaldi) vivaldi_version=$(curl -sS https://vivaldi.com/download/ | sed -rne 's/.*vivaldi-stable_([0-9]+.[0-9]+.[0-9]+.[0-9]+-[0-9]+)_amd64.deb.*/1/p') if [[ "$vivaldi_version" = "$vivaldi_version_old" ]]; then echo "nothing to do, vivaldi $vivaldi_version is current" exit fi # Download vivaldi and save hash and file path. url="https://downloads.vivaldi.com/stable/vivaldi-stable_${vivaldi_version}_amd64.deb" mapfile -t prefetch < <(nix-prefetch-url --print-path "$url") hash=${prefetch[0]} path=${prefetch[1]} echo "vivaldi: $vivaldi_version_old -> $vivaldi_version" (cd "$root" && update-source-version vivaldi "$vivaldi_version" "$hash") # Check vivaldi-ffmpeg-codecs version. chromium_version_old=$(version vivaldi-ffmpeg-codecs) chromium_version=$(bsdtar xOf "$path" data.tar.xz | bsdtar xOf - ./opt/vivaldi/vivaldi-bin | strings | grep -A2 -i '^chrome/' | grep '^[0-9]+.[0-9]+.[1-9][0-9]+.[0-9]+') if [[ "$chromium_version" != "$chromium_version_old" ]]; then echo "vivaldi-ffmpeg-codecs: $chromium_version_old -> $chromium_version" (cd "$root" && update-source-version vivaldi-ffmpeg-codecs "$chromium_version") fi </ins>
Code change:
H.264 videos and specifically those (WebM and Theora are fine) don't play, which means that videos on Facebook and Twitter (at least) report an error. There are instructions for getting a patched version of the ffmpeg lib installed into your home folder which works, but ideally wouldn't be needed: to that the H.264 video don't work but the others do. System: (NixOS: , Ubuntu/Fedora: , ...) Nix version: (run ) Nixpkgs version: (run ) Sandboxing enabled: (run )
What browser are you using? Works on Chromium, Firefox and qutebrowser (qtwebkit) on master for me.
Vivaldi, hence the title of the issue...
Oh, sorry, didn't know there's a browser called vivaldi.

Related discussion:
text: vivaldi = callPackage ../applications/networking/browsers/vivaldi {}; <ins> vivaldi-ffmpeg-codecs = callPackage ../applications/networking/browsers/vivaldi/ffmpeg-codecs.nix {}; </ins> openmpt123 = callPackage ../applications/audio/openmpt123 {}; opusfile = callPackage ../applications/audio/opusfile { };
Code change:
Steps to reproduce the behavior: macOS: Since , this fails on macOS due to case-insensitivity (). The offending PR had no description, no reviews and no reports of tests on any platform. It was merged by the author four days after it was opened. Please run and paste the result.
Fuck MacOS and their stupid case insensitive file system.
Can you try mv'ing the file first to another name like?

Related discussion:
text: cabextract --lowercase viewer1.cab # rename to more standard names <ins> # handle broken macOS file-system </ins> mv andalemo.ttf  Andale_Mono.ttf mv ariblk.ttf    Arial_Black.ttf <del> mv arial.ttf     Arial.ttf </del> <ins> mv arial.ttf     Arial.ttf.tmp mv Arial.ttf.tmp Arial.ttf </ins> mv arialbd.ttf   Arial_Bold.ttf mv arialbi.ttf   Arial_Bold_Italic.ttf mv ariali.ttf    Arial_Italic.ttf
Code change:
Steps to reproduce the behavior: macOS: Since , this fails on macOS due to case-insensitivity (). The offending PR had no description, no reviews and no reports of tests on any platform. It was merged by the author four days after it was opened. Please run and paste the result.
Fuck MacOS and their stupid case insensitive file system.
Can you try mv'ing the file first to another name like?

Related discussion:
text: mv courbd.ttf    Courier_New_Bold.ttf mv couri.ttf     Courier_New_Italic.ttf mv courbi.ttf    Courier_New_Bold_Italic.ttf <del> mv georgia.ttf   Georgia.ttf </del> <ins> mv georgia.ttf   Georgia.ttf.tmp mv Georgia.ttf.tmp   Georgia.ttf </ins> mv georgiab.ttf  Georgia_Bold.ttf mv georgiai.ttf  Georgia_Italic.ttf mv georgiaz.ttf  Georgia_Bold_Italic.ttf <del> mv impact.ttf    Impact.ttf mv tahoma.ttf    Tahoma.ttf </del> <ins> mv impact.ttf    Impact.ttf.tmp mv Impact.ttf.tmp    Impact.ttf mv tahoma.ttf    Tahoma.ttf.tmp mv Tahoma.ttf.tmp    Tahoma.ttf </ins> mv times.ttf     Times_New_Roman.ttf mv timesbd.ttf   Times_New_Roman_Bold.ttf mv timesbi.ttf   Times_New_Roman_Bold_Italic.ttf
Code change:
Steps to reproduce the behavior: macOS: Since , this fails on macOS due to case-insensitivity (). The offending PR had no description, no reviews and no reports of tests on any platform. It was merged by the author four days after it was opened. Please run and paste the result.
Fuck MacOS and their stupid case insensitive file system.
Can you try mv'ing the file first to another name like?

Related discussion:
text: mv trebucbd.ttf  Trebuchet_MS_Bold.ttf mv trebucit.ttf  Trebuchet_MS_Italic.ttf mv trebucbi.ttf  Trebuchet_MS_Italic.ttf <del> mv verdana.ttf   Verdana.ttf </del> <ins> mv verdana.ttf   Verdana.ttf.tmp mv Verdana.ttf.tmp   Verdana.ttf </ins> mv verdanab.ttf  Verdana_Bold.ttf mv verdanai.ttf  Verdana_Italic.ttf mv verdanaz.ttf  Verdana_Bold_Italic.ttf <del> mv webdings.ttf  Webdings.ttf </del> <ins> mv webdings.ttf  Webdings.ttf.tmp mv Webdings.ttf.tmp  Webdings.ttf </ins> install -m444 -Dt $out/share/fonts/truetype *.ttf
Code change:
Project description A sleek notification daemon for Wayland compositors. Metadata homepage URL: source URL: license: mpl platforms: unix, linux, darwin, ...
PR:

Related discussion:
text: <ins> { lib , rustPlatform , fetchFromGitLab , pkg-config , fontconfig , libxkbcommon , wayland }: rustPlatform.buildRustPackage rec { pname = "salut"; version = "unstable-2022-12-17"; src = fetchFromGitLab { owner = "snakedye"; repo = "salut"; rev = "aa57c4d190812908a9c32cd49cff14390c6dfdcb"; hash = "sha256-W0lhhImSXtYJDeMbxyEioYu/Bh7ZclwR1/5DzNbxM8o="; }; cargoLock = { lockFile = ./Cargo.lock; outputHashes = { "msg-api-0.1.0" = "sha256-SGEr9kitvD+KZPGejwDAISK6ERk7G2uskxX8ljiJ2To="; "smithay-client-toolkit-0.16.0" = "sha256-kiTO+BZIgpuwAr6gs9FCqz81jRg+3dV4NxzOX9kbJOc="; "snui-0.1.4" = "sha256-jJL9ukSOczHjPM2EAXcXcz620SK4DQfr+xAT8v7fp9o="; "snui-adwaita-0.1.0" = "sha256-pILhLMzqnhLZfGAXT8QQn6x+IvwG7CSa96wZqq1yrLY="; }; }; nativeBuildInputs = [ pkg-config ]; buildInputs = [ fontconfig libxkbcommon wayland ]; meta = { description = "A sleek notification daemon for Wayland"; homepage = "https://gitlab.com/snakedye/salut/-/wikis/Home"; license = lib.licenses.mpl20; maintainers = with lib.maintainers; [ eclairevoyant ]; mainProgram = "salut"; platforms = lib.platforms.linux; }; } </ins>
Code change:
Steps to reproduce the behavior: Posting on behalf of someone who was asking for help on Discord. Please run and paste the result.
Bad hash was introduced in
Looking at the ofborg history on the PR, I'm wondering if upstream did a sneaky tag change shortly after the release...
sneaky tag-switch theory pretty much confirmed. Can we switch this package to always use commit ids in the future? If they've done it once...
before switching to the more obscure commit ids, I would ask upstream not to do this anymore
I think it's better to notify in upstream so he's aware of the situation.
I already notified about this in so he's aware Meanwhile I'll change the commit hash to match the new id.
My bad. I was caused by the GitHub Action, so I force-pushed the tag . Really sorry for the inconvenience and I will never do this again

Related discussion:
text: owner = "fuyufjh"; repo = pname; rev = "v${version}"; <del> hash = "sha256-gTyjj7NND5IYtnXhc454cWSzhAE+DwfPRGEWrHH+GNM="; </del> <ins> hash = "sha256-oP0yIdYytXSsbZ2pNaZ8Rrak1qJsudTe/oP6dGncGUM="; </ins> }; cargoHash = "sha256-yKHAZpELuUD7wlM3Mi7XvxbKgdU1QxD9hsvIFcj3twE=";
Code change:
torchWithRocm hydra build fails because of too many logs. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
How exactly do you fix this? Is there a hydra option we can put in the derivation? Otherwise, do we have to omit warnings?
I have a fix by omitting some warnings, but should we do that? Should we instead get hydra to allow bigger logs?

Related discussion:
text: # error: cast from ... to ... converts to incompatible function type [-Werror,-Wcast-function-type-strict] ++ lib.optionals (stdenv.cc.isClang && lib.versionAtLeast stdenv.cc.version "16") [ "-Wno-error=cast-function-type-strict" <ins> # Suppresses the most spammy warnings. # This is mainly to fix https://github.com/NixOS/nixpkgs/issues/266895. ] ++ lib.optionals rocmSupport [ "-Wno-#warnings" "-Wno-cpp" "-Wno-unknown-warning-option" "-Wno-ignored-attributes" "-Wno-deprecated-declarations" "-Wno-defaulted-function-deleted" "-Wno-pass-failed" ] ++ [ "-Wno-unused-command-line-argument" "-Wno-maybe-uninitialized" "-Wno-uninitialized" "-Wno-array-bounds" "-Wno-stringop-overflow" "-Wno-free-nonheap-object" "-Wno-unused-result" </ins> ])); nativeBuildInputs = [
Code change:
Package is broken at version 0.1.8. It still worked at version 0.1.7, so I assume that is to blame. I've verified that the issue is fixed in 0.1.9, so I assume all that's needed would be to kick the bot. Not sure how to do that. No panic

Related discussion:
text: buildGoModule rec { pname = "bluetuith"; <del> version = "0.1.8"; </del> <ins> version = "0.1.9"; </ins> src = fetchFromGitHub { owner = "darkhz"; repo = pname; rev = "v${version}"; <del> sha256 = "sha256-b+J+8nxFZYJlAKOStpH7ItPqMw7inM5pss17kyX1brg="; </del> <ins> sha256 = "sha256-vdHnG0uQdy5PboIovtxl5i9xwFpjYLCZf2IGeiMcWe8="; </ins> }; <del> vendorHash = "sha256-d0O54KNGLXU8FGr1eSEp30JMWNVo91Le2MI8UnAfTuU="; </del> <ins> vendorHash = "sha256-pYVEFKLPfstWWO6ypgv7ntAaE1Wmq2XKuZC2ccMa8Vc="; </ins> ldflags = [ "-s" "-w" ];
Code change:
Steps to reproduce the behavior: vulkan-validation-layers 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.
The dependency causing this is vulkan-utility-libraries: 1.3.269 -1.3.270 This version bump causes vulkan-validation-layers to fail. Its only dependency is and that is fine. So problem is
The latest SDK version is 1.3.268. vulkan-utility-libraries should be rolled back to that version; we should not be packaging non-SDK versions of Vulkan SDK components, and especially not piecemeal.
indeed reverting it to fixed the build and runtime

Related discussion:
text: stdenv.mkDerivation (finalAttrs: { pname = "vulkan-utility-libraries"; <del> version = "1.3.270"; </del> <ins> version = "1.3.268"; </ins> src = fetchFromGitHub { owner = "KhronosGroup"; repo = "Vulkan-Utility-Libraries"; rev = "v${finalAttrs.version}"; <del> hash = "sha256-P1v5UEAooTDGA10K4uck8lhcrbW2ccl44gWIGVnZ6uo="; </del> <ins> hash = "sha256-O1agpzZpXiQZFYx1jPosIhxJovZtfZSLBNFj1LVB1VI="; </ins> }; nativeBuildInputs = [ cmake python3 ];
Code change:
root has not been successfully built since 2023-08-27 with version 6.26.10 by hydra.

Related discussion:
text: "-Druntime_cxxmodules=OFF" ]; <ins> # suppress warnings from compilation of the vendored clang to avoid running into log limits on the Hydra NIX_CFLAGS_COMPILE = lib.optionals stdenv.cc.isGNU [ "-Wno-shadow" "-Wno-maybe-uninitialized" ]; </ins> # Workaround the xrootd runpath bug #169677 by prefixing [DY]LD_LIBRARY_PATH with ${lib.makeLibraryPath xrootd}. # TODO: Remove the [DY]LDLIBRARY_PATH prefix for xrootd when #200830 get merged. postInstall = ''
Code change:
When specifying multiple paths in a single parityFile entry (SnapRAID ), the systemd service failes with the following error: Steps to reproduce the behavior: a SnapRAID config and specify a entry like so: run the snapraid sync: the error: The runs without error. SnapRAID has a where you can specify "split" parity files. This is useful when you're using 16tb or bigger ext4-formatted disks for parity. ext4 doesn't support files bigger than 16tb so this "split parity file" can be used to specify two parity files on a single raid disk and SnapRAID will automatically use the second file when the first cannot grow anymore (hits 16TB). You specify these multiple files by putting multiple comma-separated paths in the . This mostly already works except when it comes to the scheduled systemd sync job where it specifies . If you specify a parity with multiple files you'll get an error when the systemd job runs: It seems like since SnapRAID essentially does not allow commas in the parity file paths it would be OK to split on comma here? Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: qemu-vm module from overriding `fileSystems` by setting `virtualisation.fileSystems = lib.mkForce { };`. <ins> - When using [split parity files](https://www.snapraid.it/manual#7.1) in `snapraid`, the snapraid-sync systemd service will no longer fail to run. </ins> ## Nixpkgs Library {#sec-release-23.11-nixpkgs-lib} ### Breaking Changes {#sec-release-23.11-lib-breaking}
Code change:
When specifying multiple paths in a single parityFile entry (SnapRAID ), the systemd service failes with the following error: Steps to reproduce the behavior: a SnapRAID config and specify a entry like so: run the snapraid sync: the error: The runs without error. SnapRAID has a where you can specify "split" parity files. This is useful when you're using 16tb or bigger ext4-formatted disks for parity. ext4 doesn't support files bigger than 16tb so this "split parity file" can be used to specify two parity files on a single raid disk and SnapRAID will automatically use the second file when the first cannot grow anymore (hits 16TB). You specify these multiple files by putting multiple comma-separated paths in the . This mostly already works except when it comes to the scheduled systemd sync job where it specifies . If you specify a parity with multiple files you'll get an error when the systemd job runs: It seems like since SnapRAID essentially does not allow commas in the parity file paths it would be OK to split on comma here? Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: # to remove them if they are stale let contentDirs = map dirOf contentFiles; <ins> # Multiple "split" parity files can be specified in a single # "parityFile", separated by a comma. # https://www.snapraid.it/manual#7.1 splitParityFiles = map (s: splitString "," s) parityFiles; </ins> in unique ( <del> attrValues dataDisks ++ parityFiles ++ contentDirs </del> <ins> attrValues dataDisks ++ splitParityFiles ++ contentDirs </ins> ); } // optionalAttrs touchBeforeSync { ExecStartPre = "${pkgs.snapraid}/bin/snapraid touch";
Code change:
Budgie desktop stopped working a few months ago on because gsettings schema supplied by Budgie is missing settings which was recently to . This causes to crash during startup making Budgie DE setup unusable. budgie-desktop from . .
Are you using Budgie alongside another desktop? Otherwise LightDM is the preferred choice for Budgie, but I will still look into this.
Oh, I didn't know that. When I switched from gnome to budgie, I kept and everything worked, so I kept it. I can confirm that if I use , everything works.

Related discussion:
text: , libwacom , libxml2 , libxslt <del> , magpie </del> , meson , modemmanager , networkmanager
Code change:
Budgie desktop stopped working a few months ago on because gsettings schema supplied by Budgie is missing settings which was recently to . This causes to crash during startup making Budgie DE setup unusable. budgie-desktop from . .
Are you using Budgie alongside another desktop? Otherwise LightDM is the preferred choice for Budgie, but I will still look into this.
Oh, I didn't know that. When I switched from gnome to budgie, I kept and everything worked, so I kept it. I can confirm that if I use , everything works.

Related discussion:
text: gnome.gnome-remote-desktop gnome.gnome-settings-daemon gnome.gnome-user-share <ins> gnome.mutter </ins> gsettings-desktop-schemas gsound gtk3
Code change:
Budgie desktop stopped working a few months ago on because gsettings schema supplied by Budgie is missing settings which was recently to . This causes to crash during startup making Budgie DE setup unusable. budgie-desktop from . .
Are you using Budgie alongside another desktop? Otherwise LightDM is the preferred choice for Budgie, but I will still look into this.
Oh, I didn't know that. When I switched from gnome to budgie, I kept and everything worked, so I kept it. I can confirm that if I use , everything works.

Related discussion:
text: libsecret libwacom libxml2 <del> magpie </del> modemmanager networkmanager polkit
Code change:
Budgie desktop stopped working a few months ago on because gsettings schema supplied by Budgie is missing settings which was recently to . This causes to crash during startup making Budgie DE setup unusable. budgie-desktop from . .
Are you using Budgie alongside another desktop? Otherwise LightDM is the preferred choice for Budgie, but I will still look into this.
Oh, I didn't know that. When I switched from gnome to budgie, I kept and everything worked, so I kept it. I can confirm that if I use , everything works.

Related discussion:
text: --prefix XDG_DATA_DIRS : "${gdk-pixbuf}/share" --prefix XDG_DATA_DIRS : "${librsvg}/share" # WM keyboard shortcuts <del> --prefix XDG_DATA_DIRS : "${magpie}/share" </del> <ins> --prefix XDG_DATA_DIRS : "${gnome.mutter}/share" </ins> ) '';