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 355926 - crash in Evolution: I was trying to display ...
crash in Evolution: I was trying to display ...
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Harish Krishnaswamy
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-09-14 08:47 UTC by moebius
Modified: 2006-10-07 23:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description moebius 2006-09-14 08:47:36 UTC
What were you doing when the application crashed?
I was trying to display an image attached to an email.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 75427840 vsize: 0 resident: 293986304 share: 0 rss: 293986304 rss_rlim: 0
CPU usage: start_time: 8469 rtime: 0 utime: 1158217841 stime: 0 cutime:20124 cstime: 0 timeout: 18466 it_real_value: 0 frequency: 1658

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 805642464 (LWP 29271)]
[New Thread 881128688 (LWP 2603)]
[New Thread 948221168 (LWP 31616)]
[New Thread 949490928 (LWP 31061)]
[New Thread 939832560 (LWP 29292)]
[New Thread 891286768 (LWP 29286)]
[New Thread 872740080 (LWP 29284)]
[New Thread 863937776 (LWP 29283)]
[New Thread 855545072 (LWP 29281)]
0x0ea10220 in __waitpid_nocancel () from /lib/libc.so.6

Thread 9 (Thread 855545072 (LWP 29281))

  • #0 ___newselect_nocancel
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib/libedataserver-1.2.so.7
  • #2 em_sync_stream_get_type
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #3 em_sync_stream_get_type
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #4 camel_stream_flush
    from /usr/lib/libcamel-1.2.so.8
  • #5 camel_stream_filter_new_with_stream
    from /usr/lib/libcamel-1.2.so.8
  • #6 camel_stream_flush
    from /usr/lib/libcamel-1.2.so.8
  • #7 camel_stream_filter_new_with_stream
    from /usr/lib/libcamel-1.2.so.8
  • #8 camel_stream_flush
    from /usr/lib/libcamel-1.2.so.8
  • #9 camel_stream_filter_new_with_stream
    from /usr/lib/libcamel-1.2.so.8
  • #10 camel_stream_flush
    from /usr/lib/libcamel-1.2.so.8
  • #11 camel_data_wrapper_new
    from /usr/lib/libcamel-1.2.so.8
  • #12 camel_data_wrapper_decode_to_stream
    from /usr/lib/libcamel-1.2.so.8
  • #13 em_format_format_text
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #14 em_format_html_new
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #15 em_format_part_as
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #16 em_format_part
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #17 em_format_get_type
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #18 em_format_part_as
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #19 em_format_part
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #20 em_format_html_new
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #21 em_format_html_new
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #22 mail_enable_stop
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #23 e_msgport_reply
    from /usr/lib/libedataserver-1.2.so.7
  • #24 start_thread
    from /lib/libpthread.so.0
  • #25 start_thread
    from /lib/libpthread.so.0

Thread 8 (Thread 863937776 (LWP 29283))

  • #0 ___newselect_nocancel
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 start_thread
    from /lib/libpthread.so.0

Thread 7 (Thread 872740080 (LWP 29284))

  • #0 ___newselect_nocancel
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 start_thread
    from /lib/libpthread.so.0

Thread 6 (Thread 891286768 (LWP 29286))

  • #0 ___newselect_nocancel
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 start_thread
    from /lib/libpthread.so.0

Thread 5 (Thread 939832560 (LWP 29292))

  • #0 ___newselect_nocancel
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 start_thread
    from /lib/libpthread.so.0

Thread 3 (Thread 948221168 (LWP 31616))

  • #0 ___newselect_nocancel
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 start_thread
    from /lib/libpthread.so.0

Comment 1 Karsten Bräckelmann 2006-09-17 13:55:10 UTC
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.
Comment 2 Karsten Bräckelmann 2006-10-07 23:03:15 UTC
Unfortunately the stacktrace does not have any hints about the real cause of
the crash and does not help in debugging this issue.

For some yet unknown reason, such stacktraces are pretty common currently on
certain distros. However, almost all of them do turn out to be filed already,
once we managed to gather a useful stacktrace. To do so, simply install the
corresponding debugging packages and reproduce the issue, if possible. The
resulting stacktrace (see bug-buddy details) will help us to identify and fix
the issue.


Just in case you ever can reproduce this crash later, please consider
installing debugging packages [1] and either reopen this bug report or simply
file a new one with the resulting stacktrace.  Thanks!

Closing this bug report as no further information has been provided.


Also, please feel free to report any further bugs you find.  Thanks!


[1] debugging packages for evolution and evolution-data-server, plus debugging
    packages for some basic GNOME libs. More details can be found here:
    http://live.gnome.org/GettingTraces/DistroSpecificInstructions