Opened 13 years ago

Closed 13 years ago

Last modified 11 years ago

#2891 closed defect (invalid)

Terminal activity not consistent about storing history buffer

Reported by: greenfeld Owned by: sayamindu
Priority: Unspecified by Maintainer Milestone:
Component: Terminal Version: 0.92.x
Severity: Unspecified Keywords:
Cc: pbrobinson Distribution/OS: Fedora
Bug Status: Unconfirmed


Testing sugar-terminal-33 for Fedora 15, I noticed that I could no longer do a bunch of stuff in a terminal session, exit the Terminal activity, and then resume the session intact with the history buffer intact. This seems to be pretty consistent, and might be related to the zoom button change.

Downgrading to sugar-terminal-32 restores the ability to view the history buffer from the last session, at least in some cases. I seem to recall this being the historical behavior, although I thought it was more consistent.

Unless we are getting rid of this ability for security reasons perhaps it should be restored (although personally this is the only Terminal program I know of which saves session history without manual configuration.)

Given the version variation this could be more than one bug.


  1. Open the Terminal activity.
  2. Run ls -l /bin or something similarly long in content. You might also have to run something like nano and then exit to get a good save(?).
  3. Close the Terminal activity.
  4. Restart the saved Terminal object in the Journal from the previous step and look at the screen/backscroll data.
  5. Close and restart the Terminal session again and you might lose the backscroll data that was saved(?).

Change History (2)

comment:1 Changed 13 years ago by greenfeld

  • Resolution set to invalid
  • Status changed from new to closed
  • Version changed from Unspecified to 0.92.x

Figured it out; closing the activity from within the shell via Ctrl-D or similar causes Sugar to lose the tab's data, even if it was the last tab open.

History backscroll data and tab information is saved properly if the Sugar Stop button is used.

Need to file a new (cleaner) ticket.

comment:2 Changed 11 years ago by dnarvaez

  • Milestone 0.92 deleted

Milestone 0.92 deleted

Note: See TracTickets for help on using tickets.