GNOME Bugzilla – Bug 357373
Evolution crashes when I try to hide attached image
Last modified: 2006-09-27 21:44:13 UTC
Please describe the problem: Environment variable LANG=ru_RU.UTF-8 is set. Image is attached to the message. This image is shown in the message preview window. When I pressed the button located on the left edge of the message in order to hide attached image preview evolution crashes. But if I do the same in message viewing window evolution work normally. Also if I start evolution with environment variable LANG=C everything works normally. Steps to reproduce: Actual results: Expected results: Does this happen every time? Yes Other information: Backtrace was generated from '/usr/bin/evolution-2.8' Using host libthread_db library "/lib/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 8605)] [New Thread 32769 (LWP 8618)] [New Thread 32770 (LWP 8620)] [New Thread 49155 (LWP 8644)] [New Thread 65540 (LWP 8645)] [New Thread 229381 (LWP 9165)] [New Thread 98310 (LWP 9122)] [New Thread 114695 (LWP 9123)] [New Thread 131080 (LWP 9124)] [New Thread 245769 (LWP 9210)] [New Thread 163850 (LWP 9127)] 0xb72f16d1 in waitpid () from /lib/i686/libpthread.so.0
+ Trace 73086
Thread 11 (Thread 163850 (LWP 9127))
Thread 10 (Thread 245769 (LWP 9210))
Thread 9 (Thread 131080 (LWP 9124))
Thread 8 (Thread 114695 (LWP 9123))
Thread 7 (Thread 98310 (LWP 9122))
Thread 5 (Thread 65540 (LWP 8645))
Thread 4 (Thread 49155 (LWP 8644))
Thread 3 (Thread 32770 (LWP 8620))
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Will this be better? Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 2916)] 0xb5825b73 in efhd_image_resized () from /usr/lib/evolution/2.8/components/libevolution-mail.so (gdb) thread apply all bt
+ Trace 73328
Thread 1 (Thread 16384 (LWP 2916))
(In reply to comment #2) > Will this be better? Yup, thanks for the good stacktrace, Alexander. :) This is the same issue as bug 333864 and its duplicates. *** This bug has been marked as a duplicate of 333864 ***