<hunter0one>
I am not a CRUX user, I am a package maintainer for another distribution but I have a question for the KDE 6 ports maintainer (the email address did not point anywhere) or anyone else who has used SDDM and Wayland sessions.
<hunter0one>
On CRUX of course
hunter0one has quit [Quit: Konversation terminated!]
jason123onirc has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
jason123onirc has joined #crux
<jaeger>
hunter0one: I have not used sddm and wayland but feel free to ask
<cruxbridge>
<tim> fwiw I don't use sddm either
<cruxbot>
[opt/3.7]: nodejs: 23.10.0 -> 23.11.0
<cruxbot>
[opt/3.7]: simdutf: 6.4.0 -> 6.4.1
<cruxbot>
[contrib/3.7]: bluez: 5.80 -> 5.81
<cruxbridge>
<jloc0> There is no sddm port for crux no?
<cruxbridge>
<jloc0> I keep meaning to make myself one, but busy enough currently heh
<cruxbridge>
<tim> it does not look like it, I don't have one. I use greetd
lavaball has joined #crux
<cruxbot>
[core/3.7]: gawk: updated to version 5.3.2
<cruxbot>
[core/3.7]: curl: updated to version 8.13.0
joacim has quit [Ping timeout: 245 seconds]
lavaball has quit [Remote host closed the connection]
hunter0one has joined #crux
<hunter0one>
jaeger: Actually this happens with any Wayland compositor such as labwc but on PCLOS launching labwc, KDE Wayland, etc. from SDDM will cause the session to have shell-like behavior, most notably Ctrl + C will crash the entire session rather than copying to the clipboard (in KDE's case)
<hunter0one>
I was just wondering because I see that most things from Plasma have been ported, including the sddm KCM, except sddm itself, as if maybe they experienced the same problem?
<hunter0one>
This happens with all versions of SDDM newer than 0.18
<hunter0one>
Its rare to find other distributions with a similar setup to ours (ConsoleKit2, seatd) which may exhibit the same behavior
<cruxbridge>
<tim> ah
<cruxbridge>
<tim> I might try sddm if it helps you, no idea if many ports are missing for it
tilman has quit [Ping timeout: 260 seconds]
<hunter0one>
Currently we just run Plasma from the tty, like ck-launch-session dbus-run-session startplasma-wayland, and then it works properly
<hunter0one>
Who makes the Plasma 6 port repo?
tilman has joined #crux
<cruxbridge>
<tim> jaeger created it
<cruxbridge>
<tim> i push most of the updates
<hunter0one>
Oh ok
<hunter0one>
So sddm just isnt included because theres no interest?
<cruxbridge>
<tim> exactly
<hunter0one>
It doesnt bother me or other PCLOS devs to just run Plasma from the tty, but PCLOS is more beginner-oriented, so having a display manager that works with both X and Wayland sessions properly would be nice
<hunter0one>
It seems Venom Linux has latest sddm
<cruxbridge>
<tim> fwiw greetd should support X11 and greetd
<cruxbridge>
<tim> certainly needs a few more touches, but the problems described by hunter0one sure sound weird.. haven't experienced that either, at least I can't remember
<jaeger>
I'll give it a look
plow has joined #crux
<hunter0one>
jaeger: If you run the plasma session from a tty or maybe other display managers it wont exhibit the behavior, at least not in our case
<hunter0one>
It seems to be a problem with how sddm launches sessions, but they said they didnt see how it could be related to SDDM :p
<hunter0one>
Oh so greetd works, I'll try greetd ASAP
<hunter0one>
jaeger: Yes, it looks in /usr/share/wayland-session for .desktop files to launch
<hunter0one>
sessions*
<hunter0one>
tl;dr plasma wayland works fine if ran from the console, but if it or any other wayland compositor is launched from SDDM, it will crash when ctrl + C is pressed as if its running as a shell program
<hunter0one>
seems to be specific to sddm on distributions that do not use elogind, but freebsd doesnt seem to have this behavior either