Oh, this must be related to the doubleFork stuff. dons:

Ah ha! Yes, I also saw this starting yesterday. I wonder WTF is up.

ricardo:

...

Hi everyone.

Since yesterday I've been receiving an error dialog when launching Firefox. It says "An error occured while loading or saving configuration information for firefox. Some of your configuration settings may not work properly". Clicking on a "Details" button gives me the following:

"GConf Error: 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: Failed to execute dbus-launch to autolaunch D-Bus session)"

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.

The last three darcs builds I used were from 2009-01-12 (no problems), 2009-01-17 (I'm not sure if it had problems, since I usually suspend my laptop without rebooting or relaunching X for a few days) and 2009-01-19 (the problematic build).

I'd test the latest code, but I'm having trouble accessing the darcs repository.

Regards, -- Ricardo Martins * scarybox.net * GPG key: 0x1308F1B4

...

_______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad

_______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad

roma:

* Ricardo Martins [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

Try unpulling: Fri Jan 16 12:47:42 PST 2009 Spencer Janssen * 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. ankaan:

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 wrote:

...

roma:

...

* Ricardo Martins [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@haskell.org http://www.haskell.org/mailman/listinfo/xmonad

Fixed it here too. On Tue, Jan 20, 2009 at 18:45, Ricardo Martins wrote:

On Tue, 20 Jan 2009 09:15, Don Stewart wrote:

...

Try unpulling:

Fri Jan 16 12:47:42 PST 2009 Spencer Janssen * 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.

That fixed it, thanks. -- Ricardo Martins * scarybox.net * GPG key: 0x1308F1B4

_______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad

On Tue, 20 Jan 2009 10:10, Don Stewart wrote:

Seems just to affect gnome or gtk apps then?

rhythmbox, firefox.

I guess it affects everything that might use GConf in any way. -- Ricardo Martins * scarybox.net * GPG key: 0x1308F1B4

Before: dbus 10769 0.0 0.0 2136 820 ? Ss 18:05 0:00 /usr/bin/dbus-daemon --system Firefox also wants to set itself as the default browser after the error message, otherwise it doesn't ask. After: dbus 10769 0.0 0.0 2136 820 ? Ss 18:05 0:00 /usr/bin/dbus-daemon --system ankan 19855 0.0 0.0 2092 384 ? Ss 21:53 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session ankan 19859 0.0 0.0 2092 380 ? Ss 21:53 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session ankan 19865 0.0 0.0 2092 384 ? Ss 21:53 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session ankan 19869 0.0 0.0 2092 384 ? Ss 21:53 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session ankan 19876 0.0 0.0 2092 384 ? Ss 21:53 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session ankan 19921 0.0 0.0 2092 380 ? Ss 21:53 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session ankan 19975 0.0 0.0 2092 384 ? Ss 21:53 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session ankan 20142 0.0 0.0 2092 384 ? Ss 21:53 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session ankan 20147 0.0 0.0 2092 384 ? Ss 21:53 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session ankan 20152 0.0 0.0 2092 384 ? Ss 21:53 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session ankan 20158 0.0 0.0 2092 380 ? Ss 21:53 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session The old processes die now and new spawn all the time, in an earlier test the old ones remained and the list just got longer and longer. If firefox is started from a terminal there is no error and the process table is: dbus 28770 0.0 0.0 2136 820 ? Ss 21:58 0:00 /usr/bin/dbus-daemon --system ankan 29517 0.0 0.0 2980 684 ? SN 21:59 0:00 dbus-launch --autolaunch ce2b663d446c6cbe961910b348e74142 --binary-syntax --close-stderr ankan 29518 0.0 0.0 2136 848 ? SNs 21:59 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session If I start firefox from a dmenu now, I still get the same error in firefox, but I don't get spammed by dbus processes. Distribution: Archlinux GConf version: local/gconf 2.24.0-2 A configuration database system Gnome versions: local/ekiga 3.0.1-1 (gnome-extra) VOIP/Videoconferencing app with full SIP and H.323 support (GnomeMeeting expanded and renamed) local/evolution-data-server 2.24.2-2 Evolution Data Server provides a central location for addressbook and calendar in the GNOME Desktop local/fam 2.7.0-11 File Alteration Monitor - used by KDE, GNOME and others local/gnome-keyring 2.24.1-1 GNOME Password Management daemon local/gnome-mime-data 2.18.0-3 (gnome) The base MIME and Application database for GNOME local/gnome-vfs 2.24.0-2 The GNOME Virtual File System local/libcroco 0.6.1-1 GNOME CSS2 parsing and manipulation toolkit local/libgnome 2.24.1-1 Common libraries for GNOME local/libgnomecanvas 2.20.1.1-2 The GNOME Canvas library local/libgnomeui 2.24.0-1 User Interface library for GNOME local/libgsf 1.14.10-1 The GNOME Structured File Library is a utility library for reading and writing structured file formats. local/libsoup 2.24.2.1-1 Gnome HTTP Library dbus version: local/dbus 1.2.4-1 Freedesktop.org message bus system local/dbus-core 1.2.4-1 Freedesktop.org message bus system local/dbus-glib 0.78-1 GLib bindings for DBUS I am starting xmonad from a screen session with startx using .xinitrc. Output from startx: ankan@iblis $ startx xauth: creating new authority file /home/ankan/.serverauth.18794 X.Org X Server 1.5.3 Release Date: 5 November 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.27-ARCH i686 Current Operating System: Linux iblis 2.6.28-ARCH #1 SMP PREEMPT Tue Jan 6 10:26:22 UTC 2009 i686 Build Date: 17 December 2008 08:20:05PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jan 20 21:52:32 2009 (==) Using config file: "/etc/X11/xorg.conf" The XKEYBOARD keymap compiler (xkbcomp) reports:

Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server FoxyProxy settingsDir = /home/ankan/.mozilla/firefox/vai1a1qv.default

(firefox:19770): libgnomevfs-WARNING **: Could not create per-user Gnome application-registry directory: /home/ankan/.gnome/application-info (firefox:19770): libgnomevfs-WARNING **: Deprecated function. User modifications to the MIME database are no longer supported. (firefox:19770): libgnomevfs-WARNING **: Deprecated function. User modifications to the MIME database are no longer supported. (firefox:19770): libgnomevfs-WARNING **: Deprecated function. User modifications to the MIME database are no longer supported. (firefox:19770): libgnomevfs-WARNING **: Deprecated function. User modifications to the MIME database are no longer supported. (firefox:19770): libgnomevfs-WARNING **: Deprecated function. User modifications to the MIME database are no longer supported. (firefox:19770): libgnomevfs-WARNING **: Deprecated function. User modifications to the MIME database are no longer supported. (firefox:19770): libgnomevfs-WARNING **: Cannot open '/home/ankan/.gnome/application-info/user.applications' for writing (EE) config/hal: couldn't initialise context: (null) ((null)) Those firefox warnings do not show up when the program works correctly. I suppose that it tries to use the gnome way of setting the default application and it doesn't work... When everything works it doesn't even try to do it. Good luck and tell me if you need any more information. /Anders Engström On Tue, Jan 20, 2009 at 21:42, Spencer Janssen wrote:

On Tue, Jan 20, 2009 at 02:31:26PM -0600, Spencer Janssen wrote:

...

I need the following information from everyone experiencing this:

* versions of GNOME, GConf, dbus * how you're starting xmonad * output of ps aux | grep dbus

My theory is that you're not properly starting a DBUS session, and this is confusing GNOME.

It would also be useful to know which distribution you're running. _______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad

On Tue, 20 Jan 2009 14:42, Spencer Janssen wrote:

On Tue, Jan 20, 2009 at 02:31:26PM -0600, Spencer Janssen wrote:

...

I need the following information from everyone experiencing this:

* versions of GNOME, GConf, dbus * how you're starting xmonad * output of ps aux | grep dbus

My theory is that you're not properly starting a DBUS session, and this is confusing GNOME.

I thought so too; when I launch xmonad with 'dbus-launch --sh-syntax --exit-with-session xmonad' I don't have this problem. The thing is, 'exec xmonad' worked fine with xmonad 0.8.1.

It would also be useful to know which distribution you're running.

I'm running ArchLinux (x86_64). Output of ps aux|grep dbus:

dbus 5347 0.0 0.0 8660 968 ? Ss Jan19 1:18 /usr/bin/dbus-daemon --system meqif 11111 0.0 0.1 23316 3072 pts/4 R+ 22:28 0:00 perl /usr/bin/ack dbus meqif 14656 0.0 0.0 8384 924 ? Ss 17:44 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session meqif 14663 0.0 0.0 24700 696 tty1 S 17:44 0:00 dbus-launch --autolaunch 3e88c0b8c124a2f3b87145e94814d9f6 --binary-syntax --close-stderr root 21163 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21168 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21173 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21178 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21183 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21188 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21193 0.0 0.0 6288 404 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21198 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21205 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21213 0.0 0.0 6288 404 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21217 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21223 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21227 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21234 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21241 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21246 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21251 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21256 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21266 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21270 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21275 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21281 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21285 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21291 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21295 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21300 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21306 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21310 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21316 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21321 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21325 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21330 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21335 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21340 0.0 0.0 6288 404 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21345 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21351 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21355 0.0 0.0 6288 404 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21361 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21366 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21370 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21375 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21380 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21385 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21390 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21395 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21400 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21405 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21410 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21415 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21420 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21425 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21431 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21435 0.0 0.0 6288 404 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21441 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21445 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21450 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21455 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21460 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21472 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21477 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21482 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21487 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21492 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21497 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21502 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21507 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21512 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21517 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21523 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21527 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21532 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21538 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21543 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21547 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21552 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21558 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21563 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21567 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21573 0.0 0.0 6288 404 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21578 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21582 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21588 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21592 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21597 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21602 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21607 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21613 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21617 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21622 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21627 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21633 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21638 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21642 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21647 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21653 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21657 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21662 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21667 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21672 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21677 0.0 0.0 6288 412 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21682 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21687 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21692 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21697 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21702 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21707 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21712 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21718 0.0 0.0 6288 404 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21722 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21728 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21732 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21737 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21742 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21747 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21752 0.0 0.0 6288 404 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21757 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21762 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21767 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21772 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21777 0.0 0.0 6288 404 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21782 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21787 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21792 0.0 0.0 6288 408 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21797 0.0 0.0 6288 444 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21802 0.0 0.0 6288 448 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21807 0.0 0.0 6288 448 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21813 0.0 0.0 6288 440 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21817 0.0 0.0 6288 452 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21822 0.0 0.0 6288 444 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21827 0.0 0.0 6288 444 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21832 0.0 0.0 6288 444 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21837 0.0 0.0 6288 444 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 21842 0.0 0.0 6288 444 ? Ss 15:58 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 25162 0.0 0.0 6736 1328 ? S 11:19 0:00 /sbin/dhclient -1 -lf /var/lib/dhclient/dhclient-eth0.leases -pf /var/run/dhclient-eth0.pid -q -e dhc_dbus=31 -d eth0 --prin

I start xmonad with xinit. My .xinitrc is the following:

# # ~/.xinitrc #

FN="-*-profont-*-*-*-*-11-*-*-*-*-*-iso8859" BG="#222222" export XINERAMA_SCREENS=`~/src/xinerama`

# Load custom keymaps xmodmap ~/.Xmodmap

# Set mouse cursor xsetroot -cursor_name left_ptr &

# Set wallpaper #$(cat ~/.fehbg) nitrogen --restore #xsetroot -solid '#85a6b1'

# NVIDIA fix nvidia-settings -a InitialPixmapPlacement=2

# Start mpd nice -n -10 mpd

# Launch statusbar if [[ $XINERAMA_SCREENS == "1" ]]; then zsh ~/.xmonad/status.sh | dzen2 -ta r -fn $FN -h 16 -w 1440 -bg $BG -e '' & else zsh ~/.xmonad/status.sh | dzen2 -xs 0 -ta r -fn $FN -h 16 -w 1680 -bg $BG -e '' & zsh ~/.xmonad/status.sh | dzen2 -xs 1 -ta r -fn $FN -h 16 -w 1440 -bg $BG -e '' & fi

# Start urxvt daemon urxvtd -q -f -o

# Volume manager thunar --daemon &

# Launch tray #stalonetray -i 5 --max-height 5 --ignore-icon-resize 1 --geometry 1x1-0+0 -bg $BG --skip-taskbar & stalonetray -t --skip-taskbar &

gpomme &

# Launch network manager nm-applet &

# Launch WM exec xmonad #dbus-launch --sh-syntax --exit-with-session xmonad

DBus version:

local/dbus 1.2.4-1 Freedesktop.org message bus system local/dbus-core 1.2.4-1 Freedesktop.org message bus system local/dbus-glib 0.78-1 GLib bindings for DBUS local/dbus-python 0.83.0-2 Python bindings for DBUS local/dbus-qt3 0.62-3 QT3 bindings for DBUS

I don't have all of gnome installed, but the few bits I have are from Gnome 2.24.{0,1} gconf version:

local/gconf 2.24.0-2 A configuration database system

-- Ricardo Martins * scarybox.net * GPG key: 0x1308F1B4

It works fine for me now when I remove the workaround, but I still think I will start the dbus session with the window manager from now on. Good work. /Anders Engström On Thu, Jan 22, 2009 at 01:39, Spencer Janssen wrote:

On Tue, Jan 20, 2009 at 04:51:08PM +0000, Ricardo Martins wrote:

...

Hi everyone.

Since yesterday I've been receiving an error dialog when launching Firefox. It says "An error occured while loading or saving configuration information for firefox. Some of your configuration settings may not work properly". Clicking on a "Details" button gives me the following:

"GConf Error: 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: Failed to execute dbus-launch to autolaunch D-Bus session)"

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.

The last three darcs builds I used were from 2009-01-12 (no problems), 2009-01-17 (I'm not sure if it had problems, since I usually suspend my laptop without rebooting or relaunching X for a few days) and 2009-01-19 (the problematic build).

I'd test the latest code, but I'm having trouble accessing the darcs repository.

Regards, -- Ricardo Martins * scarybox.net * GPG key: 0x1308F1B4

This should be fixed in darcs now. Please update, clean, rebuild and reinstall xmonad and contrib. Let us know whether this fixes the issue for you.

Cheers, Spencer Janssen _______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad