Ludovic Courtès <[email protected]> writes:
> Hi, > > Antonio Carlos Padoan Junior <[email protected]> skribis: > >> I do not know why but "suspend" stopped working on my computer >> after a recent upgrade (pull & reconfigure). > > By that you mean that ‘loginctl suspend’ doesn’t have any effect? > > I’ve just tried on my laptop and it works for me with this system > generation: > > $ guix system describe > Generation 204 Oct 10 2022 00:29:29 (current) > file name: /var/guix/profiles/system-204-link > canonical file name: /gnu/store/yvaj9yi25rm16q9j6jccviaf5i55hk83-system > label: GNU with Linux-Libre 5.19.14 > bootloader: grub-efi > root device: label: "root" > kernel: > /gnu/store/8s41d36dgb700p3g5jbgl5vy7wi7lbsw-linux-libre-5.19.14/bzImage > channels: > guix: > repository URL: https://git.savannah.gnu.org/git/guix.git > branch: master > commit: e827d45db92d6e1f9dc68199cd40cb5d67de9d46 > configuration file: > /gnu/store/p4w6x2q9x9cakslb0n6qcqyydn5y0a8m-configuration.scm > > >> However I'm intrigued because my >> /run/current-system/profile/etc/elogind/logind.conf > > As Tobias wrote, it’s a trap. :-) > > The config file that’s actually use can be found like so: > > $ sudo herd status elogind > Status of elogind: > It is started. > Running value is 347. > It is enabled. > Provides (elogind). > Requires (dbus-system). > Conflicts with (). > Will be respawned. > $ sudo cat /proc/347/environ |xargs -0 > ELOGIND_CONF_FILE=/gnu/store/z14j9xi29aci66d2akcflbgxzwm4lg8q-logind.conf > > I guess we could improve that user interface. > > Ludo’. I have that issue on my netbook which uses Slim as a display manager to launch an i3wm session. It looks like Slim isn't launching dbus, which also breaks a host of other things, like managing removable storage devices. The problem is not present on my x64 machine where I manually launch Sway with dbus-run-session.
