Linux Lite Forums
Software - Support => Other => Topic started by: RobertMC on November 30, 2015, 03:49:08 PM
-
Hello everyone new here to the forum. I've been using LL for several years on lots of different machines. I am getting this message "vboxclient the virtualbox kernel service is not running" on 5 different machines after recent updates everytime the computers start or restart. I dont have Virtualbox and need to know how to get rid of this message. Thanks in advance.
-
Indeed - "VBoxClient: the VirtualBox kernel service is not running."
I'm seeing this on every system after running a normal update...
This includes 32Bit / 64Bit - with or without "VirtualBox" installed
very puzzling...
Any help greatly appreciated ...
-
If you're not running Virtualbox, remove any Virtualbox related stuff using Synaptic. Reboot.
-
Yes i tried removing the packages didn't seem to help. This is also on all of my 32/64 bit systems. This happened from doing updates.
-
That's odd because vboxclient is part of...
https://packages.debian.org/wheezy-backports/amd64/virtualbox-guest-x11/filelist (https://packages.debian.org/wheezy-backports/amd64/virtualbox-guest-x11/filelist)
Remove virtualbox-guest-x11 and you cut off vboxclients head. No more yapping at start up.
You might care to look at https://www.linuxliteos.com/forums/other/where-did-virtual-box-come-from/ where the question has been answered previously.
-
That's odd because vboxclient is part of...
https://packages.debian.org/wheezy-backports/amd64/virtualbox-guest-x11/filelist (https://packages.debian.org/wheezy-backports/amd64/virtualbox-guest-x11/filelist)
Remove virtualbox-guest-x11 and you cut off vboxclients head. No more yapping at start up.
You might care to look at https://www.linuxliteos.com/forums/other/where-did-virtual-box-come-from/ (https://www.linuxliteos.com/forums/other/where-did-virtual-box-come-from/) where the question has been answered previously.
I removed all virtualbox-guest - no joy,,, Still YAP, YAP YAP
Humm,,, curious
-
VBoxClient: the VirtualBox kernel service is not running
I'm confused. :o
systems that have NO VirtualBox installed at all. Even after "removing" all virtualbox-guest packages, still get nag at start up.
I can't think of EVER having anything like this with LL2. ???
-
Getting same error on Lappy and desktop.
Both running LL 2.6 with virtualbox installed.
Jocklad ::) ::)
-
Jocklad,
I get it on every new install last several days. 32Bit, 64Bit, with or without VirtualBox installed. Even after completely removing any and all references to VirtualBox on systems without VB.
I'm completely stumped .... :o :( :-[ :'(
-
Yes see what you mean obWAN.
I uninstalled VB from the lappy and rebooted....error still there.
Stumped as well. ??? ???
-
I don't have LL 2.6 installed on any computers right now. If have time, will install to one later today and see if I can figure out what problem is if nobody else comes along with a solution to this.
P.s. Just to clarify -- is this an error message shown during boot-up on the screen? Or does some error message pop-up after you've logged into the desktop? Does it cause any malfunction of system that you can tell? If so, describe what happens.
-
The error appears during Boot.....then disappears.
I have Windows 7 running in VB and its fine.
Jocklad ::) ::)
-
To Jocklad,
You say I uninstalled VB from the lappy and rebooted....error still there.
, then you say I have Windows 7 running in VB and its fine.
.
Do you have Virtualbox running or not?
-
Also,
The error appears during Boot.....then disappears.
Is that when you boot LL the "Host" or when you boot Win7 the "Guest"
-
To Jocklad,
You say I uninstalled VB from the lappy and rebooted....error still there.
, then you say I have Windows 7 running in VB and its fine.
.
Do you have Virtualbox running or not?
Sorry for any confusion.
VB was running on two machines laptop and desktop both running LL 2.6
Vb on desktop has Windows 7 installed.
Nothing was installed on VB on the laptop.
The error occurs on booting into LL 2.6 on both machines even with VB uninstalled on the laptop.
Jocklad
-
If this appears when you run LL on a real hardware, it is because the script that runs VboxClient, in case when Vbox kernel module isn't detected sends a notification message.
Fix is next:
Run this in terminal (providing a sudo password)
gksudo leafpad /etc/X11/Xsession.d/98vboxadd-xclientfind the line
notify-send "VBoxClient: the VirtualBox kernel service is not running. Exiting."Now change notify-send to echo
echo "VBoxClient: the VirtualBox kernel service is not running. Exiting."And save the file.
On next reboot it will not appear again.
Cheers ;)
-
Yes that did it.
No error on reboot.
Win 7 booting ok on vb.
Many thanks misko_2083.
Jocklad :) :) :)
-
It's not an error. It's an info that says you are not running a vboxguest module. And it's usefull only in the case you are running LL in VB as a guest OS.
Kind of reminder I guess.
You could have made it display some other text. :)
If you open a terminal window and run
notify-send "I Love Cookies."It will display your message as a notification. ;D
-
I do not use VirtualBox but also get the notification message. With Synaptic manager I removed all Virtual Box related packages and then reboot. This did not work. Then I saw some residual packages in Synaptic. I then used Lite Tweaks to autoremove packages, clean package cache and clean residual config files. After that and a reboot the message was gone.
I am not a computer expert but it worked and maybe this is of use for people who do not use VirtualBox at all and get that anoying message.
Greetings,
Ton.
-
If this appears when you run LL on a real hardware, it is because the script that runs VboxClient, in case when Vbox kernel module isn't detected sends a notification message.
Fix is next:
Run this in terminal (providing a sudo password)
gksudo leafpad /etc/X11/Xsession.d/98vboxadd-xclientfind the line
notify-send "VBoxClient: the VirtualBox kernel service is not running. Exiting."Now change notify-send to echo
echo "VBoxClient: the VirtualBox kernel service is not running. Exiting."And save the file.
On next reboot it will not appear again.
Cheers ;)
SWEET !!! Thank You so much - Misko_2083 "you ROCK"
After LL 2.8 Some systems also require editing /usr/bin/VBoxClient-all (open as "Administrator")
-
Thanks for this!
I am just getting into LL. My regular OS is Ubuntu 14.04 on which I run various VB VMs. None of the Ubuntu forums had the right fix for this!
-
I have removed the guest packages AND changed the line to echo, but I still get the kernel service not running announcement/error at startup. Is there another possible solution?
-
I made a script wich worked for me (VMdebian8 jessie)
debian was missing some packages.
RUN IT IN YOUR VM !!
#!/bin/bash
# INSERT VBOXADDITIONS in your vm !!
su
apt-get update -q
apt-get upgrade -q
apt-get install -q linux-headers-`uname -r` make gcc dkms build-essential
mkdir /tmp/vbox
mount /dev/sr0 /media/cdrom0/
cp -rvf /media/cdrom0/* /tmp/vbox
cd /tmp/vbox/
./VBoxLinuxAdditions.run
reboot
I hope it's helpful ;)
-
OK first post and I am a complete ICT numpty but re the virtualbox message, replacing notify-send with echo had no effect, totally removing both apps with virtualbox in the name also did not work. All by myself I had a little think, then remembering how I got Xpad to start on booting up by adding it to Startup I had a look in Settings>Settings Manager>Session and Startup, Application Autostart tab and sure enough there was 'vboxclient' with a tick by it, unchecking that worked... hope that helps somebody ;)
-
If this appears when you run LL on a real hardware, it is because the script that runs VboxClient, in case when Vbox kernel module isn't detected sends a notification message.
Fix is next:
Run this in terminal (providing a sudo password)
gksudo leafpad /etc/X11/Xsession.d/98vboxadd-xclientfind the line
notify-send "VBoxClient: the VirtualBox kernel service is not running. Exiting."Now change notify-send to echo
echo "VBoxClient: the VirtualBox kernel service is not running. Exiting."And save the file.
On next reboot it will not appear again.
Cheers ;)
Did that but i still keep getting the message when i boot up the laptop
Any idea what might be causing it? Running LL2.8
Solved after disabling vboxclient in session and startup
-
I thin You "may have" missed editing the second file ...
do both ...
gksudo leafpad /etc/X11/Xsession.d/98vboxadd-xclient
gksudo leafpad /usr/bin/VboxClient-all
-
Solved after disabling vboxclient in session and startup
Glad it worked for you as well :) , it worked on installations on two different laptops for me.