Armin K. wrote:
On 3.1.2018. 22:45, Armin K. wrote:
Still, Arch seems to have got sddm 0.17.0 working. What are the issues
you're running into with it? If it's something systemd-related, you may
always try installing elogind, a standalone systemd-logind package by
(you guessed it) Gentoo devs. If that's not an issue, I suspect
non-standard Qt install BLFS recommends (try installing it in /usr and
with plugin/qml/etc paths similar to Arch).
I suspect it does have something to do with installing qt/xorg in /opt,
but to me it is a fatal mistake to depend on directories and not use PATH
and /etc/ld.so.conf.
If plasma, xfce, lxqt, lxde, sawfish, gnome, fluxbox, icewm, openbox,
lightdm, gdm, and lxdm can work with minor, if any, changes when qt and
xorg are in /opt, then why can't sddm?
OTOH, I freely admit that I may have done something wrong when
building/configuring sddm.
I was able to get it to come up by sourcing /etc/profile in the sddm boot
script which does set the PATH. But then it would not respond to the
keyboard or mouse clicks.
But it is not just me. See http://wiki.linuxfromscratch.org/blfs/ticket/10119
https://github.com/elogind/elogind/releases
Oh, and if you're up for it and if you get elogind to work, you can then
build and use GNOME on non-systemd system, according to
https://wiki.gentoo.org/wiki/Elogind
Something to consider for the next cycle after our scheduled March
release. Adding gnome to the System V book will be a lot of work.
I'll also note that lightdm has more than the gtk based greeter.
https://www.freedesktop.org/wiki/Software/LightDM/
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
