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 513447 - evolution-alarm-notify crashed with signal 5 in g_hash_table_foreach()
evolution-alarm-notify crashed with signal 5 in g_hash_table_foreach()
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Calendar
2.22.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-01-31 13:14 UTC by Pedro Villavicencio
Modified: 2010-11-28 16:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Pedro Villavicencio 2008-01-31 13:14:32 UTC
This report has been filled here:

https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/187539

"Evolution alarm crashes when Gnome boots."

".

Thread 1 (process 6023)

  • #0 IA__g_logv
    at /build/buildd/glib2.0-2.15.4/glib/gmessages.c line 503
  • #1 IA__g_log
    at /build/buildd/glib2.0-2.15.4/glib/gmessages.c line 517
  • #2 IA__g_hash_table_foreach
    at /build/buildd/glib2.0-2.15.4/glib/ghash.c line 1067
  • #3 alarm_notify_finalize
    at alarm-notify.c line 276
  • #4 IA__g_object_unref
    at /build/buildd/glib2.0-2.15.4/gobject/gobject.c line 1793
  • #5 bonobo_object_unref
    at bonobo-object.c line 201
  • #6 main
    at notify-main.c line 170
  • #7 __libc_start_main
    from /lib/libc.so.6
  • #8 _start

Comment 1 Matthew Barnes 2008-03-11 00:34:19 UTC
Bumping version to a stable release.
Comment 2 Milan Crha 2008-09-15 16:45:11 UTC
It seems that thread 2 is querying data from calendar, but the thread 1 is ready to finalize alarm notify and exit application. I'm not sure whether we are able to do anything with this, ECal has nothing like 'cancel' method at the moment.
Comment 3 Omer Akram 2010-11-28 16:32:37 UTC
closing this bug as obsolete as there has been no duplicates in bugzilla and the only duplicate in launchpad was against version 2.21.90 plus according to original reporter the issue is fixed in 2.28