Bug 503690 – crash in Tasks: I had just started evolu...

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 503690 - crash in Tasks: I had just started evolu...


Summary:	crash in Tasks: I had just started evolu...


Status:	RESOLVED DUPLICATE of bug 523463

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Triage Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-12-15 01:11 UTC by jazbo
Modified:	2008-09-28 19:18 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description jazbo 2007-12-15 01:11:10 UTC

Version: 2.12

What were you doing when the application crashed?
I had just started evolution and selected an html message to display when it crashed.


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.8-63.fc8 #1 SMP Wed Nov 21 17:56:40 EST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 794951680 vsize: 794951680 resident: 61698048 share: 21458944 rss: 61698048 rss_rlim: 18446744073709551615
CPU usage: start_time: 1197680480 rtime: 194 utime: 163 stime: 31 cutime:1 cstime: 7 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 46912743798320 (LWP 17281)]
[New Thread 1126189392 (LWP 17402)]
[New Thread 1084229968 (LWP 17400)]
[New Thread 1105209680 (LWP 17311)]
0x00002aaaad2090bf in waitpid () from /lib64/libpthread.so.0

+ Trace 181917

Thread 1 (Thread 46912743798320 (LWP 17281))

#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
at bonobo-main.c line 311
#9 main
at main.c line 602
#10 __libc_start_main
at libc-start.c line 220
#11 _start
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors ---------------------
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/fb/47ab2f0824857cee42e161b83afefb73ee0684.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/99/2067cd33c317e94d4b485d6f8182965d609c5e.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/c8/0345ed04c98b8cd8800c4464a38e055b6dc496.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/af/d45ff0d19b2f3cff2bc7abadf962f2b0c7ab51.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/ae/0e278ef08f80a0534a13cfa6e088428ad7731c.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/8b/20dcd1812462895a942a6c602b32b5a4e56e76.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/ba/a257fc9076a2ffc67c5d959daba460272589fa.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/25/c02610856436e6ff104cd99b95b8f8cf22b845.debug
--------------------------------------------------

Comment 1 Paul Smith 2008-03-19 22:46:14 UTC

Dup of bug #523463

Comment 2 Philip Withnall 2008-09-28 19:18:31 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 ***