Description of problem: I got this abrt report after updating my machine to the latest rawhide, rebooting it and then logging into the desktop. I've not done anything special. Version-Release number of selected component: krb5-auth-dialog-3.2.1-7.fc21 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: krb5-auth-dialog --auto crash_function: gtk_assistant_get_nth_page executable: /usr/bin/krb5-auth-dialog kernel: 3.14.0-0.rc1.git4.1.fc21.x86_64 runlevel: N 5 type: CCpp uid: 500 Truncated backtrace: Thread no. 1 (2 frames) #0 gtk_assistant_get_nth_page at /lib64/libgtk-3.so.0 #1 gtk_aspect_frame_class_intern_init at /lib64/libgtk-3.so.0
Created attachment 865942 [details] File: backtrace
Created attachment 865943 [details] File: cgroup
Created attachment 865944 [details] File: core_backtrace
Created attachment 865945 [details] File: dso_list
Created attachment 865946 [details] File: environ
Created attachment 865947 [details] File: exploitable
Created attachment 865948 [details] File: limits
Created attachment 865949 [details] File: maps
Created attachment 865950 [details] File: open_fds
Created attachment 865951 [details] File: proc_pid_status
Created attachment 865952 [details] File: var_log_messages
I'm experiencing this same crash on my Rawhide system as well.
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.