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 467674 - crash in Tasks: check for pop server
crash in Tasks: check for pop server
Status: RESOLVED DUPLICATE of bug 464409
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-17 14:49 UTC by brad.hong
Modified: 2007-08-23 11:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description brad.hong 2007-08-17 14:49:33 UTC
Version: 2.10

What were you doing when the application crashed?
check for pop server


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: 131383296 vsize: 131383296 resident: 52252672 share: 34197504 rss: 52252672 rss_rlim: 4294967295
CPU usage: start_time: 1187360626 rtime: 1687 utime: 1611 stime: 76 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208600864 (LWP 3639)]
[New Thread -1228928112 (LWP 3719)]
[New Thread -1240073328 (LWP 3695)]
[New Thread -1322087536 (LWP 3693)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208600864 (LWP 3639))

  • #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_free1
    from /lib/libglib-2.0.so.0
  • #9 g_slist_free_1
    from /lib/libglib-2.0.so.0
  • #10 g_slist_remove
    from /lib/libglib-2.0.so.0
  • #11 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 gtk_window_remove_mnemonic
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 g_cclosure_marshal_VOID__OBJECT
    from /lib/libgobject-2.0.so.0
  • #15 ??
    from /lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #17 ??
    from /lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #20 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #34 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 gtk_widget_unparent
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #39 g_cclosure_marshal_VOID__OBJECT
    from /lib/libgobject-2.0.so.0
  • #40 ??
    from /lib/libgobject-2.0.so.0
  • #41 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #42 ??
    from /lib/libgobject-2.0.so.0
  • #43 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #44 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #45 gtk_container_remove
    from /usr/lib/libgtk-x11-2.0.so.0
  • #46 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #47 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #48 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #49 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #50 ??
    from /usr/lib/evolution/2.10/libeutil.so.0
  • #51 ??
    from /usr/lib/evolution/2.10/libeutil.so.0
  • #52 ??
    from /lib/libglib-2.0.so.0
  • #53 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #54 ??
    from /lib/libglib-2.0.so.0
  • #55 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #56 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #57 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (71 sec old) ---------------------
(evolution:3639): 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:3639): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9f11240'
(evolution:3639): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9f11360'
(evolution:3639): 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:3639): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9f11000'
(evolution:3639): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9f115a0'
calendar selection changed
calendar selection changed
camel_groupwise_store_finalize
--------------------------------------------------
Comment 1 Lucky Wankhede 2007-08-23 11:51:26 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 464409 ***