Oh no! Something went wrong! While starting the system after installing Kali Linux

47,746

Solution 1

Quite simple. 8GB of disk isn't enough for this version of Kali Linux. Use VBoxManage to resize the virtual disk, and GParted to expand the filesystem.

Solution 2

My situation was different. I was installing on a new laptop. My configured VM had plenty of memory and disk yet I still had this issue.

What I eventually found was that since it was a new laptop the bios configuration did not have virtualization turned on.

Once I enabled this in the bios my VMs worked as expected.

Solution 3

As I was attempting to install Kali 2.0 on VMware I was running into the same issue. Startx was not found, and even upon manually installing it would not work. The one thing that worked for me was to enable virtualization in bios. This is usually a problem that occurs with VirtualBox for me, but this time it resolves the issue with Kali 2.0 on VMware.

Solution 4

i had some problems with gnome-shell so i decided to install xfce4

apt-get install kali-defaults kali-root-login desktop-base xfce4 xfce4-places-plugin xfce4-goodies

then

update-alternatives --config x-session-manager

Solution 5

I had a similar issue with VB 5.2.6 on macOS High Sierra. I had to disable the 3D acceleration to get it to boot fully to user login screen. This only happend after installing the extension pack on my Debian guest.

VB 5.2.4 worked fine (with 3D acceleration enabled).

Downgrading to VB 5.2.4, installing the 5.2.4 extensions, and reenabling 3D acceleration fixed the issue for me.

Share:
47,746

Related videos on Youtube

DJMcMayhem
Author by

DJMcMayhem

I never trust someone who's more excited about success than about doing the thing they want to be successful at. --xkcd Off of stack Exchange, I enjoy making music and listening to music 24/7. I also like rock climbing and video games. On Stack Exchange, I greatly enjoy using the worst possible language for the task. That's why I've written two different languages: V, a golfing variant of vim that's only good at manipulating strings, but can do a bunch of other stuff if you have the patience. Brain-flak, a turing tarpit where simple tasks are obscenely difficult, and the only valid code is balanced brackets. If you ever need me for something, feel free to ping me in The Nineteenth Byte, I'm basically in that room constantly. Or you can email me at DJMcMayhem[at]gmail[dot]com. :w !sudo tee % My FAQ list: https://codegolf.meta.stackexchange.com/questions/13944/how-does-this-site-work Comment template: Hello, and welcome to PPCG! On this site, users participate in programming challenges and competitions such as [tag:code-golf], but we aren't a resource to help with general programming questions. You *might* be able to get help on [Stack Overflow](https://stackoverflow.com/help/on-topic), but make sure to read through the help center to get an idea for what kind of questions they take. Thanks! We did not invent The Algorithm. The algorithm is banned in 47 countries. The algorithm is on-topic on 87 percent of SE sites. The Algorithm consistently finds Jon Skeet. The algorithm cannot be detected by regex. This is not the algorithm. This is close.

Updated on September 18, 2022

Comments

  • DJMcMayhem
    DJMcMayhem over 1 year

    I am trying to install a virtual machine running Kali (Formerly backtrack) 1.0.7 In 64 bit. My host machine is a 64 bit MacBook pro running 10.7.5. I am using Oracle VirtualBox version 4.3.12. The install goes perfectly, but after installing it, I get an error when I try to boot. Here is a screen shot.

    I hit New virtual machine, selected 64 bit debian and created an 8gig dynamically allocated VDI. In settings, I have selected the correct ISO, and checked PAE/NX under processor. After doing all of this, the live mode works perfectly. Installing, I do everything the default way, and everything goes perfectly. After I finish the installation, it asks me if I want to boot. When I do, I get the above error.

    I have done lots of research trying to figure it out, but none of the advice I can find online has helped. Here is everything that someone has said will fix that didn't work for me.

    "Enable PAE/NX in settings"

    Made absolutely no difference.

    "When you get that error, press Ctl+Alt+F1, this will take you to the terminal tty1, now login as root:

    login: root password: "your password"..

    Once as root, start the X's: startx

    You will get your desktop...This might be a xauthority issue or dbus issue when loadind, perhaps a daemon.

    Try this first and if it works, try doing this: dpkg-reconfigure gnome-shell, then reboot."

    command: startx not found.
    

    Needless to say it didn't bring me to the desktop.

    I tried fixing the problem of the startx command not being found by reading through this forum.

    I will refer to what they said I should try.

    try typing /usr/X11R6/bin/startx

    -bash: /usr/X11R6/bin/startx no such file or directory
    

    I tried all of the following commands:

    apt-get update
    apt-get install x-windows-system
    apt-get install x-window-system
    

    All 3 resulted in this

    Bus errorackage lists... 1%
    
    • Admin
      Admin almost 10 years
      Please indicate which VM+version you're using (virtualbox I think). When you created the VM and gave it a name, did you select Debian 64-bit or similar in the last drop down? Sometimes it will make a difference. How did the install go? How come the install seems incomplete and the package manager is in such a state? Have you modified repository sources manually? Usually when it works it doesn't have such issues.
  • DJMcMayhem
    DJMcMayhem almost 10 years
    Yep, that was the problem, thankyou!
  • αғsнιη
    αғsнιη over 9 years
    @David could you please update your answer with more details.
  • DJMcMayhem
    DJMcMayhem over 9 years
    @KasiyA, I didn't end up using VBoxManage. Instead I started from scratch and allocated more memory in the VDI. I hope that helps!
  • user150344
    user150344 over 8 years
    nope, for some reason i had problems with it, so i switched to xfce4 instead
  • Admin
    Admin almost 2 years
    This will not increase the allocated size of the virtual disk (which is the issue that the user in the question has).