[gold_finger]

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.

[Jocklad]

The error appears during Boot.....then disappears.

I have Windows 7 running in VB and its fine.

Jocklad  : :

[torreydale]

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?

[Wirezfree]

Also,

The error appears during Boot.....then disappears.

Is that when you boot LL the "Host" or when you boot Win7 the "Guest"

[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?

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

[anon222]

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)

Code:

gksudo leafpad /etc/X11/Xsession.d/98vboxadd-xclient

find the line

Code:

notify-send "VBoxClient: the VirtualBox kernel service is not running.  Exiting."

Now change notify-send to echo

Code:

  echo "VBoxClient: the VirtualBox kernel service is not running.  Exiting."

And save the file.
On next reboot it will not appear again.
Cheers 

[Jocklad]

Yes that did it.

No error on reboot.

Win 7 booting ok on vb.

Many thanks misko_2083.

Jocklad 

[anon222]

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

Code:

notify-send "I Love Cookies."

It will display your message as a notification.  ;D

[AFMS]

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.

[0bWAN]

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)

Code:

gksudo leafpad /etc/X11/Xsession.d/98vboxadd-xclient

find the line

Code:

notify-send "VBoxClient: the VirtualBox kernel service is not running.  Exiting."

Now change notify-send to echo

Code:

  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" 

[size=1em]After LL 2.8  Some systems also require editing[/size][size=1.35em] /usr/bin/VBoxClient-all  (open as "Administrator")[/size]