Denmark
This space intentionally left blank.
Comment by ~kennylevinsen on ~kennylevinsen/seatd
This isn't a bug report.
REPORTED
RESOLVED INVALIDComment by ~kennylevinsen on ~kennylevinsen/greetd
See https://gitlab.freedesktop.org/plymouth/plymouth/-/merge_requests/173 for the (WIP) plymouth improvement required to not need VT shenanigans.
Comment by ~kennylevinsen on ~kennylevinsen/greetd
Plymouth is a tad complicated for my tastes, so I haven't dug much into the way it works on the inside. However, smooth hand-off should be possible if plymouth had used
drmModeCloseFB
to explicitly clean up on exit in a way that retains the KMS state and framebuffer before shutdown...When using the systemd-logind backend of libseat 0.9, sessions can be started in the background. Disabling the VT switch in greetd should then allow you to manually perform the chvt followed by plymouth quit.
[terminal] switch = false vt = 7
Comment by ~kennylevinsen on ~kennylevinsen/seatd
The roc thing sounds like an accidental dependency
And indeed it was: https://gitlab.com/asus-linux/asusctl/-/merge_requests/204
Comment by ~kennylevinsen on ~kennylevinsen/seatd
The roc thing sounds like an accidental dependency as it wouldn’t be able to use the library. I’ll check that later.
What display server are you running? Try to reproduce with nothing running (including greeters/greetd stopped), preferably with the session started directly by logging into an empty VT and just running your display server from the shell there. Then check things like htop for CPU.
busctl --user monitor
andsudo busctl monitor
will tell you if something is happening on dbus, which is how we talk to logind.You could also do a quick test with e.g. sway to see if it’s display server specific.
As mentioned, libseat doesn’t do anything when the system is up and running other than give a heads up if it has to pause because you’re switching VT, but maybe something is getting confused by a change in behavior and burning CPU or hammering the API or something.
Comment by ~kennylevinsen on ~kennylevinsen/seatd
Even if you used seatd, its only job is to open a handful of device files. It does nothing after your display server is started, and has no involvement in using them.
You likely use logind, in which case what you’re using from here is just libseat - that is, we’re not even responsible for opening the files, just for asking to have them opened.
In other words, I can’t see how it could possibly induce “lag”, nor does it have any effect on stuff like “rog-control-center” that cannot use libseat.
For cosmic greeter, if it’s started on a background VT. libseat no longer auto-switches the VT, so either use the current VT or insert a chvt when starting.
Comment by ~kennylevinsen on ~kennylevinsen/seatd
REPORTED
RESOLVED CLOSEDComment by ~kennylevinsen on ~kennylevinsen/seatd
You are likely seeing the effect of 0a86b9785ab22124144c05d572d5dd8b24fcf57e ("logind: Skip session activation"). This change means that libseat will no longer initiate a switch to the logind session (in this case, a VT switch to VT 7), allowing sessions to be started in the background. This was a usecase weston needed.
If you want to run on an inactive tty, you will need to switch to it (maybe
ExecStartPre=chvt 7
?). Alternatively pick a VT that is already active (tty1 for example) - ensure that the existing getty (e.g.,getty@tty1.service
) is in bothConflicts=
andAfter=
of the systemd service to make it go away when sway starts.Ok, submitting by email was a mistake T_T (can't edit that to be more readable apparently ?)
Fixed it for you.
Comment by ~kennylevinsen on ~kennylevinsen/greetd
Closing.
REPORTED
RESOLVED CLOSEDComment by ~kennylevinsen on ~kennylevinsen/wlsunset
wlsunset does not currently have features intended for brightness reduction, only blue light filtering.
Support for running a script on change that could be used for setting brightness has been requested often, I just never got around to it.