Regression in eb62e6aa39ea unstable channel update

This probably belongs in a issue report on GitHub, but I have very little info at the moment…

I have a minimal “base” configuration(mostly used for invoking “nixos-rebuild”, since this is quite memory hungry), and 2 specialisations(KDE Plasma 6 with Wayland resp. X, both with ‘ly’ as display manager) with configurations I actually use.
In channel update eb62e6aa39ea on unstable, ‘ly’ does not start when choosing either one of the KDE specialisations(the previous update, 9abb87b552b7f55ac8916b6fc9e5cb486656a2f3, works as it expected).

The KDE related programs does not seem to be in either the Wayland or X specialisation…

Regards,
CM

Please report these on Github instead regardless. Discourse isn’t really the place to talk about component-specific development topics; it’s usually used for discussing higher-level issues or developments.

Ideally also perform a first-parent bisect between the last known working revision and the broken one to figure out which exact PR broke ly for you.

If you want this to be fixed timely, please also provide a minimal config reproducer that we can build-vm. Reduce your configuration such that everything that isn’t necessary to repro this issue is removed.

What I don’t quite understand is why you even have specialisations for this. Shouldn’t your display-manager offer you the ability to choose a desktop session at runtime?

Specialisations cost a ton more memory and time to eval and should be avoided.

4 Likes

Thanks for the reply !
Forget everything about a regression in Nixpkgs !

It was a regression, alright…
In my PERSONAL configuration !!!

Turns out, if you try to reuse configs and modularise as much as possible, the possibility for damage is quite large if you turn your brain off… Blush !!

Regards,
CM