To Plasma Wayland users

makc_

makc_

Developer
Folks,

Please, share your experience with Plasma Wayland:

Does switching from Plasma Wayland to vt and back work for anybody (without the patch posted by Oleg)?

Does any Qt6 WebEngine app (e.g. Falkon, KMail, Akregator) work for you under Plasma Wayland?

Any success story for running Plasma Wayland on NVidia GPU?
 
makc_ said:
Folks,
Please, share your experience with Plasma Wayland:
Click to expand...
Hello, I normally use Plasma X11 so this is just a one-off experience:


Does switching from Plasma Wayland to vt and back work for anybody (without the patch posted by Oleg)?
Click to expand...
Doesn't work for me, the system froze but I was able to perform a regular shutdown using the power button.


Does any Qt6 WebEngine app (e.g. Falkon, KMail, Akregator) work for you under Plasma Wayland?
Click to expand...
Code: 
[9:26][fmc000@tu45b-freebsd ~]$ falkon
Falkon: 2 extensions loaded
[2530:37907084541968:1109/092713.294542:FATAL:check.cc(361)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
zsh: trace trap  falkon
[9:27][fmc000@tu45b-freebsd ~]$


Any success story for running Plasma Wayland on NVidia GPU?
Click to expand...
Sorry, Intel GPU here.

FreeBSD 14.3-STABLE with all the updates (i.e. KDE 6.5.2 as of today).
 
makc_ said:
Folks,

Please, share your experience with Plasma Wayland:

Does switching from Plasma Wayland to vt and back work for anybody (without the patch posted by Oleg)?

Does any Qt6 WebEngine app (e.g. Falkon, KMail, Akregator) work for you under Plasma Wayland?

Any success story for running Plasma Wayland on NVidia GPU?
Click to expand...

The patch, of course, only works for me in the setup that doesn't involve launching sddm first.
 
The patch only works for me if I run dbus-run-session ck-launch-session startplasma-wayland (or /usr/local/lib/libexec/plasma-dbus-run-session-if-needed ck-launch-session startplasma-wayland) to launch the GUI. In this situation, SDDM is not involved at all. If I switch to a bare TTY while Plasma is running and then switch back, I see the GUI, and all previously opened graphical apps stay open. In an SDDM-based setup, however, I have to kill Xorg after VT switching; otherwise, when I return to the Alt+F9 TTY, I encounter a non-functional SDDM. Killing Xorg spawns a functional SDDM, but the previously opened apps are no longer open when I access the Wayland desktop.
 
Ok my situation is completely different then.

Using sddm (latest available in the repos) when I try switching from the GUI to a tty everything seems to hang, starting from the mouse pointer. I don't even get to see a tty. However, I'm sure that the underlying system is still working because pressing the power button triggers a regular shutdown.

I can try to remap the power button to logout if you think it may help further testing, let me know.
 
I had tried Plasma Wayland a couple of times with Nvidia, but no success.
I gave up a couple of months ago and am waiting for a success message from a Nvidia user.
 
Oleg_NYC said:
In an SDDM-based setup, however, I have to kill Xorg after VT switching; otherwise, when I return to the Alt+F9 TTY, I encounter a non-functional SDDM. Killing Xorg spawns a functional SDDM, but the previously opened apps are no longer open when I access the Wayland desktop.
Click to expand...
makc_

Post in thread 'Trying to run KDE 6 Plasma with Wayland....'

This patches fixes switching between virtual terminals for me:


If you are using SDDM, please note, that SDDM greeter runs in X11 mode on ttyv8 (by default), and any wayland session (Plasma, Wayfire, etc) will be started on ttyv9. The SDDM greeter screen on ttyv8 will be frozen while wayland is running.
  • Thanks
 
makc_ said:
makc_

Post in thread 'Trying to run KDE 6 Plasma with Wayland....'

This patches fixes switching between virtual terminals for me:


If you are using SDDM, please note, that SDDM greeter runs in X11 mode on ttyv8 (by default), and any wayland session (Plasma, Wayfire, etc) will be started on ttyv9. The SDDM greeter screen on ttyv8 will be frozen while wayland is running.
  • Thanks
Click to expand...
It's there an open bug for this? I couldn't find any and it's a shame that an issues like this that already has a possible working solution is not properly tracked.

Edit: sorry, I just noticed that you're the author and committer of the patch solving the Ctrl+C bug, you know better than me what's needed 😀
 
makc_ said:
makc_

Post in thread 'Trying to run KDE 6 Plasma with Wayland....'

This patches fixes switching between virtual terminals for me:


If you are using SDDM, please note, that SDDM greeter runs in X11 mode on ttyv8 (by default), and any wayland session (Plasma, Wayfire, etc) will be started on ttyv9. The SDDM greeter screen on ttyv8 will be frozen while wayland is running.
  • Thanks
Click to expand...
This patch doesn't work for me. I compiled x11-wm/plasma6-kwin with this patch enabled and switching to VT from Wayland freezes as before (I even rebooted my system to be sure).
 
fmc000 said:
This patch doesn't work for me. I compiled x11-wm/plasma6-kwin with this patch enabled and switching to VT from Wayland freezes as before (I even rebooted my system to be sure).
Click to expand...

His patch fixes the situation for me when the Plasma GUI is launched directly from the command line. Of course, in this situation SDDM is not involved at all. I have no idea, though, what he meant when he mentioned SDDM in his post (the ttyv8 thing, etc.).
 
fmc000 said:
This patch doesn't work for me. I compiled x11-wm/plasma6-kwin with this patch enabled and switching to VT from Wayland freezes as before (I even rebooted my system to be sure).
Click to expand...
Do you run Plasma from the terminal or via SDDM? Could you try both ways?

Something is still wrong with the Plasma when it is launched from the SDDM.
 
makc_ said:
Do you run Plasma from the terminal or via SDDM? Could you try both ways?

Something is still wrong with the Plasma when it is launched from the SDDM.
Click to expand...
Definitely SDDM. Will try from the terminal and report back.

Edit: from the terminal it works fine. I use this script:

Code: 
[19:39][fmc000@tu45b-freebsd ~]$ cat .local/bin/kw
#!/bin/sh

# Clean stale serverauth files
rm -f ~/.serverauth.*

# Start Plasma under Wayland
ck-launch-session /usr/local/lib/libexec/plasma-dbus-run-session-if-needed startplasma-wayland
[19:39][fmc000@tu45b-freebsd ~]$

Edit 2: There's a weird bug. Switching from Wayland to tty and back does not bring up the non-default monitor unless the mouse pointer is active on it (i.e. the default monitor shows the GUI while the non-default monitor still shows the terminal window) . To show the GUI moving the mouse pointer on the non-default monitor is enough, no other actions are needed. The default monitor works fine 100% of the time regardless of where the mouse pointer is.

I hope I made myself clear, I'm not an English native speaker.
 
You must log in or register to reply here.
Back
Top