It looks like your shell is exiting after 22804 write(2, "sh: vifm: command not found\n", 28) = 28 22802 <... epoll_wait resumed> {{EPOLLIN, {u32=14, u64=14}}}, 32, 484) = 1 22804 exit_group(127) = ?
but that has nothing to do with the error you are seeing. In fact, that error does not appear in the strace at all. Can you strace the server then the client that fails to attach to different files? Preferably with a new user with no shell startup files. On Fri, Mar 04, 2011 at 06:52:41PM +0530, Vaibhav Bedia wrote: > Hi Micah, > > On Fri, Mar 4, 2011 at 12:12 AM, Micah Cowan <mi...@cowan.name> wrote: > > (03/02/2011 09:10 PM), Vaibhav Bedia wrote: > >> Hi, > >> > >> I am using tmux-1.4. I just started getting the error (open terminal > >> failed: missing or unsuitable terminal: xterm) when trying to attach > >> to a pre-existing session. > > > > That error message would indicate that a terminfo database entry can't > > be found for "xterm". Make sure that TERMINFO isn't set (or else, > > explicitly set it to where it should be able to find its terminfo > > database). If setting it explicitly has a positive effect, then perhaps > > your tmux 1.4 was built with a different idea of where terminfo stuff > > should be, than tmux 1.3 was. Were they built/linked against different > > versions of ncurses? Was tmux 1.4 obtained or built using different > > means than tmux 1.3 was? > > Yes its with different versions of ncurses and libevent. I was using a > pre-compiled binary for tmux-1.3 and even libevent path was set to > someone else's compiled version on a server. > > I am not sure about this but since both are in the same machine i > guess except the libevent and ncurses part the build procedure was the > same. > > > > > In addition to playing with TERMINFO, you might also try copying > > /usr/share/terminfo/x/* (or wherever it is) into ~/.terminfo/x/. > > > > Good paths to try for TERMINFO include /etc/terminfo, /lib/terminfo, and > > /usr/share/terminfo. Find out which one has an x/xterm in it and set it > > to that. > > > > Setting TERMINFO manually to /usr/share/terminfo worked. > > > If any of these tricks work, then the next step would be to find out why > > it's not looking at that place by default. > > > > However i have a really strange observation. > > I just exported TERMINFO variable and then launched a tmux session. > Then i detached from it and logged out from the server i was working > on. > > When i again log in i again check TERMINFO and its not set to anything > (since i just did an export earlier). > > But now i can reattach to the session i had invoked earlier. > > So essentially i am in the same state i was in earlier but now its working. > > If TERMINFO is not set when i want to launch a new session it fails > with the same error message about missing term. > > I can't figure out what's happening here. > > -- > Regards, > Vaibhav > > ------------------------------------------------------------------------------ > What You Don't Know About Data Connectivity CAN Hurt You > This paper provides an overview of data connectivity, details > its effect on application quality, and explores various alternative > solutions. http://p.sf.net/sfu/progress-d2d > _______________________________________________ > tmux-users mailing list > tmux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tmux-users ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users