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 302460 - Double clicking in open text field in calendar crashes
Double clicking in open text field in calendar crashes
Status: VERIFIED FIXED
Product: evolution
Classification: Applications
Component: Calendar
2.2.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 307477 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-04-29 17:45 UTC by Allen Riddell
Modified: 2013-09-10 14:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8


Description Allen Riddell 2005-04-29 17:45:42 UTC 
Steps to reproduce:
1. Start typing a new calendar entry in daily,whatever mode
2. double click on your text (i.e. to open up the full entry dialog)

crashes


Stack trace:
(gdb) thread apply all bt

+ Trace 58912

Thread 1 (Thread -1228446112 (LWP 6796))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 es_menu_hook_get_type
  • #3 <signal handler called>
  • #4 e_day_view_convert_time_to_position
    from /usr/lib/evolution/2.2/components/libevolution-calendar.so
  • #5 e_day_view_convert_time_to_position
    from /usr/lib/evolution/2.2/components/libevolution-calendar.so
  • #6 e_day_view_convert_time_to_position
    from /usr/lib/evolution/2.2/components/libevolution-calendar.so
  • #7 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-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
    from /usr/lib/libgobject-2.0.so.0
  • #12 gtk_widget_send_expose
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #16 g_main_depth
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #18 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #19 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #20 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #21 main
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0 


Other information:
Here's my log of STDOUT with CAMEL_DEBUG=all
es menu class init
adding hook target 'source'
camel_junk_plugin_init
calendar-gui-Message: ********* the state  in ok is 3 

calendar-gui-Message: ********* the state  in ok is 3 

calendar-gui-Message: ********* the state  in ok is 3 

calendar-gui-Message: ********* the state  in ok is 3 

calendar-gui-Message: ********* the state  in ok is 3 

calendar-gui-Message: ********* the state  in ok is 3 


(evolution:27172): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed

(evolution:27172): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed

(evolution:27172): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed

(evolution:27172): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed

(evolution:27172): libecal-CRITICAL **: e_cal_component_get_vtype: assertion
`priv->icalcomp != NULL' failed
calendar-gui-Message: make_title_from_comp(): Cannot handle object of type 0

(evolution:27172): libecal-CRITICAL **: e_cal_component_get_vtype: assertion
`priv->icalcomp != NULL' failed

(evolution:27172): libecal-CRITICAL **: e_cal_component_get_uid: assertion
`priv->icalcomp != NULL' failed
Comment 1 Allen Riddell 2005-04-29 17:46:57 UTC 
It happens most often when in "daily view" for me -- it's very consistent -- one
try is usually enough.
Comment 2 Chenthill P 2005-08-04 17:19:18 UTC 
Fix has been committed.
Comment 3 André Klapper 2005-12-11 03:18:17 UTC 
*** Bug 307477 has been marked as a duplicate of this bug. ***