Advertisement
Guest User

Untitled

a guest
Jun 5th, 2011
108
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.34 KB | None | 0 0
  1. Traceback (most recent call last):
  2. File "/usr/local/bin/onboard", line 14, in <module>
  3. from Onboard.OnboardGtk import OnboardGtk as Onboard
  4. File "/usr/local/lib/python2.6/dist-packages/Onboard/OnboardGtk.py", line 21, in <module>
  5. from Onboard.Indicator import Indicator
  6. File "/usr/local/lib/python2.6/dist-packages/Onboard/Indicator.py", line 5, in <module>
  7. import Onboard.utils as utils
  8. File "/usr/local/lib/python2.6/dist-packages/Onboard/utils.py", line 15, in <module>
  9. from Onboard import KeyGtk
  10. File "/usr/local/lib/python2.6/dist-packages/Onboard/KeyGtk.py", line 16, in <module>
  11. config = Config()
  12. File "/usr/local/lib/python2.6/dist-packages/Onboard/Config.py", line 104, in __new__
  13. cls.self._init()
  14. File "/usr/local/lib/python2.6/dist-packages/Onboard/Config.py", line 131, in _init
  15. self._gconf_client.add_dir("/apps/onboard", gconf.CLIENT_PRELOAD_NONE)
  16. glib.GError: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement