Custom Query (16363 matches)
Results (1681 - 1683 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16940 | duplicate | the fonts are way small. | ||
| Description |
see pix |
|||
| #16938 | fixed | since 5.1.24 not just one PulseAudio sink gets created but 10 | ||
| Description |
i am running debian, but same happens (at least) on Arch as well. For linux VM's (with Audio being ICH AC97), there are too many sinks created on the host. I am currently working around this by using Intel Audio instead. The host has too many audio controls (sliders) and after just 2 VM's (which use up 20 of them) i can no longer control host applications volume in the mixer. |
|||
| #16937 | invalid | Virtualbox vboxdrv error | ||
| Description |
ohh my.. okay.. here goes.. first some intro of my kali linux root@Risky:~# uname -a Linux Risky 4.9.0-kali3-amd64 #1 SMP Debian 4.9.18-1kali1 (2017-04-04) x86_64 GNU/Linux
"The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall virtualbox-dkms package and load the kernel module by executing 'modprobe vboxdrv' as root. where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. " ok and m like fair enough lets do this.. then it says root@Risky:~# sudo modprobe vboxdrv modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/4.9.0-kali3-amd64
edit: also when i try to reinstall virtualbox dkms.. i gets.. root@Risky:~# sudo apt install --reinstall virtualbox-dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 588 not upgraded.
Need to get 0 B/659 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 343519 files and directories currently installed.)
Preparing to unpack .../virtualbox-dkms_5.1.18-dfsg-1_all.deb ...
------------------------------
Deleting module version: 5.1.18
completely from the DKMS tree.
------------------------------
Done.
Unpacking virtualbox-dkms (5.1.18-dfsg-1) over (5.1.18-dfsg-1) ...
Setting up virtualbox-dkms (5.1.18-dfsg-1) ...
Loading new virtualbox-5.1.18 DKMS files...
Building for 4.9.0-kali3-amd64
Module build for kernel 4.9.0-kali3-amd64 was skipped since the
kernel headers for this kernel does not seem to be installed.
Job for virtualbox.service failed because the control process exited with error code.
See "systemctl status virtualbox.service" and "journalctl -xe" for details.
invoke-rc.d: initscript virtualbox, action "restart" failed.
● virtualbox.service - LSB: VirtualBox Linux kernel module
Loaded: loaded (/etc/init.d/virtualbox; generated; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2017-07-24 11:16:35 IST; 8ms ago
Docs: man:systemd-sysv-generator(8)
Process: 9962 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE)
Jul 24 11:16:35 Risky systemd[1]: Starting LSB: VirtualBox Linux kernel module...
Jul 24 11:16:35 Risky virtualbox[9962]: Loading VirtualBox kernel modules...No suitable module for running kernel found ... failed!
Jul 24 11:16:35 Risky virtualbox[9962]: failed!
Jul 24 11:16:35 Risky systemd[1]: virtualbox.service: Control process exited, code=exited status=1
Jul 24 11:16:35 Risky systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.
Jul 24 11:16:35 Risky systemd[1]: virtualbox.service: Unit entered failed state.
Jul 24 11:16:35 Risky systemd[1]: virtualbox.service: Failed with result 'exit-code'.
help me plz :| |
|||

