[SOLVED] Login-screen freezes logging in to specific account

[jakobn]

When trying to log in to my main account the login-screen freezes.

I then tried to log into the graphic plasma interface as root and that succeeded. So I made a new account from which I am writing this.
I have even made it as a new account, with the same home dir.

It still freezes the login screen

I hope someone can help me out.

[canadaist]

My first thought is that user's home directory is full. Try moving something large out of it, or empty it's trash etc. They will need much more info for answers beyond guesses like mine.

[doktor5000]

What does this mean in particular ?

I have even made it as a new account, with the same home dir.

Also, what login manager do you use currently?

If you want to find out why it is freezing then login as you normally would, and if it freezes then please switch to any tty (e.g. by pressing "Ctrl-Alt-F2") and then as root run

Code: Select all

journalctl -ab -u name_of_displaymanager.service --no-pager

and best post the whole output here. You can also redirect the output to a file and then simply attach the file here later if that's easier.

Code: Select all

journalctl -ab -u name_of_displaymanager.service > /tmp/journal.log

[jakobn]

Thank you very much both for answering!

This morning when I tried to boot i went directly to the GRUB-terminal. Using this https://www.linux.com/learn/how-rescue- ... ub-2-Linux , I got Grub started, but as soon as I started Linux it said that it had to reboot because a new graphic-driver had been installed and then I have only gotten a black screen.

I am only a graphic artist so I have a hard time figuring if this is a GRUB/BIOS problem, something related to my two-screen setup (a wacom-tablet) or some kind of hardware failure on my harddisk. Everything worked and I am not sure if I in all my failed attempts has upset something or it is a material failure.

I appreciate your advice and will try to come up with some answers if I get the chance, but I think I have to buy a new harddisk and try to set up a new system regressing to Mageia 5.1 and then move files from my old harddisk or if that is not possible from my backup.

[doktor5000]

For the issue about the graphics driver, please see the errata: https://wiki.mageia.org/en/Mageia_6_Err ... cs_drivers

[jakobn]

Thanks a lot! I will try o check it out tomorrow. If the Gods og LI & NUX will that might be solvable.

[jakobn]

Hmm. still struggling, but the Grub problem was solved by resetting the bios to default - I have not been able to get into my old /home dir and the journalctl simply said --noentry-- when i tried that.

I have bought a new harddisk and installed Mageia 6 on it and will move my files from the old disk. They are still there. (I had a backup too)

[doktor5000]

Please mark the thread accordingly by editing the topic of the first post and prefix it by [DONE], thanks

[jakobn]

so, now it is doing it again. I can't log in to my personal account.

I can log into root-graphical interface and have created another account that is also able to run plasma. from there I can log into the old account via konsole and even open firefox and doplhin etc.

I am not sure how to get data that can shed light on what is happening, but my guess is that it has something to do with x.

I have a wacom cintic that works bot as input and a secondary screen and it has not worked well under plasma 5 and mageia 6, but did so on Mageia 5 and 5.1

[doktor5000]

I am not sure how to get data that can shed light on what is happening, but my guess is that it has something to do with x.

As mentioned above, you would need to provide some journal logs, e.g. as root via

Code: Select all

journalctl -ab > /tmp/journal.log

and then attach /tmp/journal.log here.

[jakobn]

Sorry I see you already wrote that. Here it is. My main profile, the one that I can not log into is called 'jakob' - the new profile is called 'gaest' - I made a try at logging in to the profile before calling the log.

Thanks for the help.

EDIT: I have also attached the file for: journalctl -ab -u name_of_displaymanager.service - and called it: journal_display.log

[jakobn]

I have kind of solved it now. I gathered that the problem had to be something in the profile's home directory so I went through all the files and folders and renamed them one at a time. logged out and logged in again and rebooted if it was the wrong file. The problem was the .Xauthority file. There was three of them: .Xauthority .Xauthority-I .Xauthority-c . Removing all of them solved the problem. I am not sure why it was triplicated but there you are.

Thank a lot for the responses!

[doktor5000]

This seems to have been reported as https://bugs.mageia.org/show_bug.cgi?id=20835