After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 637640 - [abrt] evolution-2.32.1-1.fc14: g_malloc: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
[abrt] evolution-2.32.1-1.fc14: g_malloc: Process /usr/bin/evolution was kill...
Status: RESOLVED OBSOLETE
Product: evolution-data-server
Classification: Platform
Component: Mailer
2.32.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-12-20 08:31 UTC by Milan Crha
Modified: 2012-09-04 19:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Abrt log (76.58 KB, text/plain)
2011-01-17 20:12 UTC, henning.noren
Details

Description Milan Crha 2010-12-20 08:31:58 UTC
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=664101

abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: evolution
component: evolution
crash_function: g_malloc
executable: /usr/bin/evolution
kernel: 2.6.35.9-64.fc14.i686
package: evolution-2.32.1-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1292652180
uid: 0

How to reproduce
-----
1. Started Evolution first time under root account in Gnome (Fedora 14)
2. Evolution said something about migration and crashed.

Core was generated by `evolution'.
Program terminated with signal 6, Aborted.

Comment 1 Milan Crha 2010-12-21 09:56:34 UTC
An information from a downstream reporter:

Actually, I doubt that I had opened evolution at all before the crash, it is my
home ftp server, don't need any interactions on it.  But if it (evolution) was
installed, its version was less or equal of evolution-2.12.3-3.fc8 - I upgraded
the server from 8 to 14, gradually, of course.  Hope it helps.
Comment 2 henning.noren 2011-01-17 20:12:33 UTC
Created attachment 178556 [details]
Abrt log

I have the same problem when I try to migrate to Evolution on Fedora 14 from my old Fedora 8 installation.

This is possibly related to the old Red Hat bug 531627 (https://bugzilla.redhat.com/show_bug.cgi?id=531627) as it is the same setup I am migrating from, although this time it is to Fedora 14 (I reverted back to FC 8 after some time for various reasons).
I have tried the workaround I used at the time (eg. setting gconf variables and removing the summary, index and ibex files) the but evolution still crashes during the migration phase.

The evolution.tar.gz backup file is ~287MB and the system it happen on is a fully up to date Fedora 14 running x86_64 on a Intel Core i7 Processor:
$ rpm -qa | grep evolution
evolution-data-server-2.32.1-1.fc14.x86_64
evolution-help-2.32.1-1.fc14.noarch
evolution-2.32.1-1.fc14.x86_64
$ uname -a
Linux henning 2.6.35.10-74.fc14.x86_64 #1 SMP Thu Dec 23 16:04:50 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux

The system I migrate from is a Fedora 8 i386 installation:
$ rpm -qa | grep -i evolution
evolution-2.12.3-5.fc8
evolution-data-server-debuginfo-1.12.3-6.fc8
evolution-data-server-devel-1.12.3-6.fc8
evolution-data-server-1.12.3-6.fc8
evolution-webcal-2.12.0-1.fc8
evolution-debuginfo-2.12.3-5.fc8
$ uname -a
Linux henning 2.6.26.8-57.fc8PAE #1 SMP Thu Dec 18 19:09:47 EST 2008 i686 i686 i386 GNU/Linux

reproduce
-----
1. Migrate the settings from Evolution 2.12.3

Attached is the backtrace from abrt where I have censored three lines from the backtrace with the text ***CENSORED*** as they contained information from my mailbox. If these lines are essential for resolving the problem I am able to provide the full cleartext backtrace in a private mail to the developer.

Do let me know if there is any other information needed to resolve this as I would love to finally migrate away from my trusty old FC8 system to something a bit more modern.
Comment 3 henning.noren 2011-04-19 21:51:30 UTC
The issue does not appear in 2.32.2-1 and I managed to successfully migrate my settings twice with to this version.

I believe this ticket can be closed.
Comment 4 Milan Crha 2012-09-04 19:07:03 UTC
Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.