firefox throwing error message in 20090311

[bgc1954]

I just noticed this when I started using 20090311. I first noticed it on my t21 ibm laptop running Arch Linux and just had the same thing happen on my desktop machine. Musca will now work on my desktop as long as I don't use slim to start it. My desktop is running Arch Linux 32 bit as well. This is the error message that firefox throws up when starting it:

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://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: dbus-launch failed to autolaunch D-Bus session: Failed to waitpid() for babysitter intermediate process: No child processes
)
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://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: dbus-launch failed to autolaunch D-Bus session: Failed to waitpid() for babysitter intermediate process: No child processes
)
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://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: dbus-launch failed to autolaunch D-Bus session: Failed to waitpid() for babysitter intermediate process: No child processes
)
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://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: dbus-launch failed to autolaunch D-Bus session: Failed to waitpid() for babysitter intermediate process: No child processes
)
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://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: dbus-launch failed to autolaunch D-Bus session: Failed to waitpid() for babysitter intermediate process: No child processes
)

This did not happen in 20090310, but I had only used that version for one day. Both machines had been pacman -Syu'd before I compiled musca.

[Sean Pringle (sean-pringle)]

Have you tried using dbus-launch to start Musca, in .xinirc? Eg:

exec /usr/bin/dbus-launch --exit-with-session musca

I will -Syu shortly and check.

[bgc1954 (bgc1954-hotmail)]

Yes that works, but I'm just kind of wondering what has changed since 20090310 that didn't need this workaround. Thanks for the solution.

[Sean Pringle (sean-pringle)]

Try this: In musca.c, comment out this line (it is near the bottom in setup()):

//signal(SIGCHLD, SIG_IGN);

Then rebuild. I think we might be short cucuiting dbus waitpid() by establishing this handler in the parent musca process.

[Sean Pringle (sean-pringle)]

I'm fairly certain my previous comment identified the problem. I've pushed Musca 20090312a release to the website which includes this fix.

[bgc1954 (bgc1954-hotmail)]

This bug is gone in 20090312a. Firefox not throwing any dbus-error when launched now.