evolution-exchange-storage crashed with SIGSEGV in gconf_engine_unref()

[Matej Kenda]

Binary package hint: evolution-exchange

Evolution and gnome-keyring-daemon started to consume a lot of CPU (100% of one core) since I have added an Exchange account. These things might be related.

ProblemType: Crash
Architecture: amd64
Date: Fri May 30 12:42:25 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/evolution/2.22/evolution-exchange-storage
Package: evolution-exchange 2.22.1-0ubuntu1
PackageArchitecture: amd64
ProcCmdline: /usr/lib/evolution/2.22/evolution-exchange-storage --oaf-activate-iid=OAFIID:GNOME_Evolution_Exchange_Connector_CalFactory:1.2 --oaf-ior-fd=22
ProcEnviron:
 LANG=en_GB.UTF-8
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 SHELL=/bin/bash
Signal: 11
SourcePackage: evolution-exchange
StacktraceTop:
 ?? () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libglib-2.0.so.0
 gconf_engine_unref () from /usr/lib/libgconf-2.so.4
 gconf_client_get_default ()
 ?? ()
Title: evolution-exchange-storage crashed with SIGSEGV in gconf_engine_unref()
Uname: Linux 2.6.24-17-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy kvm lpadmin netdev plugdev powerdev scanner video

[Matej Kenda (matejken)]

I have also noticed that the process gnome-keyring-daemon was using between 1.0 and 1.3 GiB of memory at the time of the crash.

[Apport retracing service (apport)]

StacktraceTop:g_hash_table_foreach_remove_or_steal (
gconf_engine_unref (conf=0x68ff90) at gconf.c:2987
gconf_client_get_default () at gconf-client.c:438
authenticate_user (backend=0x743b80, book=0x75ad20,
ORBit_small_invoke_adaptor (adaptor_obj=0x7572a0,

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Could you try to reproduce the same with Ubuntu 8.10 or 9.04? Thanks in advance.

[Matej Kenda (matejken)]

No, this issue is not happening any more with 8.10 64-bit.

[Matej Kenda (matejken)]

Doesn't happen any more since 8.10.