Ubuntu 18.04:
It looks like the Remmina Remote Desktop app was updated today and I lost the RDP protocol in the process. VNC, SSH and SPICE are still available but no RDP.
I tried rebooting, uninstalling and reinstalling using:
sudo killall remmina
sudo apt-get purge remmina* -y
rm -Rf /home/`whoami`/.remmina/remmina.pref
sudo apt-get install remmina* -y
This combo'd with a reboot before and after but still no RDP.
I also noticed that the Ubuntu Software (Gnome Software) has 2 Remmina apps listed.
I found a link (the fix) on Remmina website by accident.
The normal install instructions on their site also did not work but then I looked at compiling from source.
https://gitlab.com/Remmina/Remmina/-/wikis/Compilation/Compile-on-Ubuntu-18.04
I added to the "purge" section of the remove command above and this worked:
sudo killall remmina
sudo apt purge "remmina*" "libfreerdp*" "libwinpr*" "freerdp*"
rm -Rf /home/`whoami`/.remmina/remmina.pref
Reboot and then install using the "Ubuntu Software", choose the one with the mostly Blue icon.
It looks like the FreeRDP libraries may have been the issue for me.
I just installed ubuntu and fire this command :
sudo modprobe -rv rtl8723be
sudo modprobe -v rtl8723be ant_set = 1
how to get it back my display?
you should do.
sudo modprobe -rv rtl8723be ant_set = 1
i hope it will work ...
In our company we have this issue just in HP laptop and we solve it in 6 step
1- open software and update icon from the search field
2- go to Additional Drivers go to Realtek Semiconductor.......
3- select the same choice in the picture
4- run this command: sudo apt install
5- run this command: sudo apt update
6- restart your computer
And enjoy :)
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
running a OpenCV-based code on Ubuntu, I incurred in the following error:
OpenCV Error: Unspecified error (The function is not implemented.
Rebuild the library with Windows, GTK+ 2.x or Carbon support.
If you are on Ubuntu or Debian, install libgtk2.0-dev and pkg-config, then
re-run cmake or configure script) in cvNamedWindow, file /home/opennao/src/OpenCV-2.3.1/modules/highgui/src/window.cpp, line 275
terminate called after throwing an instance of 'cv::Exception'
So I tried to install this libgtk2.0-dev by typing:
sudo apt-get install libgtk2.0-dev
but it returns the following:
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem."
And this is what I did. But then, during the processing of the command request, the pc restarts on its own and the problem comes again when I run my code.
For the sake of clarification, I think it's worth saying that two weeks ago an update on Ubuntu corrupted my grub to choose the OS to run (there are Ubuntu 14.04 and Windows 10 on my pc), so I restored it through minimal-bash line editing.
Now, when I run "sudo dpkg --configure -a" I see that the last printed lines before restarting refer to some information about disk images or kernels that I rembember to have handled to fix the grub. I don't know if this can be a suggestion to understand the problem.
Thank you all for your support, ask me if you need further details.
Just after booting, while Kubuntu loads its modules and checks all of it, this message appears and the loading work stops.
As a matter of fact the Kubuntu's login screen never comes and it switches automatically on the tty1 in console mode. So I only can use the ttys 1 to 6 in console mode and the tty7 still out of order.
The following procedure to re-install the NVIDIA driver did not work :
Remove the existing nvidia driver :
sudo apt-get purge nvidia-current
Upgrade to the new driver: (follow this link)
http://news.softpedia.com/news/How-to-Install-The-Latest-Nvidia-Driver-on-Ubuntu-12-04-295542.shtml
sudo add-apt-repository ppa:ubuntu-x-swat/x-updates
sudo apt-get update
sudo apt-get dist-upgrade
sudo apt-get install nvidia-current
Any idea ? Thank you very much for your time.
Fixed !
As the re-installation of the nvidia current driver version did not work I thought to install one other version.
This link shows how to install NVIDIA driver on ubuntu : BinaryDriverHowto/Nvidia
So I did exactly the same procedure as above but I replaced
nvidia-current with nvidia-319.
You can access to the possible versions list with auto-completion on :
sudo apt-get install nvidia-
It fully resolved my problem after reboot.
Afterward, I saw that the current version seems to be set on the 304 version but I don't know why precisely.