Description of problem: This crash occurred in an openQA test: https://openqa.fedoraproject.org/tests/36382 . That test boots the live image, switches to a VT and fiddles about with packages a bit to ensure an update is available, then switches back to the desktop and just sits there for 10 minutes to see what notifications show up. During that ten minutes idle time, Shell crashed and the system wound up back at GDM, which you can see in the video on the Logs & Assets tab. This crash showed up ~1 second after the gnome-shell crash reported as https://bugzilla.redhat.com/show_bug.cgi?id=1379440 . Version-Release number of selected component: evolution-3.22.0-1.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/libexec/evolution/evolution-alarm-notify crash_function: pthread_cond_wait@@GLIBC_2.3.2 executable: /usr/libexec/evolution/evolution-alarm-notify global_pid: 1834 kernel: 4.8.0-0.rc6.git0.1.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 7 (4 frames) #0 pthread_cond_wait@@GLIBC_2.3.2 at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 __gthread_cond_wait at /usr/src/debug/gcc-6.2.1-20160916/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/x86_64-redhat-linux/bits/gthr-default.h:864 #2 std::condition_variable::wait at ../../../../../libstdc++-v3/src/c++11/condition_variable.cc:53 #3 std::_V2::condition_variable_any::wait<std::unique_lock<bmalloc::Mutex> > at /usr/include/c++/6.2.1/condition_variable:251
Created attachment 1204917 [details] File: backtrace
Created attachment 1204918 [details] File: cgroup
Created attachment 1204919 [details] File: core_backtrace
Created attachment 1204920 [details] File: dso_list
Created attachment 1204921 [details] File: environ
Created attachment 1204922 [details] File: limits
Created attachment 1204923 [details] File: maps
Created attachment 1204924 [details] File: mountinfo
Created attachment 1204925 [details] File: namespaces
Created attachment 1204926 [details] File: open_fds
Created attachment 1204927 [details] File: proc_pid_status
Created attachment 1204928 [details] File: var_log_messages
Thanks for a bug report. The ABRT is wrong, this crashed in g_log_abort(), after printing "Error reading events from display: Broken pipe", from which I suppose you run Wayland, which makes sense due to gnome-shell crashing. *** This bug has been marked as a duplicate of bug 1339331 ***