Hide Forgot
Description of problem: I was copying and pasting the contents of a file in pluma. Version-Release number of selected component: clipit-1.4.2-9.fc22 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: clipit crash_function: gtk_selection_data_get_text executable: /usr/bin/clipit global_pid: 17922 kernel: 4.2.8-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (3 frames) #7 gtk_selection_data_get_text at gtkselection.c:1582 #8 request_text_received_func at gtkclipboard.c:929 #9 selection_received at gtkclipboard.c:865 Potential duplicate: bug 1100492
Created attachment 1113861 [details] File: backtrace
Created attachment 1113862 [details] File: cgroup
Created attachment 1113863 [details] File: core_backtrace
Created attachment 1113864 [details] File: dso_list
Created attachment 1113865 [details] File: environ
Created attachment 1113866 [details] File: limits
Created attachment 1113867 [details] File: maps
Created attachment 1113868 [details] File: mountinfo
Created attachment 1113869 [details] File: namespaces
Created attachment 1113870 [details] File: open_fds
Created attachment 1113871 [details] File: proc_pid_status
Created attachment 1113872 [details] File: var_log_messages
Similar problem has been detected: I was cut and pasting quite long strings into a field in a web page in Firefox when testing input field validation. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: clipit crash_function: gtk_selection_data_get_text executable: /usr/bin/clipit global_pid: 2278 kernel: 4.4.8-200.fc22.x86_64 package: clipit-1.4.2-9.fc22 reason: clipit killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.