[SOLVED] Wayland+KDE/Plasma

0BADC0DE · 2021-12-14 18:26:10

Disclaimer: this is my first time w/o Xorg.

I am trying to run KDE/Plasma on top of Wayland.
I am trying to follow the wiki at https://wiki.archlinux.org/title/Wayland .
I did a fresh new minimal installation with:
- wayland
- kwin
- xorg-xwayland
- qt5-wayland
- plasma-desktop

Then I chose tbsm (because it's just bash!) as the display manager and started it from my .bashrc as per documentation.
But tbsh insists (and fails) with Plasma (X11).
So I manually start Plasma with this command:

XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland

Maybe I can use a different display manager: which one "is best suited"(tm) for Wayland?
Can I avoid xorg-xwayland?

Thanks in advance.

Last edited by 0BADC0DE (2021-12-22 10:39:35)

cloverskull · 2021-12-14 18:42:54

Have you installed plasma-wayland-session?

V1del · 2021-12-14 19:04:58

For a Wayland only display manager afaik GDM is the only reasonable choice, though afaik SDDM's git branch should have it working as well. Whether you need xwayland depends on the applications you use, the answer is likely yes for a lot of things. (e.g. Steam and games in general you'll need it for example, and chromium has a bug on Plasma where it doesn't start properly in real Wayland mode)

Also FWIW, don't run an explicit DBUS session when you log in normally, you'll already have a valid one and you potentially mask session guarantees by starting plasma in a different session.

Last edited by V1del (2021-12-14 19:06:41)

mcloaked · 2021-12-14 20:13:20

FWIW I run plasma-wayland-session from sddm login - and I run chrome (not chromium) without xwayland using "/usr/bin/google-chrome-stable --enable-features=UseOzonePlatform --ozone-platform=wayland --touch-events=enabled %U" with the touch events flag present so that my touchscreen also works. This has been running the past month or so without any issues despite Ozone still being experimental. For firefox I avoid xwayland by setting an environment variable in as:

$ cat .config/environment.d/60-moz-wayland.conf
MOZ_ENABLE_WAYLAND=1

and now this works, and the one environment variable also allows Thunderbird beta to run under wayland and avoid xwayland - and with both programmes running checking for an xwayland programmes with xlsclients, shows that prior to making the change I had:

$ xlsclients
lenovo1  firefox
lenovo1  thunderbird

but after the changes the command gives no output as both run under wayland. For chrome I run current stable. I don't know if chromium will also run under wayland using the same method. I only run Thunderbird beta so I don't know if stock Thunderbird will also run wayland by setting the variable.

Edit: - It seems chromium will also run under wayland the same way as chrome: https://wiki.archlinux.org/title/chromi … nd_support

Last edited by mcloaked (2021-12-14 20:47:40)

AndroGR · 2021-12-14 21:52:20

0BADC0DE wrote:

Disclaimer: this is my first time w/o Xorg.
I am trying to run KDE/Plasma on top of Wayland.
I am trying to follow the wiki at https://wiki.archlinux.org/title/Wayland .
I did a fresh new minimal installation with:
- wayland
- kwin
- xorg-xwayland
- qt5-wayland
- plasma-desktop
Then I chose tbsm (because it's just bash!) as the display manager and started it from my .bashrc as per documentation.
But tbsh insists (and fails) with Plasma (X11).
So I manually start Plasma with this command:
XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland
Maybe I can use a different display manager: which one "is best suited"(tm) for Wayland?
Can I avoid xorg-xwayland?
Thanks in advance.

You didn't have to do these. Install

plasma-wayland-session

, build SDDM from source and enable it, and your Arch installation will be well more optimized for Plasma wayland.
PS: Never install something that you don't need. Arch is a distribution about maintaining order on your system.

0BADC0DE · 2021-12-15 06:21:30

cloverskull wrote:

Have you installed plasma-wayland-session?

Nope! Thanks!
But why do I get Plasma (X11) if I don't have XOrg?

V1del wrote:

For a Wayland only display manager afaik GDM is the only reasonable choice, though afaik SDDM's git branch should have it working as well. Whether you need xwayland depends on the applications you use, the answer is likely yes for a lot of things. (e.g. Steam and games in general you'll need it for example, and chromium has a bug on Plasma where it doesn't start properly in real Wayland mode)

Thanks.
I basically need a browser (any among Firefox, Chrome, Chromium, Vivaldi and Firefox) and maybe libreoffice. Anything else it's basically within KDE.
Is there a generic way to test a program without xwayland?

mcloaked wrote:

FWIW I run plasma-wayland-session from sddm login - and I run chrome (not chromium) without xwayland using
/usr/bin/google-chrome-stable --enable-features=UseOzonePlatform --ozone-platform=wayland --touch-events=enabled %U"
with the touch events flag present so that my touchscreen also works. This has been running the past month or so without any issues despite Ozone still being experimental. For firefox I avoid xwayland by setting an environment variable in as:
$ cat .config/environment.d/60-moz-wayland.conf
MOZ_ENABLE_WAYLAND=1
and now this works, and the one environment variable also allows Thunderbird beta to run under wayland and avoid xwayland - and with both programmes running checking for an xwayland programmes with xlsclients, shows that prior to making the change I had:
$ xlsclients
lenovo1  firefox
lenovo1  thunderbird
but after the changes the command gives no output as both run under wayland. For chrome I run current stable. I don't know if chromium will also run under wayland using the same method. I only run Thunderbird beta so I don't know if stock Thunderbird will also run wayland by setting the variable.
Edit: - It seems chromium will also run under wayland the same way as chrome: https://wiki.archlinux.org/title/chromi … nd_support

Woah! I need to test these things. Thanks,.

Last edited by 0BADC0DE (2021-12-24 08:26:10)

0BADC0DE · 2021-12-15 07:55:22

mcloaked wrote:

FWIW I run plasma-wayland-session from sddm login

sddm (0.19.0-7) is pulling in also xorg-server and related stuff.
When enabled and started I get both XOrg and XWayland running, I am not sure this makes any sense at all.
So I removed that along with its dependencies.

mcloaked wrote:

and I run chrome (not chromium) without xwayland using "/usr/bin/google-chrome-stable --enable-features=UseOzonePlatform --ozone-platform=wayland --touch-events=enabled %U" with the touch events flag present so that my touchscreen also works.

You suggestions (as well as the related wiki page you mention) seem not to work for me.
I can get Plasma working (with Xwayland pulled in by plasma-wayland-session).
But I cannot make chromium run under native wayland with those flags: processes are started up but they are not showing up any window.
Chromium starts up regularly without those flags.
Any hint to troubleshoot?

This is my setup (no AUR):

wayland: 1.20.0-1
xorg-xwayland: 21.1.4-1
kwin: 5.23.4-1
plasma-desktop: 5.23.4-1
plasma-wayland-session: 5.23.4-1
qt5-wayland: 5.15.2+kde+r37-1
kernel: linux-zen 5.15.7.zen1-1
GPU: Intel Corporation GeminiLake [UHD Graphics 605]

Last edited by 0BADC0DE (2021-12-15 08:21:24)

mcloaked · 2021-12-15 08:23:25

You should check that you are running a plasma wayland session by doing:

$ echo $XDG_SESSION_TYPE
wayland

If the output to that command is anything other than wayland, and specifically xwayland, then you need to change your setup so that you get the output above. If you are already running a plasma wayland session as verified this way then further work can be done to fine out what is going on when running the other programmes. Also you can see if any code you are running is not wayland by using the xlsclients command - and then any programme running under xwayland rather than wayland will be listed.

Last edited by mcloaked (2021-12-15 08:24:19)

0BADC0DE · 2021-12-15 08:35:47

mcloaked wrote:

You should check that you are running a plasma wayland session by doing:
$ echo $XDG_SESSION_TYPE
wayland
If the output to that command is anything other than wayland, and specifically xwayland, then you need to change your setup so that you get the output above.

It is wayland.

mcloaked wrote:

If you are already running a plasma wayland session as verified this way then further work can be done to fine out what is going on when running the other programmes. Also you can see if any code you are running is not wayland by using the xlsclients command - and then any programme running under xwayland rather than wayland will be listed.

Of course, if I run "plain chromium", xlsclients shows it.
If I run chromium with those extra arguments, it isn't shown up any more. But, of course, it is not working.
So chromium should work on wayland, but it doesn't. From command line I see this:

[2746:2746:0100/000000.014679:ERROR:gpu_init.cc(457)] Passthrough is not supported, GL is egl, ANGLE is

What is this ANGLE that it seems it cannot be found?
On the other hand, google-chrome works just fine with those extra parameters: xlsclients isn't showing it!
Falkon doesn't seem to support wayland yet: this is a known un-feature.
Vivaldi doesn't work either, just like chromium.

mcloaked wrote:

For firefox I avoid xwayland by setting an environment variable in as:
$ cat .config/environment.d/60-moz-wayland.conf
MOZ_ENABLE_WAYLAND=1

This works just fine. Very well!

Last edited by 0BADC0DE (2021-12-15 08:53:27)

mcloaked · 2021-12-15 10:12:57

At least you have the mozilla programmes working under wayland, as well as chrome, which is good progress, so it seems that there is a bug in chromium that is preventing it also working under wayland, and perhaps looking for chromium wayland bugs, or reporting upstream may yield either some upstream fixes or a suggested workaround to get chromium also working under wayland - though in the meantime xwayland is a fallback way to use it.

mcloaked · 2021-12-15 10:17:57

I did a quick search for the error message you quoted and found a link to something similar at https://stackoverflow.com/questions/675 … s-disabled which has one of the answers:
7

I had the same problem with selenium and chromedriver. For me the solution was to activate WebGL in Chrome browser. I did the following

chrome://settings -> Click Advanced at the bottom -> Check the Use hardware acceleration when available box
chrome://flags -> Search for WebGL in the search bar -> Enable / Activate WebGL

There are much better instructions here: https://superuser.com/questions/836832/ … my-browser

which might be worth trying in the case of chromium - running under xwayland without the parameters and activating WebGL and hardware acceleration as suggested if you have not already done that. Once done then try running under wayland again.

Last edited by mcloaked (2021-12-15 10:23:35)

0BADC0DE · 2021-12-15 12:34:15

I modified the KDE menu items like these:

For Firefox:

[[ "$XDG_SESSION_TYPE" == "wayland" ]] && MOZ_ENABLE_WAYLAND=1 /usr/lib/firefox/firefox %u || /usr/lib/firefox/firefox %u

And similarly for Chrome (I use beta channel):

[[ "$XDG_SESSION_TYPE" == "wayland" ]] && /usr/bin/google-chrome-beta --enable-features=UseOzonePlatform --ozone-platform=wayland %U || /usr/bin/google-chrome-beta %U

Both work flawlessly.
Will check the other things later and report back.

Last edited by 0BADC0DE (2021-12-15 12:35:48)

mcloaked · 2021-12-15 14:33:09

...and double check with the xlsclients command once they are running to be sure they are running under wayland - good that your method now works.

Last edited by mcloaked (2021-12-15 14:33:49)

0BADC0DE · 2022-03-17 10:10:39

After a few months of use and updates, I confirm all is working fine for all browsers:

Chrome (99.0.4844.74)
Chromium (99.0.4844.74)
Vivaldi (5.1.2567.66)

all with the modified KDE menu items shown earlier.
Falkon (3.2.0) works fine with no modification at all.
xlsclients tool doesn't show any of them.

My current setup uses KDE frameworks 5.92.0 and Qt 5.15.3.

Last edited by 0BADC0DE (2022-03-17 10:11:52)

Arch Linux

#1 2021-12-14 18:26:10

[SOLVED] Wayland+KDE/Plasma

#2 2021-12-14 18:42:54

Re: [SOLVED] Wayland+KDE/Plasma

#3 2021-12-14 19:04:58

Re: [SOLVED] Wayland+KDE/Plasma

#4 2021-12-14 20:13:20

Re: [SOLVED] Wayland+KDE/Plasma

#5 2021-12-14 21:52:20

Re: [SOLVED] Wayland+KDE/Plasma

#6 2021-12-15 06:21:30

Re: [SOLVED] Wayland+KDE/Plasma

#7 2021-12-15 07:55:22

Re: [SOLVED] Wayland+KDE/Plasma

#8 2021-12-15 08:23:25

Re: [SOLVED] Wayland+KDE/Plasma

#9 2021-12-15 08:35:47

Re: [SOLVED] Wayland+KDE/Plasma

#10 2021-12-15 10:12:57

Re: [SOLVED] Wayland+KDE/Plasma

#11 2021-12-15 10:17:57

Re: [SOLVED] Wayland+KDE/Plasma

#12 2021-12-15 12:34:15

Re: [SOLVED] Wayland+KDE/Plasma

#13 2021-12-15 14:33:09

Re: [SOLVED] Wayland+KDE/Plasma

#14 2022-03-17 10:10:39

Re: [SOLVED] Wayland+KDE/Plasma

Board footer