Tag Info

New answers tagged

0

If you are running 5.0.2, this issue may be related to your problem. Have you tried downgrading to 5.0.0?


-1

sudo apt-get install -f followed by sudo apt-get install virtualbox


3

X11 uses two buffers: PRIMARY and CLIPBOARD. To copy/paste to the CLIPBOARD buffer you can often use CTRL-C and CTRL-V. You can insert to the PRIMARY buffer by selecting a text and paste from it by pressing the middle mouse button. If you want to use the CLIPBOARD buffer, put this in your ~/.Xresources file and use Ctrl+Shift+C and Ctrl+Shift+V to ...


1

Turns out, I didn't account for the fact that X11 has two buffers: primary and clipboard. My text from xterm was copied into primary buffer, while I needed it in clipboard buffer. I was able to fix the problem by installing parcellite package, launching it and configuring it to synchronize two buffers.


0

Open xterm and highlight the text you want to copy. Go to the application in which you wish to paste and hover the mouse cursor over the field you want to paste in. Click the scroll button on your mouse. (on laptops this can be done by pressing left and right click at the same time) When you highlight text, it copies the text to your primary buffer. Keep ...


2

Increase your virtual hard disk space to 12 GB or more. I faced similar issue and the above resolved my issue.


0

We could find the problem on the Virtualbox VMs/MachineName/Logs/VBox.log. In this case the pulseaudio stucks (because 2 conflicting soundcards), by changing the default Host Audio Driver from PulseAudio to ALSA, the VM now can start normally.


-2

This works perfectly for me YouTube: Connect USB Wireless Adapter to Kali Linux in Virtualbox


0

When I was about to give in and call it a bad job I noticed that in the file name it mentioned 'AMD64', and my system was i386, so I was trying to run something which wasn't compatible with my system.


0

The issue was essentially the result of my misunderstanding of how to properly install VirtualBox guest modules. I thought everything was done on the host, I did not realize these systems required me to follow a guide like this on the guest OS too. After I followed this guide (with slight adjustments for the Debian system as the guide is for Red Hat-based ...


1

serial ports don't support the telnet TCP protocol, telnet is falling back to linemode,you need to disable telnet linemode so that it will use character mode. type ctrl-]mode characterenter and then log in.


1

This is more of a virtual box question than Linux. Please check the virtual box documentation as they have some comments on why there could be some discrepancies (tldr: the clock is shared between the two computers). As suggested above, use ntp. Sudo apt-get install ntp. It doesn't require any configuration, only network access.


0

The better solution may be to just disconnect the guest's NIC in Virtualbox's networking settings until you're ready to bring it online. If you still want to use iptables then on the guest run: sudo iptables -P INPUT DROP sudo iptables -P FORWARD DROP sudo iptables -P OUTPUT DROP This changes the default policy for the chains to DROP.


0

You could try writing a bash script that you could use to boot up virtualbox and make it so that when you start the script it configures the LWIN back to default so that there are no problems relaying a keyboard code. Then you could use xmodmap on the virtual machine itself if you need it. Should my solution not work I would recommend you take a look at ...


0

I solved this issue by adding my user account to the group vboxusers. usermod -a -G vboxusers noir


0

VirtualBox passes keycodes to the VM, not the interpreted meaning of those keys. Your keycode mapping comes in at a higher level, telling your host X server what to interpret each keycode as meaning. That said, Virtualbox does (or is that did?) use various heuristics to try to identify the keyboard you are using, and does some sort of mapping. Based on ...


0

Here's how I did it just now, after everything above failed... sudo bash /opt/VBoxGuestAddtions-*/uninstall.sh Cheers!


0

With a few rare exceptions you can use Ctrl-C instead.



Top 50 recent answers are included