New answers tagged gdm
old post but current question. The command sudo service mdm stop would successfully disable the X server in Linux Mint 17.3 temporarily. After install drivers you can do sudo service mdm start.
Ok, silly of me. The problem was my /etc/environment file. From this thread, I learned that the 2nd line: PATH="/usr/local/texlive/2015/bin/x86_64-linux:$PATH" was literally interpreted: the $PATH variable is not expanded (as it usually is in a .bashrc file). Using startx, I had my session opened, so the PATH set in the .zshrc masked the problem. But ...
From a terminal window run: sudo dpkg-reconfigure gdm There you should be able to change from gdm to whatever else you have installed. If you boot to recovery mode as root, you should be able to run the same command after you remount your drive as RW: mount -o remount,rw / dpkg-reconfigure gdm Hope this helps!
This is probably overkill, but ConfigServer Firewall (CSF) and LFD can help to monitor and protect your machines. Sending notifications about failed login attempts is just one of its many features. This should work out of the box, delivering notification email to root. In order to receive mail on a different machine, you'll need a program that can send ...
Accessing logs One with root privileges can make use of the command lastb to see all failed login attempts in the computer, also a much more detailed log file that records failed login attempts in the time span of a week can be found at /var/log/auth.log (no root privileges necessary) and the bad login attempts will be listed like this: MONTH DAY HH:MM:SS ...
the command apt-cache showpkg <package> will tell you the packages "reverse depends" i.e. what other packages - in your configured repositories (not necessarily installed packages) - depend on that package. In the case of gdm there are alot, so I wrote this script to iterate through all of the reverse dependencies to check if any were installed - ...
Some background info: User log-ins are handled by the PAM system (Pluggable Authentication Module) and in this particular case by the pam_tally subsystem (to tally the user accounts). As pam_tally itself will be deprecated, you should use pam_tally2, which comes in two parts: pam_tally2.so being the module that does the authentication itself and which ...
I had the similar issue with Ubuntu desktop 15.10. My issue was related to nvidia graphics card driver. After installing the driver from ppa resolved my issue. I was also stuck with the login loop at the unity desktop at the time of start up. Could you please elaborate regarding your case? I know this answer may not be applicable in your case.
You can reset your unity before trying to login Ctl + Alt + F1 login then try Ctl + Alt + F7 install unity-reset Installing unity-reset in tty: sudo add-apt-repository ppa:freyja-dev/unity-tweak-tool-daily sudo apt-get update sudo apt-get install unity-tweak-tool sudo apt-get install unity-tweak-tool To reset tweak tool unity-tweak-tool --reset-unity ...
Figured it out on my own after two days of trying: The problem was that the .Xauthority file for lightdm got missing somehow. Creating it with touch /var/lib/lightdm/.Xauthority and sudo chown lightdm:lightdm /var/lib/lightdm/.Xauthority fixed the issue.
Top 50 recent answers are included