unable to launch basil - nil class error about basil HOT 8 CLOSED

I'm unable to reproduce this using that ruby with either the CLI or Skype servers.

Please send me the output of the following commands:

$ /usr/bin/env ruby --version

$ bundle show

$ cat config/basil.yml

Be sure to mask any passwords in that last one

Finally, if you could update lines 27-30 of lib/basil.rb to the following:

rescue Exception => ex
  $stderr.puts ex.message
  $stderr.puts "#{ex.backtrace.join("\n")}"
  exit 1
end

That should shed a little more light.

from basil.

Hi,

Sorry - looks like an issue with my dbus not setup correctly . DISPLAY variable was not exported.
Need install dbus correctly however my config of dbus is failing. This issue can be closed! :)

from basil.

I have the same issue and it looks related to dbus. How did you solve this? Can you point me to a URL or issue?

from basil.

hi , i had to do a few things... first install :

sudo apt-get install dbus
sudo apt-get install dbus-x11

then had to at times run the following:

dbus-launch --sh-syntax > ~/.dbus.sh
source ~/.dbus.sh
screen -S Skype xvfb-run -n 0 -s "-screen 0 800x600x16" /usr/bin/skype

then in another screen session i had to run :

source ~/.dbus.sh

then call start basil in same session...

from basil.

Thanks... figured it out :)

from basil.

@mreider was that comment meant for #8?

@sukhi2012 that seems annoyingly hacky -- is your server headless? If not, can you try removing xvfb from the equation and check if things work without that workaround? I have a feeling there might be a disconnect between the fake x server and your running dbus, and if so, there might be a better way to handle it.

from basil.

I was logged in as scottyrb before - which is why my comment made no sense - but it was for this issue. My solution was to start a gnome session :)

from basil.

@pbrisbin yep my server is headless so i have no other working solution...

from basil.