can't login through x in debian 8.5

[hopefulp]

Hi, I'm novice in linux as superuser.
After installing Debian 8.5, I have used it for a few month and sometimes I rebooted it again.
In the last incidence, to insert new hard disk, I opened and cleaned using compressed air and that's all.
After selecting OS, it goes to login page. Someone says that it already shows nvidia is working and hardware has no problem.
To try to login with correct password, it looks it is bounced in a few second. It returns to login window again.
I can login in other terminal in text mode such as remote terminal or ctrl+alt+F1 or F2.

Some comments are here, but it looks not much helpful.
http://unix.stackexchange.com/questions ... t-password

Is there any remedy or can you suggest any tries?
Or do I need to reinstall nvidia?
I cannot find any similar problem in this site.

[GarryRicketson]

Is there any remedy or can you suggest any tries?

Well, I am not a "superuser", so there is a lot that I do not understand here,
but if it was me with this problem, I would start by giving some details, like,
What this means:

Someone says that it already shows nvidia is working and hardware has no problem.

"It", what shows nvidia is working ? Who says that, ...?
Another mystery, since I am not a "superuser", I can not guess what Windows Manager you are using, or is it a Desktop Environment ?
There are many,...
Or is it the console, you can not log into,..?
If you happen to be using FVWM, and can login as you say:

by hopefulp » I can login in other terminal in text mode such as remote terminal or ctrl+alt+F1 or F2.

Try typing ,

Code: Select all

 startx

or

Code: Select all

startx fvwm

If you are using Gnome, it would be something, else, kde, OpenBox,
Maybe if it is TWM,

Code: Select all

 startx twm

from:http://openbox.org/wiki/Help:Getting_started
Openbox is included in most popular linux distributions. However if the latest version is not available to you through your distribution, you can download it from the download page. Packages are available there for a few distrubutions, as well as the source code which you can compile yourself. For help compiling Openbox, please see our compiling guide.

Once Openbox is installed, running it is quite simple whether you log in through the graphical interface or through a text-based terminal. We'll first talk about the ways to run Openbox from a graphical log in (GDM/KDM), and then show how to run those same sessions from the command line. -----------------
snip, skipped ssome---------------

If you don't use a graphical log in, there are three programs included with Openbox for launching Openbox sessions similar to the three menu options discussed above.

Most likely if you are not using a graphical log in, then you are using startx to begin an X session. In that case you need to run Openbox from your ~/.xinitrc file. Rather than just running openbox however, you should choose from one of the three programs listed below:

openbox-session

Since OpenBox is so common, I am guessing maybe you have it, maybe not,
without knowing what DE or WM you do have, really that is all anybody can do,
is try to guess about it.
You might find some information here:

Code: Select all

 /var/log/Xorg.1.log 

Sorry I couldn't be of more help, I am not a "superuser" so there is a lot that
I don't know.

[hopefulp]

superuser means root user here. I am sorry if this is not common terminology.

someone means someone around me.
Why do I say nvidia is working? The login mode was as normal as it works properly. The screen is clear with moderate resolution. Before I install nvidia, the screen was very dirty with so many dashed lines. But I do not know the difference between gnome, nauveau, and nvidia, exactly. But judging with the quality of screen, he said, nvidia is working it means nvidia driver is working.

I can't get it why you mention windows manager. This is linux.
This should be console. I think I explained enough about this. I said I can log in in remote terminal.

And I am sorry that I cannot try any more. I tried to change file system in /dev/sda5 in windows and it would make a problem in linux file system. It went to another stage and I format the sda. So I cannot try any more even though your suggestion is correct.

I want to remove this thread.

[dibl]

There are two common causes of the dreaded "login loop":

1. Files in the user's directory changed to root ownership. This happens when you "sudo" a GUI package, such as kate or nautilus, and other ways. You need to use "kdesudo" or "gksu", depending on your DE. So using your remote login, examine the "dot" files in the user's home directory, especially .Xauthority, and make sure they are all owned by the user.

2. Full filesystem -- use "df" to make sure you have not gone past 95% full on an ext3 or ext4 filesystem.

[GarryRicketson]

by hopefulp » I can't get it why you mention windows manager. This is linux.

There are many types of Window Managers used on linux systems.
Also Desktop Environments, (DE)

by hopefulp » superuser means root user here. I am sorry if this is not common terminology

Yes it is a very common term, we get a lot of them here. I am not a "super user", I do
not usually administer my system as root, and do not use "sudo", etc. like the
"super users" do,...I only log in as root , if and when it is necessary.

Post by dibl »This happens when you "sudo" a GUI package, such as kate or nautilus, and other ways. You need to use "kdesudo" or "gksu", depending on your DE.

by hopefulp »It went to another stage and I format the sda

I guess it does not matter now, but note what "dibl" says, in the previous post,
and "depending on your DE",...This is what would have been needed to know
more about what to do to fix the problem. There are many different Desktop Environments, and Window Managers used in the various linux distros, it is often
necessary to know which one is being used , to trouble shoot the problem.
After you re-install the new system, I suggest reading and learning some
basic things about administering and using a Linux system, particularly Debian
if that is the distro you choose, other wise specify about the distro you use,
including the Desktop Environment, or Window Manager,...
Do not be a "super user",...they usually wreck the system. After you learn enough, you can login as root , when need be, or you can use "sudo", in the way it is intended.
--------- edited, some spelling and to clarify--------
When I say "do not be a "super user", I mean do not all ways operate as
"su" or as "super user",...use your system as a normal user.
If and when administrative tasks need to be done , and only if absolutely
necessary, then use "su" or sudo, "gksudo", etc,...Only use these if and
when required.
This is a very common mistake, with beginners, or "novice" users,
a long time ago I had similar problems, and found I could not login to my DE,
in this case it was Gnome, and on Ubuntu,..the problem started after I had
started using "sudo", something new to me.
Any way in a nut shell , after becoming "superuser", in a very short time, I could
no longer access the DE as a normal user,and things went from bad to worse,
so I re-installed and started over,.. no more "super user" for me.
The computer does tell me, if and when "root" needs to do the job,....when
I am told I must be root, I use "su" and login as root,..after reading any manual
or documentation needed to understand what I do as root.
For example , if I do not understand what a certain command will do, options,
etc,....then it is important to read the manual, first. Root can do anything, he can
repair the system, or crash/wreck it,..."format" it, what ever,...any way there
are plenty of topics on that. Just wanted to clarify.
====== end edit =======

by hopefulp »I want to remove this thread.

Why ?, Others might learn something from reading it. The administrators
do not usually do that, delete or remove threads, but you can request it:
HOWTO contact forum moderators/admins
Any way, I hope things go better on your new installation, if you are not sure
about something, it is wiseto ask first, and feel free to ask here before you try it.

[hopefulp]

Hi dibi and Garry,

Thanks for your comments.
At last I found the mistake.

After I installed debian 8.5 again, it worked normally. I can login to x-window.
When I copy the previous home directory to new home directory, the same problem happens.
It came from the two initial files of .profile and .bashrc.
Before, I modified those files to set initial environment and in those process I removed all the commented line. It look it could make a problem.
With the default initial files, I can login to x-window.

In my opinion, startx and etc might have worked if I tried before I had made mess up by touching sda5-ext4 using windows 7.

Thank you for long explanation.