GNOME Bugzilla – Bug 454065
crash in Tasks: - downloaded email - cha...
Last modified: 2007-11-30 20:10:37 UTC
What were you doing when the application crashed? - downloaded email - changed "mark message as read" from 1.5 to 0 seconds - selected new messages to read - crashed ;-) 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: 129003520 vsize: 129003520 resident: 29569024 share: 16969728 rss: 29569024 rss_rlim: 4294967295 CPU usage: start_time: 1183662734 rtime: 5141 utime: 4654 stime: 487 cutime:149 cstime: 95 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 -1208412448 (LWP 3089)] [New Thread -1326437488 (LWP 30427)] [New Thread -1336927344 (LWP 30416)] [New Thread -1239929968 (LWP 3248)] [New Thread -1264071792 (LWP 3157)] (no debugging symbols found) 0x0093d402 in __kernel_vsyscall ()
+ Trace 145969
Thread 3 (Thread -1336927344 (LWP 30416))
----------- .xsession-errors (67 sec old) --------------------- Opener: received RemoveSecret (evolution:3089): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (evolution:3089): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail' (evolution:3089): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 Setting up initial mail tree addressbook_migrate (0.0.0) DEBUG: Inbox/mtnice (mbox:/home/lola/.evolution/mail/local#Inbox/mtnice) (evolution:3089): 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:3089): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9315000' (evolution:3089): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9315120' --------------------------------------------------
-------- I also created a couple of "message filters" and clicked very fast over email message headers, before that bug occured. This happened the first time I worked in Evolution, after initial installation of system. I've restarted Evolution and carried on working again afterwards, and couldn't replicate the bug - my system is overall STABLE. --------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the Details, now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, pango, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
------------------------------------ Later on, when I used the application again, it also just closed suddenly without generating debugging information - it might be related. I've updated my system with the following debug programs for my distribution: ------------------------------------ evolution-debuginfo-2.10.2-3.fc7 evolution-data-server-debuginfo-1.10.2-3.fc7 gtkhtml3-debuginfo-3.14.2-1.fc7 gtk+-debuginfo-1.2.10-57.fc7 ------------------------------------ I'm waiting to download the rest of the debug programs that you mentioned. I can carry on using the application to read my email and when the crash happens again give you more "stack trace" information. ------------------------------------
I've installed these additional packages that you mentioned: -------------------------------- glib-debuginfo-1.2.10-26.fc7 gnome-vfs2-debuginfo-2.18.1-4.fc7 pango-debuginfo-1.16.4-1.fc7 libgnome-debuginfo-2.18.0-4.fc7 libgnomeui-debuginfo-2.18.1-2.fc7 -------------------------------- Now I'm using Evolution as my email client as usual - awaiting tha bug ;-) -
cool, thanks a lot for your help in advance!
This bug re-occurred, bug-buddy generated another report which was submitted under bug # 458202 , I did not notice a "Details" section containing the stacktrace. There was warnings like: "the debug information found in ... does not match ..." available at #458202.
Created attachment 92072 [details] Stack trace information. Checked email, added new email account, checked email again, attempted to close application with the X close button on right top of window, application crashed and bug buddy generated this attached stack traces.
Created attachment 92104 [details] Stack trace information #2. Checked email, clicked on "unmatched folders", clicked on Inbox, bam.
a classic fedora problem, we have duplicates of both traces already and no useful traces about these issues. :-(
Would it help if we could find a way of replicating this issue?
definitely!
------------- happened again ------------- - checked new email - clicked on new email - application closed without generating a bug report --------------------- me still working on replicating this issue ;-) ---------------------
as i recall: this never happened while i was using mozilla-mail with FC2 what's tha difference? --------------------------------- anyway: me still working on replicating this issue ;-) =================================
(evolution:3133): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xaa6c008' (evolution:3133): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xaa6c128' This is bug #447591, which is fixed now. *** This bug has been marked as a duplicate of 447591 ***