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


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 444924

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-26 17:05 UTC by pavel
Modified:	2007-10-29 10:49 UTC

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

Description pavel 2007-10-26 17:05:36 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.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 174010368 vsize: 174010368 resident: 71954432 share: 47714304 rss: 71954432 rss_rlim: 4294967295
CPU usage: start_time: 1193331402 rtime: 4100 utime: 3698 stime: 402 cutime:31 cstime: 18 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 -1209006368 (LWP 3181)]
[New Thread -1274692720 (LWP 24629)]
[New Thread -1226314864 (LWP 3367)]
[New Thread -1285575792 (LWP 3265)]
[New Thread -1248859248 (LWP 3189)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 173086

Thread 1 (Thread -1209006368 (LWP 3181))

#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/libgtk-x11-2.0.so.0
#11 g_hash_table_foreach
from /lib/libglib-2.0.so.0
#12 ??
from /usr/lib/libgtk-x11-2.0.so.0
#13 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#14 g_closure_invoke
from /lib/libgobject-2.0.so.0
#15 ??
from /lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#17 g_signal_emit_by_name
from /lib/libgobject-2.0.so.0
#18 ??
from /usr/lib/libgdk-x11-2.0.so.0
#19 ??
from /usr/lib/libgdk-x11-2.0.so.0
#20 ??
from /usr/lib/libgdk-x11-2.0.so.0
#21 ??
from /usr/lib/libgdk-x11-2.0.so.0
#22 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#23 ??
from /lib/libglib-2.0.so.0
#24 g_main_loop_run
from /lib/libglib-2.0.so.0
#25 bonobo_main
from /usr/lib/libbonobo-2.so.0
#26 main
#0 __kernel_vsyscall



----------- .xsession-errors (123 sec old) ---------------------
  Major opcode:  20
  Minor opcode:  0
  Resource id:  0x1202610
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x1202610
(evolution:3181): Gtk-CRITICAL **: gtk_file_system_unix_get_parent: assertion `g_path_is_absolute (filename)' failed
(evolution:3181): 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?)
(evolution:3181): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa499c80'
(evolution:3181): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa499da0'
--------------------------------------------------

Comment 1 Akhil Laddha 2007-10-29 10:49:55 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 444924 ***