Skip to content

from an kmscon session tmux prints ^@uu on startup #49

Description

@x539

Wenn starting tmux from an kmscon session tmux prints ^@u before the first bash-prompt and u directly after.

I am using kmscon 8-8.fc22 (Fedora)
and
tmux 1.9a-5.fc22 / tmux 2.1 (git: dcc2843)

How to reproduce:

  • Start kmscon
    sudo kmscon --vt=/dev/tty3 --no-switchvt
  • Switch to TTY3
  • Start tmux
    $ tmux

Output:
^@u[myname@hostname] ~$ u

Activity

  1. nicm commented on Jul 14, 2015

    @nicm
    Member

    What is TERM set to inside and outside tmux? What is in your prompt?

  2. x539 commented on Jul 14, 2015

    @x539
    Author

    TERM is xterm-256color outside and screen-256color inside
    But it makes no difference if I set TERM to linux before starting tmux.

    As prompt I use powerline but same Issue with git-prompt or plain PS1='\$'

    The chars are only printed before/after the very first Prompt after starting tmux and not if I start tmux within tmux.

  3. nicm commented on Jul 14, 2015

    @nicm
    Member

    If you do C-b r after starting tmux do the characters disappear?

  4. x539 commented on Jul 14, 2015

    @x539
    Author

    No. Also if I tmux attach to that session, from a working Terminal, they are there.

    If I tmux attach to a open Session from kmscon I only get an extra u after the Prompt (in all attached clients).

  5. nicm commented on Jul 14, 2015

    @nicm
    Member

    Please do this to reproduce the problem:

    tmux -Ltest -f/dev/null -vvvv new

    Then "exit" and send me the tmux-*.log files that will be in the directory where you ran tmux.

  6. x539 commented on Jul 14, 2015

    @x539
    Author

    Here it is.

    On 14.07.2015 15:13, Nicholas Marriott wrote:

    Please do this to reproduce the problem:

    tmux -Ltest -vvvv new

    Then "exit" and send me the tmux-*.log files that will be in the directory where you ran tmux.

  7. nicm commented on Jul 14, 2015

    @nicm
    Member

    Weird... tmux sees ^@ and u keys. My bet is the terminal is responding weirdly to something we send.

    Do you still see this if you start tmux with TERM=vt100?

  8. x539 commented on Jul 14, 2015

    @x539
    Author

    No, with TERM=vt100 there is no Problem.

    I'm not sure where the ^ and @ come from. But the Terminal response for echo -e "\e[c" is 60;1;6;9;15cu.

    So it is a bug in kmscon ?

  9. nicm commented on Jul 14, 2015

    @nicm
    Member

    Yes it is, the response should end at the c. Probably there is a zero byte between the c and the u (zero is ^@).

  10. x539 commented on Jul 14, 2015

    @x539
    Author

    Thanks for the quick help. Bug is Identified, patched and reported Upstream.

  11. lock commented on Feb 17, 2020

    @lock

    This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

  12. locked and limited conversation to collaborators on Feb 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions