o1lo01ol1o has quit [Remote host closed the connection]
o1lo01ol1o has joined #home-manager
o1lo01ol1o has quit [Ping timeout: 260 seconds]
maier has joined #home-manager
quinn has joined #home-manager
maier has quit [Ping timeout: 240 seconds]
<judson_>
I've been looking at the home-manager NixOS module. I'm wondering what the best approach is to incorporate my HM config into my NixOS one, and also be able to still `home-manager switch`
<judson_>
Do I need to do anything special, actually?
kalbasit has joined #home-manager
o1lo01ol1o has joined #home-manager
o1lo01ol1o has quit [Ping timeout: 256 seconds]
cole-h has joined #home-manager
o1lo01ol1o has joined #home-manager
KarlJoad has joined #home-manager
<infinisil>
judson_: What do you mean by incorporate?
<infinisil>
home-manager switch won't work just like that then
<infinisil>
I don't think there's a reasonable way to have home-manager switch work still when you use that
<infinisil>
The most correct one would be to alias `home-manager switch` to `nixos-rebuild switch`
<judson_>
That's pretty different though.
<judson_>
There's several features of h-m I'd lose - news, replace-with-backup, etc.
<judson_>
And it "feels" like a bigger change, even though I'm contemplating it because my general use case is single-user machines.
<rycee>
judson_: infinisil is right, there is no supported way to have the home-manager tool available when using the NixOS module.
<judson_>
My impression is that the module is intended for a different use case than mine.
<infinisil>
I guess it might be possible actually, if home-manager extracted just its configuration out of the NixOS config
<infinisil>
(needs to be implemented though, and probably won't work well tbh)
<judson_>
I'm setting up a new machine at the moment and reviewing how to streamline that.
<infinisil>
judson_: What's replace-with-backup btw? I couldn't find anything in home-manager's source
<judson_>
When you switch and have files in the way, you can pass `-b bak` to have the old files moved out of the way.
<rycee>
Aye, technically I think it would be possible and I'd like to install a home-manager tool even when using the NixOS module but with the switching logic disabled.
<judson_>
I mean, I implemented it, so I find it handy :)
o1lo01ol1o has quit [Remote host closed the connection]
<infinisil>
Ah I see
<rycee>
judson_: You can set `home-manager.backupFileExtension = "whatever"`
<judson_>
In the nixos module version? That's keen.
<rycee>
And that should work like `-b whatever`.
o1lo01ol1o has joined #home-manager
<infinisil>
About the news, it would be nice if this was integrated into NixOS somehow, such that home-manager could propagate its news entries to NixOS when running as a submodule
<judson_>
I imagine that you could have `home-manager.users.judson = import home/judson/.config/nixpkgs` as a starting point. Is that misguided?
<infinisil>
judson_: That would clear any `home-manager switch`es changes when you boot next time I think
<infinisil>
Or when you rebuild switch too
<judson_>
On *boot*? That's surprising to me.
<infinisil>
Ah no
<infinisil>
Not on a rebuild switch, but on a boot
<judson_>
nixos-rebuild switch I can see, but it'd be from the exact configuration.
<judson_>
Wait, really on boot?
<rycee>
The module sets up a systemd service that runs the activation script on boot.
<infinisil>
Yeah, because the activation script runs on boot, and that will start the home-manager activation systemd service
<judson_>
Which is the equivalent of running <generation result>/activate right?
o1lo01ol1o has quit [Ping timeout: 240 seconds]
<infinisil>
Yeah
<rycee>
Yes. So if you run `home-manager switch` it would activate a generation and then when you boot the systemd service would run the activation script that contains the configuration from the previous nixos-rebuild.
<judson_>
And NixOS would have a different generation than whatever got selected by `home-manager`
<rycee>
Aye.
<rycee>
Ideally I would like to not create a per-user profile link at all when HM is used as a NixOS module and instead place the link directly inside the NixOS generation output.
maier has joined #home-manager
maier has quit [Ping timeout: 264 seconds]
o1lo01ol1o has joined #home-manager
c0c0 has joined #home-manager
<c0c0>
I'm trying to set up i3 as the window manager. I've set 'services.xserver.enable = true;' in my system configuration and 'xsession.enable = true;' in my home manager configuration, but i don't know what 'xsession.windowManager.command' should be set to. What should I set it to?
<dermetfan>
c0c0: just set `xsession.windowManager.i3.enable = true`, it will handle that for you
<c0c0>
dermetfan: i've set that now. when i reboot, i get a login prompt in lightdm. when i try to log in, it says "Failed to start session". How do I debug this?
<c0c0>
In .xsession, I found the command. When I try to run it, I get "i3: Cannot open display". Any idea what I should do?
maier has joined #home-manager
maier has quit [Ping timeout: 240 seconds]
<dermetfan>
c0c0: I guess you ran the i3 command from the tty. i3 cannot start if no xserver is running, that's why you get that error. I guess the reason that lightdm says "Failed to start session" is a different problem though... Maybe you can see it in the unit's logs after the error: `sudo journalctl -fu display-manager`
<c0c0>
dermetfan: Not sure if this is the line I'm looking for: "display-manager.service: Failed to enqueue OnFailure= job, ignoring: Unit plymouth-quit.service not found."
<c0c0>
The rest is "Killing process <pid> (<sth>) with signal SIGKILL."
__monty__ has quit [Quit: leaving]
matt61 has joined #home-manager
<matt61>
Hello all! I'm wondering... is it recommended to simply install home-manager via the environment.systemPackages in configuration.nix?
matt61 has quit [Remote host closed the connection]
matt61 has joined #home-manager
<matt61>
Sorry I dropped there for a minute...
<matt61>
I just went ahead and installed home-manager via the GitHub instructions.
<matt61>
Strangely, after adding an example program to my home.nix (programs.bat.enable = true;), and home-manager switching, it works but also says the user systemd session is degraded. Hmm.
<matt61>
"obex.service"?
<matt61>
Something related to Bluetooth, although Bluetooth seems to be working with my keyboard.
<matt61>
Anywho, fun stuff so far.
<KarlJoad>
matt61: The systemd service being degraded is likely because home-manager doesn't attempt to restart all services.
<matt61>
OK. So nothing to worry about? I saw red text! :P
<KarlJoad>
It might be nothing to worry about, I'm not entirely sure. Check the surrounding lines.
<matt61>
Hmm, it says obex.service is loaded but not active or subbed.
<matt61>
systemctl status obex.service simply says service not found.
<KarlJoad>
If it's BlueTooth, I imagine you would have to be sudo/su to find out the status of that thing.
<matt61>
Yes I ran that via sudo.
<KarlJoad>
Huh... Strange. I don't know what obex does, so I can't offer more guidance.
<matt61>
No problem!
matt61 has quit [Remote host closed the connection]
malSet_ has joined #home-manager
malSet has quit [Ping timeout: 265 seconds]
malSet has joined #home-manager
malSet_ has quit [Ping timeout: 260 seconds]
o1lo01ol1o has quit [Remote host closed the connection]
o1lo01ol1o has joined #home-manager
o1lo01ol1o has quit [Ping timeout: 256 seconds]
DigitalKiwi has joined #home-manager
dermetfan has quit [Ping timeout: 246 seconds]
maier has joined #home-manager
maier has quit [Ping timeout: 264 seconds]
asymptotically has quit [Quit: Leaving]
o1lo01ol1o has joined #home-manager
o1lo01ol1o has quit [Ping timeout: 240 seconds]
KarlJoad has left #home-manager ["ERC (IRC client for Emacs 26.3)"]