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
Created attachment 462918 [details] File: backtrace
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
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
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.
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.
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)
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.
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.
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)
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
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.
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.
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".
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 .
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
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.
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.
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.
*** Bug 672325 has been marked as a duplicate of this bug. ***
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