Cannot use flake.nix for v0.2.1 due to smithay hash mismatch

[NectoT]

I would love to tell more if I knew what to tell. Below is the related error:

error: hash mismatch in fixed-output derivation '/nix/store/wfi7cqr63ybvrfjlnzamz3ljjzx8s00i-smithay-5312d5c.drv':
         specified: sha256-k3x4jRv20c2/TCgURomWgR/5oGpNOnUqnvyO+zovfvQ=
            got:    sha256-6iTLezGeSnefQbCoZHsXayinjFvrsC7ezW88tlZx9Y0=

[malbiruk]

Try 6da83e6 Does it fix the issue?

[NectoT]

Thanks, the flake is building now.

---

I am not sure if I should close the issue though, as the built package seems to be broken.

I've used builtins.getFlake in a configuration.nix file. Relevant configuration parts look like this:

let
  driftwm = (builtins.getFlake "github:malbiruk/driftwm/6da83e6fc517d9e15c1fd82f34b67c3d87a6aa3e").packages.x86_64-linux.default;
in
{
    nix.settings.experimental-features = [ "nix-command" "flakes" ];
    environment.systemPackages = [driftwm];
}

When launching driftwm as a separate program, I get a black polka dot canvas, with most shortcuts not working. Interestingly enough my Spectacle shortcut does open a window inside driftwm, so I managed to make this screenshot through the compositor itself:

The only error I can see is this one:

2026-04-20T20:22:21.324502Z ERROR smithay::backend::egl::ffi: [EGL] 0x300d (BAD_SURFACE) eglQuerySurface: eglQuerySurface

I also tried to build this flake in a clean virtual machine - the only changes made to a base KDE configuration were enabling experimental features and adding this flake and git as system packages. The results were the same.

Lastly, in that same VM I tried to use driftwm as a display manager, with even worse results - the screen was mostly black, or stuttering polka dot when moving the canvas. I've glanced the output of journalctl --reverse, but couldn't find anything screaming "error". Let me know if I can check any additional logs.

[malbiruk]

When launching driftwm as a separate program, I get a black polka dot canvas, with most shortcuts not working.

Polka dot is the default background, and the keybindings might be intercepted by the compositor inside which you open driftwm (nested mode), also win+enter should spawn terminal, it detects a few common ones (foot, alacritty, etc.).

Try rebuild the v0.3.0, there was a DRM syncobj on legacy/VM DRM fix after the commit on which you initially built, maybe it'll fix the runtime issue.