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 359469 - crash in Evolution:
crash in Evolution:
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-04 01:16 UTC by denise
Modified: 2006-10-04 01:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description denise 2006-10-04 01:16:48 UTC
What were you doing when the application crashed?



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

Memory status: size: 125882368 vsize: 0 resident: 125882368 share: 0 rss: 26980352 rss_rlim: 0
CPU usage: start_time: 1159924579 rtime: 0 utime: 205 stime: 0 cutime:192 cstime: 0 timeout: 13 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 -1232623952 (LWP 24076)]
[New Thread -1308632160 (LWP 24096)]
[New Thread -1300239456 (LWP 24095)]
[New Thread -1291846752 (LWP 24094)]
[New Thread -1272521824 (LWP 24090)]
[New Thread -1263735904 (LWP 24084)]
[New Thread -1255298144 (LWP 24080)]
[New Thread -1246905440 (LWP 24079)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1232623952 (LWP 24076))

  • #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 ??
  • #17 ??
    from /lib/ld-linux.so.2
  • #18 ??
    from /lib/tls/i686/cmov/libc.so.6
  • #19 __after_morecore_hook
    from /lib/tls/i686/cmov/libc.so.6
  • #20 ??
  • #21 ??
  • #22 *__GI___libc_realloc
    from /lib/tls/i686/cmov/libc.so.6
  • #23 fill_info
    from /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-gif.so
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
  • #28 ??
  • #29 __read_nocancel
    from /lib/tls/i686/cmov/libc.so.6
  • #30 ??
    from /usr/lib/libgdk_pixbuf-2.0.so.0
  • #31 ??
  • #32 ??
  • #33 ??
  • #34 gdk_pixbuf_loader_write
    from /usr/lib/libgdk_pixbuf-2.0.so.0
  • #35 gdk_pixbuf_loader_write
    from /usr/lib/libgdk_pixbuf-2.0.so.0
  • #36 html_image_set_spacing
    from /usr/lib/libgtkhtml-3.8.so.15
  • #37 gtk_html_stream_write
    from /usr/lib/libgtkhtml-3.8.so.15
  • #38 em_html_stream_new
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #39 em_sync_stream_get_type
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #40 g_io_channel_unix_get_fd
    from /usr/lib/libglib-2.0.so.0
  • #41 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #42 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #43 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #44 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #45 main
  • #0 __kernel_vsyscall

Comment 1 Elijah Newren 2006-10-04 01:19:31 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.

Looks like the stack trace in bug 359343, which has been marked as a duplicate of 353430

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