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 482360 - evolution crashed with SIGSEGV in g_object_ref()
evolution crashed with SIGSEGV in g_object_ref()
Status: RESOLVED DUPLICATE of bug 451144
Product: evolution
Classification: Applications
Component: Calendar
2.12.x (obsolete)
Other Linux
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 509935 557936 579617 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-10-01 20:14 UTC by Pedro Villavicencio
Modified: 2009-08-21 10:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Pedro Villavicencio 2007-10-01 20:14:39 UTC
This bug has been filled here:

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

"I was scrolling through the calendar which involved one fairly full standard evolution calendar which syncs with my google calendar using syncevolution, two fairly full google calendars which I was accessing read only using the ical links for each and the birthdays and anniversary calendar with only one entry. None of the calendars were excessively large as they are only for personal/home use - I would expect the average business user to have more going on.

The syncevolution client runs manually when I run the command and I have to close evolution before I run it. It wasn't running at the time of the crash."

".

Thread 1 (process 19544)

  • #0 IA__g_object_ref
    at /build/buildd/glib2.0-2.14.1/gobject/gobject.c line 1718
  • #1 e_cal_model_copy_component_data
    at e-cal-model.c line 2049
  • #2 calendar_control_sensitize_calendar_commands
    at calendar-commands.c line 422
  • #3 gcal_calendar_focus_change_cb
    at calendar-commands.c line 530
  • #4 IA__g_closure_invoke
    at /build/buildd/glib2.0-2.14.1/gobject/gclosure.c line 490
  • #5 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2440
  • #6 IA__g_signal_emit_valist
    at /build/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2199
  • #7 IA__gtk_signal_emit
    at /build/buildd/gtk+2.0-2.12.0/gtk/gtksignal.c line 360
  • #8 calendar_focus_change_cb
    at gnome-cal.c line 1050
  • #9 _gtk_marshal_BOOLEAN__BOXED
    at /build/buildd/gtk+2.0-2.12.0/gtk/gtkmarshalers.c line 84
  • #10 IA__g_closure_invoke
    at /build/buildd/glib2.0-2.14.1/gobject/gclosure.c line 490
  • #11 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2440
  • #12 IA__g_signal_emit_valist
    at /build/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2209
  • #13 IA__g_signal_emit
    at /build/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2243
  • #14 gtk_widget_event_internal
    at /build/buildd/gtk+2.0-2.12.0/gtk/gtkwidget.c line 4675
  • #15 do_focus_change
    at /build/buildd/gtk+2.0-2.12.0/gtk/gtkwindow.c line 5047
  • #16 _gtk_window_set_has_toplevel_focus
    at /build/buildd/gtk+2.0-2.12.0/gtk/gtkwindow.c line 8083
  • #17 gtk_window_focus_out_event
    at /build/buildd/gtk+2.0-2.12.0/gtk/gtkwindow.c line 5081
  • #18 _gtk_marshal_BOOLEAN__BOXED
    at /build/buildd/gtk+2.0-2.12.0/gtk/gtkmarshalers.c line 84
  • #19 IA__g_closure_invoke
    at /build/buildd/glib2.0-2.14.1/gobject/gclosure.c line 490
  • #20 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2478
  • #21 IA__g_signal_emit_valist
    at /build/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2209
  • #22 IA__g_signal_emit
    at /build/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2243
  • #23 gtk_widget_event_internal
    at /build/buildd/gtk+2.0-2.12.0/gtk/gtkwidget.c line 4675
  • #24 IA__gtk_main_do_event
    at /build/buildd/gtk+2.0-2.12.0/gtk/gtkmain.c line 1557
  • #25 gdk_event_dispatch
    at /build/buildd/gtk+2.0-2.12.0/gdk/x11/gdkevents-x11.c line 2351
  • #26 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.14.1/glib/gmain.c line 2061
  • #27 g_main_context_iterate
    at /build/buildd/glib2.0-2.14.1/glib/gmain.c line 2694
  • #28 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.14.1/glib/gmain.c line 2898
  • #29 bonobo_main
    at bonobo-main.c line 311
  • #30 main
    at main.c line 602
  • #31 __libc_start_main
    from /lib/libc.so.6
  • #32 _start

Comment 1 André Klapper 2008-01-17 01:18:27 UTC


  • #6 <signal handler called>
  • #7 IA__g_object_ref
    at /tmp/buildd/glib2.0-2.14.4/gobject/gobject.c line 1718
  • #8 e_cal_model_copy_component_data
    at e-cal-model.c line 2049
  • #9 calendar_control_sensitize_calendar_commands
    at calendar-commands.c line 422
  • #10 gcal_calendar_focus_change_cb
    at calendar-commands.c line 530

Comment 2 André Klapper 2008-01-17 01:18:38 UTC
*** Bug 509935 has been marked as a duplicate of this bug. ***
Comment 3 Milan Crha 2008-07-03 13:29:42 UTC
It was going to increase a reference counter on a comp_data->client, which has been probably unreffed because of some bug somewhere else. I recall I saw some changes in reference counting in calendar, but I'm not sure whether it was in 2.12 too or only in development version. Upgrading to actual stable (2.22.x) would help, I think.
Comment 4 Akhil Laddha 2008-10-28 06:09:31 UTC
*** Bug 557936 has been marked as a duplicate of this bug. ***
Comment 5 Fabio Durán Verdugo 2009-04-20 15:46:59 UTC
*** Bug 579617 has been marked as a duplicate of this bug. ***
Comment 6 Akhil Laddha 2009-08-21 10:10:27 UTC
This version is no longer maintained, which means that it will not receive any
further security or bug fix updates.
The current stable GNOME and Evolution version is 2.26.

Can you please check again whether this issue still happens in Evolution 2.24
or 2.26 and update this report by adding a comment and changing the "Version"
field? Thanks a lot.

Again thank you for reporting this bug and we are sorry it could not be fixed
for the version you originally used here.

Without feedback this report will be closed as INCOMPLETE in 6 weeks.
Comment 7 Akhil Laddha 2009-08-21 10:17:22 UTC

*** This bug has been marked as a duplicate of bug 451144 ***