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 448740 - crash in Tasks: opening evolution edit
crash in Tasks: opening evolution edit
Status: RESOLVED DUPLICATE of bug 475330
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 450023 452571 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-06-18 11:12 UTC by r.pheeps
Modified: 2007-10-23 17:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description r.pheeps 2007-06-18 11:12:55 UTC
Version: 2.10

What were you doing when the application crashed?
opening evolution edit


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 688394240 vsize: 688394240 resident: 58421248 share: 32514048 rss: 58421248 rss_rlim: 18446744073709551615
CPU usage: start_time: 1182162221 rtime: 930 utime: 866 stime: 64 cutime:2 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496361056 (LWP 6067)]
[New Thread 1084496208 (LWP 6088)]
[New Thread 1084229968 (LWP 6087)]
(no debugging symbols found)
0x000000357fa0d89f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496361056 (LWP 6067))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
    from /lib64/libglib-2.0.so.0
  • #4 ??
    from /lib64/libglib-2.0.so.0
  • #5 ??
    from /lib64/libglib-2.0.so.0
  • #6 g_slice_free_chain_with_offset
    from /lib64/libglib-2.0.so.0
  • #7 pango_layout_line_unref
    from /usr/lib64/libpango-1.0.so.0
  • #8 ??
    from /usr/lib64/libpango-1.0.so.0
  • #9 ??
    from /usr/lib64/libpango-1.0.so.0
  • #10 g_object_unref
    from /lib64/libgobject-2.0.so.0
  • #11 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #12 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #13 ??
    from /lib64/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #16 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #17 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #18 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #19 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #20 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #21 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #22 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #23 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #24 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #25 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #26 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #27 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #28 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #29 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #30 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #31 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #32 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #33 bonobo_socket_add_id
    from /usr/lib64/libbonoboui-2.so.0
  • #34 bonobo_control_frame_get_remote_window
    from /usr/lib64/libbonoboui-2.so.0
  • #35 ??
    from /usr/lib64/libbonoboui-2.so.0
  • #36 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #37 ??
    from /lib64/libgobject-2.0.so.0
  • #38 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #39 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #40 gtk_widget_realize
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #41 gtk_widget_map
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #42 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #43 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #44 ??
    from /lib64/libgobject-2.0.so.0
  • #45 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #46 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #47 gtk_widget_map
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #48 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #49 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #50 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #51 ??
    from /lib64/libgobject-2.0.so.0
  • #52 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #53 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #54 gtk_widget_map
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #55 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #56 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #57 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #58 ??
    from /lib64/libgobject-2.0.so.0
  • #59 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #60 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #61 gtk_widget_map
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #62 gtk_widget_set_child_visible
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #63 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #64 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #65 ??
    from /lib64/libgobject-2.0.so.0
  • #66 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #67 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #68 ??
    from /usr/lib64/evolution/2.10/libemiscwidgets.so.0
  • #69 ??
    from /lib64/libglib-2.0.so.0
  • #70 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #71 ??
    from /lib64/libglib-2.0.so.0
  • #72 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #73 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #74 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors (43 sec old) ---------------------
(evolution:6067): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922
(evolution:6067): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922
(evolution:6067): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922
(evolution:6067): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib64/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
(evolution:6067): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa2f440'
(evolution:6067): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa2fa40'
--------------------------------------------------
Comment 1 André Klapper 2007-06-18 20:47:29 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the Details, now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance!

[1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, pango, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
Comment 2 palfrey 2007-06-29 16:41:37 UTC
*** Bug 450023 has been marked as a duplicate of this bug. ***
Comment 3 palfrey 2007-06-30 15:25:35 UTC
*** Bug 452571 has been marked as a duplicate of this bug. ***
Comment 4 Tobias Mueller 2007-10-23 17:06:08 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 475330 ***