jaeger changed the topic of #crux to: CRUX 3.7 | Homepage: https://crux.nu/ | Ports: https://crux.nu/portdb/ https://crux.ninja/portdb/ | Logs: https://libera.irclog.whitequark.org/crux/
hunter0one has joined #crux
<hunter0one> Hello
<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
<hunter0one> I see, I thought about trying Ly too
<cruxbridge> <tim> and for that you can get a qt oriented greeter, too: https://gitlab.com/marcusbritanicus/QtGreet
<hunter0one> Looks nice, I'll try to build it
<cruxbridge> <tim> of course I meant wayland :p but you understood that
<hunter0one> I got it haha
<jaeger> I haven't seen ctrl-c cause any crashes, though I do experience some oddness with the clipboard
<jaeger> I'm starting my sessions via greetd/tuigreet for what that's worth
<jaeger> I don't know much about SDDM but I assume it uses /usr/share/wayland-sessions/*.desktop the same way as others. I might be wrong.
<jaeger> If you've already got a port for SDDM made I can test it locally
braewoods_ has quit [Remote host closed the connection]
braewoods has joined #crux
braewoods has quit [Read error: Connection reset by peer]
braewoods has joined #crux
serpente has joined #crux
plow has quit [Ping timeout: 244 seconds]
lavaball has joined #crux
<cruxbot> [contrib/3.7]: eza: 0.20.24 -> 0.21.0
<cruxbot> [contrib/3.7]: faudio: 25.03 -> 25.04
<cruxbot> [contrib/3.7]: p5-scalar-list-utils: 1.68 -> 1.69
<cruxbot> [contrib/3.7]: pnpm: 10.7.0 -> 10.7.1
<cruxbot> [contrib/3.7]: podman: 5.4.1 -> 5.4.2
<cruxbot> [contrib/3.7]: python3-aiohttp: 3.11.15 -> 3.11.16
<cruxbot> [contrib/3.7]: python3-multidict: 6.3.0 -> 6.3.1
<cruxbot> [contrib/3.7]: python3-termcolor: 3.0.0 -> 3.0.1
<cruxbot> [contrib/3.7]: qownnotes: 25.3.5 -> 25.4.0
<cruxbridge> <tim> jaeger: https://crux.nu/rpaste/KvXc3rq3.txt I started with one but haven't tried anything with it yet
<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
joacim has joined #crux
<jaeger> Have you tried adding --no-global-shortcuts to the kwin_wayland invocation?
<jaeger> Probably won't help but just curious
<jaeger> And to confirm, I have never seen that crash behavior when run from console or via greetd/tuigreet
ivandi has quit [Quit: WeeChat 4.6.0]
lavaball has quit [Remote host closed the connection]
serpente has left #crux [ERC 5.6 (IRC client for GNU Emacs 29.4)]
tilman has quit [Ping timeout: 272 seconds]
tilman has joined #crux
ivandi has joined #crux
<hunter0one> jaeger: No, I need to try that actually
<hunter0one> I did try to do it with sddm running sddm with kwin_wayland, but it just refused to work altogether
<hunter0one> Not for running the plasma session itself