Created attachment 102734 [details] Output of journalctl --unit=sddm.service I am having problems with login on plasma wayland. I notice this a few weeks ago, I was kinda lazy trying to report this bug. Step to reproduce 1. start sddm login screen 2. select plasma wayland 3. validate password. Result 4. the device returns to the same sddm login screen as seen in step 1. Desired result. Access to plasma wayland Other Xorg plasma desktop still seems to work and I did change my wifi card to from bcm to intel. I have attach the complete journctl log for sddm.service. Note, all wayland login attempts are unsuccessful. $lsb_release -a No LSB modules are available. Distributor ID: neon Description: KDE neon Developer Edition Release: 16.04 Codename: xenial The device is up to date with neon dev patches. I apologize if the tags are incorrect since I cannot find an sddm tag
please provide the output of qdbus org.kde.KWin /KWin supportInformation from an X11 session
Created attachment 102743 [details] output of qdbus org.kde.KWin /KWin supportInformation > qbbus.txt Here
Given the output I don't see anything which would explain it. Do you have all KWin packages installed?
I do not think I have all the kwin packages. I am not sure where to look
I do find this quite odd because wayland was working like expected. First, plasma fails to login after a few attempts. Now, it just always fails to login. I do not know any pattern of the successes and failure of sddm login
> First, plasma starts to fail to login after a few attempts I forgot the word starts
Created attachment 102749 [details] output of dpkg --get-selections
Created attachment 102750 [details] output of dpkg --get-selections | egrep -i '(kwin|qt|wayland)
Seems the relevant packages are installed. Can you check .xsession-errors?
Created attachment 102754 [details] xsession error file
I decided to reinstall kde neon dev edition, since I nuke the install during the time between I posted the xsession errors and now. I cant reproduce the bug anymore. I wonder how it became a configuration issue. Martin Graslin thank you for your time. I think I put the wrong tag since it should be kcm_sddm