Bug 794934

Summary: [abrt] evolution-3.2.3-1.fc16: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: vadim s. sabinich <vadim>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:7e727ea023df5bfbae3c0a9a6a79ac196689582a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 16:40:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: dso_list
none
File: maps
none
File: backtrace none

Description vadim s. sabinich 2012-02-17 23:26:08 UTC
libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 3
cmdline:        evolution
executable:     /usr/bin/evolution
kernel:         3.1.0-7.fc16.x86_64
pid:            6496
pwd:            /home/vadim
reason:         Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
time:           Сб. 18 февр. 2012 08:18:26
uid:            1000
username:       vadim

backtrace:      Text file, 37637 bytes
dso_list:       Text file, 21481 bytes
maps:           Text file, 95507 bytes

environ:
:XDG_VTNR=1
:XDG_SESSION_ID=2
:HOSTNAME=sabinich
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:SHELL=/bin/bash
:TERM=dumb
:HISTSIZE=1000
:XDG_SESSION_COOKIE=04952cb7e3024e76e136c3ff0000000e-1329279485.705556-933550312
:GNOME_KEYRING_CONTROL=/tmp/keyring-9HBxaM
:'IMSETTINGS_MODULE=X compose table'
:USER=vadim
:USERNAME=vadim
:MAIL=/var/spool/mail/vadim
:PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/vadim/.local/bin:/home/vadim/bin
:DESKTOP_SESSION=gnome
:QT_IM_MODULE=xim
:PWD=/home/vadim
:XMODIFIERS=@im=none
:GNOME_KEYRING_PID=1236
:LANG=ru_RU.utf8
:GDM_LANG=ru_RU.utf8
:GDMSESSION=gnome
:HISTCONTROL=ignoredups
:HOME=/home/vadim
:XDG_SEAT=seat0
:SHLVL=1
:LOGNAME=vadim
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-EY1SRD4smn,guid=2304780b63a073b68f2969c80000003e
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:WINDOWPATH=1
:XDG_RUNTIME_DIR=/run/user/vadim
:DISPLAY=:0
:XAUTHORITY=/var/run/gdm/auth-for-vadim-psFj45/database
:_=/usr/bin/gnome-session
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1242,unix/unix:/tmp/.ICE-unix/1242
:GPG_AGENT_INFO=/tmp/keyring-9HBxaM/gpg:0:1
:SSH_AUTH_SOCK=/tmp/keyring-9HBxaM/ssh
:GJS_DEBUG_OUTPUT=stderr
:'GJS_DEBUG_TOPICS=JS ERROR;JS LOG'
:DESKTOP_STARTUP_ID=gnome-shell-1462-sabinich-evolution-13_TIME12527773
:GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/evolution.desktop
:GIO_LAUNCHED_DESKTOP_FILE_PID=6496

var_log_messages:
:Feb 15 10:02:41 sabinich yum[1828]: Updated: evolution-data-server-3.2.3-2.fc16.x86_64
:Feb 15 10:03:21 sabinich yum[1828]: Updated: evolution-3.2.3-1.fc16.x86_64
:Feb 15 10:08:59 sabinich yum[1828]: Updated: evolution-NetworkManager-3.2.3-1.fc16.x86_64
:Feb 18 08:18:26 sabinich kernel: [69284.067331] evolution[6496]: segfault at 7f6900000000 ip 00007f6900000000 sp 00007fff5f5adc08 error 14
:Feb 18 08:18:30 sabinich abrt[17706]: Saved core dump of pid 6496 (/usr/bin/evolution) to /var/spool/abrt/ccpp-2012-02-18-08:18:26-6496 (206069760 bytes)

Comment 1 vadim s. sabinich 2012-02-17 23:26:12 UTC
Created attachment 564009 [details]
File: dso_list

Comment 2 vadim s. sabinich 2012-02-17 23:26:15 UTC
Created attachment 564010 [details]
File: maps

Comment 3 vadim s. sabinich 2012-02-17 23:26:18 UTC
Created attachment 564011 [details]
File: backtrace

Comment 4 Milan Crha 2012-02-20 08:26:52 UTC
Thanks for a bug report. The crashing thread (see below) doesn't show much information, at least it doesn't show what could case this crash. Could you provide some steps to reproduce it, please?

Thread 1 (Thread 0x7f69c3acc980 (LWP 6496)):
#0  0x00007f6900000000 in ?? ()
#1  0x0000003ffdc11172 in weak_refs_notify (data=0x4dadf30) at gobject.c:2244
#2  0x0000003ffdc113db in g_object_unref (_object=0x4a43000) at gobject.c:2709
#3  0x00007f699712b13d in expiry_func (data=<optimized out>) at ../../atk-adaptor/accessible-leasing.c:122
#4  0x0000003ffcc462bb in g_timeout_dispatch (source=0x514a530, callback=<optimized out>, user_data=<optimized out>) at gmain.c:3907
#5  0x0000003ffcc44acd in g_main_dispatch (context=0x1c90c00) at gmain.c:2441
#6  g_main_context_dispatch (context=0x1c90c00) at gmain.c:3011
#7  0x0000003ffcc452c8 in g_main_context_iterate (context=0x1c90c00, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3089
#8  0x0000003ffcc45815 in g_main_loop_run (loop=0x1d6fb70) at gmain.c:3297
#9  0x00000030061517fd in gtk_main () at gtkmain.c:1362
#10 0x00000000004022e3 in main (argc=1, argv=0x7fff5f5adfb8) at main.c:709

Comment 5 vadim s. sabinich 2012-02-20 10:55:16 UTC
I just read emails from gmail throgh IMAP+

Comment 6 Milan Crha 2012-02-21 07:50:39 UTC
Thanks for the update. Thinking of it, and seeing the weak_unref and accessibility code being involved, could you try to install gtk3-3.2.3-2 from bug #790190, currently in updates-testing, to see whether the bug from there didn't cause this crash, please?

Comment 7 Fedora End Of Life 2013-01-16 15:17:47 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Fedora End Of Life 2013-02-13 16:40:09 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

Thank you for reporting this bug and we are sorry it could not be fixed.