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 359343 - crash in Evolution: Je consultais un mail. I...
crash in Evolution: Je consultais un mail. I...
Status: RESOLVED DUPLICATE of bug 353430
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-10-03 18:22 UTC by harobed
Modified: 2006-10-03 20:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description harobed 2006-10-03 18:22:33 UTC
What were you doing when the application crashed?
Je consultais un mail. Il semble que l'ouverture d'un certain mail (spam) provoque ce plantage.


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

Memory status: size: 167829504 vsize: 0 resident: 167829504 share: 0 rss: 44388352 rss_rlim: 0
CPU usage: start_time: 1159899695 rtime: 0 utime: 583 stime: 0 cutime:567 cstime: 0 timeout: 16 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 -1233103184 (LWP 3719)]
[New Thread -1350181984 (LWP 3729)]
[New Thread -1293792352 (LWP 3728)]
[New Thread -1302586464 (LWP 3725)]
[New Thread -1285399648 (LWP 3724)]
[New Thread -1276970080 (LWP 3721)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1233103184 (LWP 3719))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    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 *__GI_raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 *__GI_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_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 fill_info
    from /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-gif.so
  • #11 ??
    from /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-gif.so
  • #12 ??
    from /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-gif.so
  • #13 ??
  • #14 ??
    from /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-gif.so
  • #15 ??
    from /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-gif.so
  • #16 __after_morecore_hook
    from /lib/tls/i686/cmov/libc.so.6
  • #17 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #18 fill_info
    from /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-gif.so
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 __read_nocancel
    from /lib/tls/i686/cmov/libc.so.6
  • #25 ??
    from /usr/lib/libgdk_pixbuf-2.0.so.0
  • #26 ??
  • #27 ??
  • #28 ??
  • #29 gdk_pixbuf_loader_write
    from /usr/lib/libgdk_pixbuf-2.0.so.0
  • #30 gdk_pixbuf_loader_write
    from /usr/lib/libgdk_pixbuf-2.0.so.0
  • #31 html_image_set_spacing
    from /usr/lib/libgtkhtml-3.8.so.15
  • #32 gtk_html_stream_write
    from /usr/lib/libgtkhtml-3.8.so.15
  • #33 em_html_stream_new
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #34 em_sync_stream_get_type
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #35 g_io_channel_unix_get_fd
    from /usr/lib/libglib-2.0.so.0
  • #36 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #37 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #38 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #39 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #40 main
  • #0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-10-03 20:29:35 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 353430 ***