-
Notifications
You must be signed in to change notification settings - Fork 10
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
CSS not loading? #8
Comments
Thanks for the video to get an idea on what the problem looks like! Could you please share the following files with me:
Also, what distro are you rocking? Is your other laptop where things are working properly running another distro/init/etc.? What versions of libglib-2.0, libgtk-3 and liblightdm-gobject-1 are installed (maybe you could also compare to the other system?) |
Of course! And, thank you for your prompt attention!
Sure, of course. I'll do this for both the working and "not-working" laptop ("not-working" means "no white text/boxes without restarting Note: The following is pretty lengthy so I'll summarize. Working Laptop (HP Spectre x360 15")
|
@tobiohlala Any idea where I could start in debugging this problem? It's very strange to me. |
Unfortunately, i don't have an idea either. hm. |
Haha, alright. Not a huge deal. I've switched greeters in the interim ( |
I'm having a weird problem and I'm not sure where the responsibility lies. When my computer starts, X spins up, lightdm is spawned, and this greeter starts but I'm unable to see anything that should be in white. I use this greeter on one laptop without problems. I'm trying it on a different laptop and this problem crops up. I can see the cursor blinking and I can authenticate and login. However, graphically I'm "flying blind".
I've recorded a video (on my phone...) that demonstrates this problem. Notably, this problem can be fixed for a single login round by
systemctl restart display-manager.service
. However, logging out after this results in the same problem until the service is restarted again (killing all pre-existing sessions).Any ideas whose responsibility this is and how I might fix it?
Please note that I've already added the below to
lightdm.conf
The text was updated successfully, but these errors were encountered: