Bumblebee will suddenly not start

[Sesetamhet]

Hello, I am having problems with bumblebee, on my installation of Mint 14. Previously, everything worked exactly as it should. I had bumblebee, as well as primus, and they worked well. (I do some GPU programming) However, bumblebee wouldn't start on boot, so I had to start it with

Code: Select all

$ sudo service bumblebeed start

In my attempt to fix this (I'm not sure of everything I did), I seem to have broken bumblebee beyond repair. If I run the above command, I get a report saying bumblebee has started:

Code: Select all

bumblebeed start/running, process 20882

, however, if I then try to use it:

Code: Select all

$ optirun glxgears
[ 4494.795263] [ERROR]The Bumblebee daemon has not been started yet or the socket path /var/run/bumblebee.socket was incorrect.
[ 4494.795330] [ERROR]Could not connect to bumblebee daemon - is it running?

And if I try to run just

Code: Select all

$ bumblebeed
[ 4558.829788] [ERROR]No discrete video card found, quitting

It claims no video card exists. I have however, not changed my drivers at all from when it worked. I have tried multiple reinstalls of bumblebee, bumblebee-nvidia, my linux headers, but nothing seems to have any impact. Any ideas?

Thank you!

[barcinka]

Same problem, started only a week ago, before that everything was alright.

[chico3001]

Same problem, Yesterday i purge and reinstalled bumblebee everithing was working fine, but now that i turn on my computer it's broken again...

I think its searching for /var/cat/bumblebee.socket but is nowhere to be found on my computer...

[DrHu]

For later nvidia cards (optimus ), the development version which you would have to compile from source may work..
http://bumblebee-project.org/install.html
https://launchpad.net/~hybrid-graphics-linux
--you may have to include your login name in the bumblebee group, useradd or GUI version of account control for your desktop..
http://community.linuxmint.com/tutorial/view/495
--mint forum responses, nvidia optimus card

But I would check an install guide to see what you may have to do.

[bimsebasse]

So I'm not alone - this happens to me as well.

Try:

sudo bumblebeed --daemon

(the "d" in "bumblebeed" is not a typo)

This gets things going it seems, though it's not working quite as well as it did before. If anyone finds a proper solution, please report back in here

[bimsebasse]

Well, it actually works sort of OK for me (starting the daemon). It has to be done at each system startup (adding the command to Startup Applications didn't help, can't be arsed to make a bash script), and my laptop is never completely silent as it was before, but I'm able to reach the same low CPU temperature (ca. 47 degrees with the daemon activated, ca. 58 degrees without). The temperature drop must indicate that starting the daemon means you switch to integrated graphics.

[chico3001]

Seems its affecting after upgrading to 3.1 and only on MIN 13/14:

https://github.com/Bumblebee-Project/Bu ... issues/337

Seems that the workaround is edit /etc/init/bumblebeed.conf

Find:

Code: Select all

start on    (login-session-start or desktop-session-start)
stop on     (desktop-shutdown)


Replace with:

Code: Select all

start on    (runlevel [2345])
stop on     (runlevel [016])


It worked for me...

[bimsebasse]

Worked here too, nice!

... though I now miss hearing my laptop calm down after manually starting the daemon

[GSimpson]

I had the problem too with the upgrade to 3.1
[ 408.406586] [ERROR]The Bumblebee daemon has not been started yet or the socket path /var/run/bumblebee.socket was incorrect.
[ 408.406665] [ERROR]Could not connect to bumblebee daemon - is it running?
I found this solution that has got the optirun glxspheres running fine again.
http://stackoverflow.com/questions/1178 ... er-upgrade

sudo apt-get build-dep bumblebee bumblebee-nvidia
sudo apt-get build-dep nvidia-current
sudo apt-get install bumblebee --reinstall

Now test with.....
optirun glxspheres
Ran fine for me.

EDIT: Well up until I rebooted machine and back to problem. So not a permenant solution.


EDIT: edit /etc/init/bumblebeed.conf worked for me too.