Arch Linux

DonVittorio

Member

Registered: 2013-10-23

Posts: 2

Bumblebee optirun: The Bumblebee daemon has not been started yet

I've followed every step described in the wiki, but whenever I attempt to run optirun I get this error message:

$ optirun -vv
[ 1680.156516] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
[ 1680.156785] [INFO]Configured driver: nouveau
[ 1680.156832] [ERROR]The Bumblebee daemon has not been started yet or the socket path /var/run/bumblebee.socket was incorrect.
[ 1680.156839] [DEBUG]Socket closed.
[ 1680.156849] [ERROR]Could not connect to bumblebee daemon - is it running?

Systemctl says the following:

bumblebeed.service  loaded activating auto-restart  Bumblebee C Daemon

I've restarted the service, rebooted, reinstalled numerous times but to no avail.
I have searched the forums for this problem but none of the solutions seemed to solve my problem.

Thanks in advance

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,665

Re: Bumblebee optirun: The Bumblebee daemon has not been started yet

Check the status of the service using systemctl.  Is it running, or did it fail.
Use ps -ef and verify whether there is a bumblebee process running.
If there is no process, is there a file at /var/run/bumblebee.socket ?  Is the date consistent with when you last tried to start the service.
If there is no process, remove /var/run/bumblebee.socket and try starting the service.
Is there anything interesting in the journals after you try and start the service?

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

DonVittorio

Member

Registered: 2013-10-23

Posts: 2

Re: Bumblebee optirun: The Bumblebee daemon has not been started yet

Check the status of the service using systemctl.  Is it running, or did it fail.
Use ps -ef and verify whether there is a bumblebee process running.
If there is no process, is there a file at /var/run/bumblebee.socket ?  Is the date consistent with when you last tried to start the service.
If there is no process, remove /var/run/bumblebee.socket and try starting the service.

$ systemctl status bumblebeed
bumblebeed.service - Bumblebee C Daemon
   Loaded: loaded (/usr/lib/systemd/system/bumblebeed.service; enabled)
   Active: activating (auto-restart) (Result: exit-code) since Fri 2013-11-08 08:47:54 CET; 24s ago
  Process: 1351 ExecStart=/usr/bin/bumblebeed (code=exited, status=1/FAILURE)
 Main PID: 1351 (code=exited, status=1/FAILURE)

There is no process, nor is there a bumblebee.socket file. Interestingly enough the bumblebee service fails the moment I attempt to restart it.

Is there anything interesting in the journals after you try and start the service?

Nothing gets added to the journal with the same PID using journalctl _PID=

Svenstaro

Administrator

From: Germany

Registered: 2008-11-19

Posts: 393

Re: Bumblebee optirun: The Bumblebee daemon has not been started yet

Well, why does it fail? journalctl -u bumblebeed