On Sat, Jun 03, 2017 at 05:33:25PM -0600, Alan Feuerbacher wrote:
> On 6/1/2017 2:02 PM, Bruce Dubbs wrote:
> > Alan Feuerbacher wrote:
> > > I've more or less installed KDE in BLFS version 8.0, but I can't figure
> > > out how to start it. I've searched the Web and the BLFS book. KDE Plasma
> > > has a command "startkde" but there does not appear to be the equivalent
> > > for KDE 5. What am I missing?
> > >
> > > I've gone over how the startx script works to start twm. I presume that
> > > starting KDE will be similar, given the right magic words.
> >
> > It's documented on the plasma page:
> >
> > cat > ~/.xinitrc << "EOF"
> > ck-launch-session dbus-launch --exit-with-session $KF5_PREFIX/bin/startkde
> > EOF
> >
> > startx
>
> Ok. That information ought to be in the instructions for KDE5 as well as
> Plasma.
>
No, because as you then said -
> But there's another problem: there is no "startkde" binary anywhere in the
> KDE5 installation or BLFS book for KDE5. Only for Plasma.
>
The startkde program comes from plasma-workspace, or at least it did
when I last built kde on this machine (and I won't be building it
again in the near future, I'm still on legacy UIDs < 1000 and kde
does not like those).
And just think for a moment - if both kf5 and plasma produced their
own startkde program, and you were building a distro where kde was
in /usr, which one would you ship ? Having multiple packages
install the same program is never a good idea.
KF5 allows you to build kde applications (I have difficulty
understanding why people like them, but I'm sure there are good
reasons). But startkde will start the plasma desktop.
And then after that I read the rest of your mail. For some reason I
find your posts hard to parse ;)
> The closest I can find is "kdeinit5" but that does not work. I searched on
> the Net but found nothing useful.
>
> > My full .xinitrc is a bit more complex as it takes an optional argument:
> >
> > $ cat ~/.xinitrc
> > session=${2:-xfce}
> >
> > dbus="dbus-launch --exit-with-session"
> > ck="ck-launch-session dbus-launch --exit-with-session"
> >
> > case $session in
> > fluxbox ) exec startfluxbox ;;
> > icewm ) exec icewm-session ;;
> > openbox ) exec openbox-session ;;
> > sawfish ) exec sawfish ;;
> > #kde|kde4 ) exec $ck /opt/kde/bin/startkde ;;
> > kde5|plasma ) exec $ck /opt/kf5/bin/startkde ;;
> > xfce|xfce4 ) exec $ck startxfce4 ;;
> > lxde ) exec ck-launch-session startlxde ;;
> > lxqt ) $dbus /opt/lxqt/bin/startlxqt ;;
> > lxqt2 ) exec /opt/lxqt/bin/startlxqt ;;
> >
> > twm ) xterm -g 80x40+0+0 &
> > xclock -g 100x100-0+0 &
> > twm
> > ;;
> >
> > # No known session, just say so
> > *) echo "Cannot run $1" ;;
> > esac
>
> What a useful script! I installed all of the listed window managers and
> desktops, and they all work fine with this script, except for KDE5. Even
> Plasma works fine.
>
> I changed two lines for my use:
>
> plasma ) exec $ck /opt/kf5/bin/startkde ;;
> kde5 ) exec $ck /opt/kf5/bin/kdeinit5 ;;
>
> I'm suspecting that the KDE5 build is missing some software components.
>
> Alan
Well, as I said above, startkde starts plasma. The best
documentation google found for kdeinit5 is a manpage from ubuntu:
http://manpages.ubuntu.com/manpages/zesty/man8/kdeinit5.8.html
Like so many other programs, it is part of what kde uses, but it is
not a way to start a desktop.
So, Bruce's script was correct. KDE used to be a small(ish) set of
large packages, but for 5 almost everything is in its own package,
and most of those rely on a lot of the other packages.
ĸen
--
I live in a city. I know sparrows from starlings. After that
everything is a duck as far as I'm concerned. -- Monstrous Regiment
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
