Uninstalled the following LightDM LightDM-gtk-greeter LightDm-gtk-setting Light-locker Reinstalled LightDm lightdm-gtk-greeter lightdm-gtk-settings light-locker Did a restart, still black screen Went to setting for Lightdm changed the settings Did a restart, still black screen
Looked at the website you posted, entered in Terminal this command sudo nano /etc/lightdm/lightdm.conf This what was in the editor
General configuration
start-default-seat = True to always start one seat if none are defined in the configuration
greeter-user = User to run greeter as
minimum-display-number = Minimum display number to use for X servers
minimum-vt = First VT to run displays on
lock-memory = True to prevent memory from being paged to disk
user-authority-in-system-dir = True if session authority should be in the system location
guest-account-script = Script to be run to setup guest account
logind-check-graphical = True to on start seats that are marked as graphical by logind
log-directory = Directory to log information to
run-directory = Directory to put running state in
cache-directory = Directory to cache to
sessions-directory = Directory to find sessions
remote-sessions-directory = Directory to find remote sessions
greeters-directory = Directory to find greeters
backup-logs = True to move add a .old suffix to old log files when opening new ones
[LightDM]
start-default-seat=true
greeter-user=lightdm
minimum-display-number=0
minimum-vt=7 # Setting this to a value < 7 implies security issues, see FS#46799
I did a edit so it reads proper now, scroll up and it should read proper The above message I uninstalled the four packages and then reinstalled And then you can read from the top down what I found
Here is a pic of my terminal after the command sudo nano /etc/lightdm/lightdm.conf was entered
Ok i'm back, timezones... So your trying out different display managers? You can check if lightdm spouted any errors by checking its state
$ systemctl status lightdm
But let's keep it simple, forget lightdm for a moment, let's try replacing lightdm with gdm:
1: Install gnome display manager
$ sudo pamac -S gdm
2: Disable (don't stop) lightdm
$ sudo systemctl disable lightdm
(disabled services won't load at boot, 'stop' on the other hand would, well, stop the service instantly, which isn't a problem it just throws you out of the graphical session into a TTY. But ignore that now)
Look thought the posts Nvidia users this line cause the blank screen crash, remove it Option "metamodes" "nvidia-auto-select +0+0 { ForceFullCompositionPipeline = On }"
I am using this command to fix screen tearing, because it fixes the problem and I do not have to fus with compiz or compton So if the fix is to lose that line and get a visible login screen, I will keep it the way it is. compiz or compton are a pain, could not get compton to fix screen tearing and compiz does all this fancy stuff that I do not want, but the compozitor fixes the tearing. If only compiz would just have the compozitor as a stand alone.
Sorry, I have just had a lot of trouble trying to fix screen tearing, and now that it is fixed, I am overly sensitive about it. Will read the post agian. Thanks for the info Post #17 is the one I read
Nvidia users this line cause the blank screen crash, remove it Option "metamodes" "nvidia-auto-select +0+0 { ForceFullCompositionPipeline = On }"
@nikgnomic pointed me in the right direction. The fix to the problem is removing the line. Option "metamodes" "nvidia-auto-select +0+0 { ForceCompositionPipeline = On }" from etc/X11/mhwd.d then edit file nvidia.conf This was my fix for the screen tearing and the problem with my login screen on bootup being Black. I removed the line completely and saved.
The new fix for the screen tearing is. Sessions and Startup Application Autostart Click add and give it a name, discription and add the command. nvidia-settings -assign CurrentMetaMode="nvidia-auto-select +0+0 { ForceFullCompositionPipeline = On }"
Did a restart and the login screen is back and works properly. Screen tearing is fixed as well. Again thanks everyone for helping with the fix, people on this forum are the best, being new to linux and learning new things that for a windows user is hard , like removing some programs and replacing it with something new and different that is part of the OS. Very unnerving. The more I do with linux the more relaxing it gets and the more I think linux is for me.
Awesome good to know for other people aswell. Not sure if this similar issue could popup at other rolling release distro's who offering this new kernel?
Yes, "removing" the file - like I posted over at Manjaro's Forum - is not really a solution but a quick workaround to get things going again without needing to switch TTY's to get a picture (in my case "blindy typing the password to login" didn't work).
Running a slightly "crippled" (tearing) system is better than sitting around waiting for a fix to materialize out of thin air. ;)
Knowing the exact cause of the problem, after the other posts appeared, I did what everyone else did... removing the metamode line from nvidia.conf, re-instating the file, and adding the "nvidia-settings" line to the autostart.
But... if things break right after the reboot after the update and you don't even have any errors in any log it's rather tricky to track down the exact cause. X-|
