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

Maxnix said:
Nope, if I don't explicitly start it as konqueror file:/// it segfaults. :(
Code: 
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
Click to expand...
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.
 
astyle said:
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.
Click to expand...
Got it working making it using the NVIDIA GPU with __NV_PRIME_RENDER_OFFLOAD=1 konqueror:
Schermata_20260922_234732.png

It still complains about GBM not being supported and that it needs Vulkan however. Maybe forcing konqueror using OpenGL instead of Vulkan could work? :-/
 
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
Click to expand...
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.
 
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 said:
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.
Click to expand...
Putting pass-throughs 100% aside, I myself never tried using it (as I don't have VMware environment to try), but x11-drivers/xf86-video-vmware contains manual page in its pkg (you can see share/man/man4/vmware.4x.gz in its pkg-plist.

Not 100% exact example for VMware exists, but driver name to use on X11 configuration file(s) for VMware and examples for ACTUAL GPUs like NVIDIA, Intel and AMD can be found in Chapter 5 of the Handbook.
Reading the Handbook from the beginning through its very end at least once, and coming back whenever needed is strongly recommended.

And not sure (I'm not using KDE for casual tests for years) but possibly KDE has any kind of frontends to setup screen related configurations include resolutions. Actual KDE users that run it as their daily driver is wanted for this. NOT ME, that using Mate DE on X11 as daily driver, using some KDE apps but NOT the whole KDE.

And this should be 100% specific for X11 (Xorg and/or Xlibre).
As (as far as I know) Wayland mandates DRM/KMS interface, so unless VMware emulates and exposes DRM/KDE interface WITH 100% CONFORMING WITH THE FORM WAYLAND REALLY WANTS, Wayland shouldn't run sanely (at worst, cannot detect any framebuffer devices, thus, not at all work or even NOT starts).
 
KDE under X11 runs fine (and even adjusts its screen resolution to the VMware window size). It means that the graphics driver is installed correctly, right?
Wayland-only Linux distros (KDE Linux, Fedora KDE, Ubuntu with the latest GNOME) run fine on VMware as well. Does it mean that VMware provides the required interface?
 
siealex said:
KDE under X11 runs fine (and even adjusts its screen resolution to the VMware window size). It means that the graphics driver is installed correctly, right?
Wayland-only Linux distros (KDE Linux, Fedora KDE, Ubuntu with the latest GNOME) run fine on VMware as well. Does it mean that VMware provides the required interface?
Click to expand...
For linux most distros are running a framebuffer based drm implementation (simpledrm) that gets swapped by an actual hardware accelerated implementation if there's a corresponding driver for the hardware (i.e. i915, amdgpu, radeon, nvidia, etc). That's why that while you have wayland on vmware (or vbox, or wtv) in fact you don't have an accelerated desktop. On FreeBSD there is no such framebuffer backed drm implementation (though there are requests for it, sadly the author of simpledrm does not allow the licence to be changed from GPL or dual licensed).

As for X11, like T-Aoki mentioned, there's a X11 driver that allows for basic desktop acceleration (including mode changing).

You can try a stab at porting vmware's vmwgfx drm driver that would solve both the X11 and Wayland accelerated desktop issues.
 
Big thanks for all the efforts!

I made the switch to wayland + plasma 6.7.5 in scare of 6.8 and am crazy pleasantly surprised. Even freaking HDR works in Firefox and Youtube. Ok... not in fullscreen, but it works. Steam, wine, dosbox, amiberry, just working. In Steam i had to to switch from DXVK to WINE3D but thats older titles. D2 Ressurected, Path of Exile, Viber on Linuxulator just worked. Why did i wait for the switch so long?

Desktop: AMD Ryzen 7 7700X / Radeon RX 6800 XT – FreeBSD 15.1-RELEASE, KDE Plasma 6.7.5 on Wayland

Code: 
OS:          FreeBSD 15.1-RELEASE-p5 (kernel) / -p6 (userland), amd64
Mainboard:   ASRock B650M-HDV/M.2 (BIOS 3.20, 2025-02-21), AM5
CPU:         AMD Ryzen 7 7700X, 8C/16T (amdtemp)
RAM:         32 GB DDR5-4800 (2x 16 GB Kingston Fury KF552C40-16)
GPU:         AMD Radeon RX 6800 XT (Navi 21) – both monitors attached here
iGPU:        AMD Raphael (Radeon 610M) – enabled, unused for display
Driver:      drm-612-kmod 6.12.110 (amdgpu), Mesa 26.2.2, only the needed
             gpu-firmware-amd-kmod-* packages installed
Monitors:    2x AOC CU34G2 (34", 3440x1440 @ 144 Hz, DisplayPort)
Network:     Intel I226-V 2.5 GbE (igc) – EEE off, offloads off
Storage:     NVMe Crucial P3 Plus 1 TB (FreeBSD, ZFS)
             NVMe Kingston NV2 2 TB (Linux disk)
             SATA WD Blue 2 TB WD20EZRZ (ZFS)
Audio:       Realtek ALC897 (snd_hda, front/rear analog)
             JBL Quantum 910 Wireless (USB audio)
             HDMI/DP audio (Navi 21)
Input:       Cherry USB keyboard, Logitech USB optical mouse,
             Thrustmaster USB joystick

Desktop / software
  • KDE Plasma 6.7.5 on Wayland, SDDM login, session via ConsoleKit2 (ck-launch-session); seatd is not needed for KWin
  • Xwayland 24.1 for X11 apps (Steam, Wine, dosbox-staging)
  • PipeWire 1.6 + WirePlumber only for screen sharing/recording (screencast via xdg-desktop-portal-kde works), audio stays on OSS
  • Linuxulator: Rocky Linux 9 base (linux_base-rl9) + a Debian 12 chroot; Steam via linux-steam-utils, Viber (Qt 6) runs natively on Wayland
  • Wine 11.0 / wine-proton 11.0.2
 
If you're using NVIDIA RTX 5xxx (Blackwell generation of architectures), you should need builds at commit ports 978aa957b97b or later (as Blackwell unconditionally needs GSP firmware loaded). If you want official pkg builds, you'll need to wait until official pkg repo build cluster finishes builds for them.

And if you're on quarterly (2026Q4), merge into quarterly may need much longer. Meanwhile, you can build via ports with the patch at PR 300575.
 
astyle said:
Any error messages that you were able to capture? Sometimes, it helps to SSH into the same machine from the side, and they get dumped to stderr, which becomes visible from the SSH session.
Click to expand...
I tried starting Plasma from CLI, and the problem was related to a wayland plugin that was found but could not be loaded (pretty similar to something already happened, maybe when upgrading fro 6.6 to 6.7).
stefs1 said:
I had the same problem. The initial push of packages was just incomplete. Just pkg upgrade again, worked for me.
Click to expand...
Indeed, but I took a more radical approach: I used pkg upgrade -f instead (it's interesting to know that another round of upgrade suffices)! 😆

As a note, I want to report however that some widgets (like Lock key status, Weather Report, Media frames) stopped working, since they look for a missing /usr/local/lib/libPlasma.so.7; fortunately the old (dirty) ln(1) trick ( ln -s /usr/local/lib/libPlasma.so.6.8.2 /usr/local/lib/libPlasma.so.7) makes them functional again*. :)

T-Aoki said:
If you're using NVIDIA RTX 5xxx (Blackwell generation of architectures), you should need builds at commit ports 978aa957b97b or later (as Blackwell unconditionally needs GSP firmware loaded). If you want official pkg builds, you'll need to wait until official pkg repo build cluster finishes builds for them.

And if you're on quarterly (2026Q4), merge into quarterly may need much longer. Meanwhile, you can build via ports with the patch at PR 300575.
Click to expand...
I use hybrid graphics, the discrete GPU is only (rarely) used when launching a program with GPU offload; it's a NVIDIA Quadro T1000 and I'm on latest (got version 620.70.06 today).

EDIT. * Mistery solved, x11-toolkits/plasma6-kdeplasma-addons is lacking from the repositories; it's just a matter of having it rebuilt.
 
stefs1 said:
I had the same problem. The initial push of packages was just incomplete. Just pkg upgrade again, worked for me.
Click to expand...
I'm having a similar issue with version 15.1. Repeating the "pkg upgrade" allowed me to run Plasma under x11 in a stripped-down version. The keyboard ignores previous settings, decorations and styles don't work. Wayland doesn't work at all. Same story with versions 15.2 PRERELEASE and 16 CURRENT.
 
nb said:
I'm having a similar issue with version 15.1. Repeating the "pkg upgrade" allowed me to run Plasma under x11 in a stripped-down version. The keyboard ignores previous settings, decorations and styles don't work. Wayland doesn't work at all. Same story with versions 15.2 PRERELEASE and 16 CURRENT.
Click to expand...
From within the X11 session, can you launch Konsole and use that to try and launch a Wayland session (it should appear in its own, separate X11 window)? In this scenario, Konsole should also show some of the errors in your setup.
 
astyle said:
From within the X11 session, can you launch Konsole and use that to try and launch a Wayland session (it should appear in its own, separate X11 window)? In this scenario, Konsole should also show some of the errors in your setup.
Click to expand...
I'm just starting Wayland from the terminal. I'm not using sddm.
 
Code: 
~ pkg upgrade

Checking for upgrades (13 candidates):

gdisk-1.0.10_1 is locked and may not be modified
Checking for upgrades (13 candidates)............ done
Processing candidates (13 candidates): ........ done
Checking integrity... done (2 conflicting)
- plasma6lts-libplasma-6.6.6 [FreeBSD-ports] conflicts with plasma6-libplasma-6.7.5 [installed] on /usr/local/include/Plasma/Plasma/Applet
- plasma6lts-libplasma-6.6.6 [FreeBSD-ports] conflicts with plasma6-libplasma-6.8.2 [FreeBSD-ports] on /usr/local/include/Plasma/Plasma/Applet
plasma6-kscreen-6.8.2 is held back to solve the problem
plasma6-kscreenlocker-6.8.2 is held back to solve the problem
plasma6-libplasma-6.8.2 is held back to solve the problem
plasma6-milou-6.8.2 is held back to solve the problem
plasma6-plasma-desktop-6.8.2 is held back to solve the problem
plasma6-plasma-pa-6.8.2 is held back to solve the problem
plasma6-plasma-sdk-6.8.2 is held back to solve the problem
plasma6-plasma-workspace-6.8.2 is held back to solve the problem
plasma6-powerdevil-6.8.2 is held back to solve the problem
plasma6-print-manager-6.8.2 is held back to solve the problem
Checking integrity... done (0 conflicting)
Your packages are up to date.
 
nb said:
Code: 
~ pkg upgrade

Checking for upgrades (13 candidates):

gdisk-1.0.10_1 is locked and may not be modified
Checking for upgrades (13 candidates)............ done
Processing candidates (13 candidates): ........ done
Checking integrity... done (2 conflicting)
- plasma6lts-libplasma-6.6.6 [FreeBSD-ports] conflicts with plasma6-libplasma-6.7.5 [installed] on /usr/local/include/Plasma/Plasma/Applet
- plasma6lts-libplasma-6.6.6 [FreeBSD-ports] conflicts with plasma6-libplasma-6.8.2 [FreeBSD-ports] on /usr/local/include/Plasma/Plasma/Applet
plasma6-kscreen-6.8.2 is held back to solve the problem
plasma6-kscreenlocker-6.8.2 is held back to solve the problem
plasma6-libplasma-6.8.2 is held back to solve the problem
plasma6-milou-6.8.2 is held back to solve the problem
plasma6-plasma-desktop-6.8.2 is held back to solve the problem
plasma6-plasma-pa-6.8.2 is held back to solve the problem
plasma6-plasma-sdk-6.8.2 is held back to solve the problem
plasma6-plasma-workspace-6.8.2 is held back to solve the problem
plasma6-powerdevil-6.8.2 is held back to solve the problem
plasma6-print-manager-6.8.2 is held back to solve the problem
Checking integrity... done (0 conflicting)
Your packages are up to date.
Click to expand...
Well, there you go. Resolve that conflict, and I think you'll be good to go.

I personally compile my stuff from scratch, but reading the error messages completely is usually quite beneficial - sometimes a stupid simple, easily correctable detail at the beginning is the stumbling block that breaks everything if you don't take care of it correctly early on.
 
nb said:
Code: 
~ pkg upgrade

Checking for upgrades (13 candidates):

gdisk-1.0.10_1 is locked and may not be modified
Checking for upgrades (13 candidates)............ done
Processing candidates (13 candidates): ........ done
Checking integrity... done (2 conflicting)
- plasma6lts-libplasma-6.6.6 [FreeBSD-ports] conflicts with plasma6-libplasma-6.7.5 [installed] on /usr/local/include/Plasma/Plasma/Applet
- plasma6lts-libplasma-6.6.6 [FreeBSD-ports] conflicts with plasma6-libplasma-6.8.2 [FreeBSD-ports] on /usr/local/include/Plasma/Plasma/Applet
plasma6-kscreen-6.8.2 is held back to solve the problem
plasma6-kscreenlocker-6.8.2 is held back to solve the problem
plasma6-libplasma-6.8.2 is held back to solve the problem
plasma6-milou-6.8.2 is held back to solve the problem
plasma6-plasma-desktop-6.8.2 is held back to solve the problem
plasma6-plasma-pa-6.8.2 is held back to solve the problem
plasma6-plasma-sdk-6.8.2 is held back to solve the problem
plasma6-plasma-workspace-6.8.2 is held back to solve the problem
plasma6-powerdevil-6.8.2 is held back to solve the problem
plasma6-print-manager-6.8.2 is held back to solve the problem
Checking integrity... done (0 conflicting)
Your packages are up to date.
Click to expand...
Why do you have the libraries for the LTS branch (x11/plasma6lts-libplasma)? If you want the latest version you must remove everything related to Plasma 6.6.X.
 
  • Thanks
Reactions: nb
You must log in or register to reply here.
Back
Top