From the menu, the box for authentication disappears when OK is clicked, but the GUI does not appear. Trying to open from the terminal as root results in this message:
Haven't tried any other KWhatevers that require root. No problem on Plasma without Wayland.

Maybe these thread posts provide assistance:
https://www.linuxquestions.org/quest...ml#post6206168
https://www.linuxquestions.org/quest...ml#post6206891

Hope that helps!

No, the only difference that made was to make the desktop loading slower.
Thanks, anyway.

Well, because of the Nazi security on Wayland, there are no ways yet to run a program as another user on a Wayland/Plasma5 session, for example: ksystemlog as root.

However, there's a workaround, brought to us by openSUSE: to add on KWin the XAuthority support to XWayland via a patch.

You will find this patch on KWin src.rpm from there: https://download.opensuse.org/source....5-1.1.src.rpm

The name of wanted patch is: 0001-Use-Xauthority-for-Xwayland.patch

To use it you should build your own KWin package, which starts with copying the "kde" build system from -current to somewhere else and to add into a file: patch/kwin.patch
Of course, the 0001-Use-Xauthority-for-Xwayland.patch should be put on a folder named: patch/kwin
Finally, from the base directory you execute the following command:
When the KWin package finishes to build, it will upgraded automatically, so all you have is to enjoy your XAuthority on Wayland, after a reboot - as you see in the attached screenshot.

PS. I know about this patch since long time - since Plasma5 was still on KTown, and I really hopped always to be added to our Plasma5 build, because it adds a very useful "missing feature" to Wayland/Plasma5.

PS2. If you wonder what bussines have KWin with the running graphical programs as another users - it have, as strange as it looks, because on the Wayland/Plasma5 this KWin is not only the windows manager but also the display server.

Attached Thumbnails

 

1 members found this post helpful.

Thanks, LuckyCyborg. What, if any, are the advantages of Wayland? I haven't noticed any differences in performance or appearance between Plasma(Wayland) and Plasma. Don't think I'll go to the trouble of patching & rebuilding KWin. It's certainly crazy security if I can't run it as an "ordinary" user OR root. WhoTF can run it?

Well, from what I read and understand, the X11 and/or X.org server is a mammoth stuffed with spaghetti code and having more bugs than a stray dog. In the end, the developers of this ancient technology trowed the towel, pointed that the thing is unmaintainable and they started to develop the Next Generation of Display Server for Linux: Wayland.

Also, looks like the X.org server is about to be abandoned by RedHat (which maintains it) in favor of Wayland.

First of all, I believe that we should adapt. What you heard about XFree86 in the least times? And how compatible will be a XFree86 server with the modern Linux?

Yes, XFree86 gone on the path of Dodo bird after the businesses stopped to throw money at it. This is about to happen also to Xorg and IF we will not adapt to Wayland, in few years probably we will become an ancient Linux.

What are the advantages of Wayland, after all, in my humble opinion of regular user?

They say that it is much smaller, just some core features, then the desktop environments are free to implement what features they want. For example (as it is the subject of this thread) they believe that XAuthority is not a Wayland core business, but of the Wayland compositors, which essentially are the real display servers.

So, on Plasma5 the display server is KWin, while in Gnome3 is Mutter. For those who wants lightweight solutions, there's Sway.

Every one has its own set of features, they are uber-integrated on their desktop environment, and they have the freedom to implement what features they likes.

So, in my humble opinion, the first advantage of Wayland is its versatility. Everybody have the freedom to implement their display server as they like. Be it the KDE's Plasma5 or RedHat's Gnome3, or whatever.

The second advantage of Wayland looks being the security. Every window is just stand-alone, eventually talking via the display server for information. To imagine how secure is Wayland, to note that they had to screencast the windows via an Audio/Video server - PipeWire, to get working a rather puny feature of Plasma5: the taskbar thumbnails.

BUT, there's also an big disadvantage, which you just hit: every desktop environment feature previously offered by Xorg should be eventually recreated by every interested Wayland compositor.

The Wayland has no idea how to run a graphical application as another user, like is yours KSystemLog - and IF there is a Wayland feature which permits this, it should be implemented by the Wayland compositor as it likes, via an Wayland extension.

So, the sad truth is that the KDE developers hired to develop Plasma5 does not thought that running graphical programs as another user is a useful feature to be implemented. Personally I blame them to still having wet dreams about smartphones with KDE Plasma - as if they will ever succeed where the almighty Microsoft failed.

Fortunately, we have a solution: a patch made and maintained by openSUSE.

But there are some other missing features for which we have no solution yet - even the Wayland/Gnome3 have them: the proper restoring of windows sessions and proper restoring the windows position.

And at the end of day, is not the Wayland fault, but the KDE fault.

2 members found this post helpful.

One thing I prefer about the non-Wayland Plasma is the inclusion of a Gamma control option in the Display and Monitor settings. Lowering it improves the rather washed-out look of Thinkpad screens (which is what I'm running current on: T410 & X200).

1 members found this post helpful.

That works in Wayland/Gnome3 as I tested myself on Ubuntu.

BTW, you can believe that even Sway has this particular feature on Wayland since some fraking FOUR years?

https://www.reddit.com/r/linux/comme..._adds_support/

Yet, it still have To Be Implemented on Wayland/Plasma5 ...

1 members found this post helpful.

So it's up to the KDE Plasma developers to sort it out. When I did a websearch on the problem I found loads of results - same basic problem, different applications, different distros, etc.