GNOME Bugzilla – Bug 655878
[abrt] evolution-3.1.4-1.fc16: _gdk_x11_display_error_event: Process /usr/libexec/evolution/3.2/evolution-alarm-notify was killed by signal 5 (SIGTRAP)
Last modified: 2013-08-23 18:28:13 UTC
Moving this from a downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=727625 abrt version: 2.0.5 backtrace_rating: 4 cmdline: /usr/libexec/evolution/3.2/evolution-alarm-notify comment: during a yum update crash_function: _gdk_x11_display_error_event executable: /usr/libexec/evolution/3.2/evolution-alarm-notify kernel: 3.1.0-0.rc0.git12.1.fc17.x86_64 reason: Process /usr/libexec/evolution/3.2/evolution-alarm-notify was killed by signal 5 (SIGTRAP) time: Mon Aug 1 07:44:27 2011 uid: 500 username: nim var_log_messages: Aug 1 07:44:29 arekh abrt[24021]: saved core dump of pid 10016 (/usr/libexec/evolution/3.2/evolution-alarm-notify) to /var/spool/abrt/ccpp-2011-08-01-07:44:27-10016.new/coredump (12726272 bytes) xsession_errors: (evolution-alarm-notify:27651): GLib-GIO-WARNING **: Your application does not implement g_application_activate() and has no handlers connected to the 'activate' signal. It should do one of these. warning: core file may not match specified executable file. Missing separate debuginfo for /lib64/libudev.so.0 Try: yum --disablerepo='*' --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/38/211e816387583362a36fd100f41998c3904cef /var/cache/abrt-di/usr/lib/debug/.build-id/38/211e816387583362a36fd100f41998c3904cef.1 [New LWP 10016] [New LWP 10027] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/libexec/evolution/3.2/evolution-alarm-notify'. Program terminated with signal 5, Trace/breakpoint trap.
+ Trace 228008
Thread 1 (Thread 0x7f25db34a960 (LWP 10016))
Closing as OBSOLETE since the stack trace is too old to be useful now.