Revision history [back]

I wouldn't necessarily call this an "issue", but more an unfortunate consequence of how teleop_twist_keyboard is implemented and how that interacts with the way roslaunch coordinates / starts things.

In summary: teleop_twist_keyboard uses certain bits of infrastructure to be able to read your keyboard presses from the terminal it was started in. roslaunch wraps stdin, stdout and stderr and then changes the way these interact with the terminal.

To work-around this you could start teleop_twist_keyboard in a separate terminal. You can do this with a launch prefix. Something like xterm -e should work.