Kali 2016.2 freeze out for about 20 seconds after login and show up a blank screen.

1 Attachment(s)

Greetings all,

I have recently installed Kali linux 2016.2 on my pc and updated the entire system with this commands:

apt-get update && apt-get upgrade -y && apt-get dist-upgrade -y

Everything goes well.

All but one issue:
When i login my system after boot or screen look, it takes a lot of time to show up the desktop.
I see a blank screen for 20-30 seconds then the desktop appears and i can start work normally.
Why it takes so long time to login?
Anyone know this issue?

OS Information:
uid=0(root) gid=0(root) groups=0(root)
Linux galactus 4.8.0-kali2-amd64 #1 SMP Debian 4.8.15-1kali1 (2016-12-23) x86_64 GNU/Linux
No LSB modules are available.
Distributor ID: Kali
Description: Kali GNU/Linux Rolling
Release: kali-rolling
Codename: kali-rolling
I have also installed the NVIDIA Drivers and fixed my audio device.

I see some errors (after a reboot) in /var/log/auth.log and in /var/log/syslog and in the gnome-session log but i don't know if this is relevant.

Code:

cat /var/log/auth.log Jan 6 13:49:26 galactus systemd-logind[441]: System is rebooting. Jan 6 13:49:39 galactus systemd-logind[458]: New seat seat0. Jan 6 13:49:39 galactus systemd-logind[458]: Watching system buttons on /dev/input/event5 (Power Button) Jan 6 13:49:39 galactus systemd-logind[458]: Watching system buttons on /dev/input/event4 (Power Button) Jan 6 13:49:39 galactus systemd-logind[458]: Watching system buttons on /dev/input/event7 (Eee PC WMI hotkeys) Jan 6 13:49:40 galactus gdm-launch-environment]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm by (uid=0) Jan 6 13:49:40 galactus systemd-logind[458]: New session c1 of user Debian-gdm. Jan 6 13:49:40 galactus systemd: pam_unix(systemd-user:session): session opened for user Debian-gdm by (uid=0) Jan 6 13:49:40 galactus gdm-launch-environment]: pam_unix(gdm-launch-environment:session): session closed for user Debian-gdm Jan 6 13:49:40 galactus systemd-logind[458]: Removed session c1. Jan 6 13:49:41 galactus systemd: pam_unix(systemd-user:session): session closed for user Debian-gdm Jan 6 13:49:41 galactus gdm-launch-environment]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm by (uid=0) Jan 6 13:49:41 galactus systemd-logind[458]: New session c2 of user Debian-gdm. Jan 6 13:49:41 galactus systemd: pam_unix(systemd-user:session): session opened for user Debian-gdm by (uid=0) Jan 6 13:49:48 galactus polkitd(authority=local): Registered Authentication Agent for unix-session:c2 (system bus name :1.23 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) Jan 6 13:49:48 galactus realmd[1026]: Loaded settings from: /usr/lib/realmd/realmd-defaults.conf /usr/lib/realmd/realmd-distro.conf Jan 6 13:49:48 galactus realmd[1026]: holding daemon: startup Jan 6 13:49:48 galactus realmd[1026]: starting service Jan 6 13:49:48 galactus realmd[1026]: connected to bus Jan 6 13:49:48 galactus realmd[1026]: released daemon: startup Jan 6 13:49:48 galactus realmd[1026]: claimed name on bus: org.freedesktop.realmd Jan 6 13:49:56 galactus gdm-password]: pam_unix(gdm-password:session): session opened for user root by (uid=0) Jan 6 13:49:56 galactus systemd-logind[458]: New session 3 of user root. Jan 6 13:49:56 galactus systemd: pam_unix(systemd-user:session): session opened for user root by (uid=0) Jan 6 13:50:02 galactus polkitd(authority=local): Registered Authentication Agent for unix-session:3 (system bus name :1.54 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) Jan 6 13:50:49 galactus realmd[1026]: quitting realmd service after timeout Jan 6 13:50:49 galactus realmd[1026]: stopping service Jan 6 13:55:01 galactus CRON[2025]: pam_unix(cron:session): session opened for user root by (uid=0) Jan 6 13:55:01 galactus CRON[2025]: pam_unix(cron:session): session closed for user root

Here a partial log from /var/log/syslog

Code:

cat /var/log/syslog 13:49:48 galactus dbus[468]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' Jan 6 13:49:48 galactus systemd[1]: Starting Locale Service... Jan 6 13:49:48 galactus gnome-shell[967]: JS LOG: Failed to launch ibus-daemon: Failed to execute child process "ibus-daemon" (No such file or directory) Jan 6 13:49:48 galactus dbus[468]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' Jan 6 13:49:48 galactus systemd[1]: Starting Location Lookup Service... Jan 6 13:49:48 galactus dbus[468]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' Jan 6 13:49:48 galactus systemd[1]: Starting PackageKit Daemon... Jan 6 13:49:48 galactus dbus[468]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' Jan 6 13:49:48 galactus systemd[1]: Starting WPA supplicant... Jan 6 13:49:48 galactus PackageKit: daemon start ... ... Jan 6 13:50:04 galactus dropbox.desktop[1454]: Starting Dropbox...Dropbox isn't running! Jan 6 13:50:04 galactus dropbox.desktop[1454]: Done! Jan 6 13:50:04 galactus systemd[1]: Started Daemon for generating UUIDs. Jan 6 13:50:07 galactus telepathy-haze[1393]: Exiting Jan 6 13:50:29 galactus gnome-shell[1337]: Attempting to add actor of type 'StBoxLayout' to a container of type 'ShellGenericContainer', but the actor has already a parent of type 'ShellGenericContainer'. Jan 6 13:50:29 galactus gnome-shell[1337]: Attempting to add actor of type 'StScrollView' to a container of type 'StBoxLayout', but the actor has already a parent of type 'StBoxLayout'. Jan 6 13:50:29 galactus gnome-shell[1337]: JS LOG: loading user theme: /usr/share//themes/Kali-X/gnome-shell/gnome-shell.css

I can see a long time after the login and the start of telepathy-haze.

All complete log as attachement below

This is my gnome-session log, but i think it's not relevant:

Code:

cat /var/log/messages | grep gnome-session Jan 6 13:49:18 galactus gnome-session[2858]: gnome-session-binary[2858]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Jan 6 13:49:18 galactus gnome-session[2858]: gnome-session-binary[2858]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Jan 6 13:49:18 galactus gnome-session[2858]: gnome-session-binary[2858]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Jan 6 13:49:18 galactus gnome-session[2858]: gnome-session-binary[2858]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Jan 6 13:49:18 galactus gnome-session[2858]: gnome-session-binary[2858]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Jan 6 13:49:26 galactus gnome-session[2858]: gnome-session-binary[2858]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Jan 6 13:49:26 galactus gnome-session[2858]: gnome-session-binary[2858]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Jan 6 13:49:26 galactus gnome-session[2858]: gnome-session-binary[2858]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Jan 6 13:49:26 galactus gnome-session[2858]: gnome-session-binary[2858]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Jan 6 13:49:26 galactus gnome-session[2858]: gnome-session-binary[2858]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Jan 6 13:49:26 galactus gnome-session[758]: gnome-session-binary[758]: WARNING: Lost name on bus: org.gnome.SessionManager Jan 6 13:49:40 galactus gnome-session[819]: gnome-session-binary[819]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Jan 6 13:49:48 galactus gnome-session-binary[947]: Entering running state Jan 6 13:50:02 galactus gnome-session-binary[1235]: Entering running state

Thanks for help,
Best regards Adrian

I think dmesg log also can be usefull.

I am not professional, but here is my answer: I think that slow boot has something to do with hardware and not software, although "heavy Kali" can be slow except if you bought 5000 eur PC.
so, slow boot can be related to your HDD write/read speed (22MB/s and 8MB/s), your processor, RAM, etc.
maybe you use Pentium 4 from 1998 :)

I installed Kali on USB device and it was also slow, just not so much slow like in your case, I think it is related to above mentioned things + "heavy kali with million software", although I use computers with 8GB RAM and i3 CPU 3.6GHz.
I never read if there is "minimum required hardware" to install Kali.