You are not logged in.
Pages: 1
I have a weird configuration problem with screen. I want an xterm running screen to automatically start when I log in. I do this by running xterm -e screen. This is not a problem. What is weird is that I have
screen -t files 1 vifm
screen -t log 2 tail -f /var/log/everything.log
in my .screenrc and this works fine if I open xterm then type screen, but if I run xterm -e screen vifm segfaults and the tail command just hangs with a blank screen. Any ideas what could be going wrong?
Offline
I've had all sorts of problems with 'xterm -e screen' in the past, and if I recall, ended up using a wrapper script to sleep before invoking screen.
I now use urxvt and have had no problems. I would be suspecting xterm is the cause of the problem here too, but as to a elegant solution, I'm not sure.
Offline
Just guessing - could it be an environment problem?
I.e. does the segfault occur only when you autostarted xterm -e screen? Or does it segfault as well when you called xterm -e screen from a running xterm?
In the former case xterm probably does not run in your usual environment but the one set up while running .xinit (or the like, depending how you start your DE/WM). I had problems of this kind running xterms from the IceWM command line which turned out to know of the old environment only.
To know or not to know ...
... the questions remain forever.
Offline
Just guessing - could it be an environment problem?
I.e. does the segfault occur only when you autostarted xterm -e screen? Or does it segfault as well when you called xterm -e screen from a running xterm?
The same thing happens with autostart and calling xterm -e screen from a running xterm. Maybe I'll give urxvt a try.
Offline
you could also try this workaround, it's gotten me results in the past.
xterm -e bash -cl "screen"
if that doesn't work i also suggest urxvt.
That worked, Thanks!
Offline
Pages: 1