Bug 246536 – Evo crashes when calendar view is chnaged from year to month.

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 246536 - Evo crashes when calendar view is chnaged from year to month.


Summary:	Evo crashes when calendar view is chnaged from year to month.


Status:	RESOLVED DUPLICATE of bug 246165

Product:	evolution
Classification:	Applications
Component:	Calendar
Version:	unspecified
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Evolution Triage Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2003-07-17 21:04 UTC by ximain_bugs
Modified:	2003-07-17 22:03 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description ximain_bugs 2003-07-17 21:04:06 UTC

Package: Evolution
Priority: critical
Version: GNOME2.2.2 1.4.3
os_details: Ximian, Inc.
Synopsis: Evo crashes when calendar view is chnaged from year to month.
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)
Description:
Description of Problem:
After getting a bad view
(http://bugzilla.gnome.org/show_bug.cgi?id=244539) like bug 244539

Steps to reproduce the problem:
1.  Upgrade RH 7.3 to Evo 1.4/XD2
2.  Upgrade RH 9.0
3.  Upgrade XD2
4.  Open evo
5.  Pick calendar
6. Resize pane to get calendar
7.  Calendar only in year view.
8.  Click on month
9.  Crashh

Actual Results:
It seemsed that week, day view did nothing.
Month view crashes

Expected Results:
Month view to pop up.

How often does this happen?
Every time.

Additional Information:
This box was recently upgraded from Rh7.3 to XD2.  Then to RH9, then XD2
added.

Evo has crashed a few other times, but this 100% consistent.


Debugging Information:

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

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[New Thread 1092662816 (LWP 2013)]
[New Thread 1150520624 (LWP 2028)]
[New Thread 1200876848 (LWP 2027)]
[New Thread 1192484144 (LWP 2026)]
[New Thread 1184091440 (LWP 2025)]
[New Thread 1175698736 (LWP 2024)]
[New Thread 1167306032 (LWP 2023)]
[New Thread 1158913328 (LWP 2022)]
[New Thread 1142127920 (LWP 2019)]
[New Thread 1133735216 (LWP 2018)]
[New Thread 1125342512 (LWP 2017)]
[New Thread 1116949808 (LWP 2016)]
0xffffe002 in ?? ()

+ Trace 38815

Thread 1 (Thread 1092662816 (LWP 2013))

#0 ??
#1 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 evolution_storage_set_view_factory_new_view
#3 <signal handler called>
#4 pango_layout_line_get_pixel_extents
from /usr/lib/libpango-1.0.so.0
#5 pango_layout_iter_get_line
from /usr/lib/libpango-1.0.so.0
#6 e_text_select_all
from /usr/lib/libgal-2.0.so.3
#7 g_cclosure_marshal_VOID__POINTER
from /usr/lib/libgobject-2.0.so.0
#8 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#12 e_day_view_event_sort_func
from /usr/lib/evolution/1.4/components/libevolution-calendar.so
#13 e_day_view_event_sort_func
from /usr/lib/evolution/1.4/components/libevolution-calendar.so
#14 _gtk_marshal_BOOLEAN__ENUM
from /usr/lib/libgtk-x11-2.0.so.0
#15 g_cclosure_new_swap
from /usr/lib/libgobject-2.0.so.0
#16 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#20 gtk_widget_child_focus
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_notebook_new
from /usr/lib/libgtk-x11-2.0.so.0
#22 _gtk_marshal_VOID__POINTER_UINT
from /usr/lib/libgtk-x11-2.0.so.0
#23 g_cclosure_new_swap
from /usr/lib/libgobject-2.0.so.0
#24 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#28 gtk_notebook_new
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_notebook_set_current_page
from /usr/lib/libgtk-x11-2.0.so.0
#30 gnome_calendar_get_view
from /usr/lib/evolution/1.4/components/libevolution-calendar.so
#31 gnome_calendar_set_view
from /usr/lib/evolution/1.4/components/libevolution-calendar.so
#32 calendar_goto_today
from /usr/lib/evolution/1.4/components/libevolution-calendar.so
#33 bonobo_socket_add_id
from /usr/lib/libbonoboui-2.so.0
#34 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#35 bonobo_closure_invoke_va_list
from /usr/lib/libbonobo-2.so.0
#36 bonobo_closure_invoke
from /usr/lib/libbonobo-2.so.0
#37 bonobo_socket_add_id
from /usr/lib/libbonoboui-2.so.0
#38 Bonobo_UIComponent_execVerb
from /usr/lib/libbonobo-2.so.0
#39 bonobo_ui_engine_get_ui_container
from /usr/lib/libbonoboui-2.so.0
#40 bonobo_ui_engine_get_ui_container
from /usr/lib/libbonoboui-2.so.0
#41 g_cclosure_marshal_VOID__POINTER
from /usr/lib/libgobject-2.0.so.0
#42 g_cclosure_new_swap
from /usr/lib/libgobject-2.0.so.0
#43 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#44 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#45 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#46 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#47 bonobo_ui_engine_emit_verb_on_w
from /usr/lib/libbonoboui-2.so.0
#48 bonobo_ui_sync_status_new
from /usr/lib/libbonoboui-2.so.0
#49 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#50 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#51 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#52 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#53 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#54 bonobo_ui_toolbar_item_activate
from /usr/lib/libbonoboui-2.so.0
#55 bonobo_ui_toolbar_button_item_get_type
from /usr/lib/libbonoboui-2.so.0
#56 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#57 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#58 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#59 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#60 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#61 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#62 _gtk_button_paint
from /usr/lib/libgtk-x11-2.0.so.0
#63 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#64 g_cclosure_new_swap
from /usr/lib/libgobject-2.0.so.0
#65 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#66 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#67 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#68 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#69 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#70 _gtk_button_paint
from /usr/lib/libgtk-x11-2.0.so.0
#71 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#72 g_cclosure_new_swap
from /usr/lib/libgobject-2.0.so.0
#73 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#74 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#75 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#76 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#77 gtk_widget_send_expose
from /usr/lib/libgtk-x11-2.0.so.0
#78 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#79 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#80 _gdk_events_queue
from /usr/lib/libgdk-x11-2.0.so.0
#81 unblock_source
from /usr/lib/libglib-2.0.so.0
#82 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#83 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#84 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#85 bonobo_main
from /usr/lib/libbonobo-2.so.0
#86 main
#87 __libc_start_main
from /lib/tls/libc.so.6
#0 ??




Unknown reporter: ximain_bugs@mailonly.zotnet.com, changed to bugbuddy-import@ximian.com.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Gerardo Marin 2003-07-17 22:03:02 UTC


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