Oh no! Something went wrong! While starting the system after installing Kali Linux
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%
system-installation virtualbox kali-linux gdm
edited Feb 28 at 20:00
Glorfindel
3171511
asked Jun 27 '14 at 3:29
DJMcMayhemDJMcMayhem
6281412
add a comment |
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%
system-installation virtualbox kali-linux gdm
edited Feb 28 at 20:00
Glorfindel
3171511
asked Jun 27 '14 at 3:29
DJMcMayhemDJMcMayhem
6281412
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.
– user44370
Jun 27 '14 at 5:22
add a comment |
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%
system-installation virtualbox kali-linux gdm
edited Feb 28 at 20:00
Glorfindel
3171511
asked Jun 27 '14 at 3:29
DJMcMayhemDJMcMayhem
6281412
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%
system-installation virtualbox kali-linux gdm
system-installation virtualbox kali-linux gdm
edited Feb 28 at 20:00
Glorfindel
3171511
asked Jun 27 '14 at 3:29
DJMcMayhemDJMcMayhem
6281412
edited Feb 28 at 20:00
Glorfindel
3171511
asked Jun 27 '14 at 3:29
DJMcMayhemDJMcMayhem
6281412
edited Feb 28 at 20:00
Glorfindel
3171511
edited Feb 28 at 20:00
Glorfindel
3171511
edited Feb 28 at 20:00
Glorfindel
3171511
3171511
asked Jun 27 '14 at 3:29
DJMcMayhemDJMcMayhem
6281412
asked Jun 27 '14 at 3:29
DJMcMayhemDJMcMayhem
6281412
asked Jun 27 '14 at 3:29
DJMcMayhemDJMcMayhem
6281412
6281412
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.
– user44370
Jun 27 '14 at 5:22
add a comment |
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.
– user44370
Jun 27 '14 at 5:22
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.
– user44370
Jun 27 '14 at 5:22
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.
– user44370
Jun 27 '14 at 5:22
add a comment |
8 Answers
8
active
oldest
votes
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.
edited Dec 4 '15 at 0:10
Braiam
23.7k2077142
answered Jul 9 '14 at 19:35
DavidDavid
22622
Yep, that was the problem, thankyou!
– DJMcMayhem
Jul 14 '14 at 18:03
@David could you please update your answer with more details.
– αғsнιη
Jan 22 '15 at 21:09
2
@KasiyA, I didn't end up using VBoxManage. Instead I started from scratch and allocated more memory in the VDI. I hope that helps!
– DJMcMayhem
Jan 23 '15 at 21:30
add a comment |
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.
answered Sep 1 '15 at 20:45
Armin SmailhodzicArmin Smailhodzic
111
add a comment |
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.
answered Oct 29 '15 at 16:01
garthoidgarthoid
111
add a comment |
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
hope it helps
answered Jan 6 '16 at 18:25
user150344user150344
1
nope, for some reason i had problems with it, so i switched to xfce4 instead
– user150344
Jan 6 '16 at 18:34
add a comment |
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.
answered Jan 18 '18 at 4:23
BrendanSimonBrendanSimon
11
add a comment |
I also had the same problem and I was not able to type password, because nothing happens as I type password. So I downloaded a different version of kali which supports virtual box and it worked for me.
Hope it helps!
edited Aug 1 '16 at 18:21
Thomas
4,00561329
answered Aug 1 '16 at 17:50
WarlordWarlord
1
add a comment |
this might work.. It did work for me:
# apt-get update
# apt-get install xorg
and then try startx
edited Feb 25 '15 at 14:09
HalosGhost
3,77392236
answered Feb 25 '15 at 12:41
user3451157user3451157
1
add a comment |
I had been facing same issue, tried very diffrent ways which don't work.
Eventually I've just typed:
exit
And logged again with my credentials.
Works for me, was that simple ;)
answered Oct 22 '15 at 12:02
JynventhecJynventhec
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f139460%2foh-no-something-went-wrong-while-starting-the-system-after-installing-kali-lin%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
8 Answers
8
active
oldest
votes
8 Answers
8
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
edited Dec 4 '15 at 0:10
Braiam
23.7k2077142
answered Jul 9 '14 at 19:35
DavidDavid
22622
Yep, that was the problem, thankyou!
– DJMcMayhem
Jul 14 '14 at 18:03
@David could you please update your answer with more details.
– αғsнιη
Jan 22 '15 at 21:09
2
@KasiyA, I didn't end up using VBoxManage. Instead I started from scratch and allocated more memory in the VDI. I hope that helps!
– DJMcMayhem
Jan 23 '15 at 21:30
add a comment |
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.
edited Dec 4 '15 at 0:10
Braiam
23.7k2077142
answered Jul 9 '14 at 19:35
DavidDavid
22622
Yep, that was the problem, thankyou!
– DJMcMayhem
Jul 14 '14 at 18:03
@David could you please update your answer with more details.
– αғsнιη
Jan 22 '15 at 21:09
2
@KasiyA, I didn't end up using VBoxManage. Instead I started from scratch and allocated more memory in the VDI. I hope that helps!
– DJMcMayhem
Jan 23 '15 at 21:30
add a comment |
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.
edited Dec 4 '15 at 0:10
Braiam
23.7k2077142
answered Jul 9 '14 at 19:35
DavidDavid
22622
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.
edited Dec 4 '15 at 0:10
Braiam
23.7k2077142
answered Jul 9 '14 at 19:35
DavidDavid
22622
edited Dec 4 '15 at 0:10
Braiam
23.7k2077142
edited Dec 4 '15 at 0:10
Braiam
23.7k2077142
edited Dec 4 '15 at 0:10
Braiam
23.7k2077142
23.7k2077142
answered Jul 9 '14 at 19:35
DavidDavid
22622
answered Jul 9 '14 at 19:35
DavidDavid
22622
answered Jul 9 '14 at 19:35
DavidDavid
22622
22622
Yep, that was the problem, thankyou!
– DJMcMayhem
Jul 14 '14 at 18:03
@David could you please update your answer with more details.
– αғsнιη
Jan 22 '15 at 21:09
2
@KasiyA, I didn't end up using VBoxManage. Instead I started from scratch and allocated more memory in the VDI. I hope that helps!
– DJMcMayhem
Jan 23 '15 at 21:30
add a comment |
Yep, that was the problem, thankyou!
– DJMcMayhem
Jul 14 '14 at 18:03
@David could you please update your answer with more details.
– αғsнιη
Jan 22 '15 at 21:09
2
@KasiyA, I didn't end up using VBoxManage. Instead I started from scratch and allocated more memory in the VDI. I hope that helps!
– DJMcMayhem
Jan 23 '15 at 21:30
Yep, that was the problem, thankyou!
– DJMcMayhem
Jul 14 '14 at 18:03
Yep, that was the problem, thankyou!
– DJMcMayhem
Jul 14 '14 at 18:03
@David could you please update your answer with more details.
– αғsнιη
Jan 22 '15 at 21:09
@David could you please update your answer with more details.
– αғsнιη
Jan 22 '15 at 21:09
2
2
@KasiyA, I didn't end up using VBoxManage. Instead I started from scratch and allocated more memory in the VDI. I hope that helps!
– DJMcMayhem
Jan 23 '15 at 21:30
@KasiyA, I didn't end up using VBoxManage. Instead I started from scratch and allocated more memory in the VDI. I hope that helps!
– DJMcMayhem
Jan 23 '15 at 21:30
add a comment |
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.
answered Sep 1 '15 at 20:45
Armin SmailhodzicArmin Smailhodzic
111
add a comment |
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.
answered Sep 1 '15 at 20:45
Armin SmailhodzicArmin Smailhodzic
111
add a comment |
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.
answered Sep 1 '15 at 20:45
Armin SmailhodzicArmin Smailhodzic
111
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.
answered Sep 1 '15 at 20:45
Armin SmailhodzicArmin Smailhodzic
111
answered Sep 1 '15 at 20:45
Armin SmailhodzicArmin Smailhodzic
111
answered Sep 1 '15 at 20:45
Armin SmailhodzicArmin Smailhodzic
111
answered Sep 1 '15 at 20:45
Armin SmailhodzicArmin Smailhodzic
111
111
add a comment |
add a comment |
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.
answered Oct 29 '15 at 16:01
garthoidgarthoid
111
add a comment |
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.
answered Oct 29 '15 at 16:01
garthoidgarthoid
111
add a comment |
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.
answered Oct 29 '15 at 16:01
garthoidgarthoid
111
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.
answered Oct 29 '15 at 16:01
garthoidgarthoid
111
answered Oct 29 '15 at 16:01
garthoidgarthoid
111
answered Oct 29 '15 at 16:01
garthoidgarthoid
111
answered Oct 29 '15 at 16:01
garthoidgarthoid
111
111
add a comment |
add a comment |
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
hope it helps
answered Jan 6 '16 at 18:25
user150344user150344
1
nope, for some reason i had problems with it, so i switched to xfce4 instead
– user150344
Jan 6 '16 at 18:34
add a comment |
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
hope it helps
answered Jan 6 '16 at 18:25
user150344user150344
1
nope, for some reason i had problems with it, so i switched to xfce4 instead
– user150344
Jan 6 '16 at 18:34
add a comment |
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
hope it helps
answered Jan 6 '16 at 18:25
user150344user150344
1
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
hope it helps
answered Jan 6 '16 at 18:25
user150344user150344
1
answered Jan 6 '16 at 18:25
user150344user150344
1
answered Jan 6 '16 at 18:25
user150344user150344
1
answered Jan 6 '16 at 18:25
user150344user150344
1
1
nope, for some reason i had problems with it, so i switched to xfce4 instead
– user150344
Jan 6 '16 at 18:34
add a comment |
nope, for some reason i had problems with it, so i switched to xfce4 instead
– user150344
Jan 6 '16 at 18:34
nope, for some reason i had problems with it, so i switched to xfce4 instead
– user150344
Jan 6 '16 at 18:34
nope, for some reason i had problems with it, so i switched to xfce4 instead
– user150344
Jan 6 '16 at 18:34
add a comment |
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.
answered Jan 18 '18 at 4:23
BrendanSimonBrendanSimon
11
add a comment |
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.
answered Jan 18 '18 at 4:23
BrendanSimonBrendanSimon
11
add a comment |
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.
answered Jan 18 '18 at 4:23
BrendanSimonBrendanSimon
11
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.
answered Jan 18 '18 at 4:23
BrendanSimonBrendanSimon
11
answered Jan 18 '18 at 4:23
BrendanSimonBrendanSimon
11
answered Jan 18 '18 at 4:23
BrendanSimonBrendanSimon
11
answered Jan 18 '18 at 4:23
BrendanSimonBrendanSimon
11
11
add a comment |
add a comment |
I also had the same problem and I was not able to type password, because nothing happens as I type password. So I downloaded a different version of kali which supports virtual box and it worked for me.
Hope it helps!
edited Aug 1 '16 at 18:21
Thomas
4,00561329
answered Aug 1 '16 at 17:50
WarlordWarlord
1
add a comment |
I also had the same problem and I was not able to type password, because nothing happens as I type password. So I downloaded a different version of kali which supports virtual box and it worked for me.
Hope it helps!
edited Aug 1 '16 at 18:21
Thomas
4,00561329
answered Aug 1 '16 at 17:50
WarlordWarlord
1
add a comment |
I also had the same problem and I was not able to type password, because nothing happens as I type password. So I downloaded a different version of kali which supports virtual box and it worked for me.
Hope it helps!
edited Aug 1 '16 at 18:21
Thomas
4,00561329
answered Aug 1 '16 at 17:50
WarlordWarlord
1
I also had the same problem and I was not able to type password, because nothing happens as I type password. So I downloaded a different version of kali which supports virtual box and it worked for me.
Hope it helps!
edited Aug 1 '16 at 18:21
Thomas
4,00561329
answered Aug 1 '16 at 17:50
WarlordWarlord
1
edited Aug 1 '16 at 18:21
Thomas
4,00561329
edited Aug 1 '16 at 18:21
Thomas
4,00561329
edited Aug 1 '16 at 18:21
Thomas
4,00561329
4,00561329
answered Aug 1 '16 at 17:50
WarlordWarlord
1
answered Aug 1 '16 at 17:50
WarlordWarlord
1
answered Aug 1 '16 at 17:50
WarlordWarlord
1
1
add a comment |
add a comment |
this might work.. It did work for me:
# apt-get update
# apt-get install xorg
and then try startx
edited Feb 25 '15 at 14:09
HalosGhost
3,77392236
answered Feb 25 '15 at 12:41
user3451157user3451157
1
add a comment |
this might work.. It did work for me:
# apt-get update
# apt-get install xorg
and then try startx
edited Feb 25 '15 at 14:09
HalosGhost
3,77392236
answered Feb 25 '15 at 12:41
user3451157user3451157
1
add a comment |
this might work.. It did work for me:
# apt-get update
# apt-get install xorg
and then try startx
edited Feb 25 '15 at 14:09
HalosGhost
3,77392236
answered Feb 25 '15 at 12:41
user3451157user3451157
1
this might work.. It did work for me:
# apt-get update
# apt-get install xorg
and then try startx
edited Feb 25 '15 at 14:09
HalosGhost
3,77392236
answered Feb 25 '15 at 12:41
user3451157user3451157
1
edited Feb 25 '15 at 14:09
HalosGhost
3,77392236
edited Feb 25 '15 at 14:09
HalosGhost
3,77392236
edited Feb 25 '15 at 14:09
HalosGhost
3,77392236
3,77392236
answered Feb 25 '15 at 12:41
user3451157user3451157
1
answered Feb 25 '15 at 12:41
user3451157user3451157
1
answered Feb 25 '15 at 12:41
user3451157user3451157
1
1
add a comment |
add a comment |
I had been facing same issue, tried very diffrent ways which don't work.
Eventually I've just typed:
exit
And logged again with my credentials.
Works for me, was that simple ;)
answered Oct 22 '15 at 12:02
JynventhecJynventhec
1
add a comment |
I had been facing same issue, tried very diffrent ways which don't work.
Eventually I've just typed:
exit
And logged again with my credentials.
Works for me, was that simple ;)
answered Oct 22 '15 at 12:02
JynventhecJynventhec
1
add a comment |
I had been facing same issue, tried very diffrent ways which don't work.
Eventually I've just typed:
exit
And logged again with my credentials.
Works for me, was that simple ;)
answered Oct 22 '15 at 12:02
JynventhecJynventhec
1
I had been facing same issue, tried very diffrent ways which don't work.
Eventually I've just typed:
exit
And logged again with my credentials.
Works for me, was that simple ;)
answered Oct 22 '15 at 12:02
JynventhecJynventhec
1
answered Oct 22 '15 at 12:02
JynventhecJynventhec
1
answered Oct 22 '15 at 12:02
JynventhecJynventhec
1
answered Oct 22 '15 at 12:02
JynventhecJynventhec
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f139460%2foh-no-something-went-wrong-while-starting-the-system-after-installing-kali-lin%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
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.
– user44370
Jun 27 '14 at 5:22