I use the meta port x11/plasma5-plasma, as it includes a few more niceties such as gtk theme integration and audio mixer. It is still fairly slim and does not install KDE applications. It is covered in https://community.kde.org/FreeBSD/S...Plasma_by_using_the_Binary_Package_Management
The default session is plasma Wayland which doesn't work without tweaking. You must switch to the working X11 session
Last time I tried, you gotta install x11/plasma5-plasma-desktop if you want a working Wayland session. Unfortunately, the dev who blogs at euroquis.nl says that recent versions are broken as far as Plasma Wayland is concerned.
~ $ cat /etc/rc.conf
sendmail_enable="NONE"
hostname="hpz2freebsd"
ifconfig_em0="inet 192.168.1.111 netmask 255.255.255.0"
defaultrouter="192.168.1.1"
sshd_enable="YES"
ntpd_enable="YES"
powerd_enable="YES"
# Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable
dumpdev="AUTO"
zfs_enable="YES"
# kld_list="i915kms"
#
# bluey
#
kld_list="nvidia-modeset fusefs"
dbus_enable="YES"
# gdm_enable="YES"
# gnome_enable="YES"
sddm_enable="YES"
# slim_enable="YES"
# NOTE the HAL daemon hald is no longer part of the FreeBSD desktop setup
# hald_enable="YES"
# mDNSResponder
# mdnsresponderposix_enable="YES"
# mdnsresponderposix_flags="-f /etc/mdnsresponder.conf"
netatalk_enable="YES"
# avahi-daemon[68352]: *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
# mdnsresponderposix_enable="YES"
# mdnsresponderposix_flags="-n $hostname"
avahi_daemon_enable="YES"
ubuntu_enable="YES"
cupsd_enable="YES"
~ $ ReuseSession=true~ $ cat .xinitrc
# all these are functional - kde plasma5 works best
# exec ck-launch-session mate-session
# exec /usr/local/bin/cinnamon
# exec /usr/local/bin/gnome-session
# exec /usr/local/bin/startxfce4 --with-ck-launch
exec /usr/local/bin/ck-launch-session /usr/local/bin/startplasma-x11
~ $Multiple desktop environments require that, so that was done once at the beginning.
/etc/rc.conf and .xinitrc I have been playing with for 1.5 weeks.Well, Handbook is the official one. If you follow the Handbook, and get stuck, it's easier to ask for help on the Forums. I'd suggest doing a clean reinstall of the entire FreeBSD setup and setting up KDE from scratch, following the Handbook
Hate reinstalling OS's. Prefer to debug and understand. Don't think I have had to reinstall an OS from blank forever starting with Apple II.
github.com
github.com
github.com
service sddm restart, but I don't like pulling the rug so abruptly.Sometimes, reinstalling the OS is a quick-and-dirty way to get something working properly. I tried to go the 'Debug and understand' road. I ended up wasting a LOT of my time trying awkward fixes in the middle steps, and ended up learning that those awkward fixes can be avoided if I follow the manual. The Handbook is there for a reason.
Except that it works much better if there is one - user switching is functional except for reuse.
exec /usr/local/bin/ck-launch-session /usr/local/bin/startplasma-x11 exec ck-launch-session startplasma-x11
Handbook is good. But Handbook is not the single source best reference - which is the man pages.
Have read it. But finding a place for a leftover screw requires only backtracking to figure where it is missing from. Not total engine disassembly and reassembly from scratch.
sddm user exists.
# cat/etc/passwd
[...]
sddm:*:219:219:SDDM Display Manager user:/var/lib/sddm:/usr/sbin/nologin
[...]# ps -auxw -U sddm
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
#Too much associated breakage for my liking. Spun off to a separate topic:
ConsoleKit, SDDM, switch user
Abbreviated: … ReuseSession=true … I added the line to /usr/local/etc/sddm.conf.d/kde_settings.conf (you might find the file already present), however it's not effective. We're probably bitten by something like the bugs below (ignoring the systemd aspect)...forums.freebsd.org