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 396877 - crash in Evolution: Showing an attached phot...
crash in Evolution: Showing an attached phot...
Status: RESOLVED DUPLICATE of bug 333864
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-15 14:14 UTC by webmaster
Modified: 2007-02-23 09:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description webmaster 2007-01-15 14:14:55 UTC
What were you doing when the application crashed?
Showing an attached photo inline


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

Memory status: size: 293396480 vsize: 0 resident: 293396480 share: 0 rss: 120401920 rss_rlim: 0
CPU usage: start_time: 1168869284 rtime: 0 utime: 4091 stime: 0 cutime:3943 cstime: 0 timeout: 148 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 -1232894288 (LWP 7212)]
[New Thread -1351808096 (LWP 7238)]
[New Thread -1343415392 (LWP 7237)]
[New Thread -1334314080 (LWP 7223)]
[New Thread -1325528160 (LWP 7222)]
[New Thread -1277236320 (LWP 7220)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 6 (Thread -1277236320 (LWP 7220))

  • #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 palfrey 2007-01-17 17:11:18 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 Bruno Boaventura 2007-02-21 20:27:09 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 3 André Klapper 2007-02-23 09:03:28 UTC
Unfortunately the stacktrace does not have any hints about the real cause of the crash and does not help in debugging this issue.

However, according to the description this is the same issue as bug 333864,
which is fixed in Evolution 2.8.1.1. Note, that this does not happen always,
but sporadically only.


Just in case you can reproduce this crash later, please consider installing
debugging packages [1], which help a lot in tracking down the crash.  Thanks!

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

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