<drakonis>
despite ariavp pushing a fix to error 400
<rycee>
The 88101 PR does not really fix the issue I'm having. Mainly it does not have any effect on non-graphical logins.
<worldofpeace>
rycee: Ahh, is there an issue in your tracker I can look at? (I believe this has to do with home-manager?)
<worldofpeace>
I did just rebase your PR 😸
<worldofpeace>
wait, I'm highly confused Jan Tojnar. https://github.com/NixOS/nixpkgs/pull/88101/files runs the socket manually, where I don't see how that's any different than `sockets.dbus.wantedBy =[ "sockets.target" ];`?
<rycee>
worldofpeace: Well, I don't think there is any particular issue that tracks everything. But my most recent run-in with this issue was a few days ago when I tried out using a new activation script for systemd units that use dbus to communicate with systemd.
<rycee>
But it was a bad idea since dbus is not available for non-graphical logins :-/
<worldofpeace>
ahh right, I saw that revert of using sd-switch
<rycee>
I did try using systemd's internal socket but I think it's dbus interface is a bit more limited. Something called sd-bus, I believe.
<drakonis>
nvm its the firewall
<rycee>
I haven't tried the 88101 solution so I don't know how well it works in integrating dbus activated services, like gnome terminal or a notification daemon like dunst.
<rycee>
But I imagine it should work ok.
<rycee>
Perhaps the systemctl `--wait` argument also works. If so then I think 88101 is a pretty complete solution, provided you are running a graphical setup.