[xmonad] Error message when launching Firefox
dons at galois.com
Tue Jan 20 12:15:56 EST 2009
Fri Jan 16 12:47:42 PST 2009 Spencer Janssen <spencerjanssen at gmail.com>
* Remove doubleFork, handle SIGCHLD
This is a rather big change. Rather than make spawned processes
become children of init, we handle them in xmonad. As a side effect
of this change, we never need to use waitForProcess in any contrib
module -- in fact, doing so will raise an exception. The main
benefit to handling SIGCHLD is that xmonad can now be started with
'exec', and will correctly clean up after inherited child processes.
> Same problem here. Also note the excessive number of
> "/usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7
> --session" that are started for some reason.
> Together with error message mentioned above:
> (Details - 1: Failed to get connection to session: Failed to execute
> dbus-launch to autolaunch D-Bus session)"
> They just keep on coming, have 406 processes like that now.
> On Tue, Jan 20, 2009 at 18:04, Don Stewart <dons at galois.com> wrote:
> > roma:
> >> * Ricardo Martins <ricardo at scarybox.net> [2009-01-20 16:51:08+0000]
> >> > This happens only when launching firefox from a keybinding or through dmenu
> >> > (also launched from a keybinding).
> >> >
> >> > I'm using the xmonad darcs from yesterday (19). xmonad 0.8.1 doesn't suffer from
> >> > this problem nor do other WMs (openbox and awesome), so I guess it's due to
> >> > something that changed between 0.8.1 and yesterday. Launching firefox in the
> >> > affected version from a terminal also has no problems.
> >> I doubt it has something to do with WM. You'd rather investigate how
> >> firefox is started. Maybe the cause is the difference in environment
> >> variables?
> > The semantics of how we fork processes changed in the head.
> > Spencer, thoughts?
> > -- Don
> > _______________________________________________
> > xmonad mailing list
> > xmonad at haskell.org
> > http://www.haskell.org/mailman/listinfo/xmonad
More information about the xmonad