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 368082 - crash in Evolution: Reading e-mail with pict...
crash in Evolution: Reading e-mail with pict...
Status: RESOLVED DUPLICATE of bug 308062
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-10-31 04:18 UTC by decoy
Modified: 2006-11-06 23:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description decoy 2006-10-31 04:18:55 UTC
What were you doing when the application crashed?
Reading e-mail with picture inline attachments in IMAP inbox.				


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

Memory status: size: 235958272 vsize: 0 resident: 235958272 share: 0 rss: 93421568 rss_rlim: 0
CPU usage: start_time: 1162264345 rtime: 0 utime: 4460 stime: 0 cutime:4245 cstime: 0 timeout: 215 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233099088 (LWP 4749)]
[New Thread -1324586080 (LWP 5010)]
[New Thread -1308873824 (LWP 4765)]
[New Thread -1300481120 (LWP 4764)]
[New Thread -1292088416 (LWP 4761)]
[New Thread -1269281888 (LWP 4760)]
[New Thread -1260495968 (LWP 4757)]
[New Thread -1252103264 (LWP 4755)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Comment 1 Karsten Bräckelmann 2006-10-31 19:50:24 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Could you please install some debugging packages [1] and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the "details", now containing way more information. Please copy that stacktrace and paste it as a comment here.  Thanks!


[1] debugging packages for evolution, evolution-data-server and gtkhtml,
    plus debugging packages for some basic GNOME libs. More details can
    be found here:
    http://live.gnome.org/GettingTraces/DistroSpecificInstructions
Comment 2 decoy 2006-11-01 21:39:35 UTC
I installed the debug symbols for every evolution package, every gtkhtml package and recreated the problem.  Let me know if more debugging info is needed or anything else you need from me.

Thanks!  --Jim  (decoy (at) umich (dot) edu)

__________________________________________________________________________

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

Memory status: size: 116191232 vsize: 0 resident: 116191232 share: 0 rss: 26841088 rss_rlim: 0
CPU usage: start_time: 1162416828 rtime: 0 utime: 936 stime: 0 cutime:888 cstime: 0 timeout: 48 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 -1232996688 (LWP 10088)]
[New Thread -1304470624 (LWP 10107)]
[New Thread -1296077920 (LWP 10106)]
[New Thread -1287685216 (LWP 10103)]
[New Thread -1267373152 (LWP 10102)]
[New Thread -1258570848 (LWP 10097)]
[New Thread -1250178144 (LWP 10095)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1232996688 (LWP 10088))

  • #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 em_format_set_inline
    at em-format.c line 978
  • #6 efhd_attachment_show
    at em-format-html-display.c line 1416
  • #7 efhd_attachment_button_show
    at em-format-html-display.c line 1422
  • #8 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #13 gtk_button_clicked
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_button_set_alignment
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #21 gtk_button_released
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 gtk_button_released
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #25 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #26 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #27 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #28 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #29 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 _gdk_events_init
    from /usr/lib/libgdk-x11-2.0.so.0
  • #33 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #34 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #35 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #36 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #37 main
    at main.c line 615
  • #0 __kernel_vsyscall

Comment 3 Karsten Bräckelmann 2006-11-06 23:14:58 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 308062 ***