Hi guyz,
I can’t login to my Leap anymore.
The last thing i did was to change my display manager from SDDM to KDM.
I was able to log into my system once, and after that, it hangs in the loading part:
http://i65.tinypic.com/1fa6t.jpg
No matter how much time i wait, it doesn’t go any further.
I also reverted my change and set display manager to SDDM again, as well as removing .kde4 Folder for resetting my customizing, but none of them solved the problem and I’m only able to log in with IceWM.
.kde4 is no longer used all configs are in ~/.config
Removing ~/.kde4 is useless, you’re running Plasma5, which has it’s config files in ~/.config. But, do not remove ~/.config since you will loose a lot of other configs too. Some other settings, f.e. kscreen’s now live in ~/.local/share, but the same goes for that folder, do no remove it.
Since KDM is not installed by default, you made changes to the system. Please tell us what else you changed,
To test if the system integrity is still OK, create a new user, login as that user and see if the problem exists for that user. If not, the culprit must be in your current user’s homedir.
Thanks gogalthorp for your reply and note.
Thanks Knurpht for your reply and resolution,
I created another user, and with this user I’m able to log into Plasma5, though it takes about 2~3 minutes to login and it sounds weird to me 
Actually i don’t remember any other changes, and think I just changed my display manager, (Maybe I had changed my window decoration or my theme as well)
Regards
What do you mean sounds weird?? Sounds from your machine? This can indicate hard drive going bad. Run smartctl to see if it is damaged
Cuz with my system (120 SSD + 8GB Ram) it used to take only some seconds.
Also the result of smartctl for a short test is:
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
When hard drives start to fail they tick because they try to read data until the checksums agree this can stall the machine. I suspect maybe you have added none leap repos this of course can cause major problems. So do you get a login screen? and you can not log into the GUI?? in that case try another desktop.
Don’t make use guess please say what you see since we can not see over your shoulder. Can’t log in can mean many things.
I read the same, but the OP talks about an SSD ( and if SSD’s tick …
). To me “sounds” should be read as “seems”.
A first login of a new user taking some time doesn’t mean anything, an aweful lot is going on on a first login. Check whether a second login ( where all the config files etc. have already been writen ) is as slow as the first.
Another thing to consider is kscreen: Remove the entries in ~/.local/share/kscreen whilst not logged in on the desktop. Then login, logout, login and report if things have improved.
Yet another thing to consider is the theme applied to the desktop. To remove all plasma5’s config files do
rm -rf ~/.config/plasm*
whilst not being logged in on the desktop. This puts the Plasma5 configs back to default.
No No No!
By “It sounds” I wanted to say “It seems”.
I wanted to say it’s very strange that it takes such a long time to log in.
I do see login screen, but i cannot log into with my original account, as it hangs if i try, but i’m able to login to IceWM with my original account.
Yes, I didn’t mean the first time, i mean it takes long time every time i try it.
Is there another way instead of removing them?
As i don’t want to remove all changes,
If for example i can remove only installed desktop themes, it may solve the problem.
Well you can remove individual config files but that also means you need to know which to remove ie which causes the problem.
Also check to see if there are any files with root ownership in your ~/ home directory. Note maybe hidden files ie start with a period. Do you ever log into aGUI as root?? this can cause this type of problem
also rather then remove you could just rename the directories and then move configs back one at a time to see what breaks but then it is faster and easier to just set things up again.
Hi again dear Knurpht and Gogalthorp and thanks for your replies and resolutions,
Removing Kscreen didn’t solve the problem, then I tried your second resolution, thus I backed up and remove those files and noticed that I’m able to log in.
Then I took your recommendation and found out that the source of the problem seems to be plasmashellrc file, as only removing this file let me be able to log in again successfully.
Maybe [PlasmaRunnerManager] section was the source of the problem, i dunno.
Btw, I really appreciate your great help and support dear Knurpht and Gogalthorp. 
Just one thing,
Now when i want to hibernate my system, it requires root password,
Is there something with PolicyKit, as the search results about this problem are mostly pointing to PolicyKit.
Thanks
Are your updates up to date? I believe there was a problem with polkit a while back but updates should fix that.
Thanks gogalthorp,
you’re right.
I updated my system and that error vanished