Carlos E. R. wrote:
I'll make a very wild guess - I don't have real knowledge of this, but I have a suspicion.
KDE does lots of things, and it has a kind of gnupg agent for use by programs needing gpg. Probably, if there is a .gnupg directory this program or whatever gets started and provides services. Then, it will be this program which is interacting with yours strangely.
You could have a look around these:
/opt/kde3/bin/kgpg /opt/kde3/bin/kgpgcertmanager /opt/kde3/share/apps/kgpg /opt/kde3/share/apps/kgpgcertmanager
Thanks. But what I've found is, if there is a .gnupg directory present in my home directory and I am logging it at the console via KDM, my kde session appears to start via the following command: gpg-agent --daemon --no-detach --keep-display ssh-agent /etc/X11/xinit/xinitrc If the .gnupg directory does not exsist my session starts with the following command: ssh-agent /etc/X11/xinit/xinitrc When my session starts via the gpg-agent, no realtime signals can be received by any of my applications. It appears the gpg-agent is causing me to inherate some sort of blocking mask. Don't know if that is "proper" or not but have found that if I just use sigprocmask to insure the signals I want to use are in fact unblocked, I'm ok. I wish I could find some information about this "inherated blocking mask" though because I'm not very comfortable that I should "HAVE" to do this. Regards Mark