Bug 657351

Summary: [abrt] evolution-2.32.1-1.fc14: g_type_class_meta_marshal: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Kris Buytaert <kris.buytaert>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: abdrahim_, adam.hough, allane, bernie+fedora, dijit, dlesage, fonya, jhauva, loleary, lucilanga, mbarnes, mcrha, mitr, nicolas.vieville, peter.green
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:61e2ec03ce3016cd0e3ca0dd1b6bf981aa5dfbee
Fixed In Version: evolution-data-server-2.91.6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-25 06:45:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Kris Buytaert 2010-11-25 14:54:14 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: evolution
component: evolution
crash_function: g_type_class_meta_marshal
executable: /usr/bin/evolution
kernel: 2.6.35.6-48.fc14.i686
package: evolution-2.32.1-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: Random Crash
time: 1290696619
uid: 500
Comment 1 Kris Buytaert 2010-11-25 14:54:18 UTC 
Created attachment 462918 [details]
File: backtrace
Comment 2 Milan Crha 2010-11-26 07:44:40 UTC 
Thanks for a bug report. If you say "random crash", do you really mean that this happens only occasionally? If yes, then it might be quite hard to fix.

The place of the crash is also quite strange, it's in the GDBus code, which was about to send a signal to the object in evolution, which is probably already freed or something like that. Is it possible that e-calendar-factory crashed too, just before this crash? Though I see that other threads are working with e-calendar-factory too, so I've not much idea what could happen here.

Maybe a valgrind capture of this crash with steps (though probably not reproducible), would help, especially when run like:
   $ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>evo.log
Comment 3 David Webb 2010-11-30 18:53:27 UTC 
Package: evolution-2.32.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. playing with the calander
2. scrolling into days gone past.
3. opened a past day by accident
4. close, keep scrolling.
5. Evolution dissappeared. :o
Comment 4 David Le Sage 2010-12-07 21:55:21 UTC 
Package: evolution-2.32.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Crashed while I was away overnight so presumably incoming mail did it.
Comment 5 Allan Engelhardt 2010-12-09 06:17:49 UTC 
Package: evolution-2.32.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
Evolution client was running unattended so I don't know why it would crash at this time or how to reproduce.
Comment 6 Allan Engelhardt 2010-12-20 14:28:21 UTC 
Package: evolution-2.32.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
Evolution was just running (with alltray)
Comment 7 nicolas.vieville 2010-12-21 11:05:33 UTC 
Package: evolution-2.32.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Lauch evolution
2. Use it
3. Wait sometimes a few minutes or a few hours




Comment
-----
Crash happened while using other applications. Evolution was active in background and suddenly dissapeared, then ABRT was launched to report the bug.
Nothing more that I can do than reporting these facts by ABRT, due to my limited skill in such things.
Comment 8 Juan Hauva 2010-12-29 21:04:40 UTC 
Package: evolution-2.32.1-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.In evolution calendar, i've got this linked to google calendar...
2. I've rolled mouse to  change date and crash
3.
Comment 9 Bernie Innocenti 2011-01-05 15:22:04 UTC 
Package: evolution-2.32.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
I've simply hit "send" on an email (like I usually do)
Comment 10 Allan Engelhardt 2011-01-07 20:06:08 UTC 
Package: evolution-2.32.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
Was just running in the background of a recently-started workstation
Comment 11 abdrahim_ 2011-01-11 06:40:26 UTC 
Package: evolution-2.32.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Trying to move to a new month w/ scroll bar
2.
3.
Comment 12 Peter Green 2011-01-12 14:49:51 UTC 
Package: evolution-2.32.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Attempted to view the calendar by clicking the button in the bottom left of the main Evolution window.



Comment
-----
Attempted to view the calendar pane.
Comment 13 Szabo Akos 2011-01-17 14:10:30 UTC 
Package: evolution-2.32.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Try to import a calendar file from desktop folder
2. 
3.


Comment
-----
The calendar file was automaticaly backup to webdav folder with the same version of evolution. Import as single file, icalendar, as "appointments, and meetings".
Comment 14 Kris Buytaert 2011-01-17 15:57:33 UTC 
Package: evolution-2.32.1-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
Opened a mail which contained the accept of a meeting invite .
Comment 15 Kris Buytaert 2011-01-19 13:59:00 UTC 
Package: evolution-2.32.1-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
Got mail with meeting invitation
Tried viewing it
Crash
Comment 16 Larry O'Leary 2011-01-19 15:03:26 UTC 
Package: evolution-2.32.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Launched Evolution

Comment
-----
I had previously been using Evolution twelve hours earlier and exited it. This morning, when I launched it, this segmentation fault occurred. The Evolution window briefly appeared but the message list view and message pane had not yet been populated when the crash occurred.
Comment 17 Larry O'Leary 2011-01-19 15:08:56 UTC 
Oops. Comment 16 is not accurate. Filed the wrong bug. Comment 16 should have said:

Package: evolution-2.32.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Not certain. At the time, I was attempting to update a calendar entry on a CalDAV calendar.

Comment
-----
After the crash I relaunched Evolution and attempted to edit the calendar entry a second time and had no issues. I also updated other entries to see if I could reproduce the issue but was unsuccessful in doing so. The problem seems to have been random.
Comment 18 Adam Hough 2011-01-24 20:23:12 UTC 
Package: evolution-2.32.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Setup new account as an exchange-mapi account
2. Click on Calendar
3. Segfault


Comment
-----
Tried to setup first evoltuion mail account as an Exchange-mapi account.  The Evolution will crash repeatedly when navigating around to mail, calendar, or memos.
Comment 19 Adam Hough 2011-01-24 20:28:32 UTC 
*** Bug 672325 has been marked as a duplicate of this bug. ***
Comment 20 Milan Crha 2011-01-25 06:45:37 UTC 
This is the upstream bug [1], which is supposed to be fixed in evolution-data-server 2.91.6. The change done there cannot be backported to 2.32.x, unfortunately.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=627788