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 509639 - crash in Tasks: Opening the application;...
crash in Tasks: Opening the application;...
Status: RESOLVED DUPLICATE of bug 523463
Product: evolution
Classification: Applications
Component: BugBuddyBugs
unspecified
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-01-15 13:40 UTC by richard.g.morgan
Modified: 2008-09-28 19:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description richard.g.morgan 2008-01-15 13:40:07 UTC 
Version: 2.12

What were you doing when the application crashed?
Opening the application; I had just supplied my password for ms exchange.


Distribution: Fedora release 8 (Werewolf)
Gnome Release: 2.20.2 2007-11-27 (Red Hat, Inc)
BugBuddy Version: 2.20.1

System: Linux 2.6.23.9-85.fc8 #1 SMP Fri Dec 7 15:49:36 EST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 636338176 vsize: 636338176 resident: 42319872 share: 20348928 rss: 42319872 rss_rlim: 18446744073709551615
CPU usage: start_time: 1200404031 rtime: 64 utime: 47 stime: 17 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912496394176 (LWP 8786)]
[New Thread 1147169104 (LWP 8827)]
[New Thread 1126189392 (LWP 8804)]
[New Thread 1115699536 (LWP 8803)]
[New Thread 1105209680 (LWP 8801)]
[New Thread 1094719824 (LWP 8800)]
[New Thread 1084229968 (LWP 8798)]
0x0000003f2900e0bf in waitpid () from /lib64/libpthread.so.0

+ Trace 185429

Thread 1 (Thread 46912496394176 (LWP 8786))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 IA__g_spawn_sync
    at gspawn.c line 369
  • #2 IA__g_spawn_command_line_sync
    at gspawn.c line 677
  • #3 ??
    from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 IA__g_main_context_check
    at gmain.c line 2540
  • #6 g_main_context_iterate
    at gmain.c line 2691
  • #7 IA__g_main_loop_run
    at gmain.c line 2898
  • #8 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #9 main
    at main.c line 602
  • #10 __libc_start_main
    from /lib64/libc.so.6
  • #11 _start
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors ---------------------
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/93/2d8ac5f600c646719292da9c090c3afd219f57.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/b0/8c4fdd9f6daf7a0e9c958a6b0244b8d9d483aa.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/9c/2d58d7b1840af2387c008c58d2b596650f6f9f.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/ba/a257fc9076a2ffc67c5d959daba460272589fa.debug
warning: the debug information found in "/usr/lib/debug//usr/lib64/evolution-data-server-1.2/camel-providers/libcamelexchange.so.debug" does not match "/usr/lib64/evolution-data-server-1.2/camel-provi
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/54/64caa947fee52f7e25740d92af9e62d79aec3f.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/7f/bba7706883599d6df45722d7eb779d8768a80b.debug
--------------------------------------------------
Comment 1 Paul Smith 2008-03-19 22:46:48 UTC 
Dup of bug #523463
Comment 2 Philip Withnall 2008-09-28 19:19:07 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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