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
Blank Screen Red Hat Enterprise Linux 8.2 root user #6077
Comments
the user column hasnt always been perfect when detecting if a user is logged in or not, as for the desktop being a blank screen, you need to check what GUI the linux desktop is using |
Hi @si458 , FYI, Iam able to take access when user is logged in with non-root login. The problem exists with only root user GUI. |
Ah right, so u can see a login window, but if u then login as root, u don't see a desktop and if you login with non root, u can see a desktop, that is a weird bug? |
If u login as root to the desktop (use physical access or another remote control tool), You could be having the same issue as this user where it's switch bk to wayland from x11 when u login as root |
Hi @si458, Kindly find the screen shot of the commands and output with logged in root user. |
ok ive created a redhat enterprise 8.2 VM and its the same thing, how weird!? have you tried updating your OS to a newer version like 8.9? (random i know) |
Hi @si458 , Kindly find my observation below:
we have 250+ 8.2 versions in our local and we cannot upgrade it for now. can you please us know once fixed |
Dear @Ylianst ,
We are currently facing two Linux OS issues in our environment. Kindly find the below points:
Expected behavior
When root user is logged in then logged in username must show in Mesh Portal and Desktop feature must work as expected.
Kindly Find the screenshots attached.
In the above image we can see that user column is empty when root user is logged in but when standard user logs in then only username is visible.
Server Software (please complete the following information):
Remote Device (please complete the following information):
Kindly help me to resolve this at the earliest.
The text was updated successfully, but these errors were encountered: