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 249953 - Crash while trying to see Summary "page"
Crash while trying to see Summary "page"
Status: RESOLVED DUPLICATE of bug 244444
Product: evolution
Classification: Applications
Component: Do Not Use
pre-1.5 (obsolete)
Other All
: Normal major
: ---
Assigned To: Ettore Perazzoli
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2003-10-21 19:39 UTC by Kari Paju
Modified: 2013-09-13 12:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Kari Paju 2003-10-21 19:39:32 UTC 
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:
Cannot look Summary part of evolution at all. Can be problem in my distro,
but I doubt it. 1.2.x worked fine, but 1.4.4 or 1.4.5 do not work. Here is
short cut from term:
(evolution:2725): Bonobo-CRITICAL **: file bonobo-ui-util.c: line 182
(bonobo_ui_util_xml_to_pixbuf): assertion `xml != NULL' failed

(evolution:2725): Gtk-CRITICAL **: file ../../gtk/gtkimage.c: line 1017
(gtk_image_get_pixbuf): assertion `image->storage_type == GTK_IMAGE_PIXBUF
|| image->storage_type == GTK_IMAGE_EMPTY' failed
Floating point exception


Steps to reproduce the problem:
1. In my AMD: Push/select Summary (does not matter from where)

Actual Results:
Crash, previous explanation.

Expected Results:
See my Summary page (weeks schedule, tasks, some news and temperatures from
Finland).

How often does this happen? 
Everytime (cannot use Summary at all).

Additional Information:
Comment 1 Gerardo Marin 2003-10-21 21:03:46 UTC 
Without a backtrace there's very little we can do to pinpoint the problem.
If you can reproduce this in a consistent basis, please visit
http://support.ximian.com/q?65 to learn how to provide a backtrace and
attach it to this report.
Once you do it, reopen this.
Comment 2 Kari Paju 2003-10-21 21:57:29 UTC 
Hello Ettore,

I hope this helps you forward. 

GDB backtrace:
--------------

+ Trace 41073

Thread 9 (Thread 114696 (LWP 3164))

  • #0 sigsuspend
    from /lib/i686/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/i686/libpthread.so.0
  • #2 pthread_cond_wait
    from /lib/i686/libpthread.so.0
  • #3 e_msgport_wait
    from /usr/lib/evolution/1.4/libeutil.so.0
  • #4 e_thread_busy
    from /usr/lib/evolution/1.4/libeutil.so.0
  • #5 pthread_start_thread
    from /lib/i686/libpthread.so.0
  • #6 pthread_start_thread_event
    from /lib/i686/libpthread.so.0

Thread 8 (Thread 98311 (LWP 3163))

  • #0 sigsuspend
    from /lib/i686/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/i686/libpthread.so.0
  • #2 pthread_cond_wait
    from /lib/i686/libpthread.so.0
  • #3 e_msgport_wait
    from /usr/lib/evolution/1.4/libeutil.so.0
  • #4 e_thread_busy
    from /usr/lib/evolution/1.4/libeutil.so.0
  • #5 pthread_start_thread
    from /lib/i686/libpthread.so.0
  • #6 pthread_start_thread_event
    from /lib/i686/libpthread.so.0

Thread 6 (Thread 65541 (LWP 3161))

  • #0 sigsuspend
    from /lib/i686/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/i686/libpthread.so.0
  • #2 pthread_cond_wait
    from /lib/i686/libpthread.so.0
  • #3 e_msgport_wait
    from /usr/lib/evolution/1.4/libeutil.so.0
  • #4 e_thread_busy
    from /usr/lib/evolution/1.4/libeutil.so.0
  • #5 pthread_start_thread
    from /lib/i686/libpthread.so.0
  • #6 pthread_start_thread_event
    from /lib/i686/libpthread.so.0

Thread 5 (Thread 49156 (LWP 3160))

  • #0 sigsuspend
    from /lib/i686/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/i686/libpthread.so.0
  • #2 pthread_cond_wait
    from /lib/i686/libpthread.so.0
  • #3 e_msgport_wait
    from /usr/lib/evolution/1.4/libeutil.so.0
  • #4 e_thread_busy
    from /usr/lib/evolution/1.4/libeutil.so.0
  • #5 pthread_start_thread
    from /lib/i686/libpthread.so.0
  • #6 pthread_start_thread_event
    from /lib/i686/libpthread.so.0

Thread 4 (Thread 32771 (LWP 3159))

  • #0 sigsuspend
    from /lib/i686/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/i686/libpthread.so.0
  • #2 pthread_cond_wait
    from /lib/i686/libpthread.so.0
  • #3 e_msgport_wait
    from /usr/lib/evolution/1.4/libeutil.so.0
  • #4 e_thread_busy
    from /usr/lib/evolution/1.4/libeutil.so.0
  • #5 pthread_start_thread
    from /lib/i686/libpthread.so.0
  • #6 pthread_start_thread_event
    from /lib/i686/libpthread.so.0

Thread 3 (Thread 16386 (LWP 3158))

  • #0 sigsuspend
    from /lib/i686/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/i686/libpthread.so.0
  • #2 pthread_cond_wait
    from /lib/i686/libpthread.so.0
  • #3 e_msgport_wait
    from /usr/lib/evolution/1.4/libeutil.so.0
  • #4 e_thread_busy
    from /usr/lib/evolution/1.4/libeutil.so.0
  • #5 pthread_start_thread
    from /lib/i686/libpthread.so.0
  • #6 pthread_start_thread_event
    from /lib/i686/libpthread.so.0 






Comment 3


Gerardo Marin





          2003-11-13 19:52:18 UTC
        



Please change your theme.

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