Hide Forgot
Version-Release number of selected component: gnome-abrt-1.2.3-2.fc24 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/python3 /usr/bin/gnome-abrt crash_function: ensure_row_visible executable: /usr/bin/python3.5 global_pid: 12307 kernel: 4.5.0-302.fc24.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 ensure_row_visible at gtklistbox.c:1500 #1 gtk_list_box_update_cursor at gtklistbox.c:1516 #2 gtk_list_box_select_and_activate_full at gtklistbox.c:1767 #3 gtk_list_box_multipress_gesture_released at gtklistbox.c:1964 #4 ffi_call_unix64 at ../src/x86/unix64.S:76 #5 ffi_call at ../src/x86/ffi64.c:525 #6 g_cclosure_marshal_generic_va at gclosure.c:1604 #7 _g_closure_invoke_va at gclosure.c:867 #10 gtk_gesture_multi_press_end at gtkgesturemultipress.c:282 #11 g_cclosure_marshal_VOID__BOXEDv at gmarshal.c:1950
Created attachment 1145759 [details] File: backtrace
Created attachment 1145760 [details] File: cgroup
Created attachment 1145761 [details] File: core_backtrace
Created attachment 1145762 [details] File: dso_list
Created attachment 1145763 [details] File: environ
Created attachment 1145764 [details] File: exploitable
Created attachment 1145765 [details] File: limits
Created attachment 1145766 [details] File: maps
Created attachment 1145767 [details] File: mountinfo
Created attachment 1145768 [details] File: namespaces
Created attachment 1145769 [details] File: open_fds
Created attachment 1145770 [details] File: proc_pid_status
Created attachment 1145771 [details] File: var_log_messages
Thank you for reporting this bug. Is it easily reproducible? Does it happen when you click one specific bug report or is it a case of special mouse click combination? Do you know how to reproduce it?
Similar problem has been detected: I was reporting a problem in another window and tried to switch for another app in the list in the background. reporter: libreport-2.7.1 backtrace_rating: 4 cmdline: /usr/bin/python3 /usr/bin/gnome-abrt crash_function: ensure_row_visible executable: /usr/bin/python3.5 global_pid: 10950 kernel: 4.6.3-300.fc24.x86_64 package: gnome-abrt-1.2.4-2.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: python3.5 killed by SIGSEGV reproducible: Not sure how to reproduce the problem runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I've just tried to open crash report but it disappeared right under the mouse pointer and then I got this crash ... reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/bin/python3 /usr/bin/gnome-abrt -p /var/spool/abrt/ccpp-2017-01-12-17:45:03-936 crash_function: ensure_row_visible executable: /usr/bin/python3.5 global_pid: 1238 kernel: 4.8.15-200.fc24.x86_64 package: gnome-abrt-1.2.4-3.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: python3.5 killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Still present in Fedora 26, see https://bugzilla.redhat.com/show_bug.cgi?id=1474518 and https://bugzilla.redhat.com/show_bug.cgi?id=1463663. (In reply to Rafal Luzynski from comment #14) > Thank you for reporting this bug. Is it easily reproducible? Does it happen > when you click one specific bug report or is it a case of special mouse > click combination? Do you know how to reproduce it? (In reply to Karel Volný from comment #16) > Similar problem has been detected: > > I've just tried to open crash report but it disappeared right under the > mouse pointer and then I got this crash ... Same thing happened to me, see https://bugzilla.redhat.com/show_bug.cgi?id=1474518. This bug is not easily reproducible, but it seems like it always happens the same way when clicking on a crash report at the moment it is being deleted on the backend.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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.
Please change the Fedora version to 26.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.