Testing Plasma 6 (Beta) on Endeavour OS - is this approach any good?

SemLraug · December 9, 2023, 3:37pm

Anyone else on Plasma6/Qt6 seeing this?

At shutdown the process takes longer than normal; there is a countdown of up to 90 seconds at the step:

A stop job is running for User Manager for UID 1000 (xs / 2 min)

my Plasma 5 setup does not have this problem; frankly I don’t know what the message it trying to tell me, and I’m not at all sure if it can be related to Plasma 6.
Any thoughts?

Edit: had a look at logs:

dec 08 17:13:07 aspirea31553 systemd[735]: plasma-kded6.service: Failed to kill control group /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kded6.service, ignoring: Invalid argument
dec 09 16:27:53 aspirea31553 systemd[740]: plasma-kded6.service: Failed to kill control group /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kded6.service, ignoring: Invalid argument

Can this be related?

dbarronoss · December 9, 2023, 4:15pm

I hadn’t noticed that at all during shutdown. However, I’m doing ‘sudo poweroff’ because the shutdown widget is broken (still) for me.
Also I got the new pc in place yesterday, and I’m back on Plasma5 for the moment. Just not had time to do anything with it (and not for several days hence I foresee).

SemLraug · December 9, 2023, 4:17pm

I’ll try that and see if that changes things.

Edit: nope. With sudo poweroff it’s the same. Will have a look over at bugs.kde.org.

Have fun with your new PC.

SemLraug · December 9, 2023, 6:42pm

There’s also fun to be had by reading some of the bug reports:

STEPS TO REPRODUCE

Open: Kate

Open: “Configure Keyboard Shortcuts”

Set: “Next / Previous Item” to “Custom: None”

Close

Open Kate

Open: “Configure Keyboard shortcuts”

OBSERVED RESULT

“Next / Previous Item” reset to “Default”

Me, crying in the shower

EXPECTED RESULT

“Next / Previous Item” set to “None”

Me, typing joyfully and carefree

SemLraug · December 11, 2023, 3:43pm

The KDE-issue was closed, not long after I had reported it, as according to people over at KDE the translation problem with SDDM needed to be resolved by people over at SDDM.
So I reported the problem on the SDDM-github.
But now people at SDDM tell me it is (indeed) a problem with the Plasma-theme.
So I reopened the KDE-issue.

Will wait and see…

SemLraug · December 11, 2023, 3:51pm

This report was marked as “confirmed” today.

dbarronoss · December 12, 2023, 10:25am

Ha, I feel unresolved tension between Plasma and SDDM teams.

SemLraug · December 12, 2023, 11:31am

Indeed. With me in the middle.

SemLraug · December 13, 2023, 6:22pm

Got word that
“A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kded/-/merge_requests/45”

So, I tried to see if I could find out what the devs have been doing to solve this issue.

I think they added or changed a file named plasma-kded6.service.in to the source code, with this content:


[Unit]
Description=KDE Daemon 6
PartOf=graphical-session.target
After=plasma-kcminit.service

[Service]
ExecStart=@KDE_INSTALL_FULL_BINDIR@/kded6
BusName=org.kde.kded6
Slice=session.slice
TimeoutStopSec=5sec

joekamprad · December 13, 2023, 8:21pm

https://wiki.archlinux.org/title/SDDM#Running_under_Wayland

/etc/sddm.conf.d/10-wayland.conf
--
                                
[General]
DisplayServer=wayland

[Wayland]
CompositorCommand=kwin_wayland --drm --no-lockscreen --no-global-shortcuts --locale1

dbarronoss · December 13, 2023, 10:09pm

I assume that’s working, Joe? I couldn’t get it working the other day and just moved the file out. But I’ll happily see what I might have left out from yours if it’s functional.

joekamprad · December 14, 2023, 1:21am

i do not tested this on current plasma but just tried on my kde 6 testing vm where it is not working… weston is working instead of using kwin there

GolDNenex · December 14, 2023, 2:01am

If its your actual config, its probably because you forgot to config the env for the greeter:

[General]
DisplayServer=wayland
GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell

[Wayland]
CompositorCommand=kwin_wayland --drm --no-lockscreen --no-global-shortcuts --locale1

dbarronoss · December 14, 2023, 7:12am

You are correct, I left that out in the most recent test I tried. With the environment set, even the current KDE/sddm (vs unstable) works and there is no X running.

joekamprad · December 14, 2023, 10:03am

i will check

ainz · December 14, 2023, 1:15pm

Yes, now with the greeter environment set it works with both current plasma 5.27.10 and 5.90.0.

/etc/sddm.conf.d/10-wayland.conf
----

[General]
DisplayServer=wayland
GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell

[Wayland]
CompositorCommand=kwin_wayland --drm --no-lockscreen --no-global-shortcuts --locale1 --inputmethod qtvirtualkeyboard

SemLraug · December 14, 2023, 7:56pm

They are looking into the preview problem.

I was asked to run

QT_LOGGING_RULES=kpipewire*.debug=true plasmashell --replace

and report the output.

https://bugs.kde.org/show_bug.cgi?id=477478

SemLraug · December 15, 2023, 9:21am

In 5 days Plasma 6 Beta 2 is going to be released[1].

Where do I look if I’d want to know what apps are going to be updated with that release?

[1] https://community.kde.org/Schedules/Plasma_6

emk2203 · December 15, 2023, 6:09pm

For me, I couldn’t get it to work with the 10-wayland.conf.

For testing purposes, I had a minimal Arch installation working without issues in which I wanted to install Wayland and the most basic components of KDE with SDDM (configured for Wayland) as greeter.

I enabled kde-unstable and installed plasma-desktop, sddm, plasma-nm, plasma-pa, sddm-kcm, pipewire-pulse and pipewire-alsa.

Then added the file /etc/sddm.conf.d/10-wayland.conf per your post:

[General]
DisplayServer=wayland
GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell

[Wayland]
CompositorCommand=kwin_wayland --drm --no-lockscreen --no-global-shortcuts --locale1

layer-shell-qt and kwin were pulled in from kde-unstable during the install. Did sudo systemctl enable --now sddm.service, and as soon as I had the greeter on screen, the keyboard stopped working. I could not type anything there, so no password entry possible, no login possible.

The weird thing is the mouse (Logitech trackball) continued to work. I could select drop down entries all I like. ‘Plasma (Wayland)’ is selected by the way.

I also added dolphin, konsole, kate, systemsettings, spectacle and partitionmanager, all from kde-unstable. I doubt that this plays a role here, though.

So why is the keyboard not working while the mouse still is? Any help appreciated.

To prove that this is a sddm issue, I disabled sddm.service via ssh and could work with the keyboard again. The culprit really seems to be sddm.

Getting rid of the 10-wayland.conf makes the problem go away, I can log in, everything is fine.
And it is this file only. I had the conf files /etc/sddm.conf and /etc/sddm.conf.d/kde_settings.conf copied over from KDE5, no issues with that.

How can I make sure that sddm also uses only wayland and not X?

SemLraug · December 15, 2023, 7:00pm

I’m late in responding to this, nonetheless:

Normally I don’t really use widgets. But as I am test driving Plasma 6 I decided to try out a few and see if that would lead to crashes of some sort.

I found several clock widgets that are working, and a weather widget that not only works but which I even like and will probably keep.

Installing them went well.

As far as I can see there seem to be only 4 extra widgets that can be downloaded.