Description of problem:
After invoking evolution mail tool, I go to New Message Window. In the new
message window, when I click on "Attach" button, the tool crashes
Version-Release number of selected component (if applicable):
Evolution (latest. I installed using yum install evolution on 3rd April 2008)
Just start evolution GUI and then click on NEW Message Window and then in the
new message window click on "Attach" button.
Steps to Reproduce:
After clicking on Attach button it opens a box and by the time I can read what
it is, the BUG data collection window opens up.
This crash was not happening earlier when I installed the tool one month back.
Can you attach a bug buddy output here, please? It will help us identify the
problem more quickly. Thanks in advance.
How can I create a bug buddy output here?
I am using evolution mail tool in production environment,
so if you can resolve this bug quickly it will help me a lot!
Distribution: Fedora release 8 (Werewolf)
Gnome Release: 2.20.1 2007-10-15 (Red Hat, Inc)
BugBuddy Version: 2.22.0
System: Linux 18.104.22.168-42.fc8 #1 SMP Tue Oct 30 13:55:12 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
GTK+ Theme: Nodoka
Icon Theme: Fedora
Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout:
0 it_real_value: 0 frequency: 0
This is the output I get on BUG Report window
Hmm, it is usually with stack trace or something similar. In that case, please
run evolution in gdb by hand, on the console
$ gdb evolution
then in gdb's prompt just type "run" and evolution will start. Then try to
reproduce this and in time of the crash the gdb will show its prompt again. Then
just type this gdb command: "thread apply all bt" and paste here the output of
this command (it will be a bit longer). If you see there any error/warning
messages on the console, please paste them here too. Thanks.
Reporter, could you please reply to the previous question? If you won't reply in
one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional
Closing as INSUFFICIENT_DATA.