when launched from terminal, lyx destroys terminal's newline behaviour

[Christopher Barrington-Leigh]

When I launch LyX from the command line, in the background, the terminal is left unusable.
Newlines do not work and I cannot see what I type.

This happens every time with LyX and never with any other application I use.

I'm using the latest updated 13.04

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: lyx 2.0.3-3
ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
Uname: Linux 3.8.0-22-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Wed May 29 15:24:06 2013
InstallationDate: Installed on 2013-03-18 (71 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318)
MarkForUpload: True
SourcePackage: lyx
UpgradeStatus: No upgrade log present (probably fresh install)

[Scott Kostyshak (scott-kostyshak)]

Can you give an example of how you launch LyX?

Which of the following are you currently using?
    lyx &
    lyx > /dev/null 2>&1 &
    nohup lyx &

Does the problem still happen if you use one of the others?

Just a guess (I really don't know much about this stuff), but maybe LyX is writing characters of a different encoding, which confuses the terminal?

What happens if you run one of the following after you start having the problem?
    reset (same as 'tset')
    stty sane

Also note that there is an Ubuntu PPA which will allow you to use the latest stable version, which is currently 2.0.6:
http://wiki.lyx.org/LyX/LyXOnUbuntu#toc3

[Scott Kostyshak (scott-kostyshak)]

Without more information, I'm not sure there is anything we can do (except assume the bug was fixed). I vote to close this bug soon if no new information is posted.

[Christopher Barrington-Leigh (cpbl)]

Yep, I missed your 2013 comment. Sorry.
I think this still has happened within the last 6 months, but it is certainly no longer regular / easily reproducible.
So we can assume it's fixed.

[Scott Kostyshak (scott-kostyshak)]

No problem, Christopher. Thanks for the update!

[Juhani Numminen (jsonic)]

In 2014, Scott and Christopher concluded that this bug can be closed.