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 394979 - crash in Evolution: opening a picture
crash in Evolution: opening a picture
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: 2007-01-10 11:03 UTC by janina.kuehl
Modified: 2007-02-09 07:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description janina.kuehl 2007-01-10 11:03:47 UTC
What were you doing when the application crashed?
opening a picture


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

Memory status: size: 308035584 vsize: 308035584 resident: 33230848 share: 19296256 rss: 33230848 rss_rlim: -1
CPU usage: start_time: 1168427048 rtime: 166 utime: 155 stime: 11 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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 47356819725648 (LWP 10024)]
[New Thread 1107310928 (LWP 10034)]
[New Thread 1098918224 (LWP 10033)]
[New Thread 1090525520 (LWP 10031)]
[New Thread 1082132816 (LWP 10028)]
(no debugging symbols found)
0x00002b121a1ee5cf in waitpid () from /lib/libc.so.6

Thread 5 (Thread 1082132816 (LWP 10028))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    from /lib/libc.so.6
  • #5 ??

Thread 4 (Thread 1090525520 (LWP 10031))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib64/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 em_format_html_display_new
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #5 em_format_part_as
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #6 em_format_part
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #7 em_format_get_type
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #8 em_format_part_as
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #9 em_format_part
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #10 em_format_html_new
    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 mail_enable_stop
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #13 e_msgport_reply
    from /usr/lib64/libedataserver-1.2.so.7
  • #14 start_thread
    from /lib/libpthread.so.0
  • #15 clone
    from /lib/libc.so.6
  • #16 ??

Thread 3 (Thread 1098918224 (LWP 10033))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    from /lib/libc.so.6
  • #5 ??

Thread 2 (Thread 1107310928 (LWP 10034))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    from /lib/libc.so.6
  • #5 ??

Comment 1 palfrey 2007-01-11 00:45:26 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Kjartan Maraas 2007-02-09 07:42:56 UTC
Likely a duplicate of bug 340165 or 333864. Fixed in 2.8.3 and 2.9.x

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