Bug 449671 – crash in Tasks: closing app

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 449671 - crash in Tasks: closing app


Summary:	crash in Tasks: closing app


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-06-21 03:10 UTC by dpetty
Modified:	2007-06-21 03:32 UTC

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

Description dpetty 2007-06-21 03:10:11 UTC

What were you doing when the application crashed?
closing app


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 127811584 vsize: 127811584 resident: 38633472 share: 21659648 rss: 38633472 rss_rlim: 4294967295
CPU usage: start_time: 1182394729 rtime: 833 utime: 777 stime: 56 cutime:54 cstime: 13 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 -1208469792 (LWP 14394)]
[New Thread -1302529136 (LWP 14454)]
[New Thread -1227715696 (LWP 14452)]
(no debugging symbols found)
0x002a9402 in __kernel_vsyscall ()

+ Trace 142573

Thread 1 (Thread -1208469792 (LWP 14394))

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



----------- .xsession-errors (56 sec old) ---------------------
(evolution:14394): e-data-server-DEBUG: Loaded 29 categories
(evolution:14394): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(evolution:14394): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x922a128'
(evolution:14394): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x922a248'
(evolution:14394): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:14394): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail'
(evolution:14394): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:14394): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:14394): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:14394): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
--------------------------------------------------

Comment 1 Karsten Bräckelmann 2007-06-21 03:32:12 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 ***