Description of problem: I was editing a past command. up-arrow, home, then I was typing a new start to the command. I don't think this is that helpful, though, as this does not realiably reproduce the error. It's is more likely to do with the moderately large data set I was working with at the time. I had just closed a very dense plot. Version-Release number of selected component: gnuplot-4.6.3-6.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: gnuplot crash_function: terminal_move_to_char executable: /usr/bin/gnuplot-wx kernel: 3.11.10-301.fc20.x86_64 runlevel: N 5 type: CCpp uid: 13013 Truncated backtrace: Thread no. 1 (8 frames) #0 terminal_move_to_char at terminal.c:572 #1 el_wgetc at read.c:439 #2 read_getcmd at read.c:247 #3 el_wgets at read.c:586 #4 el_gets at eln.c:80 #5 readline at readline.c:420 #6 read_line at ../../src/command.c:2669 #7 com_line at ../../src/command.c:314
Created attachment 879667 [details] File: backtrace
Created attachment 879668 [details] File: cgroup
Created attachment 879669 [details] File: core_backtrace
Created attachment 879670 [details] File: dso_list
Created attachment 879671 [details] File: exploitable
Created attachment 879672 [details] File: limits
Created attachment 879674 [details] File: maps
Created attachment 879675 [details] File: open_fds
Created attachment 879676 [details] File: proc_pid_status
Hmm, Gnuplot has crashed on my five times in about 10 hours of use since I upgraded to F20. Is anyone else have this sort of problem?
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.