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 449810 - crash in Tasks: starting evolution
crash in Tasks: starting evolution
Status: RESOLVED DUPLICATE of bug 425093
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-06-21 15:42 UTC by Joseph Stephens
Modified: 2007-06-21 16:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Joseph Stephens 2007-06-21 15:42:30 UTC
Version: 2.10

What were you doing when the application crashed?
starting evolution


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 15:37:31 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: 172351488 vsize: 172351488 resident: 48361472 share: 40628224 rss: 48361472 rss_rlim: 4294967295
CPU usage: start_time: 1182440494 rtime: 113 utime: 96 stime: 17 cutime:2 cstime: 4 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 -1208809760 (LWP 5209)]
[New Thread -1252836464 (LWP 5295)]
[New Thread -1284318320 (LWP 5294)]
[New Thread -1210909808 (LWP 5246)]
(no debugging symbols found)
0x00e28402 in __kernel_vsyscall ()

Thread 1 (Thread -1208809760 (LWP 5209))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 strchr
    from /lib/libc.so.6
  • #6 camel_url_new_with_base
    from /usr/lib/libcamel-1.2.so.10
  • #7 camel_url_new
    from /usr/lib/libcamel-1.2.so.10
  • #8 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #9 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #10 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #11 ??
    from /lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #14 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #15 g_cclosure_marshal_VOID__VOID
    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_by_name
    from /lib/libgobject-2.0.so.0
  • #20 ??
    from /usr/lib/evolution/2.10/libefilterbar.so.0
  • #21 g_object_set_valist
    from /lib/libgobject-2.0.so.0
  • #22 g_object_set
    from /lib/libgobject-2.0.so.0
  • #23 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #24 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #25 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #26 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #27 ??
    from /lib/libglib-2.0.so.0
  • #28 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #29 ??
    from /lib/libglib-2.0.so.0
  • #30 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #31 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #32 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (167 sec old) ---------------------
Lost connection to Evolution Exchange backend process
(evolution:4860): evolution-mail-WARNING **: Error occurred while existing dialogue active:
Lost connection to Evolution Exchange backend process
(evolution:4860): evolution-mail-WARNING **: Error occurred while existing dialogue active:
Lost connection to Evolution Exchange backend process
(evolution:4860): evolution-mail-WARNING **: Error occurred while existing dialogue active:
Lost connection to Evolution Exchange backend process
(evolution:4860): evolution-mail-WARNING **: Error occurred while existing dialogue active:
Lost connection to Evolution Exchange backend process
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 André Klapper 2007-06-21 16:34:09 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 425093 ***