|Summary:||History (and "history") not working on new octave-2.1.73|
|Product:||[Fedora] Fedora||Reporter:||Piergiorgio Sartor <piergiorgio.sartor>|
|Component:||octave-forge||Assignee:||Quentin Spencer <qspencer>|
|Status:||CLOSED NEXTRELEASE||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2006-03-27 21:43:25 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:||186964|
Description Piergiorgio Sartor 2006-03-27 19:10:58 UTC
Description of problem: After launching the new octave, from terminal, the history seems not to be "enabled", i.e. there is no history. Version-Release number of selected component (if applicable): 2.1.73-1 How reproducible: At the moment, it seems very often, but somehow not always, once it happen the history was updated (don't know if something special happened). Steps to Reproduce: 1. Upgrade from 2.1.72-3 to 2.1.73-1 (maybe important). 2. Start "octave". 3. Type some commands, like "ls", "plot(1:10)"... 4. History back, with arrow-up or "history" command. Actual results: The new commands are not browsed, only the one from the previous session (eventually from 2.1.72) are available and "history" does not return, of course, nothing new. Expected results: The immediate history should be browsable and available. Additional info: More funny is the following, if the ~/.octave_hist file is empty (> ~/.octave_hist), or not present (rm ~/.octave_hist), the "history" command produces a nice segmentation fault. In 2.1.72 this was not happening, since "history" returned: 1 history So, the history is always not empty.
Comment 1 Quentin Spencer 2006-03-27 21:43:25 UTC
I was partially able to duplicate this. I am still not sure what was causing it, but the problem appears to be somehow related to the incompatibility of octave-2.1.73-1 and octave-forge-2006.03.17-1 (see bug 186966). Only with both of these installed simulaneously could I duplicate the problem of not seeing past commands with the up arrow. Removing octave-forge, or installing a recompiled version of octave-forge seemed to make the problem go away. I was not able to create a core dump. I am marking this as an octave-forge bug, dependent on 186966, and I am closing it assuming that the forthcoming release of octave-forge-2006.03.17-2 will make the problem go away.