View Issue Details

IDProjectCategoryView StatusLast Update
0004002Kali LinuxGeneral Bugpublic2017-08-30 08:12
Reporter[email protected] Assigned Torhertzog  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionwon't fix 
Summary0004002: unable to log in as root
Description

I finished installing Kali 2017.1 64 bit. When it rebooted, attempting to log in resulted in the screen turning dark grey and hanging after pressing login. I am able to log in on /dev/tty2, but the gui login is broken. I reinstalled twice. Did apt-get update, upgrade, and dist-upgrade, reconfigured xorg, and everything else I could think of.

However, on a whim, I decided to create another user. I am able to log in as that user without any issues. Any help is appreciated

Attached Files
journalctl.log (189,915 bytes)

Activities

rhertzog

rhertzog

2017-05-09 07:24

administrator   ~0006643

Sorry, we are not reproducing this issue. It's up to you to provide more information... what do you see in logs? (journalctl)

Is there a process that seems to be stuck?

Compare the process tree (ps auxf) when you login as root and when you login as user.

What session are you using? The GNOME/Xorg one or the GNOME/Wayland one?

What display manager are you using?

etc.

brandon9@vt.edu

[email protected]

2017-05-13 16:44

reporter   ~0006679

Sorry for the delay. I just added the journalctl log. It actually does log in eventually, like 3-5 minutes after the gnome login screen.

I am using gnome as the display manager.

I thought it might be caused by realmd. In the journalctl, there is a message in the middle of a bunch of xorg stuff, a message "quitting realmd service after timeout". Then it goes back to more xorg stuff.

Assuming that it was realmd causing the problem, I uninstalled it. This did not fix the problem.

The only thing I see that is suspect is "systemd-logind: failed to take device /dev/ttyS0: No such device"

There is no serial port or device on this pc, so I don't know what that's about.

Thanks for looking into this

rhertzog

rhertzog

2017-08-30 08:12

administrator   ~0007184

I'm sorry, it's unlikely that I can help you out any further. I just can't reproduce this and was not able to figure out the problem from the log I saw.

Issue History

Date Modified Username Field Change
2017-05-08 21:05 [email protected] New Issue
2017-05-09 07:24 rhertzog Assigned To => rhertzog
2017-05-09 07:24 rhertzog Status new => feedback
2017-05-09 07:24 rhertzog Note Added: 0006643
2017-05-13 16:31 [email protected] File Added: journalctl.log
2017-05-13 16:44 [email protected] Note Added: 0006679
2017-05-13 16:44 [email protected] Status feedback => assigned
2017-08-30 08:12 rhertzog Status assigned => closed
2017-08-30 08:12 rhertzog Resolution open => won't fix
2017-08-30 08:12 rhertzog Note Added: 0007184