I still could not determine how to trigger that problem with a normal system, however, with some incredible hideous hacks in dbus I was able to force this condition (calling dbus-launch).
I verified that the problem is indeed that _dbus_get_autolaunch_address() does not close the reading end of the pipe in dbus 1.0.2.
This has been fixed in gutsy recently with dbus 1.1.1. The patch for Feisty is trivial, will prepare an SRU now.
I still could not determine how to trigger that problem with a normal system, however, with some incredible hideous hacks in dbus I was able to force this condition (calling dbus-launch).
I verified that the problem is indeed that _dbus_get_ autolaunch_ address( ) does not close the reading end of the pipe in dbus 1.0.2.
This has been fixed in gutsy recently with dbus 1.1.1. The patch for Feisty is trivial, will prepare an SRU now.