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 653072 - [abrt] evolution-2.32.2-1.fc14: tooltip_event_cb: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
[abrt] evolution-2.32.2-1.fc14: tooltip_event_cb: Process /usr/bin/evolution ...
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Calendar
2.32.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-06-21 04:55 UTC by Milan Crha
Modified: 2012-09-04 19:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Crha 2011-06-21 04:55:09 UTC 
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=714617

abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 39326 bytes
cmdline: evolution
component: evolution
Attached file: coredump, 82026496 bytes
crash_function: tooltip_event_cb
executable: /usr/bin/evolution
kernel: 2.6.35.13-92.fc14.i686
package: evolution-2.32.2-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1308557337
uid: 500

How to reproduce
-----
1. Open Calendar
2. Delete some recurrend calendar entries one after the other 
3. Crash...

Core was generated by `evolution'.
Program terminated with signal 11, Segmentation fault.

+ Trace 227540

Thread 1 (Thread 0xb7816880 (LWP 27638))

  • #0 tooltip_event_cb
    at e-week-view.c line 3054
  • #1 gnome_canvas_marshal_BOOLEAN__BOXED
    at gnome-canvas-marshal.c line 128
  • #2 g_closure_invoke
    at gclosure.c line 766
  • #3 signal_emit_unlocked_R
    at gsignal.c line 3252
  • #4 g_signal_emit_valist
    at gsignal.c line 2993
  • #5 g_signal_emit
    at gsignal.c line 3040
  • #6 emit_event
    at gnome-canvas.c line 2648
  • #7 pick_current_item
    at gnome-canvas.c line 2797
  • #8 gnome_canvas_motion
    at gnome-canvas.c line 2902
  • #9 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 86
  • #10 g_type_class_meta_marshal
    at gclosure.c line 877
  • #11 g_closure_invoke
    at gclosure.c line 766
  • #12 signal_emit_unlocked_R
    at gsignal.c line 3290
  • #13 g_signal_emit_valist
    at gsignal.c line 2993
  • #14 g_signal_emit
    at gsignal.c line 3040
  • #15 gtk_widget_event_internal
    at gtkwidget.c line 4992
  • #16 IA__gtk_propagate_event
    at gtkmain.c line 2460
  • #17 IA__gtk_main_do_event
    at gtkmain.c line 1665
  • #18 gdk_event_dispatch
    at gdkevents-x11.c line 2377
  • #19 g_main_dispatch
    at gmain.c line 2149
  • #20 g_main_context_dispatch
    at gmain.c line 2702
  • #21 g_main_context_iterate
    at gmain.c line 2780
  • #22 g_main_loop_run
    at gmain.c line 2988
  • #23 IA__gtk_main
    at gtkmain.c line 1237
  • #24 main
    at main.c line 679 






Comment 1


Milan Crha





          2012-09-04 19:02:26 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.