← Back to team overview

nssbackup-team team mailing list archive

Re: [Question #127322]: Plans for Non-Gnome environments?

 

Question #127322 on Simple Backup changed:
https://answers.launchpad.net/sbackup/+question/127322

    Status: Needs information => Open

Andreas gave more information on the question:
Hi Jean-Peer,

thanks for responding to my query.

It turns out pgrep (used in grep_pid()) was missing on my OS X system,
which is why seemingly some environment variables couldn't be read.
Furthermore I had not installed some more dependencies (dbus-python, py-
gnome and proctools; lots of gnome related stuff was already installed,
so can't give a full dependency list for Mac ports users).

When launching sbackup-config-gtk with sudo I get the following error
message:

"""
Unable to get PID of process 'gnome-session'.
Unable to get PID of process 'ksmserver'.
Neither Gnome nor KDE session is running
Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Error while getting gconf setting: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: Not enough memory)
Default value is used.
Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Error while setting gconf value: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: Not enough memory)
Error can be safely ignored: setting is not being changed.
Failed to start message bus: launchd's environment variable DBUS_LAUNCHD_SESSION_BUS_SOCKET is empty, but should contain a socket path.

EOF in dbus-launch reading address from bus daemon
D-Bus session bus launched

Unable to read environment variable ''. Skipped.
"""


However
$ echo  $DBUS_LAUNCHD_SESSION_BUS_SOCKET
/tmp/launch-06QVF7/unix_domain_listener
and
$ ps ax | grep dbus
  213   ??  S      0:00.02 /opt/local/bin/dbus-daemon --nofork --session

Any idea where to look next?

Thanks,
Andreas

-- 
You received this question notification because you are a member of
Simple Backup Maintainers, which is an answer contact for Simple Backup.