I've looking for why is SIGPIPE ignored in gksu process, and I found that it's caused by communication with gconfd server. When a application connect to the gconfd daemon to get properties, the underlaying communication with CORBA it's ignoring SIGPIPE signal to avoid that if server crash, the process receive the signal and terminate.
package: liborbit2 1:2.14.12-0.1 file: linc2/src/linc.c (line: 247 see comment why is signal ignored).. -- Wireshark halts in Capture Interfaces window when started using gksu (Hardy, Intrepid) https://bugs.launchpad.net/bugs/198884 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
