Your message dated Fri, 8 Aug 2014 21:35:45 +0100
with message-id
<CAD=6czp7-eqfnqehhorudcl54jhr9bfwgwnrsptfqrezrla...@mail.gmail.com>
and subject line Close #585504 - gnome-session relies on default SIGCHLD
handler but does not set it explicitly
has caused the Debian Bug report #585504,
regarding gnome-session relies on default SIGCHLD handler but does not set it
explicitly
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
585504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585504
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnome-session
Version: 2.30.0-1
Severity: normal
gnome-session relies on the default SIGCHLD behavior to get the
results of waitpid() relatively early in its launch.
However, it never explicitly demands the default handler. So if it is
exec'ed from a process which has opted to ignore SIGCHLD, and it
inherits that ignore, it will run forever in a tight waitpid() loop
(according to strace).
So somewhere early in its existence, gnome-session should explicitly
demand the default signal handler for SIGCHLD.
(yes, processes exec'ing gnome-session should probably not ask for
SIGCHLD to be ignored, but not every process can predict what it will
be exec'ing. Since gnome-session relies on the default behavior, and
can tell when SIGCHLD would be ignored, gnome-session should
explicitly request the default behavior from the system)
--dkg
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing'), (200, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
version: 3.12.1-3
I'm closing this bug now since it's unreproducible and it works fine here.
if you can still reproduce it feel free to reopen and provide more info.
thanks
regards
althaser
--- End Message ---
