similar to: xterm "secure console" insecure

When I launch ssh sessions from xterms and exit them via the command line, the processes go away, but if I just kill the xterm window an ssh was launched from via a mouse click, the ssh.exe hangs around taking up system resources until I kill it via the task manager, if I can figure out which ssh.exes are the zombies. The same problem *does not* occur from a simple bash shell window (launched via

https://bugs.freedesktop.org/show_bug.cgi?id=75279 --- Comment #13 from Benoit Jacob <bjacob at mozilla.com> --- The work-around that works for us, and that we're considering landing, is to avoid calling XCloseDisplay and, in this case, just calling XSync to handle any pending errors in glxtest. Digging in the Gecko codebase, I found at least another instance where we avoid calling

CentOS Errata and Security Advisory 2007:0701 https://rhn.redhat.com/errata/RHSA-2007-0701.html The following updated files have been uploaded and are currently syncing to the mirrors: ia64: updates/ia64/RPMS/xterm-192-8.el4.ia64.rpm -- Pasi Pirhonen - upi@iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored -------------- next part -------------- A non-text attachment was

CentOS Errata and Security Advisory 2007:0701 https://rhn.redhat.com/errata/RHSA-2007-0701.html The following updated files have been uploaded and are currently syncing to the mirrors: s390: updates/s390/RPMS/xterm-192-8.el4.s390.rpm s390x: updates/s390x/RPMS/xterm-192-8.el4.s390x.rpm -- Pasi Pirhonen - upi@iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored -------------- next

Brian's fix works for me. I did up an SRPM (unsigned) with it in: http://linuxatlax.org/trevor/srpms/rxvt-2.6.PRE2-6.src.rpm Brian D. Winters <brianw@ALUMNI.CALTECH.EDU> wrote: > On Tue, Jun 08, 1999 at 10:24:29AM -0700, Zack wrote: > > in /etc/fstab: > > > > none /dev/pts devpts gid=5,mode=620 0 0 > > This is not sufficient when

I guess I never sent the message I was going to last week about xterm. [Noteto REW: If I did, kill this message...] It seems that sending xterm an excessively long escape sequence kills it (and perchance might be made to hack it, which would be quite bad.) The xterm in XFree86-3.2 is immune to this problem. I recommend everyone upgrade ASAP. -- - David A. Holland | VINO

debug1: X11 connection requested. debug2: fd 20 setting TCP_NODELAY debug2: fd 20 is O_NONBLOCK debug2: fd 20 is O_NONBLOCK debug1: channel 3: new [X11 connection from 127.0.0.1 port 47773] debug1: channel 3: open confirm rwindow 3000 rmax 35840 debug1: server_input_channel_req: channel 3 request exit-status reply 0 debug1: session_by_channel: unknown channel 3 debug1: dump: used 1 session 0

Sometimes when I use openssh (latest) and do find . or ls -lR /dev or similiar, my xterm 'freezes up', there is no way to fix it but to kill the xterm usually. This NEVER occurs in telnet. The error is completely reproducable when you come across it. ie: one may just be browsing the filesystem and when you come across this problem, you can launch another xterm and the EXACT same thing

Hi I'm trying to set the terminal size in /usr/share/vte/termcap/xterm, but it seems that CentOS doesn't look at this file. I know this works in REHL 4.7 and Fedora 10, 11. Does anyone know a work around to this? Thanks Marcelo

I have attempted to get wine functioning for several days but have been having no output recognizable as a windows program, rather the terminal acts much as though the output was that of a cat of a binary file and requires a reset to become useful again. I am running Slack 7.1 on 2.2.18 on a dual celeron machine using XFree86 4.0.2. All other programs are functioning normally. I have used

Hi, I have just installed asterisk under Fedora5, the program runs fine except the color is not correct, it's very dark, difficult to see. And if I select a part that part's color will be fine at least clear for read purpose. All I can do now is disabling color by changing the TERM environment variable to another value. Any help is greatly appreciated !! Thanks in advance.

CentOS Errata and Security Advisory CESA-2009:0018 xterm security update for CentOS 3 i386: https://rhn.redhat.com/errata/RHSA-2009-0018.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/xterm-179-11.EL3.i386.rpm source: updates/SRPMS/xterm-179-11.EL3.src.rpm You may update your CentOS-3 i386 installations by running the

CentOS Errata and Security Advisory CESA-2009:0018 xterm security update for CentOS 3 x86_64: https://rhn.redhat.com/errata/RHSA-2009-0018.html The following updated file has been uploaded and is currently syncing to the mirrors: x86_64: updates/x86_64/RPMS/xterm-179-11.EL3.x86_64.rpm source: updates/SRPMS/xterm-179-11.EL3.src.rpm You may update your CentOS-3 x86_64 installations by running

CentOS Errata and Security Advisory 2009:0018 https://rhn.redhat.com/errata/RHSA-2009-0018.html The following updated files have been uploaded and are currently syncing to the mirrors: s390: updates/s390/RPMS/xterm-192-8.el4_7.2.s390.rpm s390x: updates/s390x/RPMS/xterm-192-8.el4_7.2.s390x.rpm -- Pasi Pirhonen - upi at iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored

CentOS Errata and Security Advisory 2009:0018 https://rhn.redhat.com/errata/RHSA-2009-0018.html The following updated files have been uploaded and are currently syncing to the mirrors: ia64: updates/ia64/RPMS/xterm-179-11.EL3.ia64.rpm -- Pasi Pirhonen - upi at iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored -------------- next part -------------- A non-text attachment was

CentOS Errata and Security Advisory 2009:0018 https://rhn.redhat.com/errata/RHSA-2009-0018.html The following updated files have been uploaded and are currently syncing to the mirrors: ia64: updates/ia64/RPMS/xterm-192-8.el4_7.2.ia64.rpm -- Pasi Pirhonen - upi at iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored -------------- next part -------------- A non-text attachment was

CentOS Errata and Security Advisory 2009:0018 https://rhn.redhat.com/errata/RHSA-2009-0018.html The following updated files have been uploaded and are currently syncing to the mirrors: s390: updates/s390/RPMS/xterm-179-11.EL3.s390.rpm s390x: updates/s390x/RPMS/xterm-179-11.EL3.s390x.rpm -- Pasi Pirhonen - upi at iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored --------------

Hi List Has anyone got any clue of why on a centos 4.3 when I am logging in to the machine I am geting the following error tput: unknown terminal "xterm-color" do I am not using xterm-color I can not start top of any other except vi. Does anyone have any clue? Kind regards Per Qvindesland

Two versions of R 1. R-patched (compiled with X11 support, and tcl/tk for X11) 2. R-devel (compiled with native tcl/tk support, without-x) UI's 1. Terminal.app (or an Xterm) with an X server running. 2. IDLE (i.e. native Python GUI with native tkinter) with Rpy loaded. No X server. Packages with "problems" 1. tcltk 2. methods The "normal" combination is to use

Dear list, I would like to know if there is any way to include xterm escape sequences in R's prompt using options( prompt= XXX, continue= XXX ), where XXX can contain, for example, "\033[1;31mRed" for chancing text color to red (see http://www.frexx.de/xterm-256-notes/). If you do this, the color escape sequences work (with an appropriate terminal emulator, e.g., xterm under Linux),