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 437038 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 465234
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 457653 473218 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-05-09 00:30 UTC by jld
Modified: 2007-09-03 16:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description jld 2007-05-09 00:30:27 UTC
What were you doing when the application crashed?



Distribution: Fedora release 6.93 (Rawhide)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3116.fc7 #1 SMP Thu Apr 26 10:36:44 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 170618880 vsize: 170618880 resident: 46931968 share: 23142400 rss: 46931968 rss_rlim: 4294967295
CPU usage: start_time: 1178639603 rtime: 8098 utime: 6773 stime: 1325 cutime:41 cstime: 58 timeout: 0 it_real_value: 0 frequency: 100

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

(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 -1209100576 (LWP 5437)]
[New Thread -1306563696 (LWP 5480)]
[New Thread -1317700720 (LWP 5456)]
[New Thread -1236604016 (LWP 5445)]
(no debugging symbols found)
0x00579402 in __kernel_vsyscall ()

Thread 1 (Thread -1209100576 (LWP 5437))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 ??
    from /lib/libglib-2.0.so.0
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 g_slice_free_chain_with_offset
    from /lib/libglib-2.0.so.0
  • #9 g_slist_free
    from /lib/libglib-2.0.so.0
  • #10 ??
    from /usr/lib/evolution/2.10/plugins/liborg-gnome-plugin-manager.so
  • #11 g_datalist_clear
    from /lib/libglib-2.0.so.0
  • #12 ??
    from /lib/libgobject-2.0.so.0
  • #13 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 g_object_unref
    from /lib/libgobject-2.0.so.0
  • #17 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #18 ??
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #21 gtk_button_clicked
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #24 ??
    from /lib/libgobject-2.0.so.0
  • #25 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #26 ??
    from /lib/libgobject-2.0.so.0
  • #27 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #28 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #29 gtk_button_released
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 ??
    from /lib/libgobject-2.0.so.0
  • #33 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #34 ??
    from /lib/libgobject-2.0.so.0
  • #35 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #36 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #37 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #39 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #40 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #41 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #42 ??
    from /lib/libglib-2.0.so.0
  • #43 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #44 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #45 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (107 sec old) ---------------------
Window manager warning: Window 0x5600020 (Welcome to) sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
Window manager warning: Window 0x5600020 (Welcome to) sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
(evolution:5437): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:5437): Gtk-CRITICAL **: gtk_toggle_button_get_active: assertion `GTK_IS_TOGGLE_BUTTON (toggle_button)' failed
(evolution:5437): 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?)
(evolution:5437): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa445490'
(evolution:5437): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa4456d0'
(evolution:5437): e-data-server-CRITICAL **: e_source_get_uri: assertion `E_IS_SOURCE (source)' failed
(evolution:5437): GConf-CRITICAL **: gconf_client_set_string: assertion `val != NULL' failed
--------------------------------------------------
Comment 1 Chenthill P 2007-05-09 10:26:45 UTC
The stack traces are not much useful and in future please provide the steps to reproduce.
Comment 2 palfrey 2007-08-17 13:04:57 UTC
*** Bug 457653 has been marked as a duplicate of this bug. ***
Comment 3 Tobias Mueller 2007-08-23 07:05:06 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 465234 ***
Comment 4 palfrey 2007-09-03 16:56:46 UTC
*** Bug 473218 has been marked as a duplicate of this bug. ***