Even with WaylandEnable=false gdm3 and lightdm only load sometimes
I am happy to use either gdm3 or lightdm, but neither are stable on my Ubuntu 18.04 system, they will work for either one or several boots after I take corrective action, but inevitably this results in the greeter not loading - the last few times (at least) I noticed this was immediately after I did a sudo apt update. The graphics card on my Intel Core i5 system is an Nvidia GTX 970, and I manually installed nvidia-driver-415 using apt when I could not load a greeter as soon as I had installed.
Searching here and elsewhere, I have tried many things to resolve this, which I will outline below. If you know something else I can try - to get either greeter stable - please let me know. gdm3 gdm3: Installed: 3.28.3-0ubuntu18.04.3 Even with WaylandEnable=false uncommented in /etc/gdm3/custom.conf, I could never login, instead of the greeter I would see either a black screen or graphic distortion like a black screen with some pink lines across the top, and I am only able to login setting nomodeset. https://i.imgur.com/iTB2YFW.jpg With gd3 not working, I tried lightdm, and on encountering similar issues switched back to gdm3 again: Code:
sudo apt-get install gdm3 https://i.stack.imgur.com/l1Qv4.jpg Another time with gdm3 I saw the following output instead of the greeter: https://i.stack.imgur.com/HFgsm.jpg https://i.stack.imgur.com/V7j78.jpg lightdm lightdm: Installed: 1.26.0-0ubuntu1 When I use lightdm instead, and the greeter does not load, I see a flashing black screen with a single white underscore top left. I can never get to a TTY using ctrl + alt + f3/f4/f5, REISUB does not work, so I hard rebooted, the greeter loads with nomodeset, and from there without logging in I switch to a TTY and I have tried what I outline below. Sometimes if I just reboot again without nomodeset the greeter will just load properly, without my changing anything. https://i.imgur.com/WKaFarS.jpg Observing these permissions: Code:
-rw------- 1 dusf dusf 56 Jan 7 17:38 .Xauthority Code:
sudo chown dusf:dusf .Xauthority Code:
sudo dpkg-reconfigure lightdm Code:
_=/usr/bin/dbus-update-activation-environment Code:
sudo mv .Xauthority .Xauthority.bak Code:
sudo apt-get purge lightdmsudo apt-get install --reinstall lightdm Code:
sudo apt upgradesudo apt purge lightdm Code:
sudo apt update /var/log/lightdm/lightdm.log /var/log/kern.log .xsession-errors I read adding an xrandr line to some files may be the next step, but the actual lines seem to be system specific, and their are recommendations on adding them to different files. How can I begin to resolve the issue, either with gdm3 or lightdm please? |
I think the the problem is:
You don't know what you are doing, and the advise you apparently follow comes from somebody like you. As such, you should just let the more knowledgeable Ubuntu design team set up your system. In the example below you will find the owner is dusf, then you changed the owner to dusf: Quote:
Quote:
So all in all, if you want to learn how to fix broken Ubuntu, just keep doing what you're doing. If you want a stable Ubuntu and rather waste your time doing something else other than wasting time fixing your "self destructed Ubuntu", just let the Ubuntu design team set up your system properly. |
All times are GMT -5. The time now is 04:47 AM. |