Hide Forgot
libreport version: 2.0.7 abrt_version: 2.0.6 backtrace_rating: 4 cmdline: /usr/libexec/e-calendar-factory crash_function: g_type_check_instance_cast executable: /usr/libexec/e-calendar-factory kernel: 3.1.2-1.fc16.i686 pid: 2478 pwd: / reason: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV) time: Fri 25 Nov 2011 08:49:17 PM EST uid: 1000 username: michael var_log_messages: Nov 25 20:49:18 mike abrt[2805]: Saved core dump of pid 2478 (/usr/libexec/e-calendar-factory) to /var/spool/abrt/ccpp-2011-11-25-20:49:17-2478 (44077056 bytes) backtrace: Text file, 20210 bytes build_ids: Text file, 3649 bytes dso_list: Text file, 7698 bytes maps: Text file, 20631 bytes environ: :SHELL=/bin/bash :DBUS_STARTER_ADDRESS=unix:abstract=/tmp/dbus-nWaUr1SUAj,guid=9b87ab62f3b866a87749f672000003db :XDG_SESSION_COOKIE=5465acb346eed5ad4bb143fb00000017-1322271333.636784-20250249 :XDG_RUNTIME_DIR=/run/user/michael :DISPLAY=:0 :DESKTOP_SESSION=gnome :SSH_AUTH_SOCK=/tmp/keyring-3MaAZx/ssh :SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/2197,unix/unix:/tmp/.ICE-unix/2197 :WINDOWPATH=2 :PATH=/usr/local/bin:/usr/bin:/bin :GNOME_DESKTOP_SESSION_ID=this-is-deprecated :GDMSESSION=gnome :XDG_VTNR=2 :USERNAME=michael :XDG_SESSION_ID=4 :GPG_AGENT_INFO=/tmp/keyring-3MaAZx/gpg:0:1 :DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-nWaUr1SUAj,guid=9b87ab62f3b866a87749f672000003db :XDG_SEAT=seat0 :XAUTHORITY=/var/run/gdm/auth-for-michael-pby9V7/database :USER=michael :DBUS_STARTER_BUS_TYPE=session :GNOME_KEYRING_PID=2192 :SHLVL=1 :PWD=/home/michael :GNOME_KEYRING_CONTROL=/tmp/keyring-3MaAZx :LANG=en_US.UTF-8 :_=/usr/bin/dbus-launch :LOGNAME=michael :HOME=/home/michael
Created attachment 544777 [details] File: dso_list
Created attachment 544778 [details] File: build_ids
Created attachment 544779 [details] File: maps
Created attachment 544780 [details] File: backtrace
Thanks for a bug report. This particular one had been reported already, thus I'm marking it as a duplicate. Please note that the original reporter was unable to reproduce the bug, thus if you can, please try to follow steps from bug #760393 comment #5 and update that bug. Thanks in advance. *** This bug has been marked as a duplicate of bug 760393 ***
*** Bug 781930 has been marked as a duplicate of this bug. ***