Moin moin

No I'm not contradicting myself, it was probably just not clearly stated...
:) -- as I said, they conflict, as they install the same
desktop in different versions...
So, don't install plasma5 if you want to use plasma6 -- the only port that
might be needed of plasma5-plasma-integration.
If you want to try to use plasma6 and try to get wayland up, make sure to
remove plasma5* and just install the plasma6-plasma
package.

I really recommend to use this tree instead of main:
https://github.com/freebsd/freebsd-ports-kde/tree/kde-it_goes_to_6


You can then create a shell-script ala

###
#!/bin/sh
export QT_DEBUG_PLUGINS=1
# export QT_WAYLAND_SHELL_INTEGRATION=xdg-shell
export WAYLAND_DEBUG=1
# export XDG_SESSION_TYPE=wayland

ck-launch-session dbus-run-session truss /usr/local/bin/startplasma-wayland
>& /memory/startplasma.log
####

to try to run plasma... you likely get an output like

###

[...]
qt.core.library:
"/usr/local/lib/qt6/plugins/platforms/libqwayland-generic.so" loaded
library
Failed to create wl_display (No such file or directory)
qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in ""
even though it was found.
qt.core.library: "/usr/local/lib/qt6/plugins/platforms/libqxcb.so"
loaded library
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 platform plugin.
[...]

###
before it fails :/

mfg Tobias

On Sun, 21 Jul 2024 at 14:05, Mario Marietto <marietto2...@gmail.com> wrote:

> ---> You should not install any plasma5 components that are not pulled in
> by plasma6 -- they conflict, as they are both the KDE Desktop... and
> therefore share files and services :) -- so stick to one version.
>
> We can't stick to one version if plasma5 and plasma6 components conflict.
> You are contradicting yourself.
>
> If there are no conflicts, the output by :
>
> diff -u -p -N /usr/ports/x11-wm/plasma5-kwin/pkg-plist
> /usr/ports/x11-wm/plasma6-kwin/pkg-plist
>
> should not have lines started with a single space. Single space of unified
> diffs on top of lines means it's common with 2 files compared.
>
> There are many common lines such as:
>
> @@ -1,49 +1,275 @@ bin/kwin_x11
> bin/kwin_wayland
> bin/kwin_wayland_wrapper
> bin/kwin_x11
> -include/kwin_export.h
> -include/kwinanimationeffect.h
>
> The "-" at the top of lines means it appears on the first file but not on
> the second.
>
> Edit: Quote functionality does not do its work as intended. [image: :(]There
> should be a single space before bin/kwin_wayland, bin/kwin_wayland_wrapper
> and bin/kwin_x11 in the quoted example above.
>
> On Sat, Jul 20, 2024 at 11:10 PM Mario Marietto <marietto2...@gmail.com>
> wrote:
>
>> Thanks.
>>
>> Can you write a small tutorial for us ? I've been working on this for
>> months.
>>
>> On Sat, Jul 20, 2024 at 10:56 PM Tobias C. Berner <tcber...@gmail.com>
>> wrote:
>>
>>> Moin moin
>>>
>>> You should not install any plasma5 components that are not pulled in
>>> by plasma6 -- they conflict, as they are both the KDE Desktop... and
>>> therefore share files and services :) -- so stick to one version.
>>>
>>>
>>> I have not yet got the plasma6-wayland session working on my end
>>> though -- I can start the plasma-desktop inside a running wayland
>>> compositor, but I cannot bring up kwin as compositor.
>>>
>>>
>>> mfg Tobias
>>>
>>> On Sat, 20 Jul 2024 at 22:36, Mario Marietto <marietto2...@gmail.com>
>>> wrote:
>>> >
>>> > Hello.
>>> >
>>> > Here at forums.freebsd.org we are trying to install KDE 6 with
>>> Wayland,but we are failing. The thread is here :
>>> >
>>> >
>>> https://forums.freebsd.org/threads/trying-to-run-kde-6-plasma-with-wayland.93951/
>>> >
>>> > Do you have some kind of suggestion to give to us ?
>>> > The main problem seems to be that there is a conflict between
>>> plasma5-kwin and plasma6-kwin ; some kde5 and kde6 packages are mixed and
>>> this creates some issues.
>>> > What should we do ?
>>> >
>>> > thanks.
>>> >
>>> > --
>>> > Mario.
>>>
>>
>>
>> --
>> Mario.
>>
>
>
> --
> Mario.
>

Reply via email to