bugGNU Screen - Bugs: bug #26633, screen -t title" will cause...

 
 

bug #26633: screen -t title" will cause screen program hanged

Submitter:  Ray Wang <rawang>
Submitted:  Thu 21 May 2009 09:46:56 AM UTC
   
 
Category:  Crash/Freeze/Infloop Severity:  3 - Normal
Priority:  * 5 - Normal Status:  Need Info
Privacy:  Public Assigned to:  None
Open/Closed:  Open Release:  4.0.2
Fixed Release:  None Planned Release:  None
Work Required:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Wed 27 May 2009 02:17:14 AM UTC, comment #8: 

Actually, I use some control character to make up my terminal prompt, is the reason why my screen get hanged?

I use opensuse 11.1 x86 and the shell is bash,

$ echo $PS1 | cat -v
\[\033[36;1m\]\u\[\033[0m\]:\[\033[33;1m\]\w\[\033[0m\]>

$ echo $PROMPT_COMMAND | cat -v
echo -ne "\033]0;$(pwd)\007"

$ rpm -q screen
screen-4.0.2-162.34

Ray Wang <rawang>
Tue 26 May 2009 05:59:29 PM UTC, comment #7: 

Well, that should invoke the "autoaka" function, so it's likely some sort of interaction with your prompt string? Inside of screen, what shell are you using? What do you get for:

$ echo $PS1 | cat -v
$ echo $PROMPT_COMMAND | cat -v

What do you get for

$ dpkg -l screen | cat

?

Micah Cowan <micahcowan>
Tue 26 May 2009 03:14:50 AM UTC, comment #6: 

after several times experiments.
I found when 'shelltitle "> |" ' is functional, the screen will be hanged.  if I comment out that line. the "screen -t blah" works.
Have you any idea?
Thank you so much! :)

Ray Wang <rawang>
Mon 25 May 2009 07:53:41 PM UTC, comment #5: 

Hm, unfortunately, I'm still unable to reproduce it here. :\

You'll have to try to isolate it by throwing out portions of the config file until you find the one line that triggers it...

Micah Cowan <micahcowan>
Sat 23 May 2009 05:34:29 PM UTC, comment #4: 

Thanks a looot!
the first one "env - TERM="$TERM" screen -t blah" won't work
the second one "screen -c /dev/null -t blah" works
the third one "bash -c 'screen -t blah' won't work
that means my configuration file have some problem.
here is my .screenrc, also it is attached

vbell off
startup_message off
defscrollback 5000
shelltitle "> |"
bindkey "^[-" prev
bindkey "^[=" next
caption always "%{Wb}%-w%{wr}[%n]%{-}%+w"
hardstatus alwayslastline "%{R}[%n %t] %=%{G}[%Y/%m/%d %D %c:%s] %{Y}${LOGNAME}@%H"


(file #18187)

Ray Wang <rawang>
Fri 22 May 2009 04:40:22 PM UTC, comment #3: 

Well, actually, it's not the act of setting TERM: that's already been set. What that command does is completely wipe out all other environment variables, and also prevent screen from loading the ~/.screenrc and /etc/screenrc files.

Since it works, this means that there's either something in your environment that screen doesn't like, or something in your ~/.screenrc. Find out by trying each of these variations:


$ env - TERM="$TERM" screen -t blah

$ screen -c /dev/null -t blah

If the "env" one works but not the "screen -c ..." one, then it must be something in your environment. If the second one works but not the first, then it must be something in your ~/.screenrc.

I suppose for completeness I should have you run:

$ bash -c 'screen -t blah'

to see if that still hangs (I would expect it to: otherwise there's something very funky with your shell setup).

Once you determine whether it's the environment or the config file, try to isolate where the problem is coming from. For instance, in the config file, you could save a copy, then throw out half the contents. If it starts working, the problem was in the thrown-out half. Keep throwing out contents until you've figured out where the problem was (and then please let me know!)

Micah Cowan <micahcowan>
Fri 22 May 2009 07:34:05 AM UTC, comment #2: 

yes, that works if I set TEAM as you suggest. That means my configuration may have some conflicts with the -t option?
Thanks a lot.

Ray Wang <rawang>
Thu 21 May 2009 07:27:48 PM UTC, comment #1: 

Can't reproduce on Ubuntu 8.10 x86, myself. Need more reproduction info.

Do you still see this issue if you run:

  env - TERM="$TERM" screen -c /dev/null -t blah

?

(That weeds out any possible interference from environment variables or screenrc)

If it suddenly works with the above, then try to find out what in your ~/.screenrc, /etc/screenrc, or environment is causing screen to misbehave.

If it still hangs, then please specify what the value of "$TERM" is, and what version of the screen package you're using. I tested with Ubuntu's 4.0.3-11.

Micah Cowan <micahcowan>
Thu 21 May 2009 09:46:56 AM UTC, original submission:  

when i issue "screen -t blah", and want to have a titled screen shell, it gets handed, i test it on opensuse 11.1 x86 and ubuntu 8.10 x86, it happens on both systems.

Ray Wang <rawang>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files
file #18187:  .screenrc added by rawang (709B - application/octet-stream)
file #18173:  Screenshot--home-ray.png added by rawang (6KiB - image/png - screenshot when i type command, and it gets hanged)
file #18174:  Screenshot--home-ray-1.png added by rawang (12KiB - image/png - screenshot when i type command, and it gets hanged)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by micahcowan (Posted a comment)
  • -email is unavailable- added by rawang (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2009-05-23 rawang Attached File- Added .screenrc, #18187
    2009-05-21 micahcowan StatusNone Need Info
    2009-05-21 rawang Attached File- Added Screenshot--home-ray.png, #18173
        Attached File- Added Screenshot--home-ray-1.png, #18174

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code