After 4ad264dbae71c361b268ef521ace36d81b118dc8 when 2 patches were added + "${FILESDIR}"/234-0002-cryptsetup-fix-infinite-timeout-6486.patch + "${FILESDIR}"/234-0003-resolved-make-sure-idn2-conversions-are-roundtrippab.patch I realized that my system won't boot in graphical mode, sddm wont start with no reason, also noticed a lot of network related errors in the log, I'm using systemd-network. Reverting above commit fixes this issue.
Isolated this problem by enabling libidn2 USE flag(was disabled by default), . After that all works fine as before 4ad264dbae71c361b268ef521ace36d81b118dc8.
Confirmed. I'm experiencing this behavior as well and the USE="libidn2" workaround also works here.
Can you reproduce this with systemd 9999? Maybe I missed a commit somewhere.
readd ssdm in systemd fixes this issue for me # systemctl disable sddm # systemctl enable sddm
i have systemd USE="-libidn2". sddm did not automatically start on startup, even though it was enabled. running `systemctl start sddm` manually worked. readding sddm fixed start on boot for me as well.
Yeah, I don't see how libidn2 would affect sddm at all. This is probably happening due to the broken display-manager.service symlink.
Bug has been referenced in the following commit: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=934192b55ae7ecc82be37fad7b9060e2bd1abd3d commit 934192b55ae7ecc82be37fad7b9060e2bd1abd3d Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2017-08-28 22:21:45 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2017-09-03 01:14:43 +0000 x11-misc/sddm: call systemd_reenable in postinst Bug: https://bugs.gentoo.org/627984 Package-Manager: Portage-2.3.6_p39, Repoman-2.3.3_p17 x11-misc/sddm/sddm-0.14.0-r2.ebuild | 4 +++- x11-misc/sddm/sddm-0.14.0-r4.ebuild | 4 +++- x11-misc/sddm/sddm-0.15.0.ebuild | 4 +++- 3 files changed, 9 insertions(+), 3 deletions(-)
