Plasma Wayland session

[Bernie Innocenti]

Hello,

the plasma-workspace-wayland package adds a "Plasma (Wayland)" session to gdm
(and probably sddm as well), but I couldn't get it to work.

The first problem seems to be that /usr/bin/startplasmacompositor couldn't find qdbus,
probably because the qt5 binary is installed as /usr/bin/qdbus-qt5. After fixing this with
a temporary symlink hack, the wayland session still fails to start:

Dec 18 17:48:19 giskard /usr/libexec/gdm-wayland-session[14439]: startplasmacompositor:
Could not start D-Bus. Can you call qdbus?
Dec 18 17:48:19 giskard /usr/libexec/gdm-wayland-session[14439]: startplasmacompositor:
Starting up...

Was anyone able to get to a working Wayland session on Fedora 27? If so, how?

[Kevin Kofler]

Bernie Innocenti wrote:
>  the plasma-workspace-wayland package adds a "Plasma
> (Wayland)" session to
>  gdm (and probably sddm as well), but I couldn't get it to work.
>  
>  The first problem seems to be that /usr/bin/startplasmacompositor couldn't
>  find qdbus, probably because the qt5 binary is installed as
>  /usr/bin/qdbus-qt5. After fixing this with a temporary symlink hack, the
>  wayland session still fails to start:
>  
>  Dec 18 17:48:19 giskard /usr/libexec/gdm-wayland-session[14439]:
>  startplasmacompositor: Could not start D-Bus. Can you call qdbus? Dec 18
>  17:48:19 giskard /usr/libexec/gdm-wayland-session[14439]:
>  startplasmacompositor: Starting up...
>  
>  Was anyone able to get to a working Wayland session on Fedora 27? If so,
>  how? 
As a quick workaround, you can try setting your local PATH to include 
/usr/lib64/qt5/bin. But the shipped /usr/bin/startplasmacompositor ought to 
be patched to run qdbus-qt5 instead of just qdbus.

        Kevin Kofler

[Bernie Innocenti]

Kevin Kofler wrote:

>  As a quick workaround, you can try setting your local PATH to include
>
>  /usr/lib64/qt5/bin. But the shipped /usr/bin/startplasmacompositor ought to 
>  be patched to run qdbus-qt5 instead of just qdbus. 
It seems startplasmacompositor looks for qtdbus in the path returned by qtpaths
--binaries-dir, so that should be fine.

A similar issue was already reported a while ago against older versions of bdm and
plasma-workspace-wayland: https://bugzilla.redhat.com/show_bug.cgi?id=1389584

There's also an upstream bug for gdm, but still not analyzed:
https://bugzilla.gnome.org/show_bug.cgi?id=760613

[Sérgio Basto]

On Sun, 2017-12-24 at 03:25 +0000, Bernie Innocenti wrote:
>  Kevin Kofler wrote:
>  
>  > As a quick workaround, you can try setting your local PATH to
>  > include 
>  > /usr/lib64/qt5/bin. But the shipped /usr/bin/startplasmacompositor
>  > ought to 
>  > be patched to run qdbus-qt5 instead of just qdbus.
>  
>  It seems startplasmacompositor looks for qtdbus in the path returned
>  by qtpaths --binaries-dir, so that should be fine.
>  
>  A similar issue was already reported a while ago against older
>  versions of bdm and plasma-workspace-wayland: https://bugzilla.redhat
>  .com/show_bug.cgi?id=1389584
>  
>  There's also an upstream bug for gdm, but still not analyzed: https:/
>  /bugzilla.gnome.org/show_bug.cgi?id=760613 
I tried https://community.kde.org/KWin/Wayland#Starting_a_nested_KWin 

kwin_wayland --xwayland &
DISPLAY=:1 rawstudio

and 

(rawstudio:19630): Gdk-WARNING **: Wayland compositor does not support
xdg_shell interface, not using Wayland display

when I want debug one rawstudio bug on wayland :( 

Digging about xdg_shell is not implemented on gtk+ so still not
possible run gtk+ on wayland ? 

Best regards and merry Christmas ! 
-- 
Sérgio M. B.