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 344865 - Evolution crash when make new appointment in calendar
Evolution crash when make new appointment in calendar
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Calendar
2.6.x (obsolete)
Other other
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 348898 355911 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-06-14 12:46 UTC by Stephens
Modified: 2006-09-14 07:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Stephens 2006-06-14 12:46:09 UTC 
From: Lawrence S. Stephens III <Stephens@Paterson.k12.nj.us>
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.14.0
Subject: Evolution crash when make new appointment in calendar

Distribution: Ubuntu 6.06 (dapper)
Package: Evolution
Severity: critical
Version: GNOME2.14.1 2.6.x
Gnome-Distributor: Ubuntu
Synopsis: Evolution crash when make new appointment in calendar
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: 2.6.x
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
When trying to make a new appoinment in calendar, Evolution suddenly
crashes.

Steps to reproduce the crash:
1. Select a time on particular day of the week.
2. Right-click and choose New Appoinment.
3. 

Expected Results:
An Alarms dialog will show and Evolution will then crash.

How often does this happen?
This happens everytime.

Additional Information:
I'm using a Apple PowerBook Bronze Keyboard with 256MB RAM and running
on Linux 2.6.15-23-powerpc OS. I'm also running Ubuntu Dapper Drake for
PowerPC.




Debugging Information:

Backtrace was generated from '/usr/bin/evolution-2.6'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 805566528 (LWP 7558)]
[New Thread 1081025776 (LWP 7665)]
[New Thread 971973872 (LWP 7632)]
[New Thread 938829040 (LWP 7580)]
[New Thread 930440432 (LWP 7578)]
[New Thread 922051824 (LWP 7577)]
[New Thread 913663216 (LWP 7576)]
[New Thread 905274608 (LWP 7574)]
[New Thread 863618288 (LWP 7568)]
[New Thread 854836464 (LWP 7567)]
[New Thread 846447856 (LWP 7565)]
(no debugging symbols found)
0x0e8883dc in waitpid () from /lib/libc.so.6

+ Trace 68838

Thread 1 (Thread 805566528 (LWP 7558))

  • #0 waitpid
    from /lib/libc.so.6
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 es_menu_hook_get_type
  • #3 <signal handler called>
  • #4 recurrence_page_get_type
    from /usr/lib/evolution/2.6/components/libevolution-calendar.so
  • #5 recurrence_page_get_type
    from /usr/lib/evolution/2.6/components/libevolution-calendar.so
  • #6 comp_editor_page_fill_widgets
    from /usr/lib/evolution/2.6/components/libevolution-calendar.so
  • #7 comp_editor_set_help_section
    from /usr/lib/evolution/2.6/components/libevolution-calendar.so
  • #8 event_editor_construct
    from /usr/lib/evolution/2.6/components/libevolution-calendar.so
  • #9 comp_editor_edit_comp
    from /usr/lib/evolution/2.6/components/libevolution-calendar.so
  • #10 e_calendar_view_create_popup_menu
    from /usr/lib/evolution/2.6/components/libevolution-calendar.so
  • #11 e_calendar_view_new_appointment_for
    from /usr/lib/evolution/2.6/components/libevolution-calendar.so
  • #12 e_calendar_view_new_appointment_full
    from /usr/lib/evolution/2.6/components/libevolution-calendar.so
  • #13 e_calendar_view_new_appointment
    from /usr/lib/evolution/2.6/components/libevolution-calendar.so
  • #14 e_calendar_view_new_appointment
    from /usr/lib/evolution/2.6/components/libevolution-calendar.so
  • #15 e_popup_add_items
    from /usr/lib/evolution/2.6/libeutil.so.0
  • #16 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #21 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 gtk_menu_shell_activate_item
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 gtk_menu_shell_activate_item
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 gtk_menu_reorder_child
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #27 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #28 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #30 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #31 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #34 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #35 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #36 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #37 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #38 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #39 main
  • #0 waitpid
    from /lib/libc.so.6 



-- 
Lawrence S. Stephens III
Technology Coordinator

Paterson Public School #26
1 East 32nd Street
Paterson, New Jersey 07514-1412

Voice:  973-321-1000 x22644
Email:  Stephens@Paterson.k12.nj.us




------- Bug created by bug-buddy at 2006-06-14 12:46 -------


Bugreport had an attachment. This cannot be imported to Bugzilla.
Contact bugmaster@gnome.org if you are willing to write a patch for this.
Comment 1 Elijah Newren 2006-06-14 18:29:50 UTC 
Looks similar to the stack traces in bug 319864 and bug 333599, which were with evo 2.4.x.  Makes me think that this stack trace might possibly be slightly corrupted (missing some frames) since there's no calls between the signal handler and recurrence_page_get_type().  

Can you get us a stack trace with debugging symbols?  Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Comment 2 Chenthill P 2006-06-15 06:01:11 UTC 
This has been in evolution-2.6.2. Fix committed on 2006-04-24.
Comment 3 Fabio Bonelli 2006-07-27 09:55:33 UTC 
*** Bug 348898 has been marked as a duplicate of this bug. ***
Comment 4 Fabio Bonelli 2006-09-14 07:58:18 UTC 
*** Bug 355911 has been marked as a duplicate of this bug. ***