GNOME Bugzilla – Bug 310831
Assert failure at gmessages.c:547 (aborted)
Last modified: 2005-08-24 16:04:39 UTC
Distribution: Fedora Core release 4 (Stentz) Package: Evolution Severity: major Version: GNOME2.10.0 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: Assert failure at gmessages.c:547 (aborted) Bugzilla-Product: Evolution Bugzilla-Component: Mailer Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: child->parent == GTK_WIDGET (container)") at gmessages.c:547 Steps to reproduce the crash: 1. evolution was running 2. it crashed 3. Expected Results: evolution doesn't crash How often does this happen? first time Additional Information: debuginfo rpm's installed. Debugging Information: Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1209059648 (LWP 3136)] [New Thread -1380996176 (LWP 3907)] [New Thread -1360016464 (LWP 3858)] [New Thread -1260389456 (LWP 3203)] [New Thread -1291859024 (LWP 3173)] [New Thread -1281369168 (LWP 3171)] [New Thread -1256203344 (LWP 3168)] [New Thread -1245709392 (LWP 3167)] [New Thread -1233118288 (LWP 3162)] [New Thread -1222284368 (LWP 3145)] [New Thread -1211794512 (LWP 3144)] 0x004a8402 in ?? ()
+ Trace 61845
Thread 1 (Thread -1209059648 (LWP 3136))
------- Bug moved to this database by unknown@gnome.bugs 2005-07-19 04:21 UTC -------
dont compile with fatal warnings
i can't see anything evolution specific there. if it is anything other than a warning which is wrongly fatal, i guess it might be in bonobo? gtk+? bouncing to bonobo incase they can make any sense of it/have seen duplicates.
ok so its a duplicate, if a bonobo thinks it looks related, see the duplicate of bug thanks. *** This bug has been marked as a duplicate of 300539 ***
This rather looks like a dup of Bug 305680 to me....
Thanks for the bug report. 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? *** This bug has been marked as a duplicate of 305680 ***