Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am running Linux Mint, after attempting to install Serviio and FFmpeg, I rebooted my PC to a login screen. Before installing this new software I booted directly into Mint without having to enter my username/password. After entered my username and then my password the login timer counts down and then the username screen returns followed by the password screen. This loop repeats itself. Username/Password are correct.
Just to troubleshoot, can you log into a console without starting X? CTL, ALT F1 should take you to a console.
Is it possible that the X server or display manager is crashing after you enter your credentials? You didn't mention which desktop you use in Mint. Knowing something about your hardware, especially graphics card might be helpful. Are you using a native graphics driver, or a proprietary driver?
Just a privacy and security thought. Automatic login without having to enter a password is never a good idea.
I'll ask the stupid but needed question. Cap lock issue?
Test keyboard maybe from single user?
There was a deal that has been around on ubuntu hence mint for a very long time where some machines have this problem but it is usually you can never log in.
If single user works then you can try to change password from there.
Since I just posted an enquiry about a laptop which might end up with the same/similar Intel graphics issue (in the Laptops-&-Notebooks section) I am keen to understand what you mean by listing directories. I don't understand. Is that some kind of instruction, or fix? If you can expand that a little and explain the concept and "fix" I would appreciate it.
As an additional comment... I have encountered a couple of distros that did the "endless cycling after login", and a couple (most notably OpenSUSE13.2) that did the "endless cycling upon display of the (SLIM?) login box" (ie cycling the login without letting me log in at all). As a "newbie" I could never solve that.
[My graphics card was a SiS-6326 which I now suspect could have been the fundamental cause of the problems I mentioned - and NOT any particular distros.]
I mention this second point only because it might be related to discussion herein. However I am looking forward to your explanation of the laptop Intel-graphics concept (and "fix").
Hi. Do you check /tmp directory permissions? Sometimes i had change the 4777 to 0777 , then users can't open a temporary session under /tmp.
Or user directory /home/user-directory can change permissions from 770 to 550.
Hi. Do you check /tmp directory permissions? Sometimes i had change the 4777 to 0777 , then users can't open a temporary session under /tmp.
Or user directory /home/user-directory can change permissions from 770 to 550.
I hope this will be usefull.
Have a nice weekend.
777 is a very poor mode for /tmp. Anyone can delete any files, anyone can alter others files (by renaming/deleting and substituting their own).
VERY poor security. That is why the sticky bit is set on /tmp (4777). No one but root or the owner of the file may do things to the entry unless the user grants access to the contents.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.