Red Hat Bugzilla – Bug 152147
Evolution hangs when creating a new mail
Last modified: 2007-11-30 17:11:02 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050302 Firefox/1.0.1 Fedora/1.0.1-1.3.2
Description of problem:
When creating a new mail or responding to an existing mail, evolution hangs (program stops responding and does not redraw any of its windows anymore) after typing some sentences.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a new mail or reply to an existing mail
2. Enter some text
Thanks for the bug report. Please can you supply a backtrace of what evolution
is doing when it hangs?
You can find information on how to do this here:
Connection with gdb to the hanging evolution process gives:
#0 0x00a587a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1 0x00cbd24e in __lll_mutex_lock_wait () from /lib/tls/libpthread.so.0
#2 0x00cb9e4f in _L_mutex_lock_32 () from /lib/tls/libpthread.so.0
#3 0x00b96ff4 in ?? () from /lib/tls/libc.so.6
#4 0x00a6dc80 in ?? () from /lib/ld-linux.so.2
#5 0x00e03ff4 in ?? () from /lib/libnss_files.so.2
#6 0xbff2d0ac in ?? ()
#7 0x00dfdca0 in _nss_files_gethostbyname_r () from /lib/libnss_files.so.2
#8 0x00dfdcc9 in _nss_files_gethostbyname2_r () from /lib/libnss_files.so.2
#9 0x00b1fa24 in gaih_inet () from /lib/tls/libc.so.6
#10 0x00b20fa1 in getaddrinfo () from /lib/tls/libc.so.6
#11 0x03897de1 in camel_service_query_auth_types ()
#12 0x03897cf3 in camel_service_query_auth_types ()
#13 0x03897ed0 in camel_getaddrinfo ()
#14 0x0388565d in camel_header_msgid_generate ()
This happened with a mail I wanted to reply to. The mail itself resides on a
mail server which I access with evolution via IMAP.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Is this problem still present in Fedora Core 6?
No. IIRC, it was fixed with Core 5 already...
Thanks for responding. Closing per comment #6.
Feel free to re-open this bug if you encounter the same problem in Fedora Core 6