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

It looks like grim only works on wlroots-based compositors. I received the message:
Code: 
grim
compositor doesn't support wlr-screencopy-unstable-v1
 
I see this grim error as a good hint as to what ENV and sysctls to look at in FreeBSD when trying to launch from TTY on metal... I have some ideas on where to look, but they may turn out to be time-consuming rabbit holes that produce no useful result. I guess my next step is to get 15.0-CURRENT and see for myself if it makes a difference in a VM. If it does - I got hardware I can test.

In the meantime, I'd say, even a pic (that shows hardware details in systemsettings ) taken with a phone would be awesome for this thread.
 
I took this picture with my phone. It was taken on my laptop computer whose characteristics are not the same as the characteristics mentioned in the previous post: https://ibb.co/mhPCqZZ . I just spoke with someone who also successfully launched wayland plasma from the TTY. He also runs 15-CURRENT.
 
I just finished downloading 15.0-CURRENT snapshot from Oct. 24, 2024, and gonna compile my way into KDE 6 again. That usually takes about 2-3 days for me if I have all the distfiles. Will report then to see if 15-CURRENT makes a difference. With 2 reported instances of success that I know of, this is encouraging! 😁
 
  • Like
Reactions: drr
The pic referenced in post # 453 was 8.2 MB, so I took the liberty to take a screenshot and re-post in case the link goes stale:
1730223759363.png
 
I mentioned the right-clicking crash earlier. It looks like it was triggered by a LLVM/libc++ bug. This problem will be fixed in the ports tree.
 
Well, I compiled my way into KDE 6 on a 15-CURRENT VM, but the Wayland launch command is unhappy that it can't find the GPU at /dev/dri/card0. Launching KDE 6 with Xorg (as per ADG's blog) gives me a warning that 'Software Renderer is in use, so desktop experience may be slow'. This is more of a comment to update what I'm doing, rather than a request for help... 😅
 
astyle said:
Well, I compiled my way into KDE 6 on a 15-CURRENT VM, but the Wayland launch command is unhappy that it can't find the GPU at /dev/dri/card0. Launching KDE 6 with Xorg (as per ADG's blog) gives me a warning that 'Software Renderer is in use, so desktop experience may be slow'. This is more of a comment to update what I'm doing, rather than a request for help... 😅
Click to expand...
Well, in your case, it's a VM, unlike my case.
 
Oleg_NYC said:
Well, in your case, it's a VM, unlike my case.
Click to expand...
Yeah, well, this thread does mention a few ENV variables that made the complaint go away for a bit. I'm gonna go back and re-read and play for a bit. I want to get a VM going with Wayland first, because my available hardware is kinda old and slow.
 
astyle said:
could it be ADG's euroquis.nl blog?
Click to expand...
thats the one,
someones little grey cells are still working ( just watching Poirot )

Plasma6 and FreeBSD 14

I just installed a new FreeBSD desktop machine. For this one, I wanted to have KDE Plasma6, since that’s already running on my Linux laptop and gaming machine – and it’s time for me to dogfood on FreeBSD. Here’s some notes.
euroquis.nl euroquis.nl

I know that Wayland can work on FreeBSD with hardware rendering – that’s why that river section is there.
Here is a very short script that can launch KDE Plasma6 with software rendering. The resulting desktop experience is rather slow.
Click to expand...
Code: 
#! /bin/sh
export KWIN_COMPOSE=Q
exec /usr/local/bin/ck-launch-session \
    /usr/local/lib/libexec/plasma-dbus-run-session-if-needed \
    /usr/local/bin/startplasma-wayland

So the TODO part of this post is: figure out why opening dri/card0 fails when kwin_wayland is not using the software renderer.
Click to expand...
 
Oleg_NYC said:
ADG's blog contains outdated info because card0 no longer fails when using the hardware renderer (specifically, Intel graphics).
Click to expand...
gotcha

outdated info
reminds me that youtube is looking at dropping the date and view count on videos

which is going to make it really difficult to find any fixes on youtube
 
Damn.... I guess I'm looking at a pretty long and onerous task of trying 15-CURRENT on an old laptop. 😩

On that laptop, /dev/dri/card0 (that kwin_wayland is looking for) is just a symlink to /dev/drm/0, but apparently even root account can't do much manipulation with that to get the whole KDE 6 / Wayland enchilada to start in the 15-CURRENT VM... it takes properly installing a GPU driver.

In other news, the 15-CURRENT VM can launch Xorg from base TTY, and only after that, the KDE 6 Wayland session can be started from XTerm. But even then, just like ADG, I get a warning about 'Software Renderer' and the performance is slow, with many papercuts like some icons rendered out of place.
 
Unbelievable... 😩

Took me 5 days to compile. BUT, Wayland still would not start. Got these errors from typing the same command as on euroquis.nl:
Code: 
% cat wayland_errors.txt 
org.kde.startup: not a reply org.freedesktop.locale1 QDBusMessage(type=Error, service="",
error name="org.freedesktop.DBus.Error.ServiceUnknown", error message="The name org.freede
sktop.locale1 was not provided by any .service files", signature="s", contents=("The name
org.freedesktop.locale1 was not provided by any .service files") )
dbus-daemon[2036]: [session uid=1001 pid=2036] Activating service name='org.kde.KSplash' r
equested by ':1.0' (uid=1001 pid=2037 comm="")
No backend specified, automatically choosing drm
MESA-LOADER: failed to open crocus: /usr/local/lib/dri/crocus_dri.so: Unsupported relocati
on type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
MESA-LOADER: failed to open kms_swrast: /usr/local/lib/dri/kms_swrast_dri.so: Unsupported
relocation type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
MESA-LOADER: failed to open swrast: /usr/local/lib/dri/swrast_dri.so: Unsupported relocati
on type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
kwin_core: Failed to create gbm device for "/dev/dri/card0"
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
MESA-LOADER: failed to open crocus: /usr/local/lib/dri/crocus_dri.so: Unsupported relocati
on type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
MESA-LOADER: failed to open kms_swrast: /usr/local/lib/dri/kms_swrast_dri.so: Unsupported
relocation type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
MESA-LOADER: failed to open swrast: /usr/local/lib/dri/swrast_dri.so: Unsupported relocati
on type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
kwin_core: Failed to create gbm device for "/dev/dri/card0"
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
MESA-LOADER: failed to open crocus: /usr/local/lib/dri/crocus_dri.so: Unsupported relocati
on type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
MESA-LOADER: failed to open kms_swrast: /usr/local/lib/dri/kms_swrast_dri.so: Unsupported
relocation type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
MESA-LOADER: failed to open swrast: /usr/local/lib/dri/swrast_dri.so: Unsupported relocati
on type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
kwin_core: Failed to create gbm device for "/dev/dri/card0"
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
MESA-LOADER: failed to open crocus: /usr/local/lib/dri/crocus_dri.so: Unsupported relocati
on type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
MESA-LOADER: failed to open kms_swrast: /usr/local/lib/dri/kms_swrast_dri.so: Unsupported
relocation type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
MESA-LOADER: failed to open swrast: /usr/local/lib/dri/swrast_dri.so: Unsupported relocati
on type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
kwin_core: Failed to create gbm device for "/dev/dri/card0"
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
MESA-LOADER: failed to open crocus: /usr/local/lib/dri/crocus_dri.so: Unsupported relocati
on type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
MESA-LOADER: failed to open kms_swrast: /usr/local/lib/dri/kms_swrast_dri.so: Unsupported
relocation type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
MESA-LOADER: failed to open swrast: /usr/local/lib/dri/swrast_dri.so: Unsupported relocati
on type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
kwin_core: Failed to create gbm device for "/dev/dri/card0"
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
MESA-LOADER: failed to open crocus: /usr/local/lib/dri/crocus_dri.so: Unsupported relocati
on type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
MESA-LOADER: failed to open kms_swrast: /usr/local/lib/dri/kms_swrast_dri.so: Unsupported
relocation type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
MESA-LOADER: failed to open swrast: /usr/local/lib/dri/swrast_dri.so: Unsupported relocati
on type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
kwin_core: Failed to create gbm device for "/dev/dri/card0"
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
MESA-LOADER: failed to open crocus: /usr/local/lib/dri/crocus_dri.so: Unsupported relocati
on type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
MESA-LOADER: failed to open kms_swrast: /usr/local/lib/dri/kms_swrast_dri.so: Unsupported
relocation type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
MESA-LOADER: failed to open swrast: /usr/local/lib/dri/swrast_dri.so: Unsupported relocati
on type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
kwin_core: Failed to create gbm device for "/dev/dri/card0"
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
MESA-LOADER: failed to open crocus: /usr/local/lib/dri/crocus_dri.so: Unsupported relocati
on type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
MESA-LOADER: failed to open kms_swrast: /usr/local/lib/dri/kms_swrast_dri.so: Unsupported
relocation type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
MESA-LOADER: failed to open swrast: /usr/local/lib/dri/swrast_dri.so: Unsupported relocati
on type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
kwin_core: Failed to create gbm device for "/dev/dri/card0"
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
MESA-LOADER: failed to open crocus: /usr/local/lib/dri/crocus_dri.so: Unsupported relocati
on type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
MESA-LOADER: failed to open kms_swrast: /usr/local/lib/dri/kms_swrast_dri.so: Unsupported
relocation type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
MESA-LOADER: failed to open swrast: /usr/local/lib/dri/swrast_dri.so: Unsupported relocati
on type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
kwin_core: Failed to create gbm device for "/dev/dri/card0"
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
MESA-LOADER: failed to open crocus: /usr/local/lib/dri/crocus_dri.so: Unsupported relocati
on type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
MESA-LOADER: failed to open kms_swrast: /usr/local/lib/dri/kms_swrast_dri.so: Unsupported
relocation type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
MESA-LOADER: failed to open swrast: /usr/local/lib/dri/swrast_dri.so: Unsupported relocati
on type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
kwin_core: Failed to create gbm device for "/dev/dri/card0"
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
MESA-LOADER: failed to open crocus: /usr/local/lib/dri/crocus_dri.so: Unsupported relocati
on type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
MESA-LOADER: failed to open kms_swrast: /usr/local/lib/dri/kms_swrast_dri.so: Unsupported
relocation type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
MESA-LOADER: failed to open swrast: /usr/local/lib/dri/swrast_dri.so: Unsupported relocati
on type 36 in non-PLT relocations
 (search paths /usr/local/lib/dri, suffix _dri)
kwin_core: Failed to create gbm device for "/dev/dri/card0"
kwin_wayland_drm: No suitable DRM devices have been found
qt.qpa.wayland: "wl-shell" is a deprecated shell extension, prefer using "xdg-shell" if su
pported by the compositor by setting the environment variable QT_WAYLAND_SHELL_INTEGRATION
qt.qpa.wayland: "wl-shell" is a deprecated shell extension, prefer using "xdg-shell" if su
pported by the compositor by setting the environment variable QT_WAYLAND_SHELL_INTEGRATION
qt.qpa.wayland: Loading shell integration failed.
qt.qpa.wayland: Attempted to load the following shells QList("xdg-shell", "wl-shell", "ivi
-shell", "qt-shell")
qt.qpa.wayland: Loading shell integration failed.
qt.qpa.wayland: Attempted to load the following shells QList("xdg-shell", "wl-shell", "ivi
-shell", "qt-shell")
org.kde.startup: "kdeinit5_shutdown" QList() exited with code 255
startplasma-wayland: Shutting down...
startplasmacompositor: Shutting down...
startplasmacompositor: Done.
qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was fo
und.
qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was fo
und.
qt.qpa.xcb: could not connect to display :0
qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb plat
form plugin.
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reins
talling the application may fix this problem.

Available platform plugins are: minimal, xcb, wayland-egl, vnc, wayland, vkkhrdisplay, off
screen.

qt.qpa.xcb: could not connect to display :0
qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb plat
form plugin.
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reins
talling the application may fix this problem.

Available platform plugins are: minimal, xcb, wayland-egl, vnc, wayland, vkkhrdisplay, off
screen.

org.kde.plasma.waitforname: WaitForName: Service was not registered within timeout
Did a bit of research on the term Unsupported relocation type 36 in non-PLT relocations, and it seems to be a problem wit my GPU driver - in 15-CURRENT, the i915kms driver is too new for my hardware - even though in 14.1-RELEASE p3 (which was installed on same hardware about a month ago), the same driver worked fine.

Turns out I needed to compile LLVM18 with a different flag!

PR 282322
1730761171175.png

gitlab.freedesktop.org

FreeBSD: Detect and use the correct TLS model for FreeBSD (!31897) · Merge requests · Mesa / mesa · GitLab

What does this MR do and why? When it is compiled with Clang 19, it fails to dlopen(3) libraries with...
gitlab.freedesktop.org gitlab.freedesktop.org

Just making sure the software stack is correct - that's no joke, especially with slow hardware like mine.
 
Well, wow.

Compiled my way into KDE 6 using the tree that ADG pointed to on the euroquis.nl blog. The command given on the same blog works, and Plasma Wayland can start. In fact, it can even see my hardware properly!

Almost all the useful apps work.

BUT...

clicking on the desktop itself causes something to crash. I suspect it's just kwin, because all the windows with apps in them - they're fine. Wayland is still running. But task switcher disappears, so does wallpaper, right-clicking on the black screen does nothing. A reboot solves the problem. I just don't see a good way to just restart plasma Wayland session...

When Wayland runs fine:
1731214894451.png


When Wayland crashes, I have to SSH in, and kill these two processes, and then restart the Plasma Wayland session:
1731215194665.png


And I'm still hunting for a screenshot tool that works.

Because dammit, the command /usr/local/bin/ck-launch-session /usr/local/lib/libexec/plasma-dbus-run-session-if-needed /usr/local/bin/startplasma-wayland works fine to start that fragile enchilada! 😭
 
The spectacle screenshot tool worked for me on plasma wayland when I compiled stuff from the kde-it_goes_to_6 branch, but only after I chose this specific option in spectacle's menu: Window Under Cursor... Are you talking about the right-clicking crash? In this situation, kwin doesn't crash, but plasmashell does. To start plasmashell again, you can just use the Super+W key combination to access kwin's search bar and then type plasmashell.
 
Oleg_NYC said:
Are you talking about the right-clicking crash?
Click to expand...
I am!

Trouble is, for me, spectacle crashes right when I try to click the configure button.

Just clicking "Window under cursor" button works, somewhat - can't save the screenie!

Yeah, lots of papercuts that need to be addressed before it's usable in same way as the Xorg session...
 
Code: 
Operating System: FreeBSD 14.1
KDE Plasma Version: 6.2.1
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.3
Kernel Version: 14.1-RELEASE-p5 (64-bit)
Graphics Platform: Wayland
Memory: 7.9 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 3000
Still no good way to save a screenshot. Restarting plasmashell as shown by Oleg_NYC in post # 470 is essential to know. Everything else works just swimmingly.

Well, in that experimental ports branch, Plasma is now at 6.2.2, but upgrading to that is a bit too much for my hardware (i5 2467M). Would be nice if I could just update my tree with just the KDE ports and recompile while leaving everything else alone. Otherwise, it's kind of hard to make myself recompile everything (and spend 5 days doing that) just to figure out if the upgraded plasmashell resolved those papercuts or not.
 
You must log in or register to reply here.
Back
Top