[SOLVED] Wayland (Sway/Plasma 5)

[lcronos]

I am trying to play with Plasma 5 on Wayland again (what I had working earlier stopped working with in a day lol, figured I'd wait a while and try again). I've done a little more experimentation and can't get any useful setups running at all. I can get Weston working with "weston-launch" from a TTY. I can get a partial Plasma 5 session running (by that I mean I can get one application running using kwin_wayland --xwayland --exit-with-session=$APPLICATION). If I just use startplasmacompositor it does the splash screen, then leaves me with a blank screen. The only thing that works there is yakuake. Sway just fails to launch completely. If I run it through SDDM it just returns me to SDDM, and if I run it in a TTY the screen flashes black for a second, then gives some errors (I'll add those once I'm back in the TTY). This happens whether I use elogind or systemd so that doesn't seem to matter. I'd like to have sway working at a minimum, though both would be better if possible. I'm in a session with only firefox atm, so I'll add my emerge info as soon as I can access a terminal.

EDIT: Okay, sway isn't returning any errors now, but has exit code 139.

emerge --info

Code: Select all

Portage 2.3.6 (python 3.4.5-final-0, default/linux/amd64/13.0/desktop/plasma, gcc-5.4.0, glibc-2.23-r4, 4.11.12-ck x86_64)
=================================================================
System uname: Linux-4.11.12-ck-x86_64-Intel-R-_Core-TM-_i5-4210U_CPU_@_1.70GHz-with-gentoo-2.3
KiB Mem:     6037480 total,   4426572 free
KiB Swap:    4194300 total,   4194300 free
Timestamp of repository gentoo: Fri, 28 Jul 2017 00:23:58 +0000
Timestamp of repository dotnet: Tue, 04 Jul 2017 13:23:23 +0000
Timestamp of repository lisp: Mon, 17 Jul 2017 08:52:00 +0000
sh dash 0.5.8.2
ld GNU ld (Gentoo 2.28 p1.2) 2.28
app-shells/bash:          4.3_p48-r1::gentoo
dev-java/java-config:     2.2.0-r3::gentoo
dev-lang/perl:            5.24.1-r2::gentoo
dev-lang/python:          2.7.12::gentoo, 3.4.5::gentoo
dev-util/cmake:           3.7.2::gentoo
dev-util/pkgconfig:       0.28-r2::gentoo
sys-apps/baselayout:      2.3::gentoo
sys-apps/openrc:          0.26.3::gentoo
sys-apps/sandbox:         2.10-r3::gentoo
sys-devel/autoconf:       2.13::gentoo, 2.69::gentoo
sys-devel/automake:       1.11.6-r1::gentoo, 1.15-r2::gentoo
sys-devel/binutils:       2.28-r2::gentoo
sys-devel/gcc:            5.4.0-r3::gentoo
sys-devel/gcc-config:     1.7.3::gentoo
sys-devel/libtool:        2.4.6-r3::gentoo
sys-devel/make:           4.2.1::gentoo
sys-kernel/linux-headers: 4.4::gentoo (virtual/os-headers)
sys-libs/glibc:           2.23-r4::gentoo
Repositories:

gentoo
    location: /usr/portage
    sync-type: git
    sync-uri: https://github.com/gentoo-mirror/gentoo
    priority: -1000

dotnet
    location: /usr/local/portage/dotnet
    sync-type: git
    sync-uri: https://github.com/gentoo-mirror/dotnet
    masters: gentoo
    priority: 50

dr
    location: /usr/local/portage/dr
    sync-type: git
    sync-uri: git://github.com/cerebrum/dr.git
    masters: gentoo
    priority: 50

flussence
    location: /usr/local/portage/flussence
    sync-type: git
    sync-uri: https://gitlab.com/flussence/overlay.git
    masters: gentoo
    priority: 50

lisp
    location: /usr/local/portage/lisp
    sync-type: git
    sync-uri: https://github.com/gentoo-mirror/lisp
    masters: gentoo
    priority: 50

powerman
    location: /usr/local/portage/powerman
    sync-type: git
    sync-uri: https://github.com/powerman/powerman-overlay.git
    masters: gentoo
    priority: 50

Installed sets: @i3
ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="* -@EULA"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=native -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/config /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c"
CXXFLAGS="-march=native -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
EMERGE_DEFAULT_OPTS="-j5 --load-average=4"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync metadata-transfer news parallel-fetch preserve-libs protect-owned sandbox sfperms splitdebug strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="ftp://ftp.ussg.iu.edu/pub/linux/gentoo ftp://lug.mtu.edu/gentoo/ http://gentoo.osuosl.org/ http://mirror.lug.udel.edu/pub/gentoo/"
LANG="en_US.utf8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
MAKEOPTS="-j5 --load-average 4"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --exclude=/.git"
PORTAGE_TMPDIR="/var/tmp"
USE="X a52 aac acl acpi alsa amd64 berkdb bindist bluetooth branding bzip2 cairo cdda cdr cli connman cracklib crypt cups cxx dbus declarative dri dts dvd dvdr egl elogind emboss encode exif fam firefox flac fortran gdbm gif glamor gles2 gpm gtk iconv ipv6 jpeg kde kipi kwallet lcms ldap libnotify mad mng modules mp3 mp4 mpeg multilib ncurses nls nptl offensive ogg opengl openmp pam pango pcre pdf phonon plasma png policykit ppds pulseaudio qml qt3support qt4 qt5 readline sdl seccomp semantic-desktop session spell ssl startup-notification svg tcpd tiff truetype udev udisks unicode upower usb vorbis wayland widgets wifi wxwidgets x264 xattr xcb xcomposite xinerama xml xscreensaver xv xvid zlib" ABI_X86="32 64" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump author" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="mmx mmxext sse sse2" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock isync itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 timing tsip tripmate tnt ublox ubx" GRUB_PLATFORMS="efi-64" INPUT_DEVICES="synaptics evdev keyboard" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php5-6" POSTGRES_TARGETS="postgres9_5" PYTHON_SINGLE_TARGET="python3_4" PYTHON_TARGETS="python2_7 python3_4" RUBY_TARGETS="ruby21 ruby22" USERLAND="GNU" VIDEO_CARDS="intel i965" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account"
Unset:  CC, CPPFLAGS, CTARGET, CXX, INSTALL_MASK, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, USE_PYTHON

[bec]

What Qt version are you using? I read that wayland support in qt-5.9 is almost broken:

https://blog.martin-graesslin.com/blog/tag/wayland/

Are you running elogind?

[lcronos]

I am using Qt 5.8 (not sure on the minor revision, I'm not at my laptop right now).

I've used OpenRC+elogind, and systemd. Neither setup worked for me.

[asturm]

Qt-5.8 is essentially a broken release.

[lcronos]

I looked at packages.gentoo.org and it doesn't look like I'd be using Qt 5.8 after all. I'll confirm when I'm on my laptop again, but it looks like the most recent version is 5.7. Asturm, I saw in another forum post that you have (or had) Plasma and Wayland working with elogind. Which version of Plasma are you running? I'm on 5.10 (though it was because I wanted to be on 5.9+, I just saw that 5.9 hit stable and I liked 5.9 more than 5.10 so I'll probably roll back), so I wonder if that's causing some problems.

I saw in another thread that my issue with sway may be caused by the "swaylock" useflag. I'll see if I have that set, if not I'll see if that fixes it.

EDIT: Okay, sway did have the swaylock use flag disabled. I'm emerging it now and will update if it works. I actually had Qt 5.7 installed (I had the KDE overlay and at one point, Plasma 5.9 required Qt 5.8 but that requirement must have changed at some point), but am rolling back to 5.9 so I'll see if that works.

[Yamakuzure]

Plasma works with wayland here with openrc+elogind. QT version is 5.7.1.

The USE flags I used are: (shortended, hopefully only the relevant ones)

Code: Select all

USE="dri3 egl elogind glamor opengl wayland wayland-compositor -gles -gles1 -gles2 -gles3"

Installed is:

Code: Select all

 ~ $ for x in dri3 egl glamor wayland wayland-compositor ; do echo "====== $x ======" ; LC_ALL=C eix -I -c -U $x ; done
====== dri3 ======
[I] media-libs/mesa (17.1.5@07/17/17): OpenGL-like graphic library for Linux
====== egl ======
[I] dev-qt/qtgui (4.8.7(4)@05/13/17 5.7.1-r1(5/5.7)@06/12/17): The GUI module and platform plugins for the Qt5 framework
[I] dev-qt/qtopengl (4.8.7(4)@05/13/17 5.7.1(5/5.7)@05/13/17): OpenGL support library for the Qt5 framework (deprecated)
[I] dev-qt/qtwayland (5.7.1(5/5.7)@05/13/17): Wayland platform plugin for Qt
[I] media-libs/gst-plugins-bad (1.10.5(1.0)@06/19/17): Less plugins for GStreamer
[I] media-libs/mesa (17.1.5@07/17/17): OpenGL-like graphic library for Linux
[I] media-plugins/gst-plugins-vaapi (1.10.5(1.0)@06/19/17): Hardware accelerated video decoding through VA-API plugin for GStreamer
[U] net-libs/webkit-gtk (2.4.11-r200(2)@06/19/17 -> 2.4.11-r1(3/25) 2.4.11-r200(2) (~)2.16.6(4/37)^t): Open source web browser engine
[I] x11-apps/mesa-progs (8.3.0@05/13/17): Mesa's OpenGL utility and demo programs (glxgears and glxinfo)
[I] x11-libs/libva (1.8.3@07/03/17): Video Acceleration (VA) API for Linux
Found 9 matches
====== glamor ======
[I] x11-base/xorg-server (1.19.3(0/1.19.3)@05/13/17): X.Org X servers
====== wayland ======
[U] dev-cpp/gtkmm (2.24.5(2.4)@05/13/17 -> 2.24.5(2.4) (~)3.22.1(3.0)): C++ interface for GTK+
[I] kde-frameworks/plasma (5.36.0(5/5.36)@07/17/17): Plasma framework
[I] kde-misc/kdeconnect (1.0.3(5)@05/14/17): Adds communication between KDE Plasma and your smartphone
[I] kde-plasma/breeze (5.10.4(5)@07/19/17): Breeze visual style for the Plasma desktop
[I] kde-plasma/kinfocenter (5.10.4(5)@07/19/17): A utility that provides information about a computer system
[I] kde-plasma/oxygen (5.10.4(5)@07/19/17): Oxygen visual style for the Plasma desktop
[I] media-libs/glfw (3.2.1@05/13/17): The Portable OpenGL FrameWork
[I] media-libs/gst-plugins-bad (1.10.5(1.0)@06/19/17): Less plugins for GStreamer
[I] media-libs/libsdl2 (2.0.5@05/13/17): Simple Direct Media Layer
[I] media-libs/mesa (17.1.5@07/17/17): OpenGL-like graphic library for Linux
[I] media-plugins/gst-plugins-vaapi (1.10.5(1.0)@06/19/17): Hardware accelerated video decoding through VA-API plugin for GStreamer
[U] net-libs/webkit-gtk (2.4.11-r200(2)@06/19/17 -> 2.4.11-r1(3/25) 2.4.11-r200(2) (~)2.16.6(4/37)^t): Open source web browser engine
[I] net-misc/freerdp (2.0.0_rc0(0/2)@07/31/17): Free implementation of the Remote Desktop Protocol
[I] x11-base/xorg-server (1.19.3(0/1.19.3)@05/13/17): X.Org X servers
[I] x11-drivers/nvidia-drivers (384.59-r1(0/384)@07/28/17): NVIDIA Accelerated Graphics Driver
[I] x11-libs/gtk+ (2.24.31-r1(2)@05/12/17 3.22.17(3)@07/21/17): Gimp ToolKit +
[I] x11-libs/libva (1.8.3@07/03/17): Video Acceleration (VA) API for Linux
[I] x11-libs/libva-intel-driver (1.8.3@07/03/17): HW video decode support for Intel integrated graphics
Found 18 matches
====== wayland-compositor ======
[I] dev-qt/qtwayland (5.7.1(5/5.7)@05/13/17): Wayland platform plugin for Qt

[asturm]

Plasma 5.9 required Qt 5.8 but that requirement must have changed at some point)

No, you've got that wrong.

[lcronos]

I think that was when it was still in beta (this was in the KDE overlay). I've since removed that.

Rolling back to 5.9 didn't fix it (I guess that makes sense since you had 5.10 working). I was under the impression GLES was needed for it to work, I'll try matching your use flags. Also you're using Plasma+Wayland and the NVidia proprietary drivers? I didn't think those worked with Plasma on Wayland yet.

Setting the swaylock useflag fixed Sway, it looks like that was a required option and shouldn't be a useflag.

[asturm]

I think that was when it was still in beta (this was in the KDE overlay). I've since removed that.

Nope. Plasma-5.9 raised minimum Qt from 5.6 to 5.7. Upstream itself considers 5.8 broken, just last week I switched the *first* ebuild to 5.8 minimal locally, but I can't even push that to kde overlay because that would make it depend on qt overlay.

Nvidia does not support Wayland with their proprietary driver, plain and simple.

[lcronos]

Huh must have been the update to 5.7 I'm thinking of.

Yay that's what I thought. I know Gnome and Sway work with NVidia's EGLStreams, so I was a little surprised to see that package in that list of packages. I don't have NVidia on my laptop though.


EDIT: Okay, I added the useflags listed above however Plasma still fails to load in Wayland. Recently a new window has started showing up, kwin's effects are failing so the error window saying that effects have been disabled appears. Kwin is definitely running (I suppose the fact that yakuake has window decorations implies that though). I have an alias to restart plasma when it crashes, running it shows that plasma-desktop isn't actually started. That would explain why there's not background or panels. Any ideas why plasma-desktop wouldn't actually start up?

[Yamakuzure]

I was under the impression GLES was needed for it to work, I'll try matching your use flags. Also you're using Plasma+Wayland and the NVidia proprietary drivers? I didn't think those worked with Plasma on Wayland yet.

I have an Optimus Laptop. It is running on modesetting drivers, and I am using Bumblebee for programs needing the discrete nvidia card.

GLES is for mobile platforms. Disable it on desktops, or you are asking for trouble.

It is relatively simple: different hardware. Desktop hardware supports OpenGL, but mobile only es. With full OpenGL we can do more and also have more extensions available which can provide better performance

So much for the general point.

For Wayland, I guess you thought of this:

Why does Wayland use EGL?

EGL is the only GL binding API that lets us avoid dependencies on existing window systems, in particular X. GLX obviously pulls in X dependencies and only lets us set up GL on X drawables. The alternative is to write a Wayland specific GL binding API, say, WaylandGL.

A more subtle point is that libGL.so includes the GLX symbols, so linking to that library will pull in all the X dependencies. This means that we can't link to full GL without pulling in the client side of X, so Weston uses OpenGL ES to render. This also enables Weston to run on GPUs which don't support the full OpenGL API.

As detailed above, clients are however free to use whichever rendering API they like.

This sounds like you had to use OpenGL ES (GLES) with wayland, but that is not true.
Wayland uses, as stated above, EGL. And for a long time, it was necessary to use GLES to start an EGL context. This is no longer the case, and GLES is no longer needed for wayland.

Some more information, if you do not believe me, or just wanted to know that:

Years later we started the effort to get KWin using optionally OpenGL ES in addition to normal OpenGL. One of the differences is that OpenGL ES doesn’t use GLX, but rather EGL. So we gained code to setup compositing using EGL. But this was still a compile time switch and only supported together with using OpenGL ES. If I remember correctly the option to create on OpenGL context on top of EGL was not yet available in our drivers back then.

But there was a time when the FLOSS drivers started to support it and since the 4.10 release in beginning of 2013 we can provide a normal OpenGL context over EGL. This option was not really exposed and only bound to an environment variable. Very few users knew about it and this was also wanted. Using EGL was a good way to shoot yourself in the foot given that not all drivers support it and that we had much more testing on the GLX backend.

Now the situation has changed. With 5.x we expose EGL also through a config interface, but more importantly EGL is the only way to get OpenGL on Wayland. The assumption that every user is using GLX doesn’t hold any more. The assumption that we don’t need to spend so much time (as it’s only relevant in the reduced feature set of mobile devices) on the EGL backend is wrong. It must reach the same quality as the GLX backend, otherwise our Wayland experience suffers.

Any ideas why plasma-desktop wouldn't actually start up?

I will test Wayland again and see if Plasma-Desktop starts on my setup. The last time I tried, it did start up, but maybe something has changed?

[lcronos]

That would explain why the NVidia-driver was there lol.

Okay, yeah I just remember seeing people suggest GLES when using Wayland. I'll have to figure out why gst-plugins-bad isn't compiling with -gles2 but I think that's an unrelated issue.

If it works, would you mind sharing your make.conf, and the useflags the plasma-meta, plasma-desktop, plasma-workspace, and wayland all have?

[Yamakuzure]

If it works, would you mind sharing your make.conf, and the useflags the plasma-meta, plasma-desktop, plasma-workspace, and wayland all have?

Well, it does not, and I destroyed my (long!) answer here with a very stupid thing I did.

btw. memo to myself: "Never ever change the used OpenGL version in Plasma (Wayland), it'll brick your system!"

Okay, so last time I tried, everything was working, although slowly due to the desktop effects I had configured. Now my applications (conky, davmail, yakuake) are started, but no Plasma Shell.

Starting it using "kstart5 plasmashell" causes kstart5 to crash, and the back trace ends with 3 frames in libxcb.
Starting it directly spits out hundreds of lines telling me, that /usr/bin/qupzilla is not a valid desktop file ("what???") and ends in a crash in functions I would think have to do with shadow drawing of the desktop effects.

I think I have to test this a bit more. But maybe it is just me using gcc-6.3.0 ? ...

Edith just noticed: All my xcb packages have been installed *before* I switched to gcc-6.3... maybe that's a clue.

[asturm]

The combination of Plasma with Qt is important - Wayland support has changed a lot over Qt-5.8 and Qt-5.9 and not always for the better. Due to the changes necessary to improve and fix regressions w/ Qt-5.9 it is possible that with Plasma-5.10/Qt-5.7.1 you have a worse experience than back with Plasma 5.8/Qt-5.7.1, unfortunately.

[Yamakuzure]

The combination of Plasma with Qt is important - Wayland support has changed a lot over Qt-5.8 and Qt-5.9 and not always for the better. Due to the changes necessary to improve and fix regressions w/ Qt-5.9 it is possible that with Plasma-5.10/Qt-5.7.1 you have a worse experience than back with Plasma 5.8/Qt-5.7.1, unfortunately.

It may have been Plasma 5.8 when I last tested wayland, indeed...

Ahh... Martin Flöser on: Plasma Wayland and Qt 5.9 and beyond

(...)
Qt 5.9 is here to stay and that’s what we have to use as integration target. Given that Qt 5.9 and Qt 5.7 behave very differently it will become difficult for us to maintain support for both. My suggestion is that we drop support for Qt 5.7 and require Qt 5.9 for the Wayland session.

Wow...
...but there is hope:

I’ve seen most of the issues myself on Arch Linux with testing and kde-testing repos enabled. Yes, it was bad and I was unhappy with Qt’s slow bug fix mentality. But now the latest Qt 5.9.1 and KDE Plasma runs quite well with Wayland and I can use my Desktop for hours unless my computer goes idle for some time, it refuses to wake up… as soon as I know what’s wrong I will report a bug, I guess it’s related to the Mesa graphic drivers.

So this sounds to me, like they start to get along with QT-5.9.1.
..maybe, when qt-5.9.2 is out... well...

[lcronos]

Sorry for the belated response, I didn't get any email notifications about new posts, and didn't see the new ones until now.

Since i3/Sway are my primary WMs I'll try installing Qt 5.9 from the Qt overlay and see if it works. I'll let you know if it worked for me or not. Thanks for all the help with this



EDIT: Okay, well updating to Qt 5.9 didn't seem to fix the problem. Plasma's Wayland issue still fails to load. I tried using kstart5 plasmashell (or whatever that command is) manually after the wayland session let me open yakuake, and found it gives me a segfault. Is it possible that's related to this issue? The only thing I can think of beyond that is that mesa didn't want to update without the gles2 useflag. I'll re-enable it for mesa, update it, and see if that works. The segfault really didn't give me any other information, but I think that's at least partially related.

[lcronos]

I looked a little closer at what you said you were seeing, yamakuzure, and I'm seeing the same thing. I didn't look at a stack trace but I don't think it's related to gcc. I'm using 5.4 and seeing the same thing you see with 6.3. I don't remember what exactly I saw with just starting plasmashell but I did see a bunch of functions and had to ctrl+c to stop it.

Qt 5.9.1 definitely didn't fix it (oh and heads up, if you want to update qtwebengine you actually have to unmerge it right now, it fails at the very end of compilation starting with 5.8 if an older version already exists) for me though. That said, I haven't noticed any adverse effects for the time being, so I'll leave everything where it's at for now. Just to make things clear, I did update back up to Plasma 5.10.4 as well. It's odd though, since some people do seem to have it working with 5.10.4 on other distros, but not everyone. Arch seems like it's hit an miss. I wonder what the build differences are.


EDIT: Scratch that. With Qt5.9.1, running plasmashell & successfully starts the session. It doesn't start on it's own though for some reason. This does technically work though.

EDIT 2: Okay I looked a little closer and while plasmashell by itself works, kstart5 plasmashell still immediately gives a segfault. I wonder if this is why I have to manually run it for the session to start.

[Yamakuzure]

Thank you for your tests!

I have very little time at the moment. But as soon as I am able to, I'll test a bit more.

[lcronos]

Take your time. This is just kind of a side project for me. If you need to me try any other tests let me know.

[Yamakuzure]

I have just tried it out again, after doing some serious cleanup, and it works! *yay*

See here:

Code: Select all

 ~ $ ps aux | grep -P "/.*(plasmashell|wayland)" | grep -v grep
sed      19309  2.6  0.4 4143380 161376 tty8   Sl+  09:20   0:11 /usr/bin/kwin_wayland --xwayland --libinput --exit-with-session=/usr/lib64/libexec/startplasma
sed      19313  1.2  0.2 392692 66472 tty8     Sl+  09:20   0:05 /usr/bin/Xwayland -displayfd 56 -rootless -wm 59
sed      19622  1.4  0.8 4120644 269776 ?      Sl   09:20   0:05 /usr/bin/plasmashell

The wayland plasma shell behaves oddly in some places, and some desktop effects do not work the same. Like window decorations that have a transparent border and window title, loose their transparency. Tested with "Seven Black" and "Freeze".

Further there are some drawing issues, and systemsettings5 can not install new decorations. The "Install" button simply does nothing. Oh! And some shortcuts seem to be rearranged (?), at least I can no longer type a circumflex, the key triggers krunner now.

However, the effects do not turn the desktop into a crawl like months before when I last tested.

So, here are the things I did before testing Plasma on Wayland again. Please note, that I have no idea which one of those did the trick.

• Updated to kde-frameworks 5.37.0
• Updated to kde-plasma 5.10.5
• Updated to kde-apps 17.08.0
• Added "-qt3support -qt4 qt5" to my global use flags
• Added:

  Code: Select all

   ~ $ cat /etc/portage/package.use/z_remove_kdelibs4
  app-office/libreoffice -kde
  media-video/vlc -kde
  dev-vcs/subversion -kwallet

• Did "emerge --ask --deep --with-bdeps y --newrepo --changed-use --update @world"
• Unmerged kdelibs
• Unmerged all packages that needed qt4/kdelibs/qt3support and had no Slot 5 ebuild in kde overlay
• Final update of @world and then "emerge --depclean" ... which removed qt4

So my system has now a fully running Plasma desktop on wayland, and neither kdelibs nor qt4.

[lcronos]

So reading through there, I just want to double check. Is this with Qt 5.7 or 5.9? I've emerge 5.10.5 but still need to manually run plasmashell when I login to plasma wayland. kde-frameworks and kde-apps were already on the same versions you listed. I am now removing qt4 and qt3support to see if that's enough. If it's working for you on Qt 5.7 I may rollback (something tells me that staying on a masked version is just asking for trouble lol) and see if that works.

[asturm]

Plasma does not care if you have applications with qt4 or qt3support installed.

[lcronos]

That's true, but is it possible an application that uses qt4 is failing to load and causes plasma itself not to load?

EDIT: I'm not sure which package did it, but removing qt4 and qt3support from my system (and the general clean up that happened when I did that) fixed it . Plasma's wayland session works as expected now. Thanks for the help with this.

[Yamakuzure]

So reading through there, I just want to double check. Is this with Qt 5.7 or 5.9?

Sorry, forgot to mention that I am still on qt-5.7.1.

asturm, that is generally correct, but I just wanted to see, if I can have a Plasma without Qt3/4+kdelibs lingering in the background.

And some of the dependencies of Plasma *do* have a qt4 USE flag. So maybe there was some "interference".
Yes, I know, that is really far fetched...