Hi Robin, On Sunday 28 October 2012 16:55:11 Robin Battey wrote: > The upstart script starts on runlevel 2345, and stops on runlevel 016. > However, the hybrid-detect task that runs upon starting lightdm (from > the nvidia-current package in x-updates) changes the graphics settings > in a way that, at least on this system, causes the graphical > environment to fail. (The VT changes but you see no video, however > from the sounds of the system it's clear that the graphical > environment is running in some framebuffer somewhere just not > attached to the screen -- I expect it's running on the wrong GPU.) > The solution is to have the bumblebeed service start when the > login-session-start (for the usual graphical login) and > desktop-session-start (for those running "startx") events occur, which > is after the display manager is running. In short, change the > upstart script start/stop semantics to this: > > start on (login-session-start or desktop-session-start) > stop on (desktop-shutdown)
Thank you for reporting. I have committed your proposed fix to the git repositories (but not the PPA yet). https://github.com/Bumblebee- Project/Bumblebee/commit/20b4ece4614744e310f8d85a9a16af62d8c61a4d Have you manually edited your bumblebeed.conf and tested it already (I guess so, but just for sure :-) ) Is this a problem that occurs on a standard installation since Quantal? If so, we need to release a fix soon but otherwise it can be queued for a future release. Regards, Peter -- Mailing list: https://launchpad.net/~bumblebee Post to : [email protected] Unsubscribe : https://launchpad.net/~bumblebee More help : https://help.launchpad.net/ListHelp
