[SOLVED] Wayland (Sway/Plasma 5)

lcronos · n00b Joined: 09 Jun 2014 Posts: 74

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

bec · Posted: Tue Aug 01, 2017 6:21 pm Post subject:

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?
_________________
abe

lcronos · n00b Joined: 09 Jun 2014 Posts: 74

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 · Developer Joined: 05 Apr 2007 Posts: 8935

Qt-5.8 is essentially a broken release.

lcronos · n00b Joined: 09 Jun 2014 Posts: 74

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 · Posted: Wed Aug 02, 2017 8:04 am Post subject:

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)

asturm · Developer Joined: 05 Apr 2007 Posts: 8935

lcronos · n00b Joined: 09 Jun 2014 Posts: 74

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 · Developer Joined: 05 Apr 2007 Posts: 8935

lcronos · n00b Joined: 09 Jun 2014 Posts: 74

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 · Posted: Thu Aug 03, 2017 11:33 am Post subject:

lcronos · n00b Joined: 09 Jun 2014 Posts: 74

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 · Posted: Mon Aug 07, 2017 8:56 am Post subject:

asturm · Developer Joined: 05 Apr 2007 Posts: 8935

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 · Posted: Mon Aug 07, 2017 10:23 am Post subject:

lcronos · n00b Joined: 09 Jun 2014 Posts: 74

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 · n00b Joined: 09 Jun 2014 Posts: 74

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 · Posted: Tue Aug 22, 2017 11:51 am Post subject:

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.
_________________
Important German:

"Aha" - German reaction to pretend that you are really interested while giving no f*ck.
"Tja" - German reaction to the apocalypse, nuclear war, an alien invasion or no bread in the house.

lcronos · n00b Joined: 09 Jun 2014 Posts: 74

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 · Posted: Thu Aug 24, 2017 7:42 am Post subject:

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

See here:

lcronos · n00b Joined: 09 Jun 2014 Posts: 74

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 · Developer Joined: 05 Apr 2007 Posts: 8935

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

lcronos · n00b Joined: 09 Jun 2014 Posts: 74

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 · Posted: Mon Aug 28, 2017 9:19 am Post subject: