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 415011 - crash in Evolution: Reading mail
crash in Evolution: Reading mail
Status: RESOLVED DUPLICATE of bug 273386
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: 2007-03-05 18:54 UTC by ks.dagi
Modified: 2007-04-16 20:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description ks.dagi 2007-03-05 18:54:20 UTC
What were you doing when the application crashed?
Reading mail


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

Memory status: size: 203968512 vsize: 0 resident: 203968512 share: 0 rss: 44875776 rss_rlim: 0
CPU usage: start_time: 1173120731 rtime: 0 utime: 769 stime: 0 cutime:739 cstime: 0 timeout: 30 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 -1232644432 (LWP 9416)]
[New Thread -1331909728 (LWP 9451)]
[New Thread -1319965792 (LWP 9435)]
[New Thread -1311376480 (LWP 9434)]
[New Thread -1302983776 (LWP 9433)]
[New Thread -1279132768 (LWP 9432)]
[New Thread -1270158432 (LWP 9427)]
[New Thread -1261765728 (LWP 9424)]
[New Thread -1253246048 (LWP 9423)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 9 (Thread -1253246048 (LWP 9423))

  • #0 gdk_pixbuf_alpha_mode_get_type
    from /usr/lib/libgdk_pixbuf-2.0.so.0
  • #1 _pixops_scale
    from /usr/lib/libgdk_pixbuf-2.0.so.0
  • #2 gdk_pixbuf_scale
    from /usr/lib/libgdk_pixbuf-2.0.so.0
  • #3 gdk_pixbuf_scale_simple
    from /usr/lib/libgdk_pixbuf-2.0.so.0
  • #4 e_attachment_bar_create_attachment_cache
    from /usr/lib/evolution/2.8/libemiscwidgets.so.0
  • #5 em_format_html_display_new
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #6 em_format_part_as
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #7 em_format_part
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #8 em_format_get_type
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #9 em_format_part_as
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #10 em_format_part
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #11 em_format_html_new
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #12 em_format_html_new
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #13 mail_enable_stop
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #14 e_msgport_reply
    from /usr/lib/libedataserver-1.2.so.7
  • #15 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #16 clone
    from /lib/tls/i686/cmov/libc.so.6

Comment 1 Akhil Laddha 2007-03-06 04:43:33 UTC
Stack trace looks similar to Bug 367091

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 ks.dagi 2007-03-06 17:34:51 UTC
Havent ben abel to redo the crash, but it sems to be the same as the other one. Evolution locks up when trying to open a mail whit an  8584x480 .jpg atachment.
This is al the info i could grab from the terminal.

(evolution-2.8:7376): camel-WARNING **: camel_exception_get_id called with NULL parameter.

(evolution-2.8:7376): camel-WARNING **: camel_exception_get_id called with NULL parameter.

(evolution-2.8:7376): GdkPixbuf-CRITICAL **: gdk_pixbuf_loader_write: assertion `buf != NULL' failed

(evolution-2.8:7376): e-attachment-bar.c-WARNING **: GdkPixbufLoader Error

(evolution-2.8:7376): camel-WARNING **: camel_exception_get_id called with NULL parameter.

(evolution-2.8:7376): camel-WARNING **: camel_exception_get_id called with NULL parameter.

Comment 3 André Klapper 2007-03-06 21:38:29 UTC
Thanks, but we really need a stacktrace with debugging packages installed, as Akhil already asked for. The terminal output is unfortunately not enough information.
Comment 4 ks.dagi 2007-03-07 00:13:17 UTC
Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 206753792 vsize: 0 resident: 206753792 share: 0 rss: 49975296 rss_rlim: 0
CPU usage: start_time: 1173225965 rtime: 0 utime: 953 stime: 0 cutime:918 cstime: 0 timeout: 35 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 -1232963920 (LWP 12946)]
[New Thread -1318978656 (LWP 12957)]
[New Thread -1297020000 (LWP 12956)]
[New Thread -1287902304 (LWP 12954)]
[New Thread -1278870624 (LWP 12953)]
[New Thread -1262085216 (LWP 12950)]
[New Thread -1253565536 (LWP 12949)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1232963920 (LWP 12946))

  • #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_hash_table_lookup
    at ghash.c line 231
  • #6 em_format_set_inline
    at em-format.c line 978
  • #7 efhd_attachment_show
    at em-format-html-display.c line 1416
  • #8 efhd_attachment_button_show
    at em-format-html-display.c line 1422
  • #9 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #10 IA__g_closure_invoke
    at gclosure.c line 490
  • #11 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #12 IA__g_signal_emit_valist
  • #13 IA__g_signal_emit
    at gsignal.c line 2243
  • #14 IA__gtk_button_clicked
    at gtkbutton.c line 889
  • #15 gtk_real_button_released
    at gtkbutton.c line 1484
  • #16 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #17 g_type_class_meta_marshal
    at gclosure.c line 567
  • #18 IA__g_closure_invoke
    at gclosure.c line 490
  • #19 signal_emit_unlocked_R
    at gsignal.c line 2370
  • #20 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #21 IA__g_signal_emit
    at gsignal.c line 2243
  • #22 IA__gtk_button_released
    at gtkbutton.c line 881
  • #23 gtk_button_button_release
    at gtkbutton.c line 1377
  • #24 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #25 g_type_class_meta_marshal
    at gclosure.c line 567
  • #26 IA__g_closure_invoke
    at gclosure.c line 490
  • #27 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #28 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #29 IA__g_signal_emit
    at gsignal.c line 2243
  • #30 gtk_widget_event_internal
    at gtkwidget.c line 3911
  • #31 IA__gtk_propagate_event
    at gtkmain.c line 2211
  • #32 IA__gtk_main_do_event
    at gtkmain.c line 1445
  • #33 gdk_event_dispatch
    at gdkevents-x11.c line 2320
  • #34 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #35 g_main_context_iterate
    at gmain.c line 2677
  • #36 IA__g_main_loop_run
    at gmain.c line 2881
  • #37 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #38 main
    at main.c line 615
  • #0 __kernel_vsyscall

Comment 5 palfrey 2007-04-16 20:17:11 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 273386 ***