Version-Release number of selected component: udev-browse-0.3-3.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: udev-browse crash_function: g_type_check_instance_cast executable: /usr/bin/udev-browse kernel: 3.14.0-0.rc2.git2.1.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance_cast at gtype.c:4002 #1 cell_info_free at gtktreeviewaccessible.c:106 #2 iter_remove_or_steal at ghash.c:789 #3 g_hash_table_iter_remove at ghash.c:816 #4 gtk_tree_view_accessible_do_remove_column at gtktreeviewaccessible.c:1752 #5 _gtk_tree_view_accessible_remove_column at gtktreeviewaccessible.c:1784 #6 gtk_tree_view_remove_column at gtktreeview.c:11935 #7 gtk_tree_view_destroy at gtktreeview.c:2026 #12 gtk_widget_dispose at gtkwidget.c:11312 #14 gtk_scrolled_window_forall at gtkscrolledwindow.c:1459
Created attachment 866404 [details] File: backtrace
Created attachment 866405 [details] File: cgroup
Created attachment 866406 [details] File: core_backtrace
Created attachment 866407 [details] File: dso_list
Created attachment 866408 [details] File: environ
Created attachment 866409 [details] File: exploitable
Created attachment 866410 [details] File: limits
Created attachment 866411 [details] File: maps
Created attachment 866412 [details] File: open_fds
Created attachment 866413 [details] File: proc_pid_status
Created attachment 866414 [details] File: var_log_messages
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
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.