From: Matthew W. O. <wei...@gr...> - 2003-04-12 00:21:20
|
-- Keith R. John Warno <kr...@op...> wrote (on Friday, 11 April 2003, 07:05 PM -0400): > ROX-Session 0.1.18 -- used in combination w/ ROX-Filer and (probably) > any window manager -- will happily hang the X session if: > > 1) an app that wants to read from stdin is clicked on via > ROX-Filer > 2) said app is too braindead to realize that stdin is not > connected to a terminal > > For example, if you were to click on /bin/passwd via ROX-Filer, it > should bomb out with an error like "passwd: Conversation error" (meaning > it could not get stdin input), and you should see this error via > ROX-Session's error log facility. > > However, if you were to, say, make a script with the following two > lines, make it executable and then click on it via ROX-Filer running > under ROX-Session, your X session might/will hang: > > #!/bin/bash > less /etc/passwd > > That is with less version 378, and bash 2.05b. That didn't do anything at all for me. > [ No, I do not have a script that does the above; I just used that as an > example. I do, however, use a script that does the something like the > following: Would have been easier just to give these in the first place! ;-) > #!/bin/bash > exec xterm -e view_rpm_script "$@" > > where in view_rpm_script we have: > > #!/bin/bash > rpm -qivlp "$@"|less > > for viewing RPM information if a given file. I went and clicked on the > view_rpm_script itself (thereby giving no arguments), rpm bitched to > stderr about no arguments, nothing was piped to less, and the X session > hung as less waited for a 'q' stroke on stdin. ] Okay, so I'm on a debian machine, so rpm doesn't work (mainly due to no RPM packages, which is really just fine by me!). But probably the equivalent is something like using 'dpkg -L' or 'apt-cache show', so I made a script like yours using similar arguments and piping to less; the other script (the first) I left the same. Worked fine for me, just clicking on it. Tries to run, can't, gives me an empty 'less' session, which I exit by hitting 'q'. > I would like to know whether anyone can or cannot reproduce this. My > system underwent a major overhaul, so it is possible something is f'ed > up. :) I can, however, reproduce this with at least two WMs: icewm and > twm. And, by the way, this was under blackbox; also running under gdm, but that shouldn't matter. Good luck debugging! -- Matthew Weier O'Phinney ma...@we... http://matthew.weierophinney.net |