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

[astyle]

Nope, if I don't explicitly start it as konqueror file:/// it segfaults.

kf.windowsystem: virtual void KX11Extras::connectNotify(const QMetaMethod &) may only be used on X11
kf.parts: KPluginMetaData(name:"Okular", plugin-id:"okularpart") still defined ServiceTypes - this is deprecated in favor of providing a  "Capabilities" list in the "KParts" object in the root of the metadata
kf.parts: KPluginMetaData(name:"Utilità di archiviazione", plugin-id:"arkpart") still defined ServiceTypes - this is deprecated in favor of providing a  "Capabilities" list in the "KParts" object in the root of the metadata
kf.parts: KPluginMetaData(name:"Visore di immagini Gwenview", plugin-id:"gvpart") still defined ServiceTypes - this is deprecated in favor of providing a  "Capabilities" list in the "KParts" object in the root of the metadata
kf.parts: KPluginMetaData(name:"Emulatore di terminale", plugin-id:"konsolepart") still defined ServiceTypes - this is deprecated in favor of providing a  "Capabilities" list in the "KParts" object in the root of the metadata
kf.parts: ServiceType "inode/directory" from KPluginMetaData(name:"Emulatore di terminale", plugin-id:"konsolepart") is not a known value that can be mapped to new Capability enum values
kf.parts: ServiceType "TerminalEmulator" from KPluginMetaData(name:"Emulatore di terminale", plugin-id:"konsolepart") is not a known value that can be mapped to new Capability enum values
kf.parts: KPluginMetaData(name:"Editor di testo avanzato incorporato", plugin-id:"katepart") still defined ServiceTypes - this is deprecated in favor of providing a  "Capabilities" list in the "KParts" object in the root of the metadata
GBM is not supported with the current configuration. Fallback to Vulkan rendering in Chromium.
zsh: segmentation fault  konqueror

I have mine compiled, and can start it as a regular browser... but when it crashes on my end of things, I get these exact error messages.

TBF, KDE does have a lot of apps that are still not ported to QT6 / Wayland. With that in mind, I see "6.8 going wayland-only" as a nudge / wake-up call for those projects to get moving on porting the code.

 

[Maxnix]

I have mine compiled, and can start it as a regular browser... but when it crashes on my end of things, I get these exact error messages.

TBF, KDE does have a lot of apps that are still not ported to QT6 / Wayland. With that in mind, I see "6.8 going wayland-only" as a nudge / wake-up call for those projects to get moving on porting the code.

Got it working making it using the NVIDIA GPU with __NV_PRIME_RENDER_OFFLOAD=1 konqueror:

It still complains about GBM not being supported and that it needs Vulkan however. Maybe forcing konqueror using OpenGL instead of Vulkan could work?

 

[T-Aoki]

Note that there's a fork of KDE that stick with X11 instead of Wayland, SonicDE.

But unfortunately, as far as I know, it's not ported to FreeBSD (yet).
Anyway, porting efforts seem to be in underway.

 

[siealex]

Is it possible to run KDE Plasma Wayland on a VMware virtual machine (if yes, how to configure it)?
My system: FreeBSD 15.1 with KDE Plasma 6.7.5 running fine on X11, VMware 26H1 on a Windows 11 machine.
Trying to run exec dbus-launch ck-launch-session startplasma-wayland or other similar commands from this thread displays a lot of messages, among them several times in a row

kwin_wayland_drm: Failed to open drm device dev/dri/card0
kwin_wayland_drm: No suitable drm devices have been found

Does it mean that the VMware virtual graphics card is not supported? Or is something wrong with my configuration?

PS, running the same command from WITHIN the X11 KDE session successfully opens a Wayland session in a window (!) without any error messages, however, mouse control is screwed up inside that window.

 

[siealex]

exec dbus-launch ck-launch-session startplasma-wayland

Putting this into ~/.xinitrc and running startx also starts Plasma, but in a fixed 1024*768 resolution. Is it possible to fix at least this?

 

[T-Aoki]

I'm NOT using VMware, but unless you somehow explicitly pass any of your GPU through to VMware, your configuration is clearly wrong. DRM/KMS drivers shouldn't work at all on VMware guests unless any GPU is passed through and 100% dedicated to the specific SINGLE guest at the same time, keeping FreeBSD host side untouching it.

And if no GPU is passed through, you may need x11-drivers/xf86-video-vmware installed and configured on guest to use it.

Anyway, I cannot test it at all to determine whether it really works or not, as I don't have VMware license and environment to run it at all.

 

[siealex]

And if no GPU is passed through, you may need x11-drivers/xf86-video-vmware installed and configured on guest to use it.

Any manuals on this package? It is installed and included in kldlist, but what to do next?
Is this specific to Wayland? KDE runs fine in X11 on this setup.