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 374739 - crash in Evolution:
crash in Evolution:
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: 2006-11-13 16:17 UTC by virtual
Modified: 2007-01-16 15:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description virtual 2006-11-13 16:17:02 UTC 
What were you doing when the application crashed?



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

Memory status: size: -1129521152 vsize: 0 resident: -1129521152 share: 0 rss: 611418112 rss_rlim: 0
CPU usage: start_time: 1163428192 rtime: 0 utime: 5235 stime: 0 cutime:4039 cstime: 0 timeout: 1196 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 -1232636240 (LWP 21464)]
[New Thread -1561334880 (LWP 22184)]
[New Thread -1377887328 (LWP 21483)]
[New Thread -1297097824 (LWP 21482)]
[New Thread -1354486880 (LWP 21481)]
[New Thread -1313883232 (LWP 21480)]
[New Thread -1280312416 (LWP 21474)]
[New Thread -1305490528 (LWP 21471)]
[New Thread -1288705120 (LWP 21469)]
[New Thread -1270133856 (LWP 21467)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 86100

Thread 9 (Thread -1288705120 (LWP 21469))

  • #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 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_malloc
    from /usr/lib/libglib-2.0.so.0
  • #10 gdk_pixbuf_alpha_mode_get_type
    from /usr/lib/libgdk_pixbuf-2.0.so.0
  • #11 _pixops_scale
    from /usr/lib/libgdk_pixbuf-2.0.so.0
  • #12 gdk_pixbuf_scale
    from /usr/lib/libgdk_pixbuf-2.0.so.0
  • #13 gdk_pixbuf_scale_simple
    from /usr/lib/libgdk_pixbuf-2.0.so.0
  • #14 e_attachment_bar_create_attachment_cache
    from /usr/lib/evolution/2.8/libemiscwidgets.so.0
  • #15 em_format_html_display_new
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #16 em_format_part_as
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #17 em_format_part
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #18 em_format_get_type
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #19 em_format_part_as
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #20 em_format_part
    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 em_format_html_new
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #23 mail_enable_stop
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #24 e_msgport_reply
    from /usr/lib/libedataserver-1.2.so.7
  • #25 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #26 clone
    from /lib/tls/i686/cmov/libc.so.6 






Comment 1


palfrey





          2006-12-17 17:57:05 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-01-16 15:08:49 UTC
        




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