Failed to connect to Bumblebee daemon after kernel updates.

Ok so ive started to notice, that sometimes..(Not always)..after a kernel update, and a restart of my system, that “Bumblebeed” doesn’t start up. I go to run a command with “primusrun” or “optirun”, and ive been getting this error.

2013/07/16 14:52:00 socat[5962] E connect(3, AF=1 “/var/run/bumblebee.socket”, 27): No such file or directory
primus: fatal: failed to connect to Bumblebee daemon: No such file or directory

So i noticed that you cant fix that issue by doing “sudo service bumblebeed start”..You just end up getting this error.

[  125.430955] [ERROR]The Bumblebee daemon has not been started yet or the socket path /var/run/bumblebee.socket was incorrect.
[  125.431012] [ERROR]Could not connect to bumblebee daemon – is it running?

So what it is, is that when the newest kernel gets applied..the new linux-header files dont get installed, and that’s what bumblebee is looking for.

So i after a kernel update, i just do “uname -a”… to see what kernel i am currently running, and then install the linux-header file to match with it. Then i restart the computer and bumblebee seems to start working again.

I dont know if i noticed this happening when i was using Linux Mint 15 on my laptop..but i do know that it does do it with Peppermint OS.

Anyway!..i hope i cleared up anyones confusion if you are experiencing the same issues.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s