Bug 489708 – 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 489708 - crash in Tasks:


Summary:	crash in Tasks:


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-10-24 07:42 UTC by jbell
Modified:	2007-10-30 04:35 UTC

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

Description jbell 2007-10-24 07:42:07 UTC

Version: 2.10

What were you doing when the application crashed?



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

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 141017088 vsize: 141017088 resident: 59625472 share: 40325120 rss: 59625472 rss_rlim: 4294967295
CPU usage: start_time: 1193180373 rtime: 4645 utime: 4339 stime: 306 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 -1208514848 (LWP 3180)]
[New Thread -1219392624 (LWP 3226)]
[New Thread -1335477360 (LWP 3211)]
[New Thread -1252009072 (LWP 3201)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 172466

Thread 1 (Thread -1208514848 (LWP 3180))

#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 ---------------------
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
** Message: Response 1
** Message: Response 1
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
--------------------------------------------------

Comment 1 Akhil Laddha 2007-10-30 04:35:42 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 ***