Trying to run KDE 6 Plasma with Wayland....

NapoleonWils0n said:
i think its possible to install KDE 6 on Freebsd 14.1 on bare metal

but its probably not worth it at the moment
due to the bugs i mentioned

if shutdown and the file manager dont work
then i would think other things like desktop widgets would probably have issues as well
Click to expand...
KDE6 on FreeBSD 14.1 works fine on bare metal if you use Xorg. In fact, usable as a daily driver, if not for the clock widget missing.

Dolphin doesn't work either way, but it's not a showstopper on my metal. I only get dolphin.core in my /home/astyle directory, and the rest is fine, no crashes.

Shutdown works fine on my metal, so I'd leave that weird string alone, it's not a showstopper for me.
 
whats interesting is that you can run an entire wayland desktop in a jail
and have it displayed on the host as a native wayland window

the only drawback is you are limited to one window
 
i changed the audio backend in Firefox to oss in the jail which works
and the audio from youtube plays on the host without using pulseaudio

however for the audio devices to show up in KDE you have to start pulseaudio on the host

Code: 
pulseaudio --start --daemonize 2>/dev/null

and start kde with pipewire

Code: 
#!/bin/sh

pipewire -v &
exec dbus-launch --exit-with-session ck-launch-session startplasma-wayland

otherwise the audio devices arent listed in system settings
or in the sound applet in the panel

so it looks like KDE uses pipewire and pulseaudio for system audio
 
NapoleonWils0n said:
sound applet in the panel
Click to expand...

Bug 258579 (closed).

NapoleonWils0n said:
sysrc sysrc seatd_enable=YES
Click to expand...

Typo (nit).

NapoleonWils0n said:
sysrc kld_list+="i915kms nvidia-modeset nvidia-drm linux linux64"
Click to expand...

If you load nvidia-drm manually, then does nvidia-modeset load automatically?

chrislongros said:
Dolphin crashes at start on KDE Plasma 6.1.2 X11
Click to expand...

Mentioned in IRC long ago, not acknowledged, I'm not aware of a report, I assume that devs are aware.
 
Sound works fine on my metal, I can record it, and I checked my hardware for the first time, looks fine on my end.
(For recording, it did take a hack that was described in this another thread a couple years ago: Thread complex-internal-microphone-on-freebsd-13r.86181/). KDE Wayland was able to see my audio hardware fine, and test it, too. I get same results in both the Wayfire on-metal (when I just call up KDE's systemsettings) and in the compositor window.
 

Attachments

  • sound.png
    sound.png
    174.1 KB · Views: 74
KDE requires lots of different packages which all have to work together
and if one package doesnt work then neither does the desktop

because there are so many packages and libraries needed for KDE
it must be a thankless task getting all them all ported to Freebsd and working together

so its a bit of an arms race having to keep so many packages working
and then if there is an update and you have to start all over again

KDE creates so many different config files in ~/.config
the os should be fined for littering

another thing that bugs me is when you set up KDE you get a donate prompt
before you have even used the os

also KDE doesnt have independent workspaces per monitor
so its awful with a multi monitor set up
 
meaw229a said:
I have never seen the donate button ever and I'm using KDE for many years.
Is this donate thing is new with KDE6 ??
Click to expand...
IIRC, it was mentioned in Nate Graham's pointiestick.com blog as something new for KDE 6... This is off the top of my head, hunting down the links to verify that is left as an exercise for the reader of this comment.
 
Compiled as per instructions from ADG's blog (even though ADG uses pkg, while I compile same stuff from scratch)... and it's even a stable, snappy experience! Given all that, it's pretty frustrating that the "Plasma Wayland on metal" part is still unresolved!

Still gotta figure out the ENV stuff! ? ?

1729812213504.png


The reason I went with 13.3-RELEASE is because 14.1-RELEASE crashes inside my VM whenever I use /usr/ports ... and 13.3 doesn't. Would patching the 14.1-RELEASE to latest patches make it stable or not?

Edit: I ended up answering my own question, and the answer is NO YES. I tried to get started with a downloaded ISO of 14.1-RELEASE, patched it to p5, but that did nothing for 14.1-RELEASE's stability inside a VBox VM, still crashes, while a p0 13.3-RELEASE is rock-solid in a VBox VM... go figga. ?

Edit 2: The 14.1-RELEASE p5 VM only crashed when I tried to transfer 10 GB' worth of distfiles in from the 13.3-RELEASE p0 VM. Compilation actually went fine in the 14.1-RELEASE p5 (As opposed to 14.1-RELEASE p0). Well, 13.3-RELEASE p0 VM did crash a couple times during the aforementioned transfer. Conclusion: Yeah, patching 14.1-RELEASE did make a difference for compilation, but not for data transfer.
 
Last edited:
Managed to reproduce results from post #443 on a 14.1-RELEASE p5 VM... Well, even ADG reported difficulties with /dev/dri/card0, so ENV variables it is. Somebody needs to have the discipline to tease out the correct combination... ?
 
Wow!!!! What?!!! To my surprise, I could simply type
ck-launch-session /usr/local/lib/libexec/plasma-dbus-run-session-if-needed startplasma-wayland and the plasma desktop loaded! There was no need for defining variables such as KWIN_COMPOSE=Q! Right clicking on the panel or the desktop crashes plasmashell though.
 
Oleg_NYC said:
Wow!!!! What?!!! To my surprise, I could simply type
ck-launch-session /usr/local/lib/libexec/plasma-dbus-run-session-if-needed startplasma-wayland and the plasma desktop loaded! There was no need for defining variables such as KWIN_COMPOSE=Q! Right clicking on the panel or the desktop crashes plasmashell though.
Click to expand...
Seriously??? I tried that, and got all kinds of errors on the TTY! or did you start that from within a DE like TWM (base Xorg) or Wayfire?

Can you please post output of printenv from before and after running ck-launch-session /usr/local/lib/libexec/plasma-dbus-run-session-if-needed startplasma-wayland, please?

Can you also post a full-screen screenshot with info of what your versions of Plasma/Frameworks/QT is???

Are you doing that on metal or a VM???

?
 
I launched it on metal from the TTY. Before I launched it, I saw this,
Code: 
LOGNAME=Oleg
PAGER=less
SAL_USE_VCLPLUGIN=qt6
LANG=C.UTF-8
MAIL=/var/mail/Oleg
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/home/Oleg/bin
EDITOR=vim
XDG_RUNTIME_DIR=/tmp/sway
ENV=/home/Oleg/.shrc
PWD=/home/Oleg
TERM=xterm
HOME=/home/Oleg
USER=Oleg
SHELL=/bin/sh
MM_CHARSET=UTF-8
BLOCKSIZE=K
and after I launched it, I saw
Code: 
XCURSOR_PATH=/usr/local/share/icons::~/.icons:/usr/share/icons:/usr/share/pixmaps:/usr/X11R6/lib/X11/icons
KDE_SESSION_VERSION=6
LOGNAME=Oleg
SAL_USE_VCLPLUGIN=qt6
PAGER=less
LANG=C.UTF-8
KDE_APPLICATIONS_AS_SCOPE=1
COLORFGBG=15;0
XDG_MENU_PREFIX=plasma-
QT_WAYLAND_RECONNECT=1
XAUTHORITY=/var/run/user/1001/xauth_YrcQeW
KONSOLE_DBUS_WINDOW=/Windows/1
MAIL=/var/mail/Oleg
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/home/Oleg/bin
XDG_SESSION_TYPE=wayland
XDG_RUNTIME_DIR=/var/run/user/1001
EDITOR=vim
ENV=/home/Oleg/.shrc
GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/Oleg/.gtkrc-2.0:/home/Oleg/.config/gtkrc-2.0
SESSION_MANAGER=local/desktop.computer.com:/tmp/.ICE-unix/2373
KDE_SESSION_UID=1001
ICEAUTHORITY=/var/run/user/1001/iceauth_hfDLOq
GTK_RC_FILES=/etc/gtk/gtkrc:/home/Oleg/.gtkrc:/home/Oleg/.config/gtkrc
DISPLAY=:0
PROFILEHOME=
PWD=/home/Oleg
XDG_CURRENT_DESKTOP=KDE
TERM=xterm-256color
DBUS_SESSION_BUS_ADDRESS=unix:path=/tmp/dbus-V9oeLL5zmG,guid=8ead4cb26b884799e36963bf671f6a22
KONSOLE_DBUS_SESSION=/Sessions/1
USER=Oleg
QT_AUTO_SCREEN_SCALE_FACTOR=0
HOME=/home/Oleg
WAYLAND_DISPLAY=wayland-0
SHELL=/bin/sh
LANGUAGE=
COLORTERM=truecolor
MM_CHARSET=UTF-8
WINDOWID=3
XDG_ACTIVATION_TOKEN=kwin-1
KDE_FULL_SESSION=true
XDG_SESSION_COOKIE=desktop.computer.com-1730112034.413767-749267251
XDG_CONFIG_DIRS=/home/Oleg/.config/kdedefaults:/usr/local/etc/xdg:/etc/xdg
KONSOLE_DBUS_SERVICE=:1.25
SHELL_SESSION_ID=2c1afad20a954d188fde3bbf56179308
BLOCKSIZE=K
KONSOLE_VERSION=240190
I installed spectacle-devel, but when I typed spectacle in konsole, nothing happened, so I wasn't able to take a screenshot. Maybe you could please tell me what program I could install to take a screenshot. In system settings, I saw
Code: 
Operating System: FreeBSD 15.0
KDE Plasma Version: 6.1.2
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.3
Kernel Version: 15.0-CURRENT (64-bit)
Graphics Platform: Wayland
Memory: 127.8 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630
Manufacturer: ASUS
. But wow! Can you please explain to me why launching wayland plasma from the TTY worked?! I am astonished.
 
Oleg_NYC said:
I launched it on metal from the TTY. Before I launched it, I saw this,
Code: 
LOGNAME=Oleg
PAGER=less
SAL_USE_VCLPLUGIN=qt6
LANG=C.UTF-8
MAIL=/var/mail/Oleg
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/home/Oleg/bin
EDITOR=vim
XDG_RUNTIME_DIR=/tmp/sway
ENV=/home/Oleg/.shrc
PWD=/home/Oleg
TERM=xterm
HOME=/home/Oleg
USER=Oleg
SHELL=/bin/sh
MM_CHARSET=UTF-8
BLOCKSIZE=K
and after I launched it, I saw
Code: 
XCURSOR_PATH=/usr/local/share/icons::~/.icons:/usr/share/icons:/usr/share/pixmaps:/usr/X11R6/lib/X11/icons
KDE_SESSION_VERSION=6
LOGNAME=Oleg
SAL_USE_VCLPLUGIN=qt6
PAGER=less
LANG=C.UTF-8
KDE_APPLICATIONS_AS_SCOPE=1
COLORFGBG=15;0
XDG_MENU_PREFIX=plasma-
QT_WAYLAND_RECONNECT=1
XAUTHORITY=/var/run/user/1001/xauth_YrcQeW
KONSOLE_DBUS_WINDOW=/Windows/1
MAIL=/var/mail/Oleg
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/home/Oleg/bin
XDG_SESSION_TYPE=wayland
XDG_RUNTIME_DIR=/var/run/user/1001
EDITOR=vim
ENV=/home/Oleg/.shrc
GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/Oleg/.gtkrc-2.0:/home/Oleg/.config/gtkrc-2.0
SESSION_MANAGER=local/desktop.computer.com:/tmp/.ICE-unix/2373
KDE_SESSION_UID=1001
ICEAUTHORITY=/var/run/user/1001/iceauth_hfDLOq
GTK_RC_FILES=/etc/gtk/gtkrc:/home/Oleg/.gtkrc:/home/Oleg/.config/gtkrc
DISPLAY=:0
PROFILEHOME=
PWD=/home/Oleg
XDG_CURRENT_DESKTOP=KDE
TERM=xterm-256color
DBUS_SESSION_BUS_ADDRESS=unix:path=/tmp/dbus-V9oeLL5zmG,guid=8ead4cb26b884799e36963bf671f6a22
KONSOLE_DBUS_SESSION=/Sessions/1
USER=Oleg
QT_AUTO_SCREEN_SCALE_FACTOR=0
HOME=/home/Oleg
WAYLAND_DISPLAY=wayland-0
SHELL=/bin/sh
LANGUAGE=
COLORTERM=truecolor
MM_CHARSET=UTF-8
WINDOWID=3
XDG_ACTIVATION_TOKEN=kwin-1
KDE_FULL_SESSION=true
XDG_SESSION_COOKIE=desktop.computer.com-1730112034.413767-749267251
XDG_CONFIG_DIRS=/home/Oleg/.config/kdedefaults:/usr/local/etc/xdg:/etc/xdg
KONSOLE_DBUS_SERVICE=:1.25
SHELL_SESSION_ID=2c1afad20a954d188fde3bbf56179308
BLOCKSIZE=K
KONSOLE_VERSION=240190
I installed spectacle-devel, but when I typed spectacle in konsole, nothing happened, so I wasn't able to take a screenshot. Maybe you could please tell me what program I could install to take a screenshot. In system settings, I saw
Code: 
Operating System: FreeBSD 15.0
KDE Plasma Version: 6.1.2
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.3
Kernel Version: 15.0-CURRENT (64-bit)
Graphics Platform: Wayland
Memory: 127.8 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630
Manufacturer: ASUS
. But wow! Can you please explain to me why launching wayland plasma from the TTY worked?! I am astonished.
Click to expand...
I'm astonished myself... but thanks for providing details! That is much appreciated.

One thing that jumps out at me is that your FreeBSD is 15.0-CURRENT... and that you have Intel graphics. This is different from me, I did not have 15.0-CURRENT...

As for screenshots, try installing grim (x11/grim). I have it, it worked under Wayfire, another Wayland compositor. Typing grim in Konsole will take a screengrab of the whole desktop, and will appear in /home/user/Pictures directory.

I'd want to confirm for myself that 15.0-CURRENT is what it's taking... because some of the ENV variables clearly do change on launch. ENV variables are notoriously hard to control and to make sure they stick...
 
You must log in or register to reply here.
Back
Top