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

vmisev said:
That was only way that I could start Wayland in VBox, script from the link you proposed doesn't work because kwin_wayland_drm can't open drm device /dev/dri/card0 - which doesn't exist in VBox guest. I have no intention to pollute nor screw my on the metal install – I have 0 interest in running Wayland, just wanted to help. I still think that ^C issue is sddm/ Wayland problem, good luck with your investigation.
Click to expand...
Thanks. Every bit of effort helps - that does include discovering that VirtualBox does not seem to support the virtual GPU driver playing well wtih /dev/dri/card0...

But yeah, having support for that in the first place is kind of a pre-requisite for solving the Ctrl-C bug. Things will need to work consistently the same on both metal and in a VM.
 
Well, damn... Reading the report that ADG references from his euroquis.nl blog,, maybe SDDM is involved somehow...
78 Starting a Wayland session:
79 Due to, what I call, the Ctrl+C bug in a Wayland session I advise against using SDDM at the moment.
Click to expand...

Looks like merely using SDDM somehow triggers the Ctrl-C bug if you log into a KDE Wayland Session from SDDM...

LibreQuest , have you tried to see if that is the case? As in, use the TTY to start a Plasma Wayland session to see if it triggers the Ctrl-C bug to crash Kate? I was hoping to see if using SDDM (or not) makes a difference for the bug.
 
astyle said:
Well, damn... Reading the report that ADG references from his euroquis.nl blog,, maybe SDDM is involved somehow...


Looks like merely using SDDM somehow triggers the Ctrl-C bug if you log into a KDE Wayland Session from SDDM...

LibreQuest , have you tried to see if that is the case? As in, use the TTY to start a Plasma Wayland session to see if it triggers the Ctrl-C bug to crash Kate? I was hoping to see if using SDDM (or not) makes a difference for the bug.
Click to expand...
I was never a dev, but I was always "jack of all trades" @ $DAYJOYB and my intuition got sharpened by finding and solving all kinds of bugs in the $JOB $WORKFLOW, so I do believe that I was close to the cause with sddm.
 
Wayland on intel laptop is working too. I just tried today. Working just fine it appears.
 

Attachments

  • Screenshot_20251002_105723.png
    Screenshot_20251002_105723.png
    385.3 KB · Views: 27
astyle said:
Well, damn... Reading the report that ADG references from his euroquis.nl blog,, maybe SDDM is involved somehow...


Looks like merely using SDDM somehow triggers the Ctrl-C bug if you log into a KDE Wayland Session from SDDM...

LibreQuest , have you tried to see if that is the case? As in, use the TTY to start a Plasma Wayland session to see if it triggers the Ctrl-C bug to crash Kate? I was hoping to see if using SDDM (or not) makes a difference for the bug.
Click to expand...
ohhh ok, I can try that on my laptop. I'll need to make the launch script. Then I'll edit and post back.

EDIT: You are correct, launching with a script will not crash in KATE with ctrl-c. However, launching from SDDM will result in a crash using ctrl-c in KATE. I have tested this on my intel laptop. I have not tested on that on my RX 6400 system. But it's likely safe to assume the results would be the same.

EDIT2: There is another issue. Seems to be impossible to return to Wayland from virt terminal. :/
 
Thanks, LibreQuest , that was very helpful.

But now I'm wondering, what if we try another (graphical, Wayland-compatible) greeter / Display Manager ? There should be a few of those in Ports.

I mean, if we are to conclude that the problem is indeed with SDDM, I'd think that the problem will go away if we try an alternative. But if we try an alternative (or a few of them), and the Ctrl-C bug only repeats itself, that is useful to know, as well.
 
Hi all. I created an account in order to participate in this topic.
A couple of days ago I installed FreeBSD 15 alpha 4 and I wanted to test various things, including Wayland-KDE. I stumbled upon problems that are reflected in this topic, but I noticed one thing that I did not see anyone mentioning here.

When my system boots-up SDDM starts, I login, and I have typical problems: pressing crtl+c crashes my Plasma session and if I switch to VT then entire SDDM kinda crashes.
However, when I start SDDM manually sometimes it happens that after I login for the second time I can no longer crash my Plasma session via crtl+c and I can no longer switch to VT at all. Like I lost the ability to run system shortcuts. Also when my desktop session is like this then I can NOT see any shutdown/reboot/sleep buttons in KDE start menu. Only logout option is shown. Also I can put my laptop to sleep (as root via CLI) while in this state and resume it and it works fine and it resumes my Plasma session.

The only problem is that my Plasma session enters this state kinda randomly. I managed to trigger this state 3 times this evening, but there is no correct order of doing things to be able to reproduce every time. I am an absolute beginner so I cannot interpret this, but maybe it will give a hint to someone experienced.
 
darth said:
Hi all. I created an account in order to participate in this topic.
A couple of days ago I installed FreeBSD 15 alpha 4 and I wanted to test various things, including Wayland-KDE. I stumbled upon problems that are reflected in this topic, but I noticed one thing that I did not see anyone mentioning here.

When my system boots-up SDDM starts, I login, and I have typical problems: pressing crtl+c crashes my Plasma session and if I switch to VT then entire SDDM kinda crashes.
However, when I start SDDM manually sometimes it happens that after I login for the second time I can no longer crash my Plasma session via crtl+c and I can no longer switch to VT at all. Like I lost the ability to run system shortcuts. Also when my desktop session is like this then I can NOT see any shutdown/reboot/sleep buttons in KDE start menu. Only logout option is shown. Also I can put my laptop to sleep (as root via CLI) while in this state and resume it and it works fine and it resumes my Plasma session.

The only problem is that my Plasma session enters this state kinda randomly. I managed to trigger this state 3 times this evening, but there is no correct order of doing things to be able to reproduce every time. I am an absolute beginner so I cannot interpret this, but maybe it will give a hint to someone experienced.
Click to expand...
Hey, hello my dear darth (for one who don't recognize him, darth runs one my fav YT channels and one the few Linux related that I follow and watch regularly @LinuxRenaissance). Welcome to the family!
FqDpW1wWYAAngXI.jpeg


I don't know much about Wayland, but few things to consider first: For the graphic to work and behave properly, you'll need proper match for your GPU between kernel version / in-base linux-kpi, and a then driver itself must be one that is built to work with all of above (with kernel source in place, you can build it from ports). Even if you not using nvdia, please check Thread 98943 to get picture about what I'm talking about here. It's simpler if user is on RELEASE branch.

Also, if all that is okay, try to use for the greeter x11/lightdm instead of x11/sddm.

Good luck and I hope that Wayland users will pick up from here and help more
 
darth said:
Hi all. I created an account in order to participate in this topic.
A couple of days ago I installed FreeBSD 15 alpha 4 and I wanted to test various things, including Wayland-KDE. I stumbled upon problems that are reflected in this topic, but I noticed one thing that I did not see anyone mentioning here.

When my system boots-up SDDM starts, I login, and I have typical problems: pressing crtl+c crashes my Plasma session and if I switch to VT then entire SDDM kinda crashes.
However, when I start SDDM manually sometimes it happens that after I login for the second time I can no longer crash my Plasma session via crtl+c and I can no longer switch to VT at all. Like I lost the ability to run system shortcuts. Also when my desktop session is like this then I can NOT see any shutdown/reboot/sleep buttons in KDE start menu. Only logout option is shown. Also I can put my laptop to sleep (as root via CLI) while in this state and resume it and it works fine and it resumes my Plasma session.

The only problem is that my Plasma session enters this state kinda randomly. I managed to trigger this state 3 times this evening, but there is no correct order of doing things to be able to reproduce every time. I am an absolute beginner so I cannot interpret this, but maybe it will give a hint to someone experienced.
Click to expand...
Well, losing the shutdown/reboot/sleep buttons in the start menu - I actually observed that happen in the Xorg side of KDE 6 when 6 was experimental, back in the days of 6.0. This is actually good to know, it does mean that the fix was not ported over to the Wayland side of things.

A word of caution: Because FreeBSD 15 is still in alpha stage , it's basically on you to report problems and successes (which is what I'm seeing), and to do your own problem-solving and filing bugs in Bugzilla. Basically, just fingers crossed that the problem has been addressed in the next version... In just a week, they will start building the beta stuff... Most people try to use -STABLE or -RELEASE tagged stuff to play with in-development projects like KDE Wayland. It means that you gotta have a pretty good reason for using 15 - like for things that are just not available in earlier versions (like support for an N-Key laptop keyboard, which did happen to me on one of my laptops).

Having said all that, welcome aboard!
 
I will switch to 14.3 and report back here if I find a way to reproduce this Plasma state. I also tried to run Plasma from tty with startplasma-wayland but it didn't work. I am on ThinkPad T580 with 8th Gen Intel iGPU.
 
astyle said:
Well, losing the shutdown/reboot/sleep buttons in the start menu - I actually observed that happen in the Xorg side of KDE 6 when 6 was experimental, back in the days of 6.0. This is actually good to know, it does mean that the fix was not ported over to the Wayland side of things.

A word of caution: Because FreeBSD 15 is still in alpha stage , it's basically on you to report problems and successes (which is what I'm seeing), and to do your own problem-solving and filing bugs in Bugzilla. Basically, just fingers crossed that the problem has been addressed in the next version... In just a week, they will start building the beta stuff... Most people try to use -STABLE or -RELEASE tagged stuff to play with in-development projects like KDE Wayland. It means that you gotta have a pretty good reason for using 15 - like for things that are just not available in earlier versions (like support for an N-Key laptop keyboard, which did happen to me on one of my laptops).

Having said all that, welcome aboard!
Click to expand...
I have all of those options in my launcher menu on Wayland Plasma. I think the more important thing is having LXQT Wayland working. It refuses to accept my selected compositor for Wayland. :/ I like LXQT more. :D
 
darth said:
Also when my desktop session is like this then I can NOT see any shutdown/reboot/sleep buttons in KDE start menu. Only logout option is shown.
Click to expand...
Glad to see you here, too!

Not on KDE, but this seems to happen when power management staff somehow crashes or upgraded when running (temporal mismatches happen). I'm running Mate DE with Compiz on X11.

Another situation I've encountered is when unlocking screensaver under quite heavy CPU and I/O intensive load like poudriere building multiple huge staff.

In both cases, I can switch to vty sanely and vty switch to any of them.
 
T-Aoki said:
Glad to see you here, too!

Not on KDE, but this seems to happen when power management staff somehow crashes or upgraded when running (temporal mismatches happen). I'm running Mate DE with Compiz on X11.

Another situation I've encountered is when unlocking screensaver under quite heavy CPU and I/O intensive load like poudriere building multiple huge staff.

In both cases, I can switch to vty sanely and vty switch to any of them.
Click to expand...
T-Aoki :

I realize that English is not your native language (and it's not mine, either), but staff and stuff are two very different things, even if pronunciation is somewhat similar... 😅

Staff means 'employees', 'people'...

Stuff is a catch-all generic term that normally used to apply an imprecise description. For example, "Staff can do stuff" can mean "The employees in this shop are very capable and skilled, they can do a wide range of duties", or it can mean "I've got thugs working under me, and they can be asked to do all kinds of shady and illegal activities, and you can count on them to pull it all off successfully". Well, "Staff" can also mean "rod" that is sometimes wielded by a priest (or a person in position of power)

Power management staff is something like this:
1759538612144.png


Sorry, I may be overdoing on this, I was having too much fun putting together an explanation... What I'm deriving from your post is that when KDE Wayland is not involved, vty does not present a problem with session management... So that's probably a good baseline for watching how the vty is different under KDE Wayland (as opposed to something else).
 
I have too few experiences on Wayland (startup, try enabling Japanese input, fail, then quit is almost all the cases), but seeing vty switching issues here and there, which is relatively rare on X11.
And yes, western languages are not my mother tongue. 😅
 
astyle said:
LibreQuest said:
By the way, the ctrl-c bug works in the entire session not just in KATE.
Click to expand...
Like I said, Kate text editor is just a convenient way to demonstrate the bug... the bug is not tied to Kate.
Click to expand...

And I as I said repeatedly here, it's most likely sddm+wayland bug. Try with
vmisev said:
try with x11/lightdm, or try without greeter and try the script astyle recommended here:
astyle said:
The setup needs to work as indicated on this page: https://euroquis.nl/kde/2025/09/07/wayland.html .
Click to expand...
Click to expand...
 
LibreQuest said:
I tried with lightdm. It wasn't wanting to log in at all. I didn't try with .xinitrc script. But none of the Wayland launchers wanted to work with lightdm for some reason.
Click to expand...
Thanks, this is good to know.

Based on this, I'm thinking there's a good chance we're all stuck with SDDM or straight launching from the vty. That does make the Ctrl-C bug more important to fix - it appears we don't have a workable alternative handy.

It's not out of question that something else might pop up that solves that bug...
 
You must log in or register to reply here.
Back
Top