GNOME Bugzilla – Bug 485482
crash in Email: i was using Pidgin Messe...
Last modified: 2007-10-11 18:44:08 UTC
Version: 2.10 What were you doing when the application crashed? i was using Pidgin Messenger and Evolution 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Bluecurve Memory status: size: 163758080 vsize: 163758080 resident: 63381504 share: 46530560 rss: 63381504 rss_rlim: 4294967295 CPU usage: start_time: 1192040832 rtime: 1383 utime: 1295 stime: 88 cutime:0 cstime: 0 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 -1208629536 (LWP 8490)] [New Thread -1339790448 (LWP 8858)] [New Thread -1269744752 (LWP 8826)] [New Thread -1258861680 (LWP 8495)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 169315
Thread 3 (Thread -1269744752 (LWP 8826))
----------- .xsession-errors --------------------- (evolution:8490): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9c6e480' (evolution:8490): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9c6e5a0' JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] --------------------------------------------------
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 460409 ***