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 326716 - Switching to contacts crash the evolution
Switching to contacts crash the evolution
Status: RESOLVED DUPLICATE of bug 323556
Product: evolution
Classification: Applications
Component: Contacts
unspecified
Other other
: High critical
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-01-12 10:59 UTC by anti
Modified: 2006-01-12 12:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Description anti 2006-01-12 10:59:59 UTC 
Distribution: Debian testing/unstable
Package: Evolution
Priority: Normal
Version: GNOME2.12.2 unspecified
Gnome-Distributor: Debian
Synopsis: Switching to contacts crash the evolution
Bugzilla-Product: Evolution
Bugzilla-Component: Contacts [was: Addressbook]
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.12.0)
Description:
Description of the crash:
Evolution can not start after that crash. It always want to start in
contacts view but it not work, and crash again....

Steps to reproduce the crash:
1. switch to contacts
2. restart evolution
3. 

Expected Results:


How often does this happen?


Additional Information:
I tried to delete the addressbook.
 after deleting evolution starts, but riport that someting is wrong with the addressbook, and recreate the file and I can switch to mails.
But if I switch back to contacts it crashs again....


Debugging Information:

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

(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 -1229743904 (LWP 25888)]
[New Thread -1242960976 (LWP 25904)]
[New Thread -1234568272 (LWP 25903)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 65151

Thread 1 (Thread -1229743904 (LWP 25888))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 es_menu_hook_get_type
  • #4 <signal handler called>
  • #5 g_object_get
    from /usr/lib/libgobject-2.0.so.0
  • #6 e_minicard_label_new
    from /usr/lib/evolution/2.2/components/libevolution-addressbook.so
  • #7 e_minicard_label_new
    from /usr/lib/evolution/2.2/components/libevolution-addressbook.so
  • #8 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #13 eab_table_adapter_new
    from /usr/lib/evolution/2.2/components/libevolution-addressbook.so
  • #14 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #19 e_book_free_change_list
    from /usr/lib/libebook-1.2.so.3
  • #20 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #21 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #22 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #23 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #24 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #25 main
  • #0 __kernel_vsyscall 




------- Bug created by bug-buddy at 2006-01-12 10:59 -------
Comment 1 Devashish Sharma 2006-01-12 12:45:17 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 323556 ***