GNOME Bugzilla – Bug 412537
RHEL4 Evolution libnss3 crash
Last modified: 2007-04-12 20:29:24 UTC
Distribution: Red Hat Enterprise Linux AS release 4 (Nahant Update 4) Package: Evolution Severity: critical Version: GNOME2.8.0 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: Unstartable Evolution Bugzilla-Product: Evolution Bugzilla-Component: Mailer Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: You click on the Evolution icon, the Evolution doesn't come up, instead of it the error widget 'The Application "evolution" has quit unexpectedly' appears. Steps to reproduce the crash: 1. start Evolution Expected Results: Evolution starts in mail mode. How often does this happen? Always (since this morning). Additional Information: Yesterday the latest Seamonkey patch was applied. Debugging Information: Backtrace was generated from '/usr/bin/evolution-2.0' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208486208 (LWP 4586)] (no debugging symbols found) 0x0088c7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 114250
Thread 1 (Thread -1208486208 (LWP 4586))
------- Bug created by bug-buddy at 2007-02-27 06:07 -------
Well, it turns out, that RHSA-2007:0077-4 solves this problem. Of course, since my mailer was the subject of the error, I didn't know this until I found an alternative access to my mail...
*** Bug 412298 has been marked as a duplicate of this bug. ***
*** Bug 412776 has been marked as a duplicate of this bug. ***
*** Bug 412258 has been marked as a duplicate of this bug. ***
*** Bug 412583 has been marked as a duplicate of this bug. ***
*** Bug 413885 has been marked as a duplicate of this bug. ***
*** Bug 413743 has been marked as a duplicate of this bug. ***
*** Bug 413726 has been marked as a duplicate of this bug. ***
*** Bug 413725 has been marked as a duplicate of this bug. ***
*** Bug 423547 has been marked as a duplicate of this bug. ***