GNOME Bugzilla – Bug 269986
Crash on reply - highlighting included mail+sig
Last modified: 2005-12-11 02:34:05 UTC
Please fill in this template when reporting a bug, unless you know what you are doing. Description of Problem: Reply to email - highlight included mail being replied to spanning "On ... " down to and including the signatire. Crash bang boom. Originally reported via bug buddy - which sent to http://bugzilla.gnome.org/show_bug.cgi?id=159736 Does this need updating to point here? Steps to reproduce the problem: 1. See above 2. 3. Actual Results: Crash - bug buddy comes up Expected Results: DUh - should work? How often does this happen? Always Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -151202112 (LWP 1909)] [New Thread -176645200 (LWP 1931)] [Thread debugging using libthread_db enabled] [New Thread -151202112 (LWP 1909)] [New Thread -176645200 (LWP 1931)] [New Thread -166155344 (LWP 1930)] [New Thread -155665488 (LWP 1928)] [New Thread 156466096 (LWP 1920)] [New Thread 99769264 (LWP 1919)] [New Thread 64097200 (LWP 1918)] [New Thread 37907376 (LWP 1913)] [New Thread 27417520 (LWP 1912)] [New Thread 53607344 (LWP 1911)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -151202112 (LWP 1909)] [New Thread -176645200 (LWP 1931)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x0082f7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 52821
Thread 10 (Thread 53607344 (LWP 1911))
Thread 9 (Thread 27417520 (LWP 1912))
Thread 8 (Thread 37907376 (LWP 1913))
Thread 7 (Thread 64097200 (LWP 1918))
Thread 6 (Thread 99769264 (LWP 1919))
Thread 5 (Thread 156466096 (LWP 1920))
Thread 4 (Thread -155665488 (LWP 1928))
Thread 3 (Thread -166155344 (LWP 1930))
Thread 2 (Thread -176645200 (LWP 1931))
please could you attach the mail and signature on which evo crashes?
Also reported downstream here: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=141032 I believe this crash is occurring when Evolution is run under KDE (on FC3)
Created attachment 44442 [details] Import this into evolution - hit reply - hilite from sig backwards (.uk)
works ok in evolution 2.2.x => assuming fixed
*** Bug 301381 has been marked as a duplicate of this bug. ***