Bug 499499 – crash in Tasks: I just told you I could ...

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 499499 - crash in Tasks: I just told you I could ...


Summary:	crash in Tasks: I just told you I could ...


Status:	RESOLVED DUPLICATE of bug 442030

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:	2007-11-25 08:51 UTC by carbee
Modified:	2007-11-25 10:53 UTC

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

Description carbee 2007-11-25 08:51:28 UTC

Version: 2.10

What were you doing when the application crashed?
I just told you I could not reproduce the problem, but yet it happened by closing a simple mail window with the cross in the upper right corner.  


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 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 142139392 vsize: 142139392 resident: 62160896 share: 41848832 rss: 62160896 rss_rlim: 4294967295
CPU usage: start_time: 1195974741 rtime: 1667 utime: 1518 stime: 149 cutime:0 cstime: 2 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 -1208199456 (LWP 3226)]
[New Thread -1245713520 (LWP 3251)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 179549

Thread 1 (Thread -1208199456 (LWP 3226))

#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_free_chain_with_offset
from /lib/libglib-2.0.so.0
#9 g_slist_free
from /lib/libglib-2.0.so.0
#10 ??
from /usr/lib/libbonoboui-2.so.0
#11 ??
from /lib/libglib-2.0.so.0
#12 bonobo_ui_engine_dispose
from /usr/lib/libbonoboui-2.so.0
#13 ??
from /usr/lib/libbonoboui-2.so.0
#14 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#15 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#18 ??
from /usr/lib/libgdk-x11-2.0.so.0
#19 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#20 ??
from /lib/libglib-2.0.so.0
#21 g_main_loop_run
from /lib/libglib-2.0.so.0
#22 bonobo_main
from /usr/lib/libbonobo-2.so.0
#23 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
warning: .dynamic section for "/usr/lib/libebook-1.2.so.9" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libecal-1.2.so.7" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libgtkhtml-3.14.so.19" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/lib/libselinux.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------

Comment 1 Susana 2007-11-25 10:53:43 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 442030 ***