I have ubuntu 16.10 version installed. I uninstalled gtk using sudo apt-get remove --purge gtk2.0. After rebooting, my whole gui is not loading, no login screen also. I can access other terminals using Ctrl+Alt+f1. How can i get my gui interface back?. Anyhelp is appreciated.thanks.
You might probably want to try this:
sudo apt-get install ubuntu-desktop^
This should install all the packages of standard Ubuntu Desktop that you've removed.
Alternatively, you can check the logs of apt /var/log/apt/history.log and install back the packages that got removed.
Can I ask that are there any scripts in Linux that similar to reset-server-realms.command on Mac that can delete all realms on server. Actually I need to reset the server and clean it before use the application officially. I try to uninstall regarding to the guides on Realm website but somehow the old data still comes up.
Thanks
Uninstalling the package doesn't remove any data. This is done on purpose, so that the upgrade process of RPMs and debs works properly.
We don't provide a script, but the easiest way to wipe everything is simply to run:
sudo rm -rf /var/lib/realm
# CentOS
sudo yum remove realm-object-server-de
sudo yum install realm-object-server-de
# Ubuntu
sudo apt-get install --reinstall realm-object-server-de
Please note that this will preserve your configuration, still. The configuration is stored in /etc/realm.
I am trying to run mean.js project based on vagrant , but I get the following error with the vagrant up command on ubuntu 14.04 LTS 64 bit.
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "d660b7d6-06a3-49bc-8b90-cbad92632c11", "--type", "headless"]
Stderr: VBoxManage: error: The virtual machine 'pets_default_1473142645576_38190' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine
I solved the using following steps:
I have completely remove older VirtualBox versions before installing VirtualBox-5.0 !
Uninstall VirtualBox
sudo apt-get purge "^virtualbox-.*"
Update the software repositories
sudo apt-get update
Clean up
sudo apt-get autoremove | sudo apt-get autoclean | sudo apt-get clean
Setup API repository (For Ubuntu 14.04 ("Trusty"))
echo "deb http://download.virtualbox.org/virtualbox/debian trusty contrib" | sudo tee /etc/apt/sources.list.d/oracle-vbox.list
Setup Oracle Key
wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -
wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | sudo apt-key add -
6.Install Oracle Virtualbox
sudo apt-get update
sudo apt-get install virtualbox-5.1
Start Virtualbox
virtualbox
For more help check to here.
I have reinstalled virtual box and the issue has been solved for me.
On my mac while installing virtual box, It has not allowed me to install. So i went system preference -> security & privacy - > general - 'allow apps download from' -> click on the "allow" button.
I have successfully installed virtual box after the above changes on system preference.
Kitchen converge -> successfully done.
I was using macOS and I had this error after updating VirtualBox. I solved the error by going to:
System Preferences --> Security & Privacy and then clicked on lock to make changes. Then, I clicked on "Allow" as shown in the picture below:
After you make the changes, a restart is requested by the system, after restart the command should work just ok :)
Move to directory:
cd /sbin/
Run script:
sudo ./vboxconfig
Start VM:
VBoxManage startvm "VM name" --type headless
It works:)
Root this problem - system updating. VBox updated partially. This script fix this problem.
For some reason my virtualbox linux host was having an outdated vboxdrv kernel module.
I did the whole remove VirtualBox package, then reinstall, but this old version kernel module remained.
Manually deleted the unwanted module, then freshly reinstalled latest VirtualBox, then usual vboxconfig to rebuild the latest modules, and we're done.
/usr/bin/vboxmanage startvm Win10-Server --type headless now working as expected. :-)
I also faced the same issue, but Santosh Shinde's answer helped me to figure it out.
I, however, want to add to it:
After uninstalling every old/previous version of Virtualbox available on your PC:
sudo apt-get purge "^virtualbox-.*"
And cleaning your system:
sudo apt-get autoremove
Rather than installing Virtualbox from the Apt repository of Ubuntu, simply visit the downloads page of Virtualbox, to download the most current version of Virtualbox.
This is because the Apt repository may not have the latest version of Virtualbox.
I have the same error after install some cripto plugin to Chrome.Then see that Virtual box extension is not working under root and user. In my linux distributive /opt owner was changed to user by cripto plugin installator. Changing /optto root owner has solved the problem.
I just had this happen on a FreeBSD box where vagrant wasn't involved at all.
[root#freebsdserver ~]# vboxmanage startvm yavm
Waiting for VM "yavm" to power on...
VBoxManage: error: The virtual machine 'yavm' has terminated unexpectedly during startup because of signal 6
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine
In this case it's because "freebsdserver" is running headless. The fix was to run:
# vboxmanage startvm yavm --type headless
So out of no where I was unable to SSH into my headless linux box.
So I hooked up a screen and started tooling with it.
My server is still fully functional and the box seems in tact. I just wouldn't let me SSH in.
So I tried follow a few online tutorials on adding my IP to the SSH allow file but nothing seemed to work.
I kept getting
"Network Connect: Connection Refused"
when attempting to SSH in with putty.
So I decided to nuke the iptables and do
sudo apt-get remove --purge iptables
which resulted in a failure.
Something like this
"processing tables for mandb " "fopen permission denied"
So I tried doing
sudo apt-get install iptables
which it said the same fopen error.
End result is my server is up and running but I have no ssh capabilities into my box. On that note though I do still have an active samba connection. Take that for what its worth.
The fopen permission denied thing when doing apt-get or dpkg, is very often a sign that your manpages cache at /var/cache/man is owned by root:root instead of man:root. Try changing this with
chown -R man:root /var/cache/man
I followed the instructions below and the problem was solved. I hope it works for you.
sudo apt autoremove
sudo dpkg --configure -a
sudo apt-get update
sudo apt-get upgrade
I was trying to install VM software on my Ubuntu system. Since I'm not very familiar with linux I followed a guide on the official Ubuntu site. Now I am running Ubuntu in a Xen environment, but I don't want to use Xen to make my virtual machines.
I installed Virtualbox in order to create my VM's, but Virtualbox doesn't run in a Xen environment.
I have tried googling for a way to remove Xen from my system, but I am unable to do it. This is what I've tried so far:
Editing /boot/grub/grub.cfg set default="Xen 4.1-amd64" to set default=1 which was recommended by a tutorial. It made my laptop start up in recovery mode and I had to generate a new grub config file which put the default back to xen.
Editing /boot/grub/menu.lst but I don't have any files called that on my system
user#BEL-8WF4XW1:~$ sudo find / -name menu.lst
user#BEL-8WF4XW1:~$
Looking through software center, but I couldn't find anything about Xen
The command make uninstall but I didn't use the source code.
I also tried to install yum and do sudo yum install kernel followed by sudo yum remove xen kernel-xen libvirt but that also didn't work.
I'm quite lost to be honest. Can anyone help me to get my Ubuntu back to how it was before I tried to follow that guide?
I'm no expert but I've executed
sudo apt-get purge xen*
and it worked for me.
You can just try
sudo apt-get remove xen-hypervisor-amd64
or
dpkg -i xen-hypervisor-amd64
to see which xen files have been installed in your machine