After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 388463 - crash in Evolution: I watched a mail in my i...
crash in Evolution: I watched a mail in my i...
Status: RESOLVED DUPLICATE of bug 340165
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-12-22 01:01 UTC by ralf
Modified: 2007-01-22 13:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description ralf 2006-12-22 01:01:48 UTC
What were you doing when the application crashed?
I watched a mail in my inbox of an imap account which contains two attached JPEG images. I could watch inline the first JPEG image without any problems but when I clicked on the second (last) one, the bug reporting tool sprung up.
This already happened to me before with another mail with attached JPEG images. Evolution always crashes when the last attachment is looked at.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 163024896 vsize: 0 resident: 163024896 share: 0 rss: 37134336 rss_rlim: 0
CPU usage: start_time: 1166727193 rtime: 0 utime: 4098 stime: 0 cutime:3729 cstime: 0 timeout: 369 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/evolution-2.8'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1233254736 (LWP 6866)]
[New Thread -1326982240 (LWP 6889)]
[New Thread -1308103776 (LWP 6884)]
[New Thread -1299317856 (LWP 6879)]
[New Thread -1290888288 (LWP 6877)]
[New Thread -1282495584 (LWP 6876)]
[New Thread -1274102880 (LWP 6875)]
[New Thread -1265710176 (LWP 6874)]
[New Thread -1257317472 (LWP 6873)]
[New Thread -1248924768 (LWP 6872)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1233254736 (LWP 6866))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/libc.so.6
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 segv_redirect
    at main.c line 426
  • #4 <signal handler called>
  • #5 IA__g_str_hash
    at gstring.c line 95
  • #6 IA__g_hash_table_lookup
    at ghash.c line 231
  • #7 em_cache_lookup
    at e-msgport.c line 347
  • #8 em_icon_stream_is_resized
    at em-icon-stream.c line 326
  • #9 efhd_change_cursor
    at em-format-html-display.c line 1643
  • #10 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #11 IA__g_closure_invoke
    at gclosure.c line 490
  • #12 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #13 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #14 IA__g_signal_emit
    at gsignal.c line 2243
  • #15 gtk_widget_event_internal
    at gtkwidget.c line 3911
  • #16 IA__gtk_main_do_event
    at gtkmain.c line 1453
  • #17 gdk_event_dispatch
    at gdkevents-x11.c line 2320
  • #18 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #19 g_main_context_iterate
    at gmain.c line 2677
  • #20 IA__g_main_loop_run
    at gmain.c line 2881
  • #21 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #22 main
    at main.c line 615
  • #0 __kernel_vsyscall

Comment 1 Kjartan Maraas 2007-01-16 11:59:28 UTC
Cannot reproduce this here. Does it always happen when you receive a message with more than one jpeg?
Comment 2 palfrey 2007-01-22 13:32:29 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 340165 ***