On 06/25/2014 09:08 PM, Alexei Robyn wrote:
> Hello Mateusz,
>
> Slimlock was originally a separate project that pretty much just hacked
> slock to read slim's configuration file & display its configured theme,
> but at some point became mostly-abandoned and then was later merged into
> slim itself, so yes, the slim package provides the slimlock binary.
>
> From what I've seen from using it on other distributions, slimlock in
> general appears to have some issues / be broken - it's not
> NixOS-specific breakage. There appear to be issues using some (but not
> all) non-default slim themes, as well as issues with multi-monitor
> configurations. There's nothing in particular stopping one from using a
> slimlock provided by a separate package, but I'm not sure any of the
> various forks are any better maintained / less buggy than the version
> integrated into slim, so you might have to investigate further there, if
> you're interested.
>
> Hope that helps, Alexei
Interesting. I am running multi-head setup so maybe that's breaking it.
I should try with a single monitor. I think what remains here is for me
to try the separate slimlock because the slim project itself seems all dead.
Thanks for clearing it up
> On Thu, Jun 26, 2014, at 01:12 AM, Mateusz Kowalczyk wrote:
>> Hi,
>>
>> I'm trying to investigate [1]. The gist of it is that when I start my
>> system, X gets started and I land at a login screen with my custom
>> theme. After I log in and I run ‘slimlock’, the theme is crippled (no
>> background and boxes are in wrong places).
>>
>> Today I tried to look into the matter but I got really confused:
>>
>> * greping for slimlock only shows a single referenc that's not a comment
>> or inside a patch file:
>>
>> ./nixos/modules/services/x11/display-managers/slim.nix:124:
>> security.pam.services.slimlock = {};
>>
>> What confuses me here is that the slimlock application as can be seen at
>> [2] is not actually packaged. From what I gather in that case is that
>> ‘slimlock’ binary is provided by the ‘slim’ package and if I were to
>> compile [2], I would get a binary of the same name, aiming to achieve
>> the same goal but that does some things differently. This alone makes me
>> think that this is where my source of trouble is: do I need to package
>> [2] and invoke that binary instead?
>>
>> * Checking the slim.nix module I see how it is ran:
>>
>> execCmd = "exec ${pkgs.slim}/bin/slim";
>>
>> But running ‘slim’ from my terminal seems to do absolutely nothing.
>>
>> Perhaps it has something to do with the run-once.patch:
>>
>> - Run();
>> + exit(OK_EXIT);
>>
>> And a comment in the default.nix for slim package:
>> # Exit after the user's session has finished. This works around
>> # slim's broken PAM session handling (see
>> #
>> http://developer.berlios.de/bugs/?func=detailbug&bug_id=19102&group_id=2663).
>>
>> berilos has shut down so I don't know why this patch is necessary.
>> However it might mean that I can't call ‘slim’ and expect it to do
>> something once I'm already logged in.
>>
>>
>> With this I'm rather confused: is ‘slimlock’ I'm using something that
>> comes from the original slim project and that perhaps happens to be
>> broken somehow on NixOS? Notably, slimlock -p pathtomytheme works
>> perfectly.
>>
>> Do we need to package [2] and use that for locking? Is that what other
>> distros are doing? I notice that on Gentoo they used to have a slimlock
>> package but now don't. In fact at [3] they say that it has been
>> integrated into slim: does this mean [2] is obsolete? [4] seems to imply
>> they are still separate projects. What should I be using?
>>
>> Can someone more knowledgeable explain the situation? Is anyone using
>> slimlock with custom theme?
>>
>> [1]: https://github.com/NixOS/nixpkgs/issues/2954
>> [2]: https://github.com/dannyn/slimlock
>> [3]: https://bugs.gentoo.org/show_bug.cgi?id=474892
>> [4]: https://bugs.gentoo.org/show_bug.cgi?id=489010
>>
>> --
>> Mateusz K.
>> _______________________________________________
>> nix-dev mailing list
>> [email protected]
>> http://lists.science.uu.nl/mailman/listinfo/nix-dev
> _______________________________________________
> nix-dev mailing list
> [email protected]
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
--
Mateusz K.
_______________________________________________
nix-dev mailing list
[email protected]
http://lists.science.uu.nl/mailman/listinfo/nix-dev
