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.
** Changed in: cupsys (Debian)
Importance: Unknown => Undecided
Bugwatch: Debian Bug tracker #425944 => None
Status: Fix Released => New
** Changed in: cupsys (Debian)
Importance: Undecided => Unknown
Bugwatch: None => Debian Bug tracker #425944
Status: New => Unknown
** Changed in: dbus (Ubuntu)
Sourcepackagename: cupsys => dbus
Status: Incomplete => Fix Released
--
MASTER [Feisty] cupsd leaking file descriptors (was: Multiple jobs are not
printed)
https://bugs.launchpad.net/bugs/112803
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
