Wayland session freezes when using Ctrl+Alt to switch to another terminal

I know this is not a very new problem for Wayland, but I failed to find an answer to this issue. X session is unaffected, but as it is being made obsolete in plasma, it won't help for long. Is anyone aware of a possible light in the tunnel for this problem?
 
Not (yet?) ported to FreeBSD, but there's a fork of KDE that states supports for X11, SonicDE. Not sure whether it's sustainable or not, though. And not at all tried.

KDE is no longer my emergency desktop environment for the time Mate DE is somehow broken, as recent version was invasive to configurations affecting Mate DE, thus, broke parts of my daily driver desktop by polluting Gtk configs that KDE itself shouldn't basically using. This never happened older versions. So now KDE is a platform to build/run some apps I need but not full desktop for me, except for dedicated user to test Wayland compositors on upgrading NVIDIA driver ports (start up Wayland version of KDE desktop on the user).

Of course, forcibly touching configurations for Qt is OK, as KDE is based on Qt. But why Gtk, too? Sigh.
 
IT-Doody did you have an update (or make us of) drm-kmod or amdgpu or drm-6??-kmod ?
I've had serious issues using drm-66-kmod and much less with drm-612-kmod
I've seen this suggestion before, but don't clearly understand the difference between these versions. I thought driver(kernel module) version was determined by hardware model. Can you confirm there is no difference in real life performance by using drm-612-kmod? I am indeed using the default drm-66-kmod at the moment.

Update: switching to drm-612-kmod unfortunately didn't solve the problem:(
 
What about this in loader.conf? I'd try 0 if 1 doesn't affect it:
Code:
hw.dri.fbdev_emulation="1"
I'm not following you. What is this option supposed to accomplish? I have only this in /etc/loader.conf:
Code:
kern.geom.label.disk_ident.enable="0"
kern.geom.label.gptid.enable="0"
zfs_load="YES"
 
I found some suggestion to try bypassing sddm and running plasma from tty, but when I executed startplasma-wayland I got a message: "startplasmacompositor could not start d-bus, can you call qdbus?"(I confirmed dbus is running). Then running dbus-run-session startplasma-wayland gave me a desktop without mouse or keyboard and I couldn't even switch tty's(both with dbus already running and first stopped). There was some error message in terminal but it was gone too fast to read it.
 
Back
Top