Description of problem: I edited with "modifica appunti" Version-Release number of selected component: parcellite-1.1.7-2.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: parcellite crash_function: __mempcpy_sse2 executable: /usr/bin/parcellite kernel: 3.12.8-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 __mempcpy_sse2 at ../sysdeps/x86_64/memcpy.S:166 #1 _IO_default_xsputn at genops.c:463 #2 _IO_new_file_xsputn at fileops.c:1348 #3 _IO_fwrite at iofwrite.c:43 #4 save_history at history.c:290 #5 truncate_history at history.c:446 #6 append_item at history.c:392 #7 update_clipboard at main.c:416 #8 check_clipboards at main.c:536 #9 check_clipboards_tic at main.c:590
Created attachment 852886 [details] File: backtrace
Created attachment 852887 [details] File: cgroup
Created attachment 852888 [details] File: core_backtrace
Created attachment 852889 [details] File: dso_list
Created attachment 852890 [details] File: environ
Created attachment 852891 [details] File: exploitable
Created attachment 852892 [details] File: limits
Created attachment 852893 [details] File: maps
Created attachment 852894 [details] File: open_fds
Created attachment 852895 [details] File: proc_pid_status
Created attachment 852896 [details] File: var_log_messages
Another user experienced a similar problem: I "edited" a multiline item in the "persistent" archive. The crash happened at the next ctrl-alt-x (needed to show the persistend archive in my config). After the crash, the data in both volatile and persistent archive had been reset. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: parcellite crash_function: __mempcpy_sse2 executable: /usr/bin/parcellite kernel: 3.15.6-200.fc20.x86_64 package: parcellite-1.1.7-2.fc20 reason: parcellite killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
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.