Skip to content
This repository has been archived by the owner on Nov 11, 2018. It is now read-only.

Segmentation Fault when using history recall #43

Closed
lobhater opened this issue May 19, 2013 · 6 comments
Closed

Segmentation Fault when using history recall #43

lobhater opened this issue May 19, 2013 · 6 comments

Comments

@lobhater
Copy link

username@host:~$ finalterm
** Message: TerminalOutput.vala:337: Partially supported control sequence: '\u001b]0;username@host: ~\u0007' (TERMINAL_STREAM_STREAM_ELEMENT_CONTROL_SEQUENCE_TYPE_SET_TEXT_PARAMETERS)
** Message: TerminalOutput.vala:252: Command mode entered
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: ''
** Message: Terminal.vala:112: Command updated: 'ssh username@192.168.1.103'
Segmentation fault (core dumped)

@lobhater
Copy link
Author

The clear command creates a new prompt at the top of the terminal but does not erase the old text below

@p-e-w
Copy link
Owner

p-e-w commented May 19, 2013

The clear issue is a duplicate (#18). About the other issue: How can I reproduce?

@lobhater
Copy link
Author

I always have to launch final term from the bash shell using the sudo
command otherwise final term doesn't work at all. The segmentation fault
occurs when I use the up or down arrows to recall the command history. The
segmentation fault error is displayed im the original bash shell terminal
used to launch final term. It is very hit and miss the error does not
always occur. Please let me know what other information would be helpful?
On May 19, 2013 2:45 PM, "Philipp Emanuel Weidmann" <
notifications@github.com> wrote:

The clear issue is a duplicate (#18#18).
About the other issue: How can I reproduce?


Reply to this email directly or view it on GitHubhttps://github.com//issues/43#issuecomment-18124444
.

@p-e-w
Copy link
Owner

p-e-w commented May 21, 2013

I always have to launch final term from the bash shell using the sudo command otherwise final term doesn't work at all.

That's the first time I hear of this. Which distro are you on? How did you install?

@p-e-w
Copy link
Owner

p-e-w commented May 21, 2013

BTW I strongly advise against running Final Term as sudo. It's simply not stable enough for that.

@p-e-w
Copy link
Owner

p-e-w commented Jan 10, 2014

Closing this because I cannot reproduce it using the instructions provided.

@p-e-w p-e-w closed this as completed Jan 10, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants