Bug 507915 – crash in Tasks:

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 507915 - crash in Tasks:


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 458670

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

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-07 19:43 UTC by garth
Modified:	2008-01-10 04:19 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description garth 2008-01-07 19:43:14 UTC

Version: 2.10

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 20:28:15 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Glider
Icon Theme: gnome

Memory status: size: 762204160 vsize: 762204160 resident: 143912960 share: 45383680 rss: 143912960 rss_rlim: 18446744073709551615
CPU usage: start_time: 1199726068 rtime: 8961 utime: 7611 stime: 1350 cutime:1736 cstime: 671 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496383344 (LWP 3667)]
[New Thread 1136679248 (LWP 4449)]
[New Thread 1136945488 (LWP 3721)]
[New Thread 1094719824 (LWP 3692)]
(no debugging symbols found)
0x0000003e37c0d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 184440

Thread 1 (Thread 46912496383344 (LWP 3667))

#0 waitpid
from /lib64/libpthread.so.0
#1 ??
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_utf8_offset_to_pointer
from /lib64/libglib-2.0.so.0
#4 ??
from /usr/lib64/libedataserverui-1.2.so.8
#5 ??
from /usr/lib64/libedataserverui-1.2.so.8
#6 ??
from /usr/lib64/libedataserverui-1.2.so.8
#7 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#8 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#9 ??
from /lib64/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#11 g_signal_emit
from /lib64/libgobject-2.0.so.0
#12 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#13 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#15 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#16 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#17 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#18 ??
from /lib64/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#20 g_signal_emit
from /lib64/libgobject-2.0.so.0
#21 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#22 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#23 ??
from /usr/lib64/libgdk-x11-2.0.so.0
#24 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#25 ??
from /lib64/libglib-2.0.so.0
#26 g_main_loop_run
from /lib64/libglib-2.0.so.0
#27 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#28 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors ---------------------
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a0156c specified for 0x4a0160c ().
report junk?? Re: [ops] SALE 70% OFF on Pfizer
report junk?? [ops] Hot repl1ca w4tches from 2008 vTr9X
report junk?? Re: [ops] SALE 70% OFF on Pfizer
report junk?? [ops] Winter qual1ty w4tches offer bplx
report junk?? [ops] Hot repl1ca w4tches from 2008
report junk?? [ops] Repl1ca r0lex w4tches! SAVE Big!
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff271fd000
--------------------------------------------------

Comment 1 Akhil Laddha 2008-01-10 04:19:28 UTC

Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you
find.


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