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 468653 - crash in Tasks: Had just clicked "Reply"...
crash in Tasks: Had just clicked "Reply"...
Status: RESOLVED DUPLICATE of bug 427105
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-20 20:43 UTC by derrick.norris
Modified: 2007-09-21 13:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description derrick.norris 2007-08-20 20:43:18 UTC
Version: 2.10

What were you doing when the application crashed?
Had just clicked "Reply" on an email.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 152563712 vsize: 152563712 resident: 65724416 share: 33165312 rss: 65724416 rss_rlim: 4294967295
CPU usage: start_time: 1187642430 rtime: 855 utime: 815 stime: 40 cutime:2 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208248608 (LWP 24806)]
[New Thread -1300898928 (LWP 25007)]
[New Thread -1245058160 (LWP 24905)]
[New Thread -1290409072 (LWP 24903)]
[New Thread -1234175088 (LWP 24842)]
0x0011e402 in __kernel_vsyscall ()

Thread 1 (Thread -1208248608 (LWP 24806))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 segv_redirect
    at main.c line 408
  • #4 <signal handler called>
  • #5 slab_allocator_free_chunk
    at gslice.c line 1020
  • #6 magazine_cache_push_magazine
    at gslice.c line 567
  • #7 thread_memory_magazine2_unload
    at gslice.c line 697
  • #8 IA__g_slice_free1
    at gslice.c line 806
  • #9 IA__g_slist_free_1
    at gslist.c line 59
  • #10 IA__g_slist_remove
    at gslist.c line 214
  • #11 bonobo_ui_engine_update
    from /usr/lib/libbonoboui-2.so.0
  • #12 bonobo_ui_engine_xml_merge_tree
    from /usr/lib/libbonoboui-2.so.0
  • #13 ??
    from /usr/lib/libbonoboui-2.so.0
  • #14 _ORBIT_skel_small_Bonobo_UIContainer_setNode
    from /usr/lib/libbonobo-2.so.0
  • #15 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #16 Bonobo_UIContainer_setNode
    from /usr/lib/libbonobo-2.so.0
  • #17 ??
    from /usr/lib/libbonoboui-2.so.0
  • #18 bonobo_ui_component_set
    from /usr/lib/libbonoboui-2.so.0
  • #19 bonobo_ui_util_set_ui
    from /usr/lib/libbonoboui-2.so.0
  • #20 menubar_setup
    at menubar.c line 845
  • #21 set_frame_cb
    at editor-control-factory.c line 127
  • #22 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #23 IA__g_closure_invoke
    at gclosure.c line 490
  • #24 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #25 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #26 IA__g_signal_emit
    at gsignal.c line 2243
  • #27 ??
    from /usr/lib/libbonoboui-2.so.0
  • #28 _ORBIT_skel_small_Bonobo_Control_setFrame
    from /usr/lib/libbonobo-2.so.0
  • #29 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #30 Bonobo_Control_setFrame
    from /usr/lib/libbonobo-2.so.0
  • #31 bonobo_control_frame_bind_to_control
    from /usr/lib/libbonoboui-2.so.0
  • #32 bonobo_widget_construct_control_from_objref
    from /usr/lib/libbonoboui-2.so.0
  • #33 bonobo_widget_construct_control
    from /usr/lib/libbonoboui-2.so.0
  • #34 bonobo_widget_new_control
    from /usr/lib/libbonoboui-2.so.0
  • #35 create_composer
    at e-msg-composer.c line 3876
  • #36 e_msg_composer_new_with_type
    at e-msg-composer.c line 4049
  • #37 em_utils_reply_to_message
    at em-composer-utils.c line 1382
  • #38 reply_to_message
    at em-composer-utils.c line 1877
  • #39 get_message_done
    at mail-ops.c line 1707
  • #40 mail_msg_idle_cb
    at mail-mt.c line 480
  • #41 g_idle_dispatch
    at gmain.c line 3928
  • #42 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #43 g_main_context_iterate
    at gmain.c line 2677
  • #44 IA__g_main_loop_run
    at gmain.c line 2881
  • #45 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #46 main
    at main.c line 586
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:24806): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:24806): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
(evolution:24806): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(evolution:24806): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xaabf020'
(evolution:24806): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xaabf140'
(evolution:24806): e-data-server-DEBUG: Loading categories from "/home/dnorris/.evolution/categories.xml"
(evolution:24806): e-data-server-DEBUG: Loaded 29 categories
Cannot access memory at address 0xfffff7fc
--------------------------------------------------
Comment 1 palfrey 2007-09-21 13:28:38 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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