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 344618 - Evolution crashes on start
Evolution crashes on start
Status: RESOLVED DUPLICATE of bug 343764
Product: evolution
Classification: Applications
Component: Calendar
2.8.x (obsolete)
Other other
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-06-11 23:26 UTC by David Hagood
Modified: 2013-09-13 00:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description David Hagood 2006-06-11 23:26:20 UTC
Distribution: Fedora Core release 5.89 (Rawhide)
Package: Evolution
Severity: Normal
Version: GNOME2.15.2 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: Evolution crashes on start
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.15.1cvs20060505)
Description:
Description of the crash:
Evolution crashes right after bringing up the Calendar window from the
Gnome panel clock.

Steps to reproduce the crash:
1. Click on the Gnome panel clock to bring up the month calendar and the
current list of items.
2. Click on a day to launch Evolution itself
3. 

Expected Results:
Evolution should start, and run

How often does this happen?
Every time.


Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209178432 (LWP 6090)]
[New Thread -1301931104 (LWP 6137)]
[New Thread -1268360288 (LWP 6136)]
[New Thread -1285145696 (LWP 6131)]
[New Thread -1259701344 (LWP 6095)]
[New Thread -1250514016 (LWP 6094)]
[New Thread -1242121312 (LWP 6092)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1209178432 (LWP 6090))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 POA_GNOME_Evolution_DataServer_InterfaceCheck__fini
  • #4 <signal handler called>
  • #5 e_table_header_draw_button
    from /usr/lib/evolution/2.8/libetable.so.0
  • #6 ethi_change_sort_state
    from /usr/lib/evolution/2.8/libetable.so.0
  • #7 gnome_canvas_root
    from /usr/lib/libgnomecanvas-2.so.0
  • #8 gnome_canvas_item_new
    from /usr/lib/libgnomecanvas-2.so.0
  • #9 gtk_marshal_BOOLEAN__VOID
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 g_value_set_static_boxed
    from /lib/libgobject-2.0.so.0
  • #11 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #12 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #14 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #15 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gnome_canvas_window_to_world
    from /usr/lib/libgnomecanvas-2.so.0
  • #17 gnome_canvas_set_scroll_region
    from /usr/lib/libgnomecanvas-2.so.0
  • #18 g_source_is_destroyed
    from /lib/libglib-2.0.so.0
  • #19 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #20 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #21 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #22 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #23 POA_GNOME_Evolution_DataServer_InterfaceCheck__fini
  • #24 __libc_start_main
    from /lib/libc.so.6
  • #25 ??




------- Bug created by bug-buddy at 2006-06-11 23:26 -------

Comment 1 André Klapper 2006-06-12 09:33:54 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 343764 ***