Kali Linux v2.0 live Installation link not working.

[Sopalajo de Arrierez]

I have downloaded Kali Linux v2.0 32 bits version and I am testing the installer included into the live version.
These are my steps:

1.- Boot from pendrive (Kali v2.0).
2.- Select Live 686 (first option on boot loader).
3.- X Windows starts normally, then I run the "Install Kali" .desktop direct link.
4.- A shell opens and closes itself in a few seconds.

So I try to manually run the installation in a X Windows terminal:

root@kali:~$ more /usr/share/applications/debian-installer-launcher.desktop
[Desktop Entry]
Version=1.0
Name=Install Kali
Comment=Install this system permanently to your hard disk
Exec=su-to-root -X -c /usr/sbin/debian-installer-launcher
Icon=debian-installer-launcher
Type=Application
Categories=Application;System;
StartupNotify=true
Terminal=false

And then I start it forwarding stdin and stderr to two files:

root@kali:~# mkdir temporal 
root@kali:~# cd temporal/
root@kali:~/temporal# su-to-root -X -c /usr/sbin/debian-installer-launcher > output.txt 2>errors.txt

The process stops (nothing on screen), and, after manually stopping it (Ctrl+C):

root@kali:~/temporal# ls -la
total 8
drwxr-xr-x  2 root root  80 Oct  2 21:36 .
drwxr-xr-x 16 root root 340 Oct  2 21:36 ..
-rw-r--r--  1 root root 156 Oct  2 21:37 errors.txt
-rw-r--r--  1 root root 490 Oct  2 21:37 output.txt
root@kali:~/temporal# more errors.txt
mount: mounting /dev/fd0 on /media failed: No such device or address
umount: can't umount /media: Invalid argument
umount: /lib/live/installer: not mounted
root@kali:~/temporal# more output.txt
Stopping network-manager (via systemctl): network-manager.service.
Loading debian-installer...
non-network local connections being added to access control list
cdrom-detect/try-usb=true
boot=live
username=root
hostname=kali
initrd=/live/initrd.img
BOOT_IMAGE=/live/vmlinuz
Starting system log daemon: syslogd, klogd.























Starting network-manager (via systemctl): network-manager.service.
Starting network-manager (via systemctl): network-manager.service.

Note the several empty lines.

Why is this happening and how could I solve it?

Of course, I can start the installation by selecting "Install" or "Graphical Install" on boot loader, but the other method always worked for me on v1.x .

[Sopalajo de Arrierez]

After a while, the installer has started normally.
I am still trying to reproduce the problem, to detect if this is the usual behavior.

By the way, on v1.x versions the installer did not delay so much to open.