KDE Plasma X11; KDE Plasma Wayland

It is not often you pick your DE and you have two of everything, one being an X11 and one being Wayland. I use KDE, and there is KDE X11 and KDE Wayland and both seem to have problem with them. In one once you enter you Secret Password, it comes back and asks you for it again and again; in the other you get to the screen which then freezes, so you go back and start all over again. I think I am now using the X11 version. I’ve also nuked SDDM and switched over to LightDM, but what is it with the X11 version and the Wayland Version. Choose one or the other, but offering 2 of everything? makes life more complicated than it needs to be.

Don’t say that ! someone’ll remove the “wrong” one … of something. …again.

That said, I don’t use Wayland because I have 2 monitors and it only lets me place the 2nd on the right when my physical monitor is on the left and it won’t allow you to select a “primary” monitor - such fundamental shortcomings you wonder how it got released.

IT today is just a huge fragemented mess and is most likely going to keep getting worse. But you can help stop this: the next time someone says “this new programming language is really cool !” just tell them to **** off … and maybe use a mallet to get your point across.

(Not having any issues with KDE at the moment.)

Thanks for the tip. I too use two monitors. I’ve have been educated that “Wayland” is still "experimental: while X11 is the “Standard” DM, still I wish that someone would make Wayland and optional inclusion. I know that it plays havoc with me. I have since ditched SDDM and installed LightDM as I do not like GDM.

Other display related things I’ve found which may be of use:

  1. Use VGA and DVI but not HDMI :

I have one monitor connected to the vga out on the video card - never had any problems on that.
The other was on the card’s hdmi out. There’s also a kvm (keyb/video/mouse) switch in the middle to muddy the diagnosis waters.

I was getting screen blacking out occasionally - most days for a while in the afternoons usually - on the hdmi monitor only.
There was talk online about it being related to the hdmi audio.
I couldn’t find any of the settings they were talking about and don’t currently have the time to look into what my system is using for audio - possible complications from the fact I have Gnome and KDE stuff installed etc - so for a possible quick fix I got a DVI-to-HDMI cable (£3.76 new on ebay) and put the hdmi monitor on the card’s DVI out and have had no screen problems since.

  1. Screen alignment

When I first switched from HDMI to DVI the monitor’s image was slighlty off and none of the “auto adjust” options were available. So there was a gap in my extended desktop where the 2 monitor images “meet”.
I manged to fix/clear this by changing both monitors to the highest resolution available on both that was just below the resolution of the lower one so where I have
Monitor1: 1680x1050
Monitor2: 1440x900
I changed both to 1280x1024 where the alignment corrected itself and then back to their original resolutions where they all remained correctly aligned and no issues with that since.

  1. Diplay managers

I’m not having any issues with the standard Display Manager(s). I updated an issue with my install notes for KDE here :

  1. Login loop

I had what sounds like the same problem as you “…Secret Password, it comes back and asks you for it again and again” a while back.
Alas I don’t seem to have made any notes on how I fixed it…but I do now recall having to get selinux to relabel everything as part of fixing stuff and it would make sense that an selinux denial during login would send you back.
To fix it I had to do the emergency target thing at boot to access the file system (you could also boot from an alt OS on a usb drive and mount the filesystem) and then
create the file /.autorelabel and reboot. I may have done touch /.autorelable if it was already there. But you should see the system being relabeled during the next boot.

  1. Nvidia problems ?

My original nvidia issues - mostly solved by switching to a radeon may in part have been hdmi related but I’m not going to look into that just yet.

  1. KDE multi monitor desktop problem

Sometimes when I login, 1 monitor is black (no wallpaper) and does not respond to right clicks but is otherwise usable. When this happens the other monitor will have 2 wallpaper images overlapped.

You can restart KDE plasmashell without logging out/losing your workspace state and this will clear that problem - similar to restarting Windows explorer when it gets confused.
kquitapp5 plasmashell || killall plasmashell && kstart5 plasmashell
from kwin - Can I restart the KDE Plasma Desktop without logging out? - Ask Ubuntu

  1. Mallets

For persistent offenders a taser may be more effective: short,sharp,shock,they won’t do it again.

Thanks for the reply. I am still aways from finishing configuring RL 8.5, but at least it is now installed, and I keep ticking off things on my “Punch List” before I swap it out with my current WS.

  1. One of the things will be to temporarily remove the DVI- D cable from leopard and add it to ocelot to create a 2-monitor system. The graphics card is a new / old Nvidia GeForce GTX 1050Ti, but has no VGA, so I got a Display Port => VGA adapter to hook into my 4-position KVM switch… which is VGA . The second monitor will simply plug into the DVI-D port on the card.

  2. Om screen alignment… I have a 24" Ben Q and a 20" ViewSonic both True 8 Bit Color and non flickering – important because I am an epileptic – so I am sort of stuck at HD 1280x1024 resolution

3.I’ve got KDE 5.whatever installed 10 VD each with a separate wallpaper and its own set of widgets

  1. Login loops. X11 version of KDE lead to login loops, switch to KDE Wayland and you could login only to have the blood screen freeze, then it was back to X11 and at last yo could login. Very Clumsy. I Nuked SDDM and switched to LightDM and that solved the problem (of course you are going to have the hassle of installing LightDM but it was worth it).

  2. Nvidia problems. Yep!! The nouveau driver works just fine. It is currently running on openSUSE 15.3 Leap. On RL 8.5 however I eventually want to install the Nvidia drivers , but that is literally will be the LAST thing I will do, long after I have finished the configuration, have the 2 TB cleaned off and set up for BACKUP, have BackupNinja installed and configured and I have the entire disk Backed up so I can restore the entire disk just in case this goes south. I’d rather spend 3 hrs. restoring the system than 3 months because I have a jacked system that has problems.

  3. The Multi Monitor problem has occurred to me me too. The solution – at least in CentOS 7.x – is to going to System Settings => Display Configuration and more likely than not you will see on display over lapping the other. Pull them apart so that they are edge-to-edge next to each other and that should solve the problem. I’ll find out once I temporarily set ocelot up as a 2-monitor system.

Again, Thanks for your reply.

D’Cat

#4
Not convinvced about the move to LightDM. As I say, I have sddm, x11 and KDE 5(.18 on RL 8.4 and .23 on RL8.5) and no login loops so the real problem must be or have been something else - a conflict specific to your system or something that got cleared somehow about the same time you switched to LightDM. But hey ! if it’s working and you’re happy with LightDM then why not stick with it.

On the need to relabel my system - pretty sure it was after restoring files as part of trying to recover the system which’d make sense. In some situations relabeling will happen automatically and you may not even notice or it’ll look like the system has hung for a bit - that sounds like your wayland freeze and x11 retry unless it was happening repeatedly.

#5
In system building/configuration the approach I’m using is to doc/script everything (slowwww process) and use VMs with live and backing qcow2 images so I can make/try changes and if all’s well commit to the base image and if not, discard the changes and try again. Then when all done I’ll have an image I can use to create a working system and a set of scripts I can use/tweak to configure a new build including when the next upgrade-without-an-upgrade-path arrives.

#6
GTK ! that sounds like the right fix for the problem - I’ll try that if/when it happens next.

all the best !