How to start wayland kde from command line

phalange · 06-02-2021, 11:51 AM

I tried from a post on Alien Bob's blog

Code:

startkwayland

and also

Code:

XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland

Both result in a hard system lockup.

ZhaoLin1457 · 06-02-2021, 12:17 PM

Quote:

Originally Posted by phalange

I tried from a post on Alien Bob's blog

Code:

startkwayland

and also

Code:

XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland

Both result in a hard system lockup.

Let me guess, did you have a NVIDIA graphics card?

Unfortunately, the NVIDIA graphics is an utterly disaster on Wayland.

And they are only one which gives hard lookup on Wayland. The AMD or Intel graphics works fine.

phalange · 06-02-2021, 02:42 PM

Quote:

Originally Posted by ZhaoLin1457

Let me guess, did you have a NVIDIA graphics card?

Unfortunately, the NVIDIA graphics is an utterly disaster on Wayland.

And they are only one which gives hard lookup on Wayland. The AMD or Intel graphics works fine.

This is an Intel graphics card.

Code:

lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)

pghvlaans · 06-02-2021, 09:58 PM

Does "dbus-run-session --exit-with-session startplasma-wayland" work any better?

LuckyCyborg · 06-03-2021, 03:07 AM

Quote:

Originally Posted by phalange

This is an Intel graphics card.

Code:

lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)

Here works perfectly the default command "startkwayland" on runlevel 3 console, on any of my boxes[1], for example: with an Intel Ivy Bridge i3-3220T with HD Graphics 2500

Code:

Operating System: Slackware 14.2
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2
Kernel Version: 5.10.41
OS Type: 64-bit
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-3220T CPU @ 2.80GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 2500

If you get a hard system lookup, probably something is wrong with your graphics stack.

It's certainly a drivers issue, so you waste your time trying to tune the Wayland/Plasma5 launch command - it works fine as it is.

What you do is like trying to tune the "startx" command because your X11 session goes hard lookup.

[1] True, I've avoided the NVidia graphics, which forces me to use my boxes like they like, not like I will like to do.

Regnad Kcin · 06-04-2021, 12:08 AM

Quote:

I've avoided the NVidia graphics, which forces me to use my boxes like they like, not like I will like to do.

The 470 series of NVIDIA drivers are expected to support Wayland. Only 465.xx drivers are available thus far. The Intel onboard graphics doesn't cut the mustard for 3 or more monitors which is my common style and can cause problems with only 2 monitors. So I wait to see what Wayland can do for me.

enorbet · 06-04-2021, 10:39 AM

Just a suggestion but running the KWayland menuitem from the SDDM login/DM/Chooser does crash so far with nVidia but at least it doesn't system lock.

murdo · 11-11-2021, 07:13 AM

In my experience so far using the NVIDIA 495.44, which supports Wayland, logging into Plasma Wayland from the SDDM gives a black screen for a few seconds before returning to the login screen. There doesn't seem to be any console output for this, that I can see.

The interesting thing is, if I log in to my normal DE (Xfce) and run

Code:

kwin_wayland --xwayland

it will start successfully, giving me a black window that I can send other KDE services to with commands such as

Code:

kwrite --xwayland

I can't run non-KDE services in it though. Tried to load something from Dolphin using a non-KDE service and Dolphin crashed. kwin_wayland and all the other services in it stayed running.