gconfd does not unblock signals properly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gconf |
Fix Released
|
Medium
|
|||
gconf (Ubuntu) |
Fix Released
|
Medium
|
Ubuntu Desktop Bugs |
Bug Description
Binary package hint: libgconf2-4
This bug has already been submitted to upstream, but they won't react:
http://
When gconfd-2 is started it does not unblock signals properly. This becomes an
issue when the following two conditions are satisfied:
- The gconf library is used from a process which has previously blocked some
signals
- The process is responsible for launching the daemon for first time.
If that happens gconfd-2 will not receive some signals which are supposed to be
delivered, such as SIGHUP, SIGTERM...
Steps to reproduce:
1. kill any gconfd-2 process
2. use the library from a process which blocks signals like HUP, TERM
3. try to send SIGTERM or SIGHUP signals
Related branches
Changed in gconf: | |
status: | Unknown → New |
Changed in gconf: | |
status: | New → Fix Released |
Changed in gconf: | |
importance: | Unknown → Medium |
Here is a patch that fixes the problem by unblocking all the signals