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

Since this is related to the use of KDE with Wayland (I don't recall this problem with the X session), I'm leaving it here just in case someone else is bugged by this:
To better match GTK decoration buttons with KDE ones when using CSD (client side decoration), like Firefox or Thunderbird do with titlebar hidden, there is the need to install devel/dconf:
buttons.png

It still doesn't draw the red circle to the close button (if you configured it), but at least is a better match.
 
Ok, upgraded to 15.1-RELEASE, upgraded all packages too, and now SDDM doesn't want to start the Wayland session; BUT it works flawlessly from command line with the same command used by SDDM:
/usr/local/share/sddm/scripts/wayland-session /usr/local/lib/libexec/plasma-dbus-run-session-if-needed /usr/local/bin/ck-launch-session /usr/local/bin/startplasma-wayland
Will try to see if I messed something up...
 
Hi

I installed one system from scratch with 15.1 -RELEASE
Used the REPOS for everything but the graphics drivers
Built nvidia-drm-kmod from todays port tree which pulled in nvidia-drm-612 and drm-612-kmod


$ pkg info nvidia* drm*
nvidia-driver-595.80
nvidia-drm-612-kmod-595.80.1501000_1
nvidia-drm-kmod-595.80
nvidia-kmod-595.80.1501000
nvidia-settings-595.58.03
nvidia-xconfig-595.58.03
drm-612-kmod-6.12.85.1501000_1

Ports tree on the release DVD does not include DRM 612 drivers. :oops:
Repos only have DRM-612 built for 16-current :'‑(

plasma_wayland_15.1.png
 
Maxnix said:
Ok, upgraded to 15.1-RELEASE, upgraded all packages too, and now SDDM doesn't want to start the Wayland session; BUT it works flawlessly from command line with the same command used by SDDM:
/usr/local/share/sddm/scripts/wayland-session /usr/local/lib/libexec/plasma-dbus-run-session-if-needed /usr/local/bin/ck-launch-session /usr/local/bin/startplasma-wayland
Will try to see if I messed something up...
Click to expand...
Nope, no dice. Tried reinstalling all pkgs again, but nothing; tried compiling SDDM locally after updating the ports collection, nothing.
I'll wait for the release official announcement, just in case; otherwise I'll file a bug report.
 
Maxnix said:
Nope, no dice. Tried reinstalling all pkgs again, but nothing; tried compiling SDDM locally after updating the ports collection, nothing.
I'll wait for the release official announcement, just in case; otherwise I'll file a bug report.
Click to expand...
My experience as well Wayland works from command line , not from sddm -

( exec dbus-launch ck-launch-session startplasma-wayland ) this works.
 
I'm compiling everything from scratch on a 15.1-RELEASE on my ROG Zephyrus AMD Advantage laptop.

Will post about this in here when the compilation is done.

The Zephyrus laptop is a strange beast where in the past I was unable to get Xorg going, or a KDE Wayland session - but amdgpu worked fine on it, and Wayfire worked from command-line. Hoping for different results with 15.1-RELEASE and drm-kmod-612...
 
Maxnix said:
Ok, upgraded to 15.1-RELEASE, upgraded all packages too, and now SDDM doesn't want to start the Wayland session; BUT it works flawlessly from command line with the same command used by SDDM:
/usr/local/share/sddm/scripts/wayland-session /usr/local/lib/libexec/plasma-dbus-run-session-if-needed /usr/local/bin/ck-launch-session /usr/local/bin/startplasma-wayland
Will try to see if I messed something up...
Click to expand...
Same here on an old Dell Latitude E7240.

Was installed using packages and ran 15.0-p10 with plasma/wayland fine but after upgrade (pkg) to 15.1 the sddm/wayland login loops back with below log entries.

Running from shell works just fine.

(II) DAEMON: Message received from greeter: Connect
(WW) DAEMON: Signal received: SIGTERM
(WW) HELPER: Signal received: SIGTERM
(II) DAEMON: Greeter stopping...
(II) HELPER: [PAM] Closing session
(II) HELPER: [PAM] Ended.
(WW) DAEMON: Auth: sddm-helper exited with 255
(II) DAEMON: Greeter stopped. SDDM::Auth::HelperExitStatus(255)

/grandpa
 
astyle said:
I'm compiling everything from scratch on a 15.1-RELEASE on my ROG Zephyrus AMD Advantage laptop.

Will post about this in here when the compilation is done.

The Zephyrus laptop is a strange beast where in the past I was unable to get Xorg going, or a KDE Wayland session - but amdgpu worked fine on it, and Wayfire worked from command-line. Hoping for different results with 15.1-RELEASE and drm-kmod-612...
Click to expand...
Update: The Zephyrus did not offer much of an improvement with the latest versions of Ports.

With the scfb driver (which shows up as llvmpipe in KDE, I can launch SDDM, and get an Xorg KDE session going. It looks beautiful, and behaves correctly with themes.

From that same SDDM login screen, I can launch the basic Xorg/TWM, as well, but NOT a KDE Wayland session. BUT: From within Xorg/TWM, I can run
/usr/local/bin/ck-launch-session /usr/local/lib/libexec/plasma-dbus-run-session-if-needed /usr/local/bin/startplasma-wayland, and have a nice KDE Wayland session inside a TWM window! In there, I get to see llvmpipe, and a Wayland session - while all the stuff remains correctly themed.

Installing the amdgpu firmwares for the Zephyrus and enabling them - that gets things awkward.

Can't start SDDM, can't start Xorg, can't start KDE Wayland - but Wayfire starts fine from command-line.

When launching KDE systemsettings app within Wayfire - theming is lost, but GPU settings show up correctly, and it shows Wayland.

Maybe I should try compiling on hardware where GPU drivers behave under Xorg - like my desktop with a Ryzen 7600.

I guess there is one improvement I can report - Konqueror now works under Wayland. It still has a weird crash (which leaves a core dump) if I try to configure it from anywhere but file manager mode.

FWIW, sound on Zephyrus is still not possible to control.

Oh, and one more thing: I compiled my way in trying to use LLVM 22 (devel/llvm22). Not everything compiled with it, I sometimes had to use the CC compiler that is in base (based on llvm19).
 
astyle said:
I'm compiling everything from scratch on a 15.1-RELEASE on my ROG Zephyrus AMD Advantage laptop.

Will post about this in here when the compilation is done.

The Zephyrus laptop is a strange beast where in the past I was unable to get Xorg going, or a KDE Wayland session - but amdgpu worked fine on it, and Wayfire worked from command-line. Hoping for different results with 15.1-RELEASE and drm-kmod-612...
Click to expand...

Doing make -j4 buildkernel KERNCONF=GENERIC here as well after unregistering the pkg kernel since I have some small patches for my DAC to apply. Takes a while to build here at the lower end with laptops from yorn though ...

I've noticed that if I unregister a kernel, patch it and build then it's called -dirty when I do uname which is kind of hilarious...

It looks like wayland/plasma is a bit stubborn when started from sddm. Maybe they're waiting for something that's initialized after user is logged in to be able to run properly since starting from user shell works?

/grandpa
 
I switched to using ly (TUI display manager for X and Wayland) . Gets it done.

For other compositor (labwc , sway) I use a wraper launcher in the wayland-session file:

Code: 
 ~ │ $  cd /usr/local/share/wayland-sessions/
 .../share/wayland-sessions │ $  ls
hyprland.desktop  labwc.desktop     plasma.desktop    sway.desktop
 .../share/wayland-sessions │ $  cat labwc.desktop
[Desktop Entry]
Name=labwc
Comment=A wayland stacking compositor
Exec=labwc_launch
Icon=labwc
Type=Application
DesktopNames=labwc;wlroots
 .../share/wayland-sessions │ $  cat /usr/local/bin/labwc_launch
#!/bin/sh

# Session
export XDG_SESSION_TYPE=wayland
export XDG_SESSION_DESKTOP=labwc
export XDG_CURRENT_DESKTOP=wlroots

# Wayland stuff
export MOZ_ENABLE_WAYLAND=1
export QT_QPA_PLATFORM=wayland
export SDL_VIDEODRIVER=wayland
export _JAVA_AWT_WM_NONREPARENTING=1

exec dbus-run-session labwc "$@"
 
You must log in or register to reply here.
Back
Top