Trying to run KDE 6 Plasma with Wayland....

Oleg_NYC said:
"When locked: Immediately"
Click to expand...
My setting is different: "When locked: after 1 minute".

Looking at Xorg.0.log entries that SDDM makes, I'm noticing that the greeter part just drops keyboard and mouse when I get kicked out of the Wayland session back to the greeter. SSH-ing in and restarting SDDM gets the keyboard and mouse back.

Oleg_NYC said:
mouse (but not the keyboard) was non-functional until I deleted 40-libinput.conf
Click to expand...
I did delete the file, but that did not make a difference for my problem.

Right now, I'm actually doing some research on getting SDDM to start in a Wayland compositor rather than Xorg. That's because I'm thinking that passing the keyboad/mouse works from Xorg to Wayland, but not the other way around, and that it should work in both directions, not just one.

Uninstalling/disabling SDDM and starting Wayland from command-line is still on the table on my end of things.
 
One more thing: Session management seems to work in 6.5.0 - but I had to change a default setting as described in the attached screenshot.
 

Attachments

  • session_restore.png
    session_restore.png
    47.1 KB · Views: 34
astyle said:
Uninstalling/disabling SDDM and starting Wayland from command-line is still on the table on my end of things.
Click to expand...
Tried that. Lockscreen is there, it reacts and shows up when I wiggle the mouse and mash the keyboard, but without a greeter enabled, there's no way for me to unlock it by typing in my password. I'd have to disable specifically the lockscreen if I were to go without a greeter like SDDM.
 
I don't get it. What greeter? The lockscreen feature in the Plasma environment is completely independent from the functionality of a display manager. You can lock the screen, unlock it, turn off the screen in the settings, etc. if you launch Plasma from the command line. There is no need for any greeter or display manager.
 
Well, when I launch from command-line, and let the screen get locked, I lose mouse and keyboard, and there's no way for me to unlock that lockscreen... do you know of a way?

I mean, even the clock on the lockscreen freezes, so I get an exact timestamp of when that happens.
 
One idea that I have is to add some code to the daemon that checks for presence of keyboard/mouse, and re-launches SDDM if there's no keyboard/mouse attached... It would take me some time to play with that idea, though... 😓 and to see if it's any good.
 
fmc000 said:
Well, you're mixing things.

First of all, the Ctrl+C bug has nothing to do with KDE it's a pure sddm bug that is now partially address with the latest release in the ports (which now crashes for me when trying to move from the Wayland GUI to a VT with for example Ctrl+Alt+F1).

Second, saving the session like you describe always worked, even way before 6.5.0 was released. The apps are correctly restored but when using Wayland all of them appear on the default monitor whilst under Xorg all is working as expected and every app is restored in the monitor it was running previously.

I just checked right now with 6.5.2 and there's no difference at all with respect to the previous versions, it's absolutely the same behavior. BTW, I have a dual monitor setup.
Click to expand...
Hold it right there.

I'm not mixing things.

1. Ctrl-C bug, while not related to KDE, still used to cause a session crash. (I know the Ctrl-C bug is mostly resolved at this point, meaning the Ctrl-C key combo is harmless now. That means that session crashes happen for other reasons.)
2. When a session crashes (be it from the Ctrl-C bug or something else), I get kicked to black screen.
3. SSH-ing in and running service sddm restart gets SDDM restarted, and I can log back into the session that crashed.
4. When I log back into the session (that crashed in step 2), I noticed that Firefox window is gone without a trace, not even a core dump. I had to restart Firefox by hand. And, Konsole and systemsettings5 app were mimimized to the taskbar.
5. Issues that I pointed out in Step 4 - they went away when I applied a simple settings change as described in post #702.

These steps are actually reproducible for me.

And now for the real reason I said to hold it it right there:

Session crashing when being sent from Wayland GUI to a VT (for whatever reason, like screen locking or turning off) - that is probably what I'm seeing as well. I did experience it when I did normal logouts. I'd get back to SDDM (that was 50-50 proposition), but logging back in - my Plasma Wayland session just did not look the same as when I logged out (until I did step 5).

Teasing out sequences and details like this can be really helpful here. If you have more questions, and/or need more info, I'll be happy to provide it in this thread.
 
You must log in or register to reply here.
Back
Top