search

nefelim4ag / systemd-swap

Script for creating hybrid swap space from zram swaps, swap files and swap partitions.
GNU General Public License v3.0
550 stars 81 forks source link

Does not allow logging in to windows manager #178

Closed CrowMEV closed 2 years ago

CrowMEV commented 3 years ago

IMG_20200814_163303 Arch linux I upload a photo because when systemd-swap is running, I can't login to DE

vilgotf commented 3 years ago

Does commenting out scheduling=fifo in the .service file of systemd-swap fix this?

CrowMEV commented 3 years ago

not help

CrowMEV commented 3 years ago

161 maybe it has something to do with it again

Jturnerusa commented 3 years ago

Whoops I didn't realize this was a duplicate issue, sorry about that!

It might also be worth noting that I have 24 threads, I don't know if the issue is related to the other bug that effects high core count CPUs but I figured it might be worth mentioning.

Also on my system it is effecting more than just the window manager. I don't use systemd to login to my window manager, I have getty auto login my user to tty1 and .zprofile calls startx when logged in. Somehow it still prevents x from starting despite me being logged in.

It completely breaks any systemctl --user features as well. Hopefully some of this information is helpful!

vilgotf commented 3 years ago

@Jturnerusa @EvgenyMalikov Could you run on latest master and see if issue still persists?

dataprolet commented 3 years ago

I've got the same issue on a clean Arch install. Everything works fine after I enable ZRam in the swap.conf-file. After doing so and rebooting I get several journalctl-errors:

Dez 01 13:52:54 Fugaku systemd[1]: Failed to start Network Manager Wait Online.
Dez 01 13:52:54 Fugaku systemd[1]: systemd-logind.service: Unexpected error response from GetNameOwner(): Connection terminated
Dez 01 13:52:54 Fugaku systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated
Dez 01 13:52:54 Fugaku sddm-helper[1059]: pam_systemd(sddm-autologin:session): Failed to create session: Message recipient disconnected from message bus wi>
Dez 01 13:52:55 Fugaku sddm[897]: Failed to read display number from pipe
Dez 01 13:52:55 Fugaku sddm[897]: Could not start Display server on vt 1
Dez 01 13:54:06 Fugaku login[1104]: pam_systemd(login:session): Failed to release session: Interrupted system call

I've found a temporary workaround, but I'm not sure what this actually does. Maybe it's useful for somebody: https://github.com/systemd/systemd/issues/15316#issuecomment-643599192

oold commented 2 years ago

Very likely that this is a bug in systemd or something else. Happens to lots of people who aren't even using systemd-swap. A comment on the systemd issue suggests they forgot to update some code after they had initially fixed the problem (https://github.com/systemd/systemd/issues/15316#issuecomment-1000842001).

oold commented 2 years ago

AFAIK, the systemd bug in question was fixed some time ago. I'm going to close this.