Bug#756068: gdm3 blocks SIGUSR1 for all applications

[Mathieu Desnoyers]

The following upstream commit appears to take care
of this issue:

commit ef6954833cf43bef8306823d7fcfb6a04b903ad7
Author: Ray Strode <rstrode at redhat.com>
Date:   Fri May 30 10:26:02 2014 -0400

    worker: don't block SIGUSR1
    
    When the slaves were folded into the main manager process, we had
    to add support for detecting multiple simultaneous X servers starting
    up.
    
    We did that by creating a detected thread to listen for SIGUSR1 and
    then examining the siginfo to find out which X server is ready.
    
    In order to ensure only the dedicated thread received the SIGUSR1
    signals from the X server we blocked SIGUSR1 from the main thread.
    
    That blocked signal is inherited to the worker processes and the
    session.  Some programs depend on SIGUSR1 but don't explicitly unblock
    SIGUSR1 at start up, since the signal is presumed to be unblocked out
    the box.
    
    This commit makes sure SIGUSR1 is unblocked before starting the session
    to keep these programs functioning correctly.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=731228

Would it be possible to make sure it makes its way into Jessie ?

Thanks,

Mathieu

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com