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 355393 - crash in Evolution: I'd just started Evoluti...
crash in Evolution: I'd just started Evoluti...
Status: RESOLVED DUPLICATE of bug 353430
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Harish Krishnaswamy
Evolution QA team
: 355551 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-09-11 07:22 UTC by David Bridson
Modified: 2006-09-18 21:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description David Bridson 2006-09-11 07:22:49 UTC
What were you doing when the application crashed?
I'd just started Evolution. It started up in offline mode, then crashed immediately while doing two things: "Generating message list" and Formatting message"


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

Memory status: size: 180453376 vsize: 0 resident: 180453376 share: 0 rss: 65032192 rss_rlim: 0
CPU usage: start_time: 1157959206 rtime: 0 utime: 834 stime: 0 cutime:778 cstime: 0 timeout: 56 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/evolution-2.8'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232447824 (LWP 3992)]
[New Thread -1334088800 (LWP 4011)]
[New Thread -1325696096 (LWP 4010)]
[New Thread -1278309472 (LWP 4001)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1232447824 (LWP 3992))

  • #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 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 ??
  • #0 __kernel_vsyscall

Comment 1 André Klapper 2006-09-11 13:02:15 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Could also be a gtk+ issue according to stacktrace.
Comment 2 David Bridson 2006-09-11 23:14:27 UTC
Thanks for your quick reply. Here's a stack trace from gdb including debugging symbols:

(gdb) run
Starting program: /usr/bin/evolution 
[Thread debugging using libthread_db enabled]
[New Thread -1232869712 (LWP 6041)]
CalDAV Eplugin starting up ...
[New Thread -1282569312 (LWP 6049)]
[New Thread -1333372000 (LWP 6053)]
[New Thread -1341764704 (LWP 6054)]
[New Thread -1350550624 (LWP 6055)]

(evolution-2.8:6041): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion `pixbuf != NULL' failed

(evolution-2.8:6041): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion `pixbuf != NULL' failed

(evolution-2.8:6041): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_has_alpha: assertion `pixbuf != NULL' failed

GdkPixbuf-ERROR **: file io-gif.c: line 987 (gif_get_lzw): assertion failed: (gdk_pixbuf_get_has_alpha (context->frame->pixbuf))
aborting...

Program received signal SIGABRT, Aborted.
[Switching to Thread -1232869712 (LWP 6041)]
0xffffe410 in __kernel_vsyscall ()
(gdb) thread apply all bt


Comment 3 André Klapper 2006-09-12 09:37:39 UTC
*** Bug 355551 has been marked as a duplicate of this bug. ***
Comment 4 Karsten Bräckelmann 2006-09-18 21:23:58 UTC
Thanks for the good stacktrace, David. :)

According to the crashing Thread 1 in the last stacktrace, this actually is a duplicate of bug 353430.


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 ***
Comment 5 Karsten Bräckelmann 2006-09-18 21:32:07 UTC
Also, since Evo crashed on start for you:  David, if you need some pointers how to get out of a crashing loop, just poke me. I already added some short notes and a link to a few bugs recently, outlining this. :)