Open Ericson2314 opened 5 years ago
Yeah, the only thing that could be "some dbus thing was down" would probably be accountsservice.
Anything funny going on in the files at /var/lib/AccountsService/users
, for example SystemAccount=True
?
home manager controlled xsession
I believe we've disabled xterm in 19.09 in some manner, so perhaps try enabling services.xserver.desktopManager.xterm.enable
. IIRC home-manager was somehow relying on that.
@worldofpeace Yup! services.xserver.desktopManager.xterm.enable = true
fixed it. Thanks! @rycee heads up for installation instructions etc.
Now that just leaves eh missing user list, which I should open a separate issue for.
Regardless of home manager, there probably should be some sort of state dir or warning or something that xterm isn't on by default?
It looks like exactly this same issue has happened again in 20.03, which resulted in an unpleasant half-hour of vterm configuration debugging when I updated. lightdm requires some sessions defined to let you log in, and there are none defined by default. Enabling any session at all fixes things, because the nixos session wrapper script tries ~/.xsession before doing what it's supposed to.
I see https://github.com/NixOS/nixpkgs/pull/68371 might have been a fix, but it's been abandoned for a few months.
@Ralith The solution is to enable some sort of desktop manager, xterm. It was in the release notes when this was relevant. The bug is more of a home-manager issue, so it lives there https://github.com/rycee/home-manager/issues/1116. The docs could be updated there to enable xterm, or it could provide a nixos module with an empty one.
It was in the release notes when this was relevant.
This was not in the 20.03 release notes, and it worked fine before updating, presumably due to the above reversions. Indeed I carefully reviewed the 20.03 release notes before updating, and this did not prevent my system from being broken.
@Ralith What I meant by "when this was relevant" is the issue existed in 19.09. So it was in the 19.09 release notes, because it was where the change happened. That wasn't meant to be a jab at your competence, you couldn't have been aware because the issue wasn't a 20.03 change. It's indeed interesting you'd encounter this now though, did you change your stateVersion?
No, my stateVersion remains at 19.09.
@Ralith An alternative might be to do something like the suggestion here: https://discourse.nixos.org/t/opening-i3-from-home-manager-automatically/4849/8
Hello, I'm a bot and I thank you in the name of the community for opening this issue.
To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human.
The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it.
If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use Git blame or GitHub's web interface on the relevant files to find them.
Lastly, you can always ask for help at our Discourse Forum or at #nixos' IRC channel.
Describe the bug
When I tried 19.09 (https://github.com/Ericson2314/nixos-configuration/commit/4182b732eb1b07cc6fa0070108e75ffa9584a531 should be representative, I am booting from an old nixos generation with that ATM), LightDM no longer had me under the easy-access dropdown list of users. When I logged in by typing my username instead, the login failed, and I couldn't find anything fresh in:
~/.xsesssion-errors
/var/log/lightdm.log
3journalctl --user <stuff>
I temporary switched display managers to slim, and that did work. (well my user systemd units seemed a bit messed up, but I am not sure that is releted.)
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context
@matthewbauer thought that perhaps there was some dbus thing was down, and so lightdm neither learned who the list of users was, nor had enough information do the log in.
Metadata Please run
nix run nixpkgs.nix-info -c nix-info -m
and paste the result.Maintainer information: