Re: Terminal signal handling
On 24 November 2013 19:32, Peter Oliver
<lists.fedoraproject.org(a)mavit.org.uk> wrote:
I've started having a couple of odd issues with terminals in the
last week
or so on my Fedora 19 desktop machine and I think they're probably related.
My laptop, also running Fedora 19, appears to be unaffected.
Sometimes, terminals are unresponsive to ^Z, and I'm unable to suspend a
process by using 'kill -TSTP' on that process. However, 'kill -STOP'
works.
Running 'stty -a' shows 'susp = ^Z' as expected.
This affects both xterm and gnome-terminal. It affects all children of an
affected process. However, sometimes if I start a new terminal from Gnome
Shell it will not be affected.
A workaround is to run "exec ksh -c 'exec $SHELL'" from an affected
terminal. It appears that ksh does some initialisation that bash, dash and
tcsh do not.
My second problem is that alpine is sometimes unresponsive to changes in
terminal size. I suspect that SIGWINCH is not being handled correctly.
See
http://superuser.com/questions/667380/sigint-and-sigtstp-ignored-by-most-...
for an example of someone with similar but slightly different symptoms (he
has problems with SIGINT, but my SIGINT works fine).
Using 'pstree -ps $$' and then working my way up the tree with 'grep SigBlk
/proc/$pid/status' shows 'SigBlk: 016717d03fdb4a00' for gnome-session but
'SigBlk: 0000000000000000' for its parents. This makes me suspect that the
problem originates in gnome-session.
Any ideas?
If you're using the nvidia proprietary driver 331.20 then it's probably:
https://bugzilla.redhat.com/show_bug.cgi?id=1028272
--
Peter Oliver
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
--
Ahmad Samir