-
Notifications
You must be signed in to change notification settings - Fork 315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
logs flows into login screen (bug/feature request) #537
Comments
I'm also experiencing this issue, recently it has worsened to the point of covering the entire screen with logs 😕 |
@beastr45 @LennyPhoenix You may be able to redirect the stdout and stderr through the config file (e.g. |
This is an issue with Ly startup, it happens even before launching the Xorg session |
Quoting OP:
I'm not sure if we can do anything about the logs upon startup. Perhaps changing TTY helps? |
Oh my apologies I must have misread 😅 I'll try using a different TTY. If that doesn't work should I file a separate issue? |
Yes, please. |
I am experiencing similar issue. I have set the tty to "9", so it does not conflict with the ttys enabled in a default Void Linux install (tty1-tty6). However, some boot message (seems to be hardware warnings) supposed to be show up in tty1 as usual comes into the ly login screen. |
so ive attached an image with the problem as it is very hard to describe but error messages will flow into the password field of ly display manager after xorg session close. These messages arent only xorg logs and will typically be anything. This Is a MAJOR issue because a lot of distros will have this behavior and its extremely annoying. I believe in order to solve this bug you might want to sanitize the input rendered in the password field based on non system accounts or refresh the password field but it is probably best to find this bug at the root source. If there is a way to circumvent this, the feature resquest is to put it in the documentation right away so its not impossible to find a solution and you have time to fix this bug later. this isnt an issue on ly startup but rather when switching ly sessions which i often do. please dont close this as a duplicate of the guy who had ly in the wrong order on startup because this dosent happen on system startup.
The text was updated successfully, but these errors were encountered: