* Wolfgang Bauer
Am Mittwoch, 3. Juni 2015, 07:10:57 schrieb Patrick Shanahan:
Last trials and conversation here indicate sddm is broken, not releasing and not stopping plymouthd to allow reaching graphical target. sddm *should* not be recommended for use.
Wrong. sddm only was "broken" when you enabled it with "systemctl enable sddm.service". If you use the standard display-manager.service and configure sddm in /etc/sysconfig/displaymanager, it should work fine.
Anyway, that problem should be fixed with the latest Tumbleweed snapshot: - Add sddm-service-handle-plymouth.patch -- sddm has some rudimentary support for plymouth handling, which only works with plymouth-quit.service (the servce is not enabled on openSUSE). For users of sddm.service, we need to issue plymouth quit command by hand in this case
It's of course your decision whether you use sddm or keep using kdm (or any other like lightdm for that matter) though. Both should in fact work fine. sddm still lacks features compared to kdm, like e.g. remote login.
Tks for notice, but I still have a problem with it. Of 5 machines my main desktop was the only working with sddm, installed as you describe. The latest update borked that and I had to change /etc/sysconfig/displaymanager from sddm to kdm{xdm,...} or I had only the "green screen" and no login. But the plymouthd instance present in earlier trials on other machines was not there :). I still feel too many "rough" edges to sddm for recommendation to "regular" users. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org