FreeBSD 15 probably will include KDE as DE installtion option

I wish FreeBSD moved to COSMIC as it does support non systemd installations. It looks like both Gnome and KDE are now out of scope.
 
Isn't "simply don't use login manager and use legacy CUI login, then, startx" sufficient?
Or use other login manager that support starting up KDE, if any?
 
SDDM supports KDE just fine, see the my comment (#725) in Thread trying-to-run-kde-6-plasma-with-wayland.93951, towards the end.
I myself don't use login managers as already described, but I have impression that sddm seems to be fragile at least for Wayland.

As discussions looks mangled here between each speakers (maybe the person already updated to fixed version or not?), I'm confused with the situation.

But if it is continuously maintained independent from KDE project, it may be fine.

I hope Mate DE does NOT go through such a way.
 
I've always hated KDE. I've always seen it as a big, clunky thing.

That said, we have the choices; nothing is forced.

We install FreeBSD, with whatever third-party components we want.
As I said earlier, my choice is and will remain Openbox for a long time, with my personal menu, and Plank or Tint2.

A terminal emulator.
Why such a behemoth?...
To each their own tastes
 
Now this is rather unfortunate, esp. given that FreeBSD cooperated with KDE for nearly 25 years... Looks like I may need to explore alternatives, I like KDE.
This is only the login manager, which itself is a fork of SDDM. KDE helped with OpenBSD support:

> Improved and fixed support for OpenBSD in multiple places.

 
I like KDE for a desktop environment. I’m running KDE Plasma Desktop + Wayland here.

I think 8GB of the 13GB+ in my main boot environment at /home/rc are disk images for Parrot OS. I’m setting up Parrot OS in a virtual machine environment

This is FreeBSD 15.0-RELEASE-p1
Screenshot_20260103_221528.jpeg
 
Is this still likely to happen given KDE seems to be dropping FreeBSD support?

This is a misunderstanding, it just means you won't be able to use the Plasma login manager on FreeBSD. https://floss.social/@kde/115933236466022060

But now that KDE Plasma will be implemented in FreeBSD 15.1 they will surely use Wayland instead of X11 because KDE Plasma 6.8 will drop X11 support.

Yes, the target is 15.1 now.

The installer improved in ways that matter to laptop users, too. In FreeBSD 15.0, the installer now supports downloading and installing firmware packages after the base system installation is complete. In 15.1, users can also install the KDE graphical desktop environment during installation.

Well folks, it’s the beginning of a new era: after nearly three decades of KDE desktop environments running on X11, the future KDE Plasma 6.8 release will be Wayland-exclusive! Support for X11 applications will be fully entrusted to Xwayland, and the Plasma X11 session will no longer be included.

Description of the Program Manager Alice Sowerby:

She is known for her collaborative approach and commitment to impactful, community-driven initiatives.

She surely didn't ask this community if we want KDE Plasma and Wayland. :-/
 
I believe that FreeBSD should not actively support projects that do not support FreeBSD by requiring stuff like systemd or Wayland. FreeBSD is about choice. There are enough desktop environments that are less "prejudiced". I believe MATE is one of them. Very well supported on FreeBSD and no "my way or the highway" attitude.
 
I personally like this choice because we are not all freebsd users technical, some use it just because they like it for everyday tasks so having KDE as a choice is preety nice as long as its optional. It would also be cool if that same option also configured packagekit for kde discover because for now, I werent able to install view or remove packages with discover and until then its preety limited to just updates.
So i think we can basically all benefit from this as long as its not forced automatically.
 
Does KDE at install-time mean out-the-box hookups for stuff like Partition Manager, plugging in exfat/NTFS/FAT32 drives and Dolphin viewing, tray wifi icon, and Android/mobile MTP in Dolphin?
 
Does KDE at install-time mean out-the-box hookups for stuff like Partition Manager, plugging in exfat/NTFS/FAT32 drives and Dolphin viewing, tray wifi icon, and Android/mobile MTP in Dolphin?
That's a good question. I use the automount and networkmgr for the network tray icon. Last I tried dolphin wasn't working and filesystem specific guis are not ported to work with native filesystems.
 
Does KDE at install-time mean out-the-box hookups for stuff like Partition Manager, plugging in exfat/NTFS/FAT32 drives and Dolphin viewing
Yes but only in a parallel universe.
Well, in this very universe I was able to mount a:
  • EXT4 partition
  • FAT32 partition
  • NTFS partition (fusefs.ko and filesystems/ntfs needed)
  • FreeBSD UFS partition
without any problems from Dolphin ;); didn't check for exfat. My user didn't need to be in the operator group, and with vfs.usermount set to 0. :)

KDE Partition Manager instead has not been ported yet.

tray wifi icon, and Android/mobile MTP in Dolphin?
As said by LibreQuest, the better option to have a netowrk manager GUI is indeed net-mgmt/networkmgr. It is not integrated as well as NetworkManager, but I hope this will be worked on.
MTP could work with FUSE, but cannot confirm it.
 
Offcourse, But did you have a partition manager
Actually not, but at least is in the TODO list: https://wiki.freebsd.org/KDE/TODO :)
or where able to mount btrfs.
Nope: the only way to mount a btrfs filesystem on FreeBSD actually is through filesystems/fusefs-lkl, but sysutils/bsdisks doesn't seem to use it.
Exfat works also think it needs "user space".
Yes there is filesystems/exfat, but I don't know if bsdisks actualy uses it.

You have a valid point, however this is not KDE fault, since it relies on bsdisks (just as it relies on Udisks2 on Linux) and if the latter doesn't support a filesystem KDE tools can't either.
 
Back
Top