Red Hat Bugzilla – Bug 141032
Crash on reply - highlighting included mail
Last modified: 2008-08-02 19:40:33 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0 Description of problem: Evolution - runnign under kde - fc3 fully yum updated. Imap mail. Reply - attempt to highlight included email and the signature thereof - boom crash burn. Happens every time. No apparent data loss but makes evolution substantially less usefulf for responding to email! Filed in upstream as well: http://bugzilla.gnome.org/show_bug.cgi?id=159736 Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Reply to email 2.Highlight included text+sig 3. Actual Results: Crash -> bug buddy Expected Results: Errm .. not crash? Additional info:
Bug buddy filed bug as above - gnome.org asked this to be refiled in ximian buugzilla: Done - now filed upstream http://bugzilla.ximian.com/show_bug.cgi?id=69986 g/
Further - it appears that the problem is needs a signature to trigger it - both in the included text and possibly also the auto signature of the sender. And, I have not yet tried when running under gnome. g/
Does it work if you run it under GNOME?
No - it crashes the same way under both KDE and Gnome - I posted a sample mail upstream which does it for me. Regards, g/
Another crash situation - may be related. FC3 - updated - running Gnome How to 1) Open Evolution - go to mail 2) New-> create a blank email 3) Paste in text (haven't zeroned in on the size required, but enough to cause scrollbar to be active (more than one viewport worth). 3) At the end of the paste, you are seeing the end of the pasted text. Using the scrollbar, slowly (or fast..) scroll up so you can see the top of the text. 4) Boom crash blinkout. You will never see the beginning of the pasted text. No trace of message in drafts or ... when you restart evolution. Looks like a buffer problem.
Please can you ensure that the gtkhtml3-debuginfo package is installed, generate a stack backtrace, and attach to this bug; see this page for more information: http://fedora.linux.duke.edu/wiki/index.cgi/StackTraces Thanks