GNOME Bugzilla – Bug 444866
crash in 3x?? / g_slice_free_chain_with_offset / g_slist_free / 2x?? / html_object_destroy
Last modified: 2008-02-27 02:03:56 UTC
What were you doing when the application crashed? Setting up message filtering rules 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: 123858944 vsize: 123858944 resident: 40591360 share: 20901888 rss: 40591360 rss_rlim: 4294967295 CPU usage: start_time: 1181157460 rtime: 3955 utime: 3690 stime: 265 cutime:2 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 -1209071904 (LWP 26972)] [New Thread -1220781168 (LWP 26989)] (no debugging symbols found) 0x00667402 in __kernel_vsyscall ()
+ Trace 138864
Thread 1 (Thread -1209071904 (LWP 26972))
----------- .xsession-errors (109 sec old) --------------------- (evolution:26972): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9366130' DEBUG: Inbox/bwwonline (mbox:/root/.evolution/mail/local#Inbox/bwwonline) DEBUG: Inbox/bwwonline (mbox:/root/.evolution/mail/local#Inbox/bwwonline) DEBUG: Inbox/Comcast David (mbox:/root/.evolution/mail/local#Inbox/Comcast%20David) DEBUG: Inbox/Comcast Nancy (mbox:/root/.evolution/mail/local#Inbox/Comcast%20Nancy) DEBUG: Inbox/Hotmail David (mbox:/root/.evolution/mail/local#Inbox/Hotmail%20David) DEBUG: A Moment in Time (mbox:/root/.evolution/mail/local#A%20Moment%20in%20Time) DEBUG: Kim Komando (mbox:/root/.evolution/mail/local#Kim%20Komando) (evolution:26972): 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:26972): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9366250' (evolution:26972): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9366370' --------------------------------------------------
*** Bug 446342 has been marked as a duplicate of this bug. ***
*** Bug 446295 has been marked as a duplicate of this bug. ***
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. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
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, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
*** Bug 447008 has been marked as a duplicate of this bug. ***
*** Bug 447398 has been marked as a duplicate of this bug. ***
*** Bug 448636 has been marked as a duplicate of this bug. ***
*** Bug 448680 has been marked as a duplicate of this bug. ***
*** Bug 449099 has been marked as a duplicate of this bug. ***
*** Bug 449911 has been marked as a duplicate of this bug. ***
*** Bug 452696 has been marked as a duplicate of this bug. ***
What were you doing when the application crashed? Setting up message filtering rules..? No. Was the first runnings, after setting the account email. Evolution was downloading a big number of email in the server, and stooped and next crushed. In the next Evolution running, the database was corrupted. I erased all email, unchek the spam verification (because was so slow). When finish download, check the spam verification, and now all is running good.
*** Bug 453055 has been marked as a duplicate of this bug. ***
*** Bug 452899 has been marked as a duplicate of this bug. ***
*** Bug 453534 has been marked as a duplicate of this bug. ***
OK, everyone -- can you please confirm a few facts? Is one of these true? (a) Displaying images is enabled Edit / Preferences / Mail Preferences / HTML Mail / Loading Images *not* set to "Never load images from the internet" but either set to Contacts, or All and Evo crashed viewing a HTML mail (b) While displaying a HTML mail, you enabled View / Load Images Developers: I just spotted a report with matching descriptions by the same submitter with a really short delay. These traces actually are slighly different. See bug 453532 and bug 453533. I believe both these traces, which are suspect to be the same issue anyway, actually *are* the same issue, related to displaying images in HTML mail. Reporters: We still need a better stacktrace. Please see http://live.gnome.org/GettingTraces for more information on how to do so and get us a stack trace with debugging symbols, if you can reproduce this crash. Thanks! [1] debugging packages for evolution, evolution-data-server and gtkhtml, plus debugging packages for glib, gtk+ and gnome-vfs, GNOME's main libraries
*** Bug 453532 has been marked as a duplicate of this bug. ***
*** Bug 443732 has been marked as a duplicate of this bug. ***
*** Bug 451619 has been marked as a duplicate of this bug. ***
*** Bug 458242 has been marked as a duplicate of this bug. ***
*** Bug 457517 has been marked as a duplicate of this bug. ***
*** Bug 454970 has been marked as a duplicate of this bug. ***
*** Bug 457635 has been marked as a duplicate of this bug. ***
*** Bug 465700 has been marked as a duplicate of this bug. ***
*** Bug 468807 has been marked as a duplicate of this bug. ***
*** Bug 467144 has been marked as a duplicate of this bug. ***
*** Bug 466830 has been marked as a duplicate of this bug. ***
*** Bug 466588 has been marked as a duplicate of this bug. ***
*** Bug 431068 has been marked as a duplicate of this bug. ***
*** Bug 470586 has been marked as a duplicate of this bug. ***
*** Bug 469577 has been marked as a duplicate of this bug. ***
*** Bug 465143 has been marked as a duplicate of this bug. ***
*** Bug 479460 has been marked as a duplicate of this bug. ***
*** Bug 476153 has been marked as a duplicate of this bug. ***
*** Bug 474654 has been marked as a duplicate of this bug. ***
*** Bug 475953 has been marked as a duplicate of this bug. ***
*** Bug 476121 has been marked as a duplicate of this bug. ***
*** Bug 480119 has been marked as a duplicate of this bug. ***
*** Bug 480385 has been marked as a duplicate of this bug. ***
*** Bug 480419 has been marked as a duplicate of this bug. ***
*** Bug 480430 has been marked as a duplicate of this bug. ***
*** Bug 481157 has been marked as a duplicate of this bug. ***
*** Bug 481564 has been marked as a duplicate of this bug. ***
*** Bug 482411 has been marked as a duplicate of this bug. ***
*** Bug 470607 has been marked as a duplicate of this bug. ***
*** Bug 475864 has been marked as a duplicate of this bug. ***
*** Bug 477624 has been marked as a duplicate of this bug. ***
*** Bug 477626 has been marked as a duplicate of this bug. ***
*** Bug 479470 has been marked as a duplicate of this bug. ***
*** Bug 479964 has been marked as a duplicate of this bug. ***
*** Bug 479976 has been marked as a duplicate of this bug. ***
*** Bug 482015 has been marked as a duplicate of this bug. ***
Dear reporters, Unfortunately the stack trace here is still 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 answer the questions in comment 16 and also 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
*** Bug 482863 has been marked as a duplicate of this bug. ***
*** Bug 484638 has been marked as a duplicate of this bug. ***
*** Bug 485122 has been marked as a duplicate of this bug. ***
*** Bug 484975 has been marked as a duplicate of this bug. ***
*** Bug 484935 has been marked as a duplicate of this bug. ***
*** Bug 487446 has been marked as a duplicate of this bug. ***
*** Bug 487742 has been marked as a duplicate of this bug. ***
*** Bug 479958 has been marked as a duplicate of this bug. ***
*** Bug 491185 has been marked as a duplicate of this bug. ***
Are there any usable backtraces for this bug? Perhaps in one of the dupes?
(evolution:26972): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9366130' This is bug #447591, which is fixed now. *** This bug has been marked as a duplicate of 447591 ***
*** Bug 485755 has been marked as a duplicate of this bug. ***
*** Bug 488586 has been marked as a duplicate of this bug. ***
*** Bug 489092 has been marked as a duplicate of this bug. ***
*** Bug 489807 has been marked as a duplicate of this bug. ***
*** Bug 500630 has been marked as a duplicate of this bug. ***
*** Bug 494491 has been marked as a duplicate of this bug. ***
*** Bug 494621 has been marked as a duplicate of this bug. ***
*** Bug 495541 has been marked as a duplicate of this bug. ***
*** Bug 477673 has been marked as a duplicate of this bug. ***
*** Bug 503408 has been marked as a duplicate of this bug. ***
*** Bug 503438 has been marked as a duplicate of this bug. ***
*** Bug 518267 has been marked as a duplicate of this bug. ***
*** Bug 495756 has been marked as a duplicate of this bug. ***
*** Bug 504151 has been marked as a duplicate of this bug. ***
*** Bug 504199 has been marked as a duplicate of this bug. ***
*** Bug 505876 has been marked as a duplicate of this bug. ***
*** Bug 505951 has been marked as a duplicate of this bug. ***
*** Bug 506396 has been marked as a duplicate of this bug. ***
*** Bug 492567 has been marked as a duplicate of this bug. ***
*** Bug 515244 has been marked as a duplicate of this bug. ***
*** Bug 518074 has been marked as a duplicate of this bug. ***
*** Bug 457474 has been marked as a duplicate of this bug. ***